Custody and control
Custody asks who can authorize transfers and what claim you have if that party fails. A visible account balance does not answer either question by itself.
A USEFUL DISTINCTION
Start with who can authorize a transfer, then examine the recovery and failure model.
| Look at | Self-custody | Custodial account |
|---|---|---|
| Control | You control the keys or authorization arrangement. | A provider controls assets and maintains your account claim. |
| Recovery | Depends on your backups and wallet design. | Depends on the provider’s identity and recovery procedures. |
| Transaction access | Requires functioning software and network access. | Can depend on provider availability and withdrawal approval. |
| Principal failures | Lost keys, malicious signatures, compromised devices or contracts. | Custodian failure, restricted withdrawals, account compromise. |
| Remaining dependencies | Wallet code, RPC services, contracts and network rules. | All relevant network dependencies plus the provider. |
THE KEY DISTINCTION
Self-custody changes the responsibility and control model. It does not make every smart-contract interaction safe or remove all third-party dependencies.
MAKE IT CONCRETE
A wallet address with assets controlled by your key and an exchange dashboard showing a balance may look similar; only the former gives direct signing authority for those assets.
Custody asks who can authorize transfers and what claim you have if that party fails. A visible account balance does not answer either question by itself.
A wallet connects human intent to cryptographic authorization and network state. The assets remain recorded by the network, not inside the app.
A recovery phrase can recreate many wallet keys. It is powerful secret material, and its compatibility depends on the wallet’s actual recovery scheme.