Documentation
These pages are distilled from the design documents, review records and measurement artifacts in the seven repositories. They are written for someone who builds or evaluates market infrastructure and wants to know exactly what is proved, what is measured, and what is still a claim.
How to read this
- Architecture gives the shape: who decides, who instructs, who settles, and which secret sits where.
- zkPI and DeFMI are the protocol core. Read them together; the instruction is meaningless without the ledger that consumes it.
- QOMM and OCLOB are the two venues built so far. Use cases is the argument that they are examples, not the product.
- Binding, Audit, Accountability and Deployment are deep dives into the RFQ venue, where most of the MPC measurements were taken. They are about QOMM; the settlement layer does not depend on them.
- Security, Measurements and Status are the evidence pages. If you only read one, read Status: it says what is accepted and what is not. How this project works explains why the evidence pages are shaped the way they are.
Conventions used on this site
- Every number is from an artifact. Measurements name the host label (
host-a,host-b,host-c) and the JSON file underartifacts/that carries them. A machine's calibration is stated beside its figures; compare calibrations before comparing anything else. - "Built" and "accepted" are different words. Built means the code exists and its tests pass. Accepted means it ran in the repository's release gate. Neither means production.
- "Not claimed" is a section, not a footnote. Each protocol page ends with what it does not do. Those lists come from the review records and are as much part of the design as the mechanisms.
Pages
Architecture
Data flow, secret ownership, repositories, primitives, execution target.
zkPI
The instruction: what it commits, what it proves, the version-2 wire layout, the vectors, where it runs.
DeFMI
Guarantees, balance width, asset tags, netting models, overdraft limits, default waterfall, notes and rings, PvP, reconciliation, viewing, vetting, the Avalanche VM.
DeKYX
Credentials, anonymous presentations, scope nullifiers, revocation, rotation, what "scope-pseudonymous" means.
DeCCP
Clearing books, admission, margin, three netting modes, guarantee facilities, default waterfall, receipts.
Aethel
Payment streams as receivables; provider capabilities; confidential guarantees through DeCCP; settlement through zkPI.
Binding computed to committed
The gap in the middle of the stack, the two closures, the compile-flag error, VOLE-in-the-Head measured, post-quantum, quantum networks.
Audit machinery
Cover slots, receipts and slashing, relays, the quote proof, the pricing-rule language, oblivious asset selection, where the rounds go.
Accountability and robustness
The five-rung ladder, Reed–Solomon decoding in the engine, rung 5 at nine nodes, dishonest majority priced, the taker as a party.
Choosing a deployment
Placement against collusion, why 26 s is affordable, three profiles, the switches that default off, component choices.
Cryptography in use
Group, generators, every transcript label, the six sigma protocols, range proofs, one-of-many, notes, adaptors, FROST, the matched-field MPC, DeKYX, the hybrids; where code and documents disagree.
How this project works
No number by hand, predictions before runs, retractions in public, fail closed, no TEE.
FAQ
Token, blockchain, EVM, TEEs, seven nodes, regulators, post-quantum, dark pools, production.
Roadmap
Done, next by dependency, products in order, blocked outside the code, open questions.
Applications beyond venues
Fund subscription, collateral, PvP, issuance, receivables, certificates, insurance; an implementation order.
Measurements
The decision-relevant numbers in one place, with artifacts.
Security and trust boundary
Adversaries, the accountability ladder, what validators verify and do not, anonymity as traffic, what is not defended.
Post-quantum migration
Hybrid signatures and key exchange across the stack, what passed on one host and is now on main, what stays classical, what is still unverified.
Position against prior work
Five papers, six axes, three retracted claims, four open questions.
Comparison with other systems
Eighteen products and platforms in one table against zkFMI, Canton in depth, nine decisions, the wording refused.
Regulation
What the architecture needs from a legal system, Japan in detail, four other jurisdictions, what may and may not be claimed.
Status and acceptance
Per-component state, what the gates cover, what blocks production.
Get started
Clone, test, verify vectors, run the L1 gate, enterprise PoC guides.
Glossary
The terms of art, both the cryptographic and the market-infrastructure ones.
From the technical deck to implementation
The 37-topic cryptography catalogue maps purpose, equations, actors and limitations. Follow the settlement lifecycle for state transitions and optimistic assurance for the two demos and their native settlement boundary.