How to Store a Seed Phrase Securely

On metal, offline, in a physically secure place. Stamped or engraved steel survives fire and flood in a way paper does not, and it cannot be read remotely by anything. Keep a second copy in a second location, because the realistic failure is not a hacker, it is a house fire, a flood, or a move.

Paper is acceptable as a stopgap and much better than nothing, but it fails in exactly the situations backups exist for. If paper is what you have today, protect it from water and put a metal plate on the list.

Never in a photo, a password manager note, an email to yourself, or cloud storage. Those are the four ways most phrases leak, and all of them turn a physical secret into a networked one.

A device that goes online has an enormous attack surface: the operating system, the browser, every extension and app, and whatever you installed at 1am last year. Malware that reads the clipboard or takes screenshots is common and cheap, and it operates while you are logged in, which is exactly when your encrypted note is decrypted and on screen.

Encryption at the application level does not help against that. It protects the file at rest from someone holding the disk. It cannot protect plaintext from software running as you, on your machine, at the moment you look at it.

Everything around the phrase, which is more than people expect and is usually scattered:

• Verification. Dash’s seed phrase block lays the words out in a numbered grid and validates each against the BIP-39 wordlist, so a transcription error on your metal backup shows up as a red mark rather than as a failed recovery years later.
• Wallet inventory: which device holds which wallet, firmware versions, when each was last checked.
• Derivation paths and address types, without which recovery in a different wallet becomes guesswork.
• Passphrase hints, never the passphrase itself.
• An inheritance procedure: the ordered steps someone you trust would need to follow.

If you do use the seed phrase block to check a backup, lock the note, keep app lock on with a short timer, and treat it as a working aid rather than the backup itself.

1. Metal backup, made carefully, checked word by word against the wallet.
2. A second copy in a second physical location.
3. No photograph of it at any stage, including while you were making it.
4. A passphrase you keep only in memory, if your threat model calls for one.
5. A test recovery on a spare wallet, because an unverified backup is a hope, not a backup.
6. Notes covering wallet inventory, derivation paths and the recovery procedure, locked.