Labelling Derivation Paths on Paper Backups

Handwritten seed phrase cards rarely include derivation path information. Holders assume they will remember which path they used—or that the device will display it. Years later, neither assumption holds.

Our notation standard

We use a three-part label on every allocation sheet row:

1. Seed label: Seed A, Seed B, etc.—matching the physical envelope or metal plate
2. Account index: The number after the seed in your device interface (often 0, 1, 2)
3. Full path: Written as m/84'/0'/0'/0/5 for a native SegWit Bitcoin address at index 5

Example row on the right column: Seed A · acc 0 · m/84'/0'/0'/0/3

Device-specific notes

Ledger Live displays account names you assign. Record both the account name and the underlying path—names like “Savings” migrate between devices inconsistently.

Trezor Suite shows passphrases as hidden wallets. Each passphrase wallet is a separate seed label in our system (Seed A-passphrase1, not a sub-path of Seed A).

Coldcard users often use custom derivation paths for multisig. Write the full path including co-signer configuration reference if applicable.

Common gaps

• Change addresses on Bitcoin: many holders document receive addresses but omit change paths. Include at least the first five change addresses per account or note “change: auto” if you rely on wallet software to track them.
• Ethereum account 0 vs account 1: EVM chains share address formats. A single Ethereum derivation path may hold assets on Polygon, Arbitrum, and Base. List the path once and note all chains in the left column.

Practice exercise

Take one seed phrase backup. Without opening a device, write every derivation path you believe you have used. Then connect the device offline and compare. The gaps between your paper list and the device list are exactly what an allocation audit resolves.