A balance is a display; control is a mechanism
An account screen can show an amount without explaining how a transfer is authorized. Treat those as separate pieces of evidence. A useful custody description says who holds signing authority, what recovery depends on, and which service can refuse or delay access.
This distinction runs through our underlying Bitcoin history research: a protocol and an intermediary have different failure modes. We do not need a fresh price chart or an incident count to make that point. We need an accurate description of the arrangement in front of us.
What the documentation establishes
The Bitcoin developer guide describes wallets as systems for handling keys and transactions. It distinguishes arrangements such as full-service wallets, signing-only wallets, and hardware wallets. Those categories describe where sensitive operations happen; they do not provide a universal safety score.
A recovery procedure deserves the same scrutiny as day-to-day signing. Backing up the wrong information, relying on a single inaccessible device, or misunderstanding an additional recovery requirement can leave a plan incomplete. Document the procedure for the particular wallet and version rather than assuming that every recovery design works alike.
A custody record worth keeping
| Question | Useful record |
|---|---|
| Who can sign? | A plain-language account of the keys, devices, and people involved |
| Who can recover access? | The official recovery procedure and its prerequisites |
| Who can block a withdrawal? | Service terms, account restrictions, and operational dependencies |
| What is assumed? | Any claim you have not independently established |
Two arrangements, two responsibilities
For a service-held account, read the service’s custody and withdrawal terms. Record the exact entity offering the account and the scope of its promises. A generic statement about “institutional security” does not answer whether a particular account can withdraw during a disruption.
For a personally controlled wallet, the operational questions become more immediate: who can access the signing device, where is the official recovery documentation, and what happens if the owner is unavailable? These are planning questions, not a request to put secrets into a spreadsheet. Keep the description of the process separate from the secrets themselves.
A public form, editorial inbox, or person offering to check a wallet does not need your private key or recovery phrase. Our contact and submission forms are for documents and corrections.
What remains uncertain
Documentation can be incomplete. A service’s assertions can be difficult to verify. A personally controlled setup can fail through misunderstanding. Our proposed custody record makes those gaps visible; it is not a certification that a particular arrangement is safe. Use it to identify what you still need to understand before making a consequential decision.
Sources & reading trail
- Bitcoin developer guide: wallets — technical explanation of wallet functions and signing arrangements.
- Bitcoin whitepaper — the distinction between transaction authorization and agreement on transaction history.
The record-keeping framework is an editorial adaptation of the project’s custody research. It is educational and does not recommend an asset or custody product.