SUIBROKERS DAO · field note
Self-custody and custody: keys, recovery, and transaction control
A practical comparison of who controls keys, recovery, balances, approvals, and withdrawals in self-custody and custodial systems.
The first custody question is who can authorize the transaction. In self-custody, a wallet holds or derives the key material used to sign. In custody, a provider controls the account or signing process under its own recovery, withdrawal, and operational rules. The difference changes where you check authority and what evidence you retain.
Compare control and recovery
| Check | Self-custody wallet | Custodial account |
|---|---|---|
| Approval | User reviews and signs a wallet request | Provider authorizes under platform controls |
| Recovery | User protects and tests recovery material | Provider's account recovery and identity process |
| Withdrawal | Wallet submits a network transaction | Provider policy, limits, and processing |
| Balance view | Network state read through the wallet or app | Provider ledger, with onchain settlement if applicable |
| Completion | Digest, effects, and application record | Provider receipt plus any onchain evidence |
Sui's wallet documentation describes wallets as holding keys that prove ownership of onchain assets and signing submitted transactions. That authority comes with work: keep recovery material private, verify the network and address, inspect the full prompt, and understand what an app can read after connection. Connecting is not signing.
Custody moves some key and recovery responsibilities to a provider, but it does not remove review. Check which asset and network are supported, whether you can withdraw directly, which limits or identity checks apply, how the provider handles outages, and which record proves settlement. The phrase “balance” may describe an internal ledger rather than a network object owned by your own address.
The same action changes hands
Imagine exchanging SUI for USDC. In a self-custody Sui flow, the wallet shows the account, coin type, amount, recipient or package, gas, and output condition; the user signs, and the digest records the network result. In a custodial flow, a provider may debit an internal balance and execute later under its own controls. The provider's order or balance status is useful evidence, but it is not automatically an onchain transaction.
The current SUIBROKERS Swap surface illustrates the self-custody boundary: a compatible wallet connects, the app prepares a route, and the wallet still requests an explicit signature. A quote or UI status cannot authorize a transaction. If the prompt differs from the intended asset, amount, or network, reject it.
Questions for a real choice
Write down who controls the keys, who can pause access, how recovery works, which network and asset are used, what the user signs, and where a final record appears. Then read the wallet or provider's current primary terms. Self-custody concentrates signing and recovery responsibility with the user; custody concentrates operational control with the provider. Neither label answers whether a particular asset, route, or withdrawal will settle as intended.
For the network side of the check, read Sui wallet ownership and Sui versus Ethereum account state.