Security
Built so that a breach cannot sign a transaction.
Most crypto losses start with a private key in the wrong place. We remove that key from the application entirely, then layer encryption, monitoring and human review on top.
Address derivation without signing power
The treasury stores only public extended keys (zpub/xpub). A database compromise cannot move funds.
Multi-signature sweep
Deposits sweep to cold storage under a 3-of-5 multisignature quorum on hardware across three jurisdictions.
Encrypted payout details
Payout emails, IBANs and account names are AES-256-GCM encrypted before they reach the database.
Continuous chain monitoring
mempool.space, TronGrid and public EVM RPCs are polled for every open order.
Session and device forensics
Every sign-in records IP, device class, browser and timestamp. Anomalies force re-authentication.
Incident response
24/7 on-call, 15-minute acknowledgement target, regulator notice within 72 hours and a public post-mortem.
Control register
The specific mechanisms behind each claim. Reviewed every quarter and summarised in the Trust Center.
| Layer | Control |
|---|---|
| Password storage | bcrypt, cost factor 10+, per-user salt |
| Session tokens | 256-bit random, stored as SHA-256 hash only, httpOnly |
| Transport | TLS 1.3, HSTS, strict referrer policy, frame-ancestors restricted |
| Payout data | AES-256-GCM envelope encryption, key outside the database |
| Treasury keys | xpub/zpub only, seed never stored by the service |
| Sanctions screening | Every counterparty, on every order, before release |
Found a vulnerability?
We run a paid disclosure programme with a 24-hour triage SLA.