When a co-signer opens a bound worksheet during a power outage, they should see enough information to confirm whether an address belongs to the family vault—without booting a networked device. That means choosing fields carefully.
The minimum viable row
Each address row on our standard worksheet contains:
- Derivation path (e.g., m/84’/0’/0’/0/14)
- Receive address with checksum
- Associated xpub fingerprint (first 8 characters)
- Expected balance in satoshis or whole units, depending on client preference
- Last confirmed block height of the snapshot
We deliberately omit transaction history. A worksheet is a position statement, not a ledger replay.
Why we list fingerprint prefixes
Full xpub strings span 111 characters—unreadable on paper and prone to transcription error. The fingerprint prefix ties an address row to a co-signer role without exposing enough material to reconstruct the key.
Common mistakes we correct during intake
Clients often paste receive addresses without derivation paths. Paths without index numbers. Balance figures copied from block explorers that include unconfirmed mempool entries. Each of these creates a worksheet that looks authoritative but fails reconciliation.
The air-gap verification step
Before binding, we ask one non-technical signatory to locate a random address row using only the worksheet and a printed checksum table. If they cannot, the layout needs revision.
When to add a second volume
More than 150 active derivation indices warrant a split: Volume A for receive chains, Volume B for change chains. Thinner volumes survive handling better during annual reviews.
Questions about your xpub layout? Send us your intake template for a complimentary format review.