If either key is lost, the seed phrase CANNOT be decrypted. This is the risk of self custody. Unless there are other means of retrieval, the Bitcoin is gone. Legacy does not save any data.
Yes. You can create as many Benefactor/Beneficiary key combinations as you like, each associated with a different seed phrase.
Download "Legacy-offline.html" from github. Disconnect from wifi. Open the file in a web browser.
No. Beneficiary Key and Benefactor Key may contain all uppercase, lowercase, numbers, and special characters.
The Beneficiary needs to receive:
1. Benefactor Key
2. Encrypted Seed Phrase
3. Working copy of "Legacy-offline.html"
See Deadman Switch options for setup guidance.
The best keys are 4–5 random, unrelated words separated by spaces — for example, cloud mango river tuesday. This approach gives you high entropy while remaining memorable enough to carry in your head or communicate verbally to your Beneficiary. You should never need to write both keys down together or store them with the encrypted QR.
Legacy uses PBKDF2 with 600,000 iterations of SHA-256, which makes even a modest passphrase extremely resistant to brute force. The dual-key design means an attacker who obtains one key still cannot decrypt anything — they need both.
Keep the Benefactor Key and Beneficiary Key stored separately. Never store either key alongside the encrypted QR.
✓ Good keys — random, unrelated words with no personal connection:
cloud mango river tuesdaylamp orbit forest eleven quietthunder anchor velvet paradeseven bridge harbor silk moonarctic bench window plum escape✗ Bad keys — guessable by anyone who knows you, or by anyone in the Bitcoin space:
bitcoin — single obvious wordsatoshi2009 — predictable Bitcoin referencejohn1985 — name + birth year, trivially guessablepassword123 — among the most common passwords in existenceiloveyou — common and emotionally predictable for an inheritance toolNote: the examples above are illustrations only — do not use them. Choose your own words at random.
For best results when scanning an encrypted QR:
Visit the Protocol page for detail summary.