Escrow architecture
Escrowed crypto is not pooled in a single company hot wallet. Escrow and custody depend on a verified funded live route, available signers, and the displayed release, refund, dispute, and recovery terms.
Public security and deployment evidence
Trust & Security
Straightforward answers about how the platform protects trades — including what it does and does not protect against.
Threat model — what escrow does and doesn't cover
It does not eliminate every risk. Keep communication and payment evidence within the trade. Escrow and custody depend on a verified funded live route, available signers, and the displayed release, refund, dispute, and recovery terms.
Dispute process
If a trade goes wrong, either party can open a dispute. An arbitrator reviews the in-trade evidence (messages, payment proof) and co-signs to release funds to the buyer or refund the seller. The arbitrator alone cannot take funds — two of three signatures are always required.
Identity-verification exceptions
Wallet-based browsing does not guarantee eligibility or reduced verification. Identity, volume, payment, risk, and jurisdiction checks may apply; access can be restricted when requirements are not met.
Arbitrator key custody
Current server-side arbitrator keys use software custody: AES-256-GCM encrypted in PostgreSQL and decrypted in process memory for signing. Hardware HSM integration such as CloudHSM or YubiHSM remains future work.
Contract verification
Escrow deposits, releases and refunds can be inspected on the relevant public block explorer. The EVM escrow contract source is published, but source publication alone is not proof that deployed bytecode matches it: check the displayed contract address and explorer verification where available. We do not claim a third-party audit or certification we have not received.
Bitcoin / LitecoinLive on-chain multisig
P2WSH 2-of-3Base / EVMSource published; production deployment not published
packages/contractsMonero / Solana / TRON / CardanoIn development; do not treat as live multisig
packages/escrowCXCash / AztecTestnet only
packages/cxcash-contractPublished contract-address record
No EVM escrow production address or verified deployment manifest is currently published.
Reproducible deployment and source verification
pnpm --filter @coinexchange/contracts compilepnpm --filter @coinexchange/contracts deploy:base-sepoliapnpm --filter @coinexchange/contracts verify:base-sepolia -- <address>
Data retention
Retention depends on the data: trade and transaction records are kept for at least 5 years; KYC records, when collected, are generally kept for 5 years after the relationship ends; audit logs for at least 2 years; trade chat for the trade plus 1 year; and session/security logs for up to 90 days. We do not sell personal data. See the Privacy Policy for the complete schedule.
Read the full Privacy PolicyUptime & incident transparency
We do not currently publish an independently verified uptime percentage or promise an uptime SLA. Availability depends on the web app, API, wallet providers and the relevant blockchain. Material security or availability incidents will be described in dated public updates after containment when disclosure will not increase risk; users can report issues through the Help Center.
No entries have been added to this public incident register. This is not proof that no incident occurred and is not an uptime guarantee.
Live API readiness
Check current API status
This point-in-time check is not an uptime SLA or historical availability report.