For long term storage, you need indestructible and physically secured backup of your keys. Basically, you just need to write down the 12 or 24 seed words generated by your hardware wallet and try to keep the words safe from destruction and theft. It's recommended to use a indestructible material such as steel for these, and then store or hide them safely. For more advanced security, seed words can be split in multiple parts using the SLIP39 seed format.
For hardware wallets, e.g.:
For long term storage, e.g.:
Why is that in any way more secure than writing down the private key itself? (inb4 "need to find both the hardware and the written seed words" that's equivalent to writing down the private key and then cutting the paper in half)
Hardware wallet is assumed to generate BIP39 seed words securely. If you don't trust the RNG, some hardware wallets also support adding your own entropy with dice rolls. [0]
[0] https://coldcardwallet.com/docs/verifying-dice-roll-math
The point is that you can decide what to do with it... be your own bank. You can also add a password to a seed phrase backup if that makes more sense for your threat model.
Then just keep those details safe.
Too many people I know haven’t instructed their dependents how to access their crypto.
As for if you die … you could use one of those services that will send an email out to your significant others if you don’t log in for X amount of time.
And put your bitcoin private key in there? Surely whoever runs those services would take all your money.
Being your own secure bank isn’t a trivial task. Hopefully this can get easier in the future
You can also have normal software wallets (don't recommend it for larger amounts) or paper wallets.
And if you’re backing up your keys on USB drives, use high-endurance SLC NAND industrial drives. They provide the highest reliability and endurance available.
"There's nothing special about ZFS that requires/encourages the use of ECC RAM more so than any other filesystem. If you use UFS, EXT, NTFS, btrfs, etc without ECC RAM, you are just as much at risk as if you used ZFS without ECC RAM. Actually, ZFS can mitigate this risk to some degree if you enable the unsupported ZFS_DEBUG_MODIFY flag (zfs_flags=0x10). This will checksum the data while at rest in memory, and verify it before writing to disk, thus reducing the window of vulnerability from a memory error.
I would simply say: if you love your data, use ECC RAM. Additionally, use a filesystem that checksums your data, such as ZFS."
https://arstechnica.com/civis/viewtopic.php?f=2&t=1235679&p=...
You stated "Also a good idea to use ECC Memory with the ZFS filesystem".
You should have probably stated its a good idea to use ECC memory, period. Instead you tied ECC to ZFS.
Both are better than either, and either is better than neither. Especially if you're storing cryptocurrencies on it.