TRANSPARENCY
Append-only hash chains, conservation enforced as a gate, benchmarks published with their methodology. The receipts, in one place — so you can check the platform instead of taking its word.
Most exchanges ask you to trust them between audits. You should not have to. Verifiability is built into how the system is constructed — so the honest claims below end in a mechanism you can check, not an assurance you have to believe.
01 · Property, not promise
A yearly audit is a snapshot; construction is permanent. Balances conserve because of how transfers are written, and the audit chain is tamper-evident because each record commits to the last. The guarantee is a property of the design, re-checked on every run — not a certificate on a wall.
Mechanism: invariants enforced by construction — verified continuously, not once a year.
02 · Show the receipts
No adjective without a mechanism. Where a page says a balance is conserved or a record cannot be silently edited, there is a gate or a hash chain behind it — and, increasingly, a way for you to check it yourself rather than take it on faith.
Mechanism: claims terminate in a gate, a hash chain, or an external verifier.
This hub gathers the verifiability mechanisms from across the platform into one map. The principle sits at the centre; each spoke is a mechanism that proves it, linking to the page where it actually runs. Follow any spoke to see the receipt in context.
Don’t trust — verify.
Every fill, transfer, and balance change is hashed into an append-only BLAKE3 chain — edit one record and the cascade of hashes breaks visibly.
Verify on TechnologyBalances sum to zero per asset by construction, and a conservation gate checks the invariant on every run — like a test, not a promise.
Verify on AccountAn external crypto-audit is a release gate before mainnet: withdrawals do not switch on until the threshold-signature custody stack has passed it.
Verify on CustodyEach marketplace collection is a hash-chained, signature-sealed ledger anyone can replay end-to-end with a verifier — provenance without a blockchain.
Verify on MarketplaceLong-lived ledger records are signed with a hybrid of Ed25519 and ML-DSA-65 (FIPS 204), wrapped in a crypto-agile envelope so a forgery must break both schemes.
Verify on Post-quantumA latency figure means nothing without the conditions that produced it. So every performance number ships with how it was measured — and p50 and p99 are shown together, never just the flattering one.
Measured under
in-process matching path, single instrument, canary hardware
Synthetic sustained load — headroom beyond any real-world exchange order flow.
On the throughput number
The throughput figure is marked honestly: it is a benchmark, not production traffic. No live order flow on any exchange, the largest CEX included, reaches the density sustained on a single instrument. The synthetic nature is not a weakness — it means the measured ceiling sits well above any flow you would actually see. And competitors are not named: their public numbers are marketing claims, not verifiable measurements — the differentiator is the published methodology, not someone else's figures.
Mechanism: synthetic sustained load — headroom beyond any real-world exchange order flow.
The mechanisms above are Live today. The next step is to turn them into public surfaces — and that is labelled honestly as Planned, committed in the landing roadmap, not shipped.
Published proof surfaces that let anyone confirm integrity from outside — moving the audit chain and conservation checks from "trust the gate" to "run the check yourself". Planned for Phase 02.
Downloadable artefacts — hash-tips and ledger snapshots — packaged for independent verification, so a third party can attest the chain without privileged access. Planned.
What you can verify today, what off-box means, and what is honestly still ahead.
Today you can verify the marketplace asset-ledger end-to-end: each collection is an append-only, hash-chained, signature-sealed ledger, and an external verifier replays it to confirm no event was altered. The exchange audit chain and the conservation gate run continuously on the exchange side and the hash-tip is exported off-box so it cannot be silently rewritten; full public proof surfaces that let you re-run those checks yourself are Planned for Phase 02. That boundary is stated plainly rather than overclaimed.
The audit chain is append-only: each record commits to the hash of the one before it, so the latest hash — the "tip" — fixes the entire history. That tip is exported off the machine that produces it. Because an external copy of the tip exists, the chain cannot be quietly rewritten after the fact: any attempt to edit old history would no longer match the tip already published off-box. It is the difference between a log you control and a commitment someone else is holding.
Because a number without its method is marketing. A latency figure depends entirely on the path measured, the instrument count, and the hardware — so those conditions are published next to every figure ("in-process matching path, single instrument, canary hardware") and p50 is shown alongside p99. The throughput number is also marked as synthetic sustained load: it is a benchmark, not production traffic, and the headroom beyond any real-world order flow is the point. The published methodology is the differentiator — not a comparison to someone else.
Public proof surfaces that move verification from the exchange side to yours: a way to confirm the audit chain and conservation checks from outside, plus downloadable hash-tips and ledger snapshots packaged for independent verification by a third party without privileged access. This is committed in the landing roadmap and labelled Planned for Phase 02 — with no pretence that it ships today.
Transparency is the index; these are the pages where the mechanisms actually run — the trust posture, the cryptography that signs the records, and the ledger that conserves them.