Non-Custodial
Service that never controls user funds or private keys.
Non-custodial describes a wallet or service that does not independently hold the private keys or signing authority needed to move a user's assets. The user approves transactions through a self-controlled wallet. The term reduces one kind of intermediary control but does not mean the complete product is decentralized or risk-free.
A non-custodial wallet stores keys on the user's device, hardware wallet, or distributed recovery setup. A non-custodial dapp prepares transactions that the wallet signs. Connecting a wallet normally reveals an address, while a signature or transaction grants specific authority. Users should distinguish connection, message signing, approval, and asset transfer.
The term matters because a custodian can freeze withdrawals, fail, or become insolvent. Direct key control avoids waiting for the company to authorize an ordinary blockchain transfer. It also removes familiar password recovery unless the wallet includes guardians, MPC, or smart contract recovery.
Non-custodial products can still place funds into contracts. Depositing into a lending market or bridge transfers control under code and administrator rules. An unlimited token approval lets another contract move assets later. A compromised frontend can prepare a malicious request even when the underlying protocol is sound.
Users carry responsibility for seed backups, device security, address verification, fees, and irreversible mistakes. No support agent can restore a lost key in a traditional self-custody wallet. Smart contract recovery reduces that risk while adding guardians, upgrades, and service dependencies.
Recovery should be designed before significant funds arrive. Write down the recovery process, test it with a low-value wallet, and make sure trusted heirs can follow it without exposing the secret early. Hardware wallets reduce online key exposure, but users must verify transaction details on the device screen. Cloud backups can be convenient, yet weak account security or poor encryption may turn them into a single point of compromise.
Before use, map who can move funds, pause withdrawals, upgrade contracts, or censor the interface. Verify every transaction on a trusted screen, use limited allowances, and keep valuable holdings separate. Non-custodial architecture gives users direct authority, but practical safety still depends on keys, contracts, governance, wallets, data providers, and careful decisions.
Frequently asked questions
- Users keep signing authority and do not become ordinary unsecured creditors of a platform holding their assets. They can verify and transact without waiting for a custodian's withdrawal approval. This reduces one counterparty risk, but shifts key protection, recovery, transaction review, and tax records to the user. Contracts and interfaces still create separate dependencies.
- A non-custodial interface should not control user keys, but assets can move into smart contracts, pools, escrows, or bridges after the user signs. Those contracts may restrict withdrawals or contain admin powers. Some services use delegated permissions or smart wallets. Evaluate who can move assets in every state instead of assuming “non-custodial” means funds never leave the wallet.
- Verify the official domain, network, contract addresses, audits, administrator powers, and withdrawal path. Read every signature and use limited approvals. Keep recovery information offline, separate valuable assets from routine dapp activity, and test with a small amount. Learn how to revoke permissions and use an explorer or alternative interface if the primary website becomes unavailable.