Technology
Why a coordination protocol, the post-quantum cryptography in the libraries, and how consensus and zones are designed.
Why this architecture
Verifiable coordination and settlement for autonomous services that operate across organizational boundaries.
PQ identities from inception
Design basisPost-quantum signatures and identities are in the protocol libraries from the start; sessions use a post-quantum handshake in the current libraries. Architectural alignment with NIST standards and NSA CNSA 2.0 guidance, not a certification claim.
Assets and settlement
Architecture targetNative asset typing and multiparty settlement patterns. Controls are designed to support selected GDPR, MiCA and HIPAA-style requirements; this is not certified compliance.
Selective disclosure
LibrariesSTARK proof paths exist in the libraries; proving attributes without exposing raw records is a design goal, and the current circuits do not yet hide the data. Designed to support compliance controls — not compliance-ready as a product claim.
Parallel coordination
Design objectiveDAG ordering plus zone execution aims to reduce global-state contention. Horizontal scaling is a design objective under validation — not a measured production result.
Post-quantum signatures from the first version, with privacy and verifiable policy as design priorities rather than add-ons.
Standards referenced · not awards or live-net claims
Protocol Cryptography
Post-quantum cryptography
ML-DSA-87 (FIPS 204), ML-KEM-1024 (FIPS 203), SPHINCS+-SHAKE-128s (pre-standard basis of SLH-DSA, cold path, security category 1), plus a hybrid KEM (ML-KEM + X25519) that is disabled by default.
Implemented in protocol libraries; external audit pending. Architectural alignment only, not certification.
- GDPR Alignment Target
- HIPAA Alignment Target
- MiCA Alignment Target
- SOC2 Alignment Target
Primitives in libraries · audit pending
Three post-quantum primitives
FIPS 204 · 203 · SPHINCS+
ML-KEM for key establishment, ML-DSA for hot-path signatures, and SPHINCS+ (the basis of SLH-DSA) for selected cold-path operations. ML-KEM and ML-DSA are the standardized versions; the hash-based signature is the pre-standard one. Implemented in the protocol libraries; not CAVP-validated; external audit pending.
Hybrid KEM
ML-KEM + X25519
A combiner over ML-KEM and X25519, designed so that the session key holds if either of the two does. Present in the libraries and disabled by default; external audit pending.
ISMS alignment target
ISO 27001 · operating entity
Organizational security-management target for the operating entity (ISMS). No ISO 27001 certification is currently claimed for the entity or the protocol.
No trusted setup
STARK Proofs
STARK proofs with a transparent setup: no ceremony to trust. Zero-knowledge is not implemented yet: the current proofs use a non-hiding configuration.
Six building blocks
Open each one for the design underneath. Each says whether it is in the libraries or still a design.
ECDSA / RSA
Shor-vulnerable
NIST FIPS 203/204/205
204 · 203 · 205
ML-DSA, ML-KEM, SPHINCS+ — audit pending
Technical detail
Three post-quantum primitives in the protocol libraries: ML-DSA-87 (FIPS 204) and ML-KEM-1024 (FIPS 203) in their standardized form, and SPHINCS+-SHAKE-128s, the pre-standard basis of SLH-DSA (FIPS 205), on the cold path. A hybrid KEM is present and disabled by default. Scope today: internal libraries. External audit pending.
O(n²)
O(n) Gossip
Coherence layer over the DAG, with a fast path (design)
Technical detail
QronCord is the semantic coherence layer over the Mysticeti-derived DAG. It is designed to enable a fast path and cross-zone atomic transactions; zero-knowledge privacy is a design goal.
STARK proofs for selective disclosure (design)
Technical detail
Prove an attribute — solvency, eligibility, a compliance condition — without revealing the record behind it. Part of the protocol design rather than an application on top.
Protocol-level assets with recorded lineage
Technical detail
Implemented in the protocol libraries; validation on a public network is pending. Assets carry their type, their lineage and their attestations as protocol state; selective disclosure for trade secrets is a design goal.
Delay
STARK proof
Search
A share of emission reserved for work (specified)
Technical detail
Proof of Extraction (RFC-ECONOMICS-004): a sequential delay, a STARK proof and a difficulty search. By design it reserves a fixed share of new ZQN for miners, independent of validation capital. Specified; not implemented end to end.
Post-quantum attestation layer for autonomous systems
Technical detail
Implemented in the protocol libraries; validation on a public network is pending. An agent registry, a delegation framework and attestation primitives, for third parties to build on.
By design
Architecture in depth
DAG coordination, post-quantum primitives and privacy-preserving design, as implemented in the libraries or as designed.
QronCord
Per-claim coherence checks and nullifier tracking over the ordering layer, designed to avoid a single global-state bottleneck. A fast path for non-conflicting claims is in the libraries.
Post-quantum primitives
ML-DSA-87 (FIPS 204), ML-KEM-1024 (FIPS 203) and SPHINCS+-SHAKE-128s (pre-standard basis of SLH-DSA, cold path), plus a hybrid KEM that is disabled by default. Implemented in the protocol libraries; external audit pending.
Finality levels
A claim moves from included to final to settled; the levels are defined in the specification. Timings have not been measured on a public network.
Semantic Zones
Execution contexts with their own rules, linked at protocol level.
Coordination topology
Local state validation precedes global propagation, enabling deterministic sub-second finality while preserving DAG causality.