Private pre-testnet

Current validation boundary
← Home

Technology

Why a coordination protocol, the post-quantum cryptography in the libraries, and how consensus and zones are designed.

Design rationale

Why this architecture

Verifiable coordination and settlement for autonomous services that operate across organizational boundaries.

PQ identities from inception

Design basis

Post-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 target

Native 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

Libraries

STARK 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 objective

DAG 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.

Design note, not an external assessment

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.

Core building blocks

Six building blocks

Open each one for the design underneath. Each says whether it is in the libraries or still a design.

Post-quantum stack

ECDSA / RSA

Shor-vulnerable

Migration

NIST FIPS 203/204/205

204 · 203 · 205

Three PQ primitives in libraries

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.

By design

Architecture in depth

DAG coordination, post-quantum primitives and privacy-preserving design, as implemented in the libraries or as designed.

In-repo

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.

Atomic
Cross-zone commit (design)
QronCord Semantic Coherence