Offline Balance Verification Without Exposing Keys
How families verify multisig reserve holdings using xpub fingerprints recorded in their device register — entirely offline.
Families often ask: how do we know our documented derivation paths still match our actual holdings without connecting hardware wallets to the internet?
The answer lies in extended public keys — xpubs — recorded during device registration.
What an Xpub Fingerprint Proves
During registration, each signer’s device exports an xpub for the documented derivation path. The register records this fingerprint. Later, using an air-gapped computer or a dedicated offline verification device, you can derive receive addresses from the xpub and compare them against blockchain records.
No private key leaves the hardware wallet. No internet connection touches the signing device.
The Quarterly Check
We recommend a fifteen-minute verification every three months:
- Open your device register to the derivation path section
- On an air-gapped machine, derive the first five receive addresses from each recorded xpub
- Compare against addresses shown in your last known transaction or a previously saved address list
- Note the verification date in the register’s amendment log
If addresses match, your documentation remains accurate. If they diverge, schedule a register amendment before attempting any withdrawal.
When Verification Fails
Address mismatches usually trace to firmware updates that changed derivation defaults, a signer who created a new account index without informing others, or a device that was reset and re-seeded with a different mnemonic.
Each scenario has a documented recovery path — but only if your register is current.
Included in Registration
Every full registration engagement includes one guided verification session within 90 days of register delivery.