Every ledger in production today secures yesterday's transactions with cryptography that a quantum computer will retroactively break — and enforces compliance with services bolted on beside the data. TrustDB is a data substrate where post-quantum protection and compliance are properties of the storage layer itself. Not middleware. Not policy. Structure.
New US National Security System acquisitions must use FIPS 203/204 (ML-KEM / ML-DSA). Systems that bolted classical crypto into the storage path face a re-architecture, not an upgrade.
Everything stored today under RSA and elliptic-curve cryptography is already being collected for retroactive decryption. For a ledger, the exposure is permanent: the history is the product.
EU institutions must prove — not document — that originator and beneficiary information travels with value. Bolt-on compliance programs now have to demonstrate the bolt can't be removed.
Regulated dollar tokens are now a permitted, supervised business — and the statute requires exactly the controls (sanctions screening, freeze authority, auditability) that retrofitted chains struggle to provide.
TrustDB is a post-quantum, confidence-native data substrate built in Rust. Crypto settlement is not what it is — it's the first use case the substrate makes possible without the compromises every other approach accepts.
Every record is written and read under CNSA 2.0-aligned post-quantum protection (ML-KEM-1024 hybrid key encapsulation; ML-DSA-87 signatures). There is no separate encryption service to remove, misconfigure, or migrate.
Access control, audit, and compliance are properties of the record itself. A query that would violate policy doesn't get blocked — it structurally cannot produce output.
Every output is cryptographically anchored to the records that produced it. Ask "why?" of any result and receive a verifiable path back to sources, confidence, and governance state at the time.
Per-observer, per-jurisdiction disclosure is a first-class operation — prove a claim to a regulator without revealing identity or balance to anyone else.
Signature algorithms are governed, versioned properties of the network. When standards move again — and they will — the network rotates without a hard fork and without changing a single address.
| Capability | Status | Notes |
|---|---|---|
| Post-quantum storage layer | SHIPPED | Production Rust; NIST-standard algorithms, known-answer-test gated. |
| Compliance-by-construction gate | SHIPPED | Travel-rule envelope, sanctions anchoring, and auditable history enforced at write time — end to end. |
| Federated, fault-tolerant ledger | BUILT | Multi-node replication with deterministic finality; public multi-operator network is being stood up. |
| iOS wallet client | BUILT | Thin, honest client over the substrate — integer-exact amounts, compliance envelope on send. |
| Public network status | LIVE | Hourly snapshot of the running gateway — full real-time explorer ships with the public multi-operator network. |
Every public claim on this site is backed by shipped code or it isn't made. Anything aspirational is labeled as such. We maintain an internal "honest gaps" register as an engineering discipline — if a claim can't be tied to running code and a passing test, it moves to that register instead of this page. Read the claims-and-verification page →
Stablecoin issuers under the new US framework. Banks piloting tokenized deposits and wholesale settlement. Defense and government programs facing the 2027 post-quantum acquisition deadline. If your ledger has to be defensible in 2035, the storage layer is the decision that matters.