What we claim, and how to verify it.

This page is the public face of an internal engineering discipline: if a statement can't be tied to shipped code and a passing test, it is not made here — it lives in our internal gaps register until it can be. Marketing that can't survive an auditor isn't marketing we want. Anything marked NDA is available to qualified counterparties with verification instructions included.

The storage layer runs NIST-standard post-quantum cryptography

SHIPPED

Records are protected with ML-KEM-1024 hybrid key encapsulation and ML-DSA-87 signatures (FIPS 203/204 — the CNSA 2.0 algorithms), implemented in production Rust and gated by NIST known-answer tests. Encryption is not a service in front of the database; the database does not operate without it.

Algorithm choices and test methodology walked through in a technical briefing; known-answer-test evidence and code review under NDA.

Compliance is enforced at write time, end to end

SHIPPED

When a compliance gate is installed, a transfer without a valid envelope (originator/beneficiary identification, jurisdiction, travel-rule attestation) does not execute and produce an audit trail — it structurally fails to commit. Sanctions list state is anchored into the ledger history itself, so "what did the operator know and when" is answerable cryptographically.

Live demonstration against our running gateway — ask for the compliance-gate walkthrough.

Settlement reaches deterministic finality on a federated, fault-tolerant ledger

BUILT

The ledger replicates across nodes with crash-fault-tolerant consensus and produces a verifiable state commitment per transfer — "final" is a mathematical state, not a probabilistic confirmation count. A public multi-operator network with a live explorer is being stood up now.

State commitments and finality demonstrated live; explorer link will appear on the home page when public.

Signature algorithms can rotate without a fork and without changing addresses

BUILT

Cryptographic algorithm choice is a governed, versioned property of the network. When standards evolve, the network migrates by governance epoch — no hard fork, no address migration, no flag day. This is the property that makes "survives Q-day" a maintenance plan rather than a slogan.

Rotation demonstrated in the technical briefing.

Per-element provenance and confidence

SHIPPED

Every stored element carries provenance and a confidence state; outputs are traceable to the inputs that produced them. The system can distinguish "I know X from source S at confidence C" from "X is statistically likely" — including saying "I don't know."

Walkthrough against live substrate in briefing.

Performance and scale benchmarks

UNDER NDA

We publish benchmark numbers only with full methodology, hardware specification, and reproduction instructions attached — and that package is shared under NDA rather than compressed into a marketing number. If a number can't be reproduced from the document we hand you, we don't hand it to you.

Request the benchmark package: ashley@digital-fabric.com.

Public network explorer

IN PROGRESS

A publicly observable multi-node network where anyone can watch transfers reach finality and verify post-quantum signatures. Listed here because we intend to claim it soon — and per our own rules, it doesn't get a "shipped" badge until you can click it.

When live, the explorer itself is the verification.
What you will not find on this site: a token, a token sale, or an invitation to speculate. Digital Fabric sells settlement and compliance infrastructure to regulated institutions. We also do not claim Byzantine fault tolerance, formal certifications (FIPS 140-3 validation, SOC 2), or production custody until those exact words are true — each is on our roadmap register with its real status, available in diligence.