The thesis
Modern banking compliance is cryptographic theater. Regulators receive position-level extracts they cannot fully process. Auditors recompute on samples and attest with disclaimers. Counterparties exchange gross exposure data through tri-party agents that leak commercially sensitive information. Every layer carries a tax — in cost, in breach risk, in time-to-supervision.
zkDB collapses this by making the answer the thing that travels, and the proof the thing that travels with it.
Where we engage
Regulatory capital and stress testing
Submit a CET1 ratio, an LCR, or a CCAR / DFAST projection to a regulator with a 38 KB proof that the number was correctly computed on a committed ledger. The regulator verifies in milliseconds. The general ledger never leaves your custody.
Relevant frameworks: Basel III/IV · Dodd-Frank CCAR/DFAST · EBA stress tests · FFIEC Call Reports · SEC Rule 17a-4.
MiFID II and best-execution reporting
Prove that every executed order satisfied the firm's best-execution policy across the venue set, without disclosing client identity or order-flow patterns. The proof is filed; the supervisor accepts it; the order book stays sealed.
AML and sanctions screening
Prove a counterparty was screened against the live OFAC list — and that no screening was bypassed, deferred, or backdated — without disclosing the full counterparty database. Particularly powerful for correspondent banking and trade-finance flows.
Inter-bank exposure and solvency proofs
Two banks running a bilateral exposure check exchange proofs that net exposure satisfies an agreed bound. Neither bank discloses positions. No tri-party collateral agent is required. Settles in minutes, not days.
Tokenized private credit and structured products
For firms tokenizing private credit, real-estate cash flows, or other structured exposures: prove the on-chain claim is backed by the off-chain ledger, prove the cash-flow waterfall executes correctly, prove the underlying loan tape satisfies the offering memorandum — all without putting the loan tape on-chain.
How an engagement is shaped
A typical financial-services engagement runs in four phases:
- Confidential briefing (1 session) — your team frames the regulatory question; ours sketches the cryptographic shape and feasibility band.
- Architecture assessment (4–8 weeks) — proof-system selection, commitment cadence, key custody, integration surface with your existing data warehouse and submission pipelines.
- Pilot (8–16 weeks) — a single end-to-end workflow built and verified, typically against a synthetic regulatory submission.
- Production engagement — full rollout under your CTO's program governance, with sustained advisory support.
Engagements are confidential. We do not publish customer logos. Reference conversations are arranged firm-to-firm under NDA when the procurement reaches that stage.
What we typically deliver
- Proof-system selection and architecture document
- Circuit specifications for your exact query set
- Reference implementation in production-grade Rust + integration shims for Java / .NET / Python data pipelines
- Verifier-side libraries and key-custody design for your regulator's IT
- Governance playbook: commitment ceremony, key rotation, incident response
- Training for your compliance, internal audit, and engineering teams
Request a briefing
Briefings are reserved for senior engineering, risk, and compliance principals at regulated financial institutions. Request a briefing →
