Designing My Self-Sovereign Digital Inheritance Solution (DIS): A Field Guide
Designing My Self-Sovereign Digital Inheritance Solution (DIS): A Field Guide
I have spent the past months designing and documenting my own Digital Inheritance Solution, or DIS. It is a personal, self-custodial system that I introduced to my family to make sure our digital assets, especially Bitcoin, but also important accounts, do not disappear in case something happens to me. I wanted to build a plan that is truly sovereign: no custodians, no centralized gatekeepers, and no blind trust in institutions. Instead, it had to be resilient, private, and executable by my heirs when the time comes.
In case you are interested in self-sovereig lifestyle you can already **pre-order **my new Book **“Brick By Brick: Building a Sovereign Life on Bitcoin” -> **https://twentyone.life/brick-by-brick
Facing the Threat Model
The starting point was my threat model. I asked myself: what if the house burns down, all hardware is stolen, or I have to leave the country in a hurry? What if I die suddenly or fall into a coma, leaving no chance to explain where the keys are? What if someone forces me to hand over my access? These are uncomfortable scenarios, but facing them head-on is the only way to build something that can withstand them.
The Core Architecture
At the core is a VeraCrypt container. It uses a hidden inner volume, which remains invisible unless you know the right password, and an outer decoy volume that looks convincing enough to hand over under pressure or to train my heirs. Inside the hidden volume sits a KeePass database. This is where I keep the critical information: account credentials, step-by-step recovery instructions, wallet descriptors, and device fingerprints. It is not just a password vault, but a playbook for my family to follow.
For the Bitcoin itself I use a three-of-four multisignature setup managed in Sparrow Wallet. Each device of the 3/4 multisig has its own seed phrase, and all of them are protected with additional passphrases. The Coldcard seed has a special low-tech backup too: it is encoded through the Border Wallet method, which can be reconstructed from an ordinary book e.g. https://amzn.to/3Irjc9i. That means even if everything else is destroyed or confiscated, my family can still recover the Coldcard seed following the instructions in KeePass.
Passwords are not stored whole in any one place. Instead, I split them into halves. One half travels one route, the other half a different route. Only when combined can they open the inner volume or the KeePass vault. The effect is that no single service or person ever holds the full secret. It also introduces delays: my heir must request one half through a password manager’s emergency access process, and wait for the other half to be released after a timed dead-man switch. By the time both pieces arrive, they should already have found a copy of the DIS container on a USB stick, NAS, iCloud backup, or Google Drive folder. Everything sensitive is always encrypted; nothing is ever stored in plaintext.
The Recovery Playbook
The recovery playbook is simple enough that a less-technical person can execute it under stress. Once the two halves of the password are combined, the heir mounts the VeraCrypt container, opens KeePass, and follows the step-by-step guides inside. These include instructions for logging into banks and insurance accounts, as well as detailed walkthroughs for restoring the multisig Bitcoin wallet, confirming device fingerprints, and signing with the necessary quorum. For practice, the heir can even try out the decoy volume with its fake KeePass database, so they are familiar with the process without touching the real data. We are meeting once per year to walk though the steps and discuss changes that have been introduced.
Building Resilience
Resilience was a guiding principle throughout. If hardware is stolen, the multisig prevents a thief from moving any funds with a single device. If the house burns down, the cloud and USB copies of the encrypted container ensure nothing is lost. If someone tries coercion, the outer VeraCrypt volume and the fake KeePass database provide plausible deniability. Even in extreme situations such as fleeing across a border with nothing in hand, the Border Wallet method ensures the Coldcard seed can still be recovered.
Weak Points and Improvements
There are, of course, weak points. Depending on online services for split password delivery introduces a potential single point of failure, and I am working toward replacing this with Shamir’s Secret Sharing so that multiple trusted people each hold a share of the password. I also learned that relying on a single MFA device, such as one YubiKey, is dangerous if it fails or gets lost, so I now plan to register multiple keys and document backups. And perhaps the biggest risk is human: heirs need to be able to execute the plan correctly when the time comes. That is why I have started annual practice sessions with the decoy vault and keep a sealed, one-page quick-start guide as a safety net.
Why This Is Self-Sovereign
What makes this solution self-sovereign is that no institution or custodian stands between my family and the assets. The Bitcoin remains in our multisig, never on an exchange. The data is encrypted and replicated in places I control, not in a proprietary service that could shut down or lock us out. I decide the triggers, the distribution, and the backup methods. It is both private and recoverable.
Practical Checklist
Design your inheritance plan by defining the threats you want to withstand, then build layers of protection against them. Use strong encryption for all data and ensure your heirs can execute recovery without you. For Bitcoin, multisig adds resilience against theft and device loss. Always keep multiple backups across different media and locations. When splitting secrets, think about redundancy so that no single point of failure can ruin the plan. Test the process regularly with your heir, using decoy data if necessary, and update everything when accounts or wallets change. Finally, make sure your inheritance solution is aligned with your legal will, so that the cryptographic plan and the legal plan reinforce each other.
In case you are less technical oriented but still want a very good inheritance solution take a look at the https://nunchuk.io/, with their new microcode feature it is a very sound solution.
Closing
This DIS isn’t theoretical, it’s running, tested, and taught to my family. It keeps our digital life private, recoverable, and uncensorable. If you manage Bitcoin or critical online accounts, consider building your own self-sovereign plan. Start small, iterate, and, most importantly, practice the recovery with the people who will need it.
If you’d like my structure or checklist as a template, feel free to reach out, I am happy to share a redacted version that you can adapt for your own family.
