Self-custody gives you authority over crypto assets because you control the private keys. It also makes you responsible for backup, recovery, device security and transaction review. The best setup is not necessarily the most complicated one; it is the one you can operate and recover correctly under pressure.
Match custody to the job
Instead of prescribing fixed portfolio percentages, divide funds according to use:
| Tier | Purpose | Typical approach |
|---|---|---|
| Cold | Long-term holdings with infrequent access | Hardware wallet or carefully designed multisignature setup |
| Operational | Transfers and occasional transactions | Dedicated software or hardware wallet with a limited balance |
| Spending | Near-term card purchases | Limited funded card balance |
The amount in each tier should reflect your circumstances, not an arbitrary 70/20/10 formula. Less frequently used funds can tolerate more operational friction; spending funds should be convenient but limited in size.
Choose tools you understand
Hardware wallets can isolate signing keys from an internet-connected computer, but they do not protect against every risk. A user can still approve a malicious transaction, lose the recovery material or buy a tampered device. Purchase from a trusted source, initialize it yourself, verify transaction details on the device and install updates only through official software.
Multisignature can reduce dependence on one key, but it adds coordination and recovery complexity. Document the policy, key locations and wallet configuration information. Test the complete recovery process before storing significant value.
Design backups for actual failures
- Record recovery material offline and protect it from theft, fire, water and accidental disposal.
- Keep copies or shares in locations that are not exposed to the same event.
- Do not photograph a seed phrase or enter it into cloud storage.
- Test recovery with the wallet’s documented procedure, ideally before the wallet holds a large balance.
- Make sure trusted successors can follow an appropriate plan without giving one person unnecessary present-day access.
SLIP-39 defines an interoperable form of Shamir secret sharing for mnemonic backups. It is not the same as manually cutting a seed phrase into pieces, and it is not compatible with every wallet. Use it only when your wallet supports the standard and you understand the group and threshold design. More shares also mean more opportunities for loss or operational mistakes.
Build a safe transaction routine
Verify addresses on the signing device, confirm the network and asset, and use a small test transaction for a new destination. Review token approvals periodically and treat unexpected signing requests as hostile. Never type recovery words into a website or share them with support; legitimate support does not need them.
Privacy practices should remain lawful and defensible. Avoid address reuse where the protocol and wallet support fresh receiving addresses, protect account metadata, and keep records required for taxes or accounting. Privacy does not remove the need to document the lawful origin of funds.
Spending creates a custody boundary
Agora Cards can be part of the spending tier, but the card balance is not self-custodied. USDT or USDC remains under your control only while it is in your own wallet. After a top-up, the funds are held by licensed and regulated custodian partners so card payments can be processed.
That makes balance sizing important. Load what you intend to spend, allow for the 2% top-up fee, and retain core holdings under your own keys. The card limits are $20,000 per transaction, $240,000 daily and $900,000 monthly, but those ceilings are not balance recommendations. Physical ATM limits are $1,500 daily and $15,000 monthly; virtual cards have no ATM access.
For a closer look at this arrangement, see Self-Custody, Custodial and Hybrid Crypto Models Explained. The goal is not to eliminate every dependency. It is to know exactly where each dependency begins and keep its exposure proportionate to the service it provides.