Confirmation Depth and Settlement vs Self-Custody vs Hosted Wallets: How They Differ
How confirmation depth and settlement and self-custody vs hosted wallets interact, and what to check before you rely on either.
Two terms that interact
Confirmation Depth and Settlement and Self-Custody vs Hosted Wallets are separate ideas, but in practice they shape each other. Comparing them clarifies what actually changes the outcome for you.
What a confirmation is
A confirmation is a block added after the one containing your transaction. More confirmations mean the transaction is buried deeper and is harder to reverse.
Who sets the threshold
The number of confirmations treated as final is chosen by the receiving service, not by the blockchain. Different services wait for different depths.
Who controls the keys
In self-custody you control the private keys and the funds are yours to move. With a hosted wallet the service controls the keys and you rely on their terms and availability.
The trade-off
Self-custody removes counterparty risk but puts the burden of address accuracy and backups on you. Hosted wallets are simpler but depend on the provider.
How they combine
Read confirmation depth and settlement alongside self-custody vs hosted wallets rather than in isolation: a favourable figure in one can be undercut by a strict term in the other. The combined effect is what matters, and it is worth confirming both before you act.
What to verify in writing
Confirm the current terms for both confirmation depth and settlement and self-custody vs hosted wallets with the operator, and keep the reply. A single written confirmation covering both avoids acting on a half-understood rule.