Everything you need to know about Legacy Encryption
It depends on whether you're still around to fix it.
If you're alive, nothing is lost. Your seed phrase — backed up physically, as it always should be — is the source of truth. Just choose new keys and re-encrypt. This is why Legacy is a protocol you maintain, not a one-time action: periodically confirm your keys still decrypt, and re-encrypt whenever a key is lost, forgotten, or possibly compromised.
If it's for inheritance and you're gone, a lost key means that encrypted copy can't be opened — and unless there's another means of retrieval, those coins are unreachable. Legacy stores no data and cannot recover keys for you. That's exactly why we recommend redundancy: multiple copies of the encrypted QR and a sealed break-glass fallback (see Who It's For).
The key principle: always maintain a physical backup of your seed phrase. Legacy does not replace your primary seed backup — it is a means of recovery and transfer, layered on top of it.
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.
Recommended — fully air-gapped on SeedSigner: flash the Legacy firmware onto a SeedSigner (see the SeedSigner setup guide). Your seed phrase never touches a computer or the internet at any point in the process.
Alternative: Disconnect from wifi and open the file in any web browser on your computer.
No. Beneficiary Key and Benefactor Key may contain all uppercase, lowercase, numbers, and special characters.
The Beneficiary needs to receive:
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 gives you high entropy while remaining memorable enough to carry in your head or communicate verbally to your Beneficiary. Never write both keys down together or store them with the encrypted QR.
Legacy uses PBKDF2 with 600,000 iterations of SHA-256, making even a modest passphrase extremely resistant to brute force. The two keys are the two halves of one combined password (joined by an untypeable separator), so an attacker who obtains only one half still has to brute-force the other — they need both to decrypt. Note this is a single split password, not threshold cryptography.
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:
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.
SeedSigner is the recommended way to use Legacy — the entire workflow runs air-gapped. Encrypt on SeedSigner, scan the QR into your Deploy email, and your seed phrase never touches the internet.
For best results when scanning an encrypted QR into SeedSigner:
Visit the Protocol page for a detailed summary.
Take your time — there is no time pressure, and nothing in the email is secret on its own. The encrypted payload is useless without the two passwords.
Normal path: open the Legacy Decryption page (or your saved copy of Legacy-offline.html) on an offline computer, paste the ciphertext into the Encrypted Seed Phrase field, enter your Beneficiary Key and the Benefactor Key, and click Decrypt.
Do NOT type the passwords into any other website, and do not share them with anyone who offers to "help recover" — run everything offline.
If no copy of the tool runs anymore: any software engineer can rebuild decryption from the specification below using any mainstream cryptography library. The full specification, with test vectors that prove a rebuilt tool is correct, is PROTOCOL-SPEC.md.
TECHNICAL SPECIFICATION OF THE ENCRYPTED PAYLOAD (Legacy protocol)
The payload is a single line of text made of letters, digits, "-" and
"_" (base64url). It deliberately has no label or prefix: it looks like
random data, so only someone who has been told can know what it is.
1. Prepare the two passwords (do this to EACH one, exactly as written):
- Replace curly quotes with straight ones (' and "), and replace tabs,
line breaks and no-break spaces with ordinary spaces.
- Collapse repeated spaces to one space; remove leading and trailing
spaces.
- The result is plain ASCII text (US keyboard characters only).
Capitalization matters. Do not change anything else.
2. Combined password = benefactor password, then the single byte 0x1F
(the ASCII Unit Separator control character), then beneficiary
password. Order matters.
3. base64url-decode the payload (base64url uses "-" and "_" instead of
"+" and "/"; add "=" padding back if your decoder needs it). The
decoded bytes are:
bytes 0-15 : salt
bytes 16-27 : IV (GCM nonce)
bytes 28-end : ciphertext, 16-byte GCM tag at the end
4. Key = PBKDF2-HMAC-SHA256(combined password, salt, 600,000 iterations,
32 bytes).
5. AES-256-GCM decrypt (no associated data). A failed authentication tag
means a wrong password, swapped passwords, or a damaged payload; it
never decrypts to garbage.
6. The first plaintext byte is the padding length N (0-4). Drop that
first byte and the last N bytes.
The result is a BIP-39 seed phrase: 12 or 24 lowercase English words
separated by single spaces. Verify it against the BIP-39 word list, then
follow standard Bitcoin wallet recovery procedure with hardware you control.