Why Side-by-Side Sheets Beat Spreadsheets for Cold Storage
Spreadsheets require a computer. Allocation sheets sit in your safe beside your seed phrases.
Many holders start with a spreadsheet to track cold storage addresses. It works until the spreadsheet lives on a laptop that also connects to the internet—or until the file syncs to a cloud folder by default.
A side-by-side allocation sheet solves a different problem. The left column records what each address holds. The right column records which seed phrase and derivation path control that address. Both columns exist on paper, stored in the same physical location as your backups.
The pairing principle
The value is not in either column alone. An address list without derivation paths tells you balances but not how to recover them. A seed index without balances tells you recovery paths but not whether you have accounted for every address.
Pairing them on one sheet means you can verify completeness: every address on the left should map to exactly one row on the right, and every active derivation path on the right should have a corresponding address on the left.
When to update
Update your sheet when you:
- Generate a new address on an existing device
- Add a new hardware wallet
- Move funds between your own cold addresses (note the transfer in a margin, not a new row)
- Discover an address you had forgotten (common after years of holding)
Do not update the sheet after every small balance change from staking rewards or dust accumulation unless your reconciliation process requires it. Quarterly review is sufficient for most holders.
Paper specifications
We print on 120 gsm archival paper with pigment ink. Sheets are landscape orientation, folded once for A5 storage in a standard envelope. The fold line runs between the two columns so each half can be read independently if you separate them for storage.
Starting from blank
If you have no existing documentation, begin with the right column: list every seed phrase backup you possess, label them Seed A, Seed B, and so on, then record each derivation path you have used. Only then query balances for the addresses those paths produce.
This order prevents the common mistake of listing addresses first and then struggling to match them to the correct seed.