Why Founders Move Reserves Off Exchanges — and What They Forget
The custody shift is straightforward. The documentation gap that follows catches teams during the first personnel change or investor diligence.
The decision to move treasury reserves from a custodial exchange to hardware wallets is usually made in a single afternoon. A founder reads about an exchange insolvency, calls a co-founder, and by Friday three devices are labeled, seeded, and funded. The exchange account balance drops to operating minimums. Everyone feels safer.
What rarely happens in that same week is writing down what was done.
The custody gap
Six months later, the picture looks different. The CTO who set up the wallets is focused on a product launch. The CFO knows two of the three devices are in a safe but cannot recall which label corresponds to which signing role. A board member asks during a quarterly review whether the company has a treasury continuity plan. The answer is a nervous silence followed by “we should document that.”
This is the custody gap — not a security failure, but a documentation failure. The reserves are offline and likely secure. The knowledge of how to access them under pressure is concentrated in one or two people and stored nowhere durable.
What gets missed
Founders who contact us typically have one or more of these gaps:
- Inconsistent labeling. Wallet names in a spreadsheet do not match physical labels on devices or safe contents.
- No signer escalation path. If the primary signer is unreachable, no one knows the backup authorization sequence or timeframe thresholds.
- Geographic assumptions. Seed phrase fragments distributed across countries without a map showing which holder has which fragment and how they coordinate.
- Board unreadiness. Governance documents reference “company reserves” but contain no procedure for offline treasury authorization.
The documentation that survives personnel change
The minimum viable continuity record for an offline treasury includes four elements:
- A custody map naming every key holder, their role, and geographic location
- A device inventory with consistent labels across physical and digital records
- A recovery runbook describing authorization sequence for emergency transfers
- A one-page emergency sheet stored separately from the full documentation
None of these require revealing seed phrases or balances. They describe process and responsibility, not secrets.
When to document
The best time is within thirty days of initial cold storage setup — when memory is fresh and signers are still aligned. The second-best time is before any of these events: a co-founder departure, a funding round with investor diligence, a relocation of physical storage, or an incident that requires urgent treasury access.
If your reserves are already offline and undocumented, the gap is common and fixable. A structured audit typically takes two sessions and produces documents your board can read without a technical background.