Self-custody means using your own private keys to control the sending of bitcoin. These keys are secret data that a wallet uses to create a digital signature proving authority to spend. You do not need to ask an exchange for a withdrawal. You also take responsibility for the keys and their backup: if you lose them, nobody can restore access with a simple password reset.
Anna buys bitcoin on an exchange. The balance in her account initially means that the exchange owes her that amount of bitcoin; the exchange holds the keys needed to send it. Once she withdraws to her own wallet address, she can send the funds herself. The bitcoin does not move into her phone. The network records unspent transaction outputs, or UTXOs: each specifies an amount and the conditions for spending it. Anna controls the necessary keys. She can create a transaction without the account provider’s consent, but confirmation still requires it to reach the network and be included in a block.
How does the network know Anna can spend the money? It does not check her identity document or name. Nodes, the computers verifying Bitcoin transactions, check digital signatures and the other conditions written in a Bitcoin script. A script is a short program specifying what a spend must satisfy. Sometimes one key’s signature is enough; other arrangements require several signatures or a waiting period. A restored wallet must know these rules too. If a service supplies some of the signatures, check that you control enough keys independently of that service to satisfy the rules. Self-custody depends on your ability to control the funds yourself, not the product’s name.
Imagine Anna loses her phone. Many wallets can be recovered using a Seed Phrase: a backup sequence of words from which the seed, the secret starting data for deriving keys, can be recreated. With BIP 39, if a passphrase was used, that exact additional phrase is also required. It is not the device PIN, and a different phrase produces different keys. Recovery may also require a description of the wallet. A Descriptor records which keys and spending rules to use; a derivation path identifies where to look in the tree of keys. With Multisig, which requires multiple signatures, preserve the information about all participating public keys and their arrangement under the chosen script. Payment labels help you understand the history, but do not replace keys. Test a backup by safely recovering known addresses, not merely by counting the words you wrote down.
A Hardware Wallet is a separate device designed to sign transactions securely. It separates signing keys from a general-purpose computer. Its firmware (the device’s internal software), correct addresses and backups still matter. Multisig can limit the impact of one lost or compromised key, but adds devices, information and recovery steps. Security depends on the entire arrangement, not just a product name or key count.
Check receiving addresses on a trusted display, on the device itself when using a Hardware Wallet. Before signing, check recipients, amounts, fees and change. Follow transactions through your own Full Node, which independently verifies Bitcoin’s rules, or a source whose limitations you understand. Plan for updates, lost devices and emergencies too.
A Seed Phrase may be incomplete or exposed, and a required passphrase may be lost. Even with the correct keys, a wallet may fail to find the expected addresses if the derivation paths or spending rules are missing. Check the keys, wallet configuration and backups together. Receiving a test payment alone does not prove that you can recover or spend the funds: a receiving address can be displayed without the private key. It is also worth verifying safe recovery and signing a small outgoing transaction.
Test restoration in a separate trusted environment using your wallet’s procedure; never enter a real backup into a web form or untrusted device. Restore the rules from verified backups, compare known addresses and verify that you can sign a small transaction. Emergency and inheritance plans must give the right people access to secrets and required information under defined conditions, without exposing them prematurely.
Satoshi Nakamoto — Bitcoin: A Peer-to-Peer Electronic Cash System · BIP 32 — Hierarchical Deterministic Wallets · BIP 39 — Mnemonic code for generating deterministic keys · BIP 174 — Partially Signed Bitcoin Transactions · BIP 380 — Output Script Descriptors General Operation · Bitcoin Core — Managing wallets · Bitcoin Core — External signer
For the clearest picture, read this entry together with Bitcoin, Private Key, Seed Phrase, Wallet, Hardware Wallet, Multisig. The reverse links also lead from Cold Storage, Lightning Watchtower, KYC, Custodial Exchange.
01Does self-custody mean keeping bitcoin on a phone?+
No. The blockchain records UTXOs: unspent transaction outputs specifying an amount and its spending conditions; you control the keys and can satisfy the spending conditions without an account custodian’s consent. A mobile wallet, Hardware Wallet, offline setup or Multisig are possible arrangements. The device type alone guarantees neither security nor recoverability.
02What should I verify before a large withdrawal?+
Verify the receiving address in a trusted wallet, on its own display when using a Hardware Wallet. Make a small test and independently verify confirmation. Before moving the remainder, safely rehearse recovery including any required passphrase, derivation paths and script information. Do not enter the real backup on a website or an untrusted device. Receiving a small amount alone proves neither that recovery works nor that the setup is secure.