Layered storage
Customer assets are segregated from platform assets; the working balance sits in a hot wallet and the rest in cold storage. The hot wallet holds only what withdrawals and market-making need; anything above the threshold is swept automatically.
Cold-wallet keys are held offline and split among people in different functions, so no single party can move funds alone. That is what "do not trust a single point" means in practice, rather than as a slogan.
Why withdrawals need multi-sig
A single signature means one key controls everything, and one leak is a total loss. Multi-signature requires several keys to sign before a withdrawal completes, so an attacker must compromise several holders at once.
The cost is speed: large withdrawals wait for approval. The trade-off is deliberate — large withdrawals should be slow rather than single-point; small withdrawals use an automated path, with a delay as a buffer.
Three independent risk chains
| Chain | Main checks | Action when triggered |
|---|---|---|
| Login | Device fingerprint, location, abnormal frequency | Step-up verification or temporary freeze |
| Withdrawal | Address allowlist, behaviour deviation, amount thresholds | Manual review |
| Order | Order frequency, cancel ratio, anomalous prices | Rate limiting or manual confirmation |
The three are kept separate because their risks differ. Merging login and withdrawal checks would let a single credential leak lead directly to funds leaving.
What these mechanisms do not prove
Stating the boundaries matters more than listing the strengths:
- They are not a substitute for external audit. This describes internal mechanisms and makes no third-party certification or audit claim.
- They do not remove platform risk. Controls can fail, and custody always carries counterparty risk.
- They do not protect asset prices. Security protects against misappropriation, not market losses.
- They do not cover user-side mistakes. A leaked seed phrase, a compromised device or a malicious approval cannot be undone by the platform.
For the full statement on credentials and compliance, see security and compliance. For protecting yourself, see guides and tutorials.