Security
Built to be trusted with real money.
Every mechanism below is real, live in the platform today — not aspirational security marketing.
OTP-gated withdrawals
Every withdrawal request requires a one-time code sent to your email before it's queued — a stolen session alone can't move funds out of your account.
HMAC-signed API requests
Every request to the developer API is signed with your own secret key, never transmitted in plaintext — a signature that doesn't match, or a replayed timestamp, is rejected outright.
Double-entry ledger accounting
Every balance is derived by summing immutable ledger entries, not stored and mutated directly — there's no code path that can silently corrupt a balance without leaving a traceable entry behind.
Confirmation thresholds on crypto
Deposits on Ethereum, Polygon, Celo, Optimism, and Solana each wait for network-appropriate confirmation counts before crediting your wallet — tuned per network's own reorg risk, not a single one-size-fits-all number.
Role-based access control
Platform administration (role assignment, fee schedules, dispute resolution) is gated by specific, narrow permissions — no account has blanket 'admin' access by default.
Encrypted key storage
Crypto wallet private keys are envelope-encrypted at rest, never stored in plaintext, and decrypted only transiently when a transaction actually needs signing.
Append-only audit trail
Security-relevant actions — logins, role changes, withdrawals, API key use — are recorded in an audit log that database-level triggers actively prevent from being edited or deleted after the fact.
Escrow requires mutual confirmation
Funds held in escrow release only once both the depositor and receiver confirm — no single party, including the platform, can unilaterally move escrowed funds without a defined dispute-resolution path.
Have a security question or found something concerning?
We take reports seriously — reach out and we'll respond directly.