How do seed phrases work, and how should I store one?

• Hardened children (index written with ') need the parent private key to derive.
• Non-hardened children can be derived from the parent public key. That's how an extended public key (xpub) lets a watch-only server generate receive addresses without holding secrets.

The catch is that if someone has an xpub and any non-hardened child private key under it, they can compute the parent private key. Treat xpubs as sensitive: they reveal your whole address history, and they are one leaked child key away from a full compromise.

BIP-44: standard paths

m / purpose' / coin_type' / account' / change / address_index

When a restored wallet "shows zero balance", the cause is almost always a different derivation path or a missing passphrase. The words themselves are rarely the problem.

Seeing it in code

This uses the public Hardhat/Anvil test mnemonic. Never generate or type a real seed phrase into a script on an internet-connected machine.

import { HDNodeWallet, Mnemonic, randomBytes } from "ethers";

// PUBLIC test mnemonic used by Hardhat and Anvil. Never send real funds to it.
const phrase = "test test test test test test test test test test test junk";

for (let i = 0; i < 3; i++) {
  const w = HDNodeWallet.fromPhrase(phrase, undefined, `m/44'/60'/0'/0/${i}`);
  console.log(w.path, w.address);
}
// m/44'/60'/0'/0/0 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 ...

// Same words + a passphrase = a completely different wallet
const withPass = HDNodeWallet.fromPhrase(phrase, "correct horse", "m/44'/60'/0'/0/0");
console.log(withPass.address);

// The checksum catches most typos
console.log(Mnemonic.isValidMnemonic(phrase));                         // true
console.log(Mnemonic.isValidMnemonic(phrase.replace("junk", "test"))); // false

const fresh = Mnemonic.fromEntropy(randomBytes(16)); // 128 bits -> 12 words

How to store a seed phrase

Never put it anywhere digital. That means no photos, no cloud notes, no password-manager notes synced to the cloud, no email to yourself, no chat messages, no screenshots, and never into a website, browser extension prompt, support form or AI chat. Legitimate support will never ask for it. Any page that asks for your seed phrase is a phishing attempt.

What works:

1. Generate it on a hardware wallet so the words never touch a networked computer.
2. Write it down by hand, with the word numbers, and check every word against the device.
3. Use a durable medium for long-term storage: stamped or engraved metal survives fire and water far better than paper.
4. Keep at least two copies in separate secure places, so one fire, flood or burglary doesn't take all of them.
5. Test recovery before you fund the wallet properly. Wipe the device or use a second one, restore from the backup, and confirm you get the same first address.
6. Consider a passphrase, stored separately from the words, so a found backup alone isn't enough. Only do this if you'll reliably keep both.

Avoid splitting a 24-word phrase into thirds. Each piece gives away part of the secret, and losing one piece can make recovery impossible. If you need to spread trust across people or places, use a scheme designed for it: a multisig wallet, or SLIP-39 Shamir backups on hardware that supports them.

For developers

• Keep development mnemonics (like the one above) completely separate from anything holding real value. Bots sweep funds sent to known test mnemonics almost immediately.
• Never log, print or commit a mnemonic or private key. Add .env to .gitignore, and assume any key that has sat in a .env on a laptop is a hot key.
• For production deployers and signers, use a hardware wallet, a multisig, or a KMS/HSM-backed signer instead of a raw mnemonic.
• Treat xpubs as private data in your backend.

Checklist

1. BIP-39 turns 128–256 bits of entropy plus a checksum into 12–24 words, then PBKDF2 turns words plus passphrase into a seed.
2. BIP-32 derives a key tree from the seed. BIP-44/84/86 paths pick the keys.
3. Restore problems are usually a path or passphrase mismatch.
4. Store the words offline, on durable media, in more than one place, and test recovery.
5. Never type a real seed phrase into anything online.

How many confirmations should I wait for before trusting a transaction?

On Bitcoin, scale confirmation depth with the amount at risk, since finality is probabilistic. On Ethereum, wait for the finalized checkpoint. On rollups, wait for the batch to be final on L1.

#consensus#transactions