The core idea
Self-custody means controlling the keys required to spend bitcoin. It removes dependence on an exchange or custodian for routine access, but it also makes the user responsible for backup, transaction verification, device security and inheritance planning.
- “Not your keys” describes control, not a guarantee of good security.
- A seed phrase is usually sufficient to recreate the wallet and spend funds.
- A passphrase can add protection but creates another secret that must be recovered exactly.
- Multisignature can reduce single-point failure while increasing setup and coordination complexity.
How it works in practice
A self-custodial wallet generates keys and a recovery backup locally. The user receives to addresses derived from those keys and signs outgoing transactions. Recovery normally depends on the seed phrase and, in some setups, an additional passphrase or multiple-signature policy.
Practical checklist
- Practice with a small balance.
- Create two geographically separated backups when appropriate.
- Do not photograph, email or cloud-sync the seed phrase.
- Document the wallet type, derivation or recovery procedure without exposing secrets.
- Plan how trusted heirs can recover funds without gaining premature access.
Limits and risks
Self-custody can fail through lost backups, damaged devices, forgotten passphrases, malware, coercion or unclear inheritance instructions. Complexity is itself a risk. The strongest setup is not necessarily the most elaborate; it is the one the owner can verify, maintain and recover under stress.
Sources and further reading
Use primary documentation where possible and compare claims across independent sources.
Frequently asked questions
Is self-custody always better?
It removes custodian risk but adds personal operational risk. The better model depends on competence, amount, threat model and recovery needs.
Can I recover without the original device?
Usually yes if the recovery backup and any required passphrase are correct and compatible with the wallet standard.
Should I split a seed phrase into pieces?
Improvised splitting can create fragile backups. Use a documented backup or multisignature design rather than inventing a scheme you may not reconstruct.