paperback VS SecretSharingDotNet

Yes. QR codes are meant to store only a few kilobytes at most. They are not suitable for encoding gigabytes of data.

At perhaps 2KB per page, you'd need 524288 pages to store a 1GB. That's 1048 reams. Please just use an archival optical disk instead.

Even if the scheme using multiple QR codes in sequence rather than a single large code block. The paper backup implementations that use QR codes https://github.com/intra2net/paperbackup https://github.com/cyphar/paperback are only meant to be used for private key backup.

There's a cool paper-based backup tool that also uses Shamir Secret Sharing to let you distribute a bunch of paper copies to your friends to restore a file optically:

https://github.com/cyphar/paperback

Paperback will do it automatically for you, open source and free. Thier README also has recommendations for long term storage of paper.

That exists: https://github.com/cyphar/paperback (or the paper-store script suggested by /u/nurupoga/ below).

there are ready-made solutions for that, like https://github.com/cyphar/paperback

You could encrypt your key info using paperback. This then requires at least X amount of people holding parts of the decrypt key to come together to decrypt your last will.

I know you're joking but there's actually software that was made just for that

I trust it enough no solve my DR scenario. If I was targeted by the NSA, I don't expect this to keep me safe.

I don't think SecretSharingDotNet has had any audits, and I'm pretty sure i hasn't been checked for side-channel attacks. I couldn't find anything in GitHub [1] saying it's no longer maintained though.

I'm pretty sure a well founded attacker would be able to hack me, but I think it's orders of magnitude more likely that I'll forget my master password, I'll get stolen, my apartment will catch on fire or I'll just die. Those are the scenarios I'm preparing for.

[1]: https://github.com/shinji-san/SecretSharingDotNet