Skip to content

DVA Institutional Crypto Trading

High-performance cryptocurrency trading platform with secure custody, compliant onboarding, and a high-throughput trading engine for institutional desks and partners.

01 — The problem

What we were solving

Regulated market participants needing segregated balances, clear audit trails, and sub-second order paths during volatility spikes.

  • Custody and trading logic must stay separated while still feeling like one product to traders.
  • KYC/AML checks cannot block legitimate flows during peak listing windows.
  • Matching and risk checks must scale horizontally without double spends.
02 — The approach

What we built

  1. MPC-based custody integration with explicit withdrawal policies and quorum approvals.
  2. Modular trading rails: retail, merchant, and OTC flows share risk and ledger primitives.
  3. Load-tested matching path with deterministic replay for incident analysis.
Architecture notes for your engineers
  • Event-sourced ledger slices for reconstructing balances after disputes.
05 — Outcomes

Key results

  • Fireblocks MPC-based custody
  • KYC/AML via Sumsub
  • Retail, Merchant & OTC modules
  • Scalable matching engine
06 — Stack

What it was built on

Representative tools and patterns — exact vendors vary per client environment.

Custody & compliance

Fireblocks MPC patternsSumsub (or equivalent) KYC/AMLTravel rule hooks

Trading core

Order book serviceRisk checksSettlement workers

Platform

PostgreSQL / durable storeRedis for hot stateKubernetes
07 — Learnings

What we'd tell the next team

  • Treat compliance as workflows, not one-off screens - auditors ask for history, not screenshots.
  • Separate hot trading paths from cold compliance jobs to protect latency.
  • Rehearse chain reorganisations and stuck withdrawals in staging; money bugs are existential.
FAQ

Questions this engagement anticipated

How was custody separated from trading logic?

With explicit policy and quorum flows for withdrawals while sharing risk primitives across retail, merchant, and OTC surfaces so traders still experience one coherent product.

What latency risks were designed around?

Volatile listing windows and burst order flow - hot paths were isolated from compliance jobs so matching stayed predictable under spike load.

Compare your situation to this case.

Bring your constraints - environment, timeline, and budget. We scope before we quote.

Get started

Leave your email - we'll reach out.

Share your work email and we'll follow up with a tailored note on security, AI, or data programmes - usually within one business day.

No spam. We only use your email to respond to this request.

Explore services →