QuantumHarmony × ModulusZK

Post-Quantum Consensus meets First-Order Logic Proving

Integration Proposal January 2026 Technical Scoping

Paraxiom × ModulusZK Partnership Discussion

01 / 13

The Opportunity

"Verifiable decision trails over incentive-based trust"

QuantumHarmony Brings

  • Post-quantum L1 with Proof of Coherence consensus
  • QKD-derived entropy (hardware quantum)
  • Winterfell STARKs for measurement verification
  • CCAE (Coherence & Compliance Adversarial Evaluation) framework
  • Threshold QRNG with device STARK proofs

ModulusZK Brings

  • FOL arithmetization (10-100× faster)
  • Direct logic-to-polynomial mapping
  • Compliance attestations
  • Cross-chain proof infrastructure
  • Layer X proof coordination
02 / 13

What is FOL? (First-Order Logic)

ModulusZK's arithmetization — how logic becomes math

Traditional ZK (SNARKs)

// Standard pipeline Logical Statement ↓ Circuit (R1CS) ← BottleneckPolynomial Constraints ↓ Proof

FOL (ModulusZK)

// Skip circuit compilation Logical Statement ↓ Polynomial Constraints ↓ Proof // 10-100× cost reduction

Based on Dr. Murdoch Gabbay's polynomial semantics. A predicate compiles to a polynomial — verification = evaluate at random point, check if zero.

Key insight: FOL is the arithmetization. The polynomial commitment scheme underneath determines quantum resistance.

03 / 13

QuantumHarmony: Existing STARK Implementation

We use Winterfell STARKs — hash-based, quantum-resistant

qkd_client/src/zk/stark/winterfell/

// VRF Air Constraints impl Air for VrfAir { fn evaluate_transition(...) { // Winterfell constraint system result[0] = next[0] - (current[0] + current[1] + k); result[1] = next[1] - (current[1] * current[2]); } }

FRI Commitments Hash-based No trusted setup

Coherence Gadget Flow

  • Collect STARK proofs from QRNG reporters
  • Verify proofs using Winterfell verifier
  • Calculate coherence from QBER measurements
  • Sign vote with Falcon1024
  • Broadcast via Triple Ratchet
  • Finalize when >2/3 agree
04 / 13

Proof of Coherence: 5 Adaptive Levels

Consensus upgrades automatically as quantum hardware becomes available

Level 1: Classical BFT Base Substrate • Ed25519 signatures
Level 2: Post-Quantum BFT + SPHINCS+ validator account signatures
Level 3: Coherence-Weighted + Falcon1024 coherence votes • Validator selection by score
Level 4: QRNG-Enhanced + Hardware QRNG • Winterfell STARK proofs
Level 5: Full Proof of Coherence + QKD links (≥2 peers) • Complete quantum stack

Note: SPHINCS+ is a signature algorithm (Level 2+), not the consensus itself. Proof of Coherence is the consensus mechanism.

05 / 13

Cryptographic Stack: What Each Algorithm Does

Clear separation of concerns in the post-quantum architecture

AlgorithmTypePurposeQuantum Safe
SPHINCS+ Hash-based signature Validator account signatures (extrinsics) ✓ Yes
Falcon1024 Lattice-based signature Coherence vote signing (finality gadget) ✓ Yes
Winterfell STARKs Hash-based ZK proof Quantum measurement verification ✓ Yes
Triple Ratchet Key agreement protocol Encrypted P2P vote broadcasting ✓ Yes
BLAKE3 / SHA-3 Hash function Commitments, Merkle trees, FRI ✓ Yes

The entire stack is post-quantum secure — no elliptic curve dependencies in the critical path.

06 / 13

Threshold QRNG: Three-Level Proof Stack

Each quantum entropy share carries a STARK proof of measurement authenticity

Level 1: Device STARK Proofs Quantum measurement authenticity • Per-device proofs
Level 2: Shamir Reconstruction Proofs Leader correctness • Commitment = Hash(shares || entropy || leader)
Level 3: Byzantine Consensus >2/3 validators agree • Falcon1024 signatures
// threshold_qrng.rs - DeviceShare structure pub struct DeviceShare { pub device_id: DeviceId, // Toshiba, Crypto4A, KIRQ pub entropy_share: Vec<u8>, // Raw quantum entropy pub qber: u32, // Quantum Bit Error Rate pub stark_proof: Vec<u8>, // STARK proof of measurement }
07 / 13

CCAE: Coherence & Compliance Adversarial Evaluation

A stateful adversarial testing framework for consensus systems

"Not a static code audit — a stateful adversarial evaluation of consensus trajectories under compliance constraints."

Stateful Fuzzing

Multi-epoch test scenarios with network partitions, Byzantine validators, timing attacks, entropy manipulation

Coverage-Guided

WASM runtime coverage, consensus state machine edges, STARK verifier branches, economic paths

Invariant Oracles

Safety (no double-finalize), Liveness (bounded progress), Compliance (proof acceptance), PoC (coherence)

Reproducible

Deterministic sandbox, seedable PRNG, virtual clock, snapshot rollback — minimal repro traces

08 / 13

Proposed Integration Architecture

ModulusZK FOL Proofs Fast compliance attestations • Audit proofs • Policy verification
QuantumHarmony STARK Gate Winterfell verification • Consensus gating • Finality anchoring
CCAE Harness Adversarial testing • Coverage instrumentation • Regression suite

Key question: Can FOL proofs integrate with our existing Winterfell-based verification pipeline, or do they require a separate verifier?

09 / 13

Critical Technical Questions

FOL is the arithmetization. The polynomial commitment scheme determines quantum resistance.

Commitment SchemeBased OnQuantum Safe?
KZGElliptic curve pairingsNo
FRI (what we use)Hash functionsYes
IPA / BulletproofsElliptic curvesNo

Q1: Polynomial Commitment

"FOL is your arithmetization. What polynomial commitment scheme sits underneath — hash-based like FRI, or curve-based like KZG?"

Q2: Verification Interface

"Can your proofs integrate with Winterfell verification, or do we need a custom FOL verifier pallet?"

Q3: Substrate Integration

"Your Polkadot support — parachain-level or direct Substrate solo chain integration?"

Q4: Layer X Scope

"How does Layer X relate to L1 finality? Proof coordination, or its own settlement?"

Q1 determines everything. If curve-based, it contradicts our post-quantum thesis.

10 / 13

Partnership Structure Options

ModelStructureWhen to Use
Model AModulusZK as Proof ProviderThey generate compliance proofs, we verify through STARK gate
Model BCCAE as ServiceWe run their proof system through CCAE, deliver threat model + regression suite
Model CJoint Ecosystem GrantPolkadot Treasury or other ecosystem funding
Model DStrategic AlignmentToken swap or equity arrangement for long-term integration

Current stage: Technical scoping first, then determine which structure creates real value for both sides.

11 / 13

QuantumHarmony Current Status

Live Infrastructure

  • Alice — OVH Montreal (51.79.26.123)
  • Bob — OVH Beauharnois (51.79.26.168)
  • Charlie — DigitalOcean Frankfurt (209.38.225.4)
Testnet Live Proof of Coherence Winterfell STARKs

Near-Term Focus

  • Security audit
  • Additional validator onboarding
  • Mainnet preparation
  • CCAE harness completion
  • Compliance proof use cases
12 / 13

Next Steps

1. Answer Q1

Clarify polynomial commitment scheme — hash-based (compatible) or curve-based (incompatible with our thesis)

2. Proof Format Spec

Share proof format documentation to assess Winterfell integration path

3. Test Corpus

Sample proofs to run through CCAE harness for initial coverage analysis

4. Scope Definition

Define specific compliance predicates to target (policy proofs, audit attestations)

Contact: sylvain@paraxiom.org

GitHub: github.com/Paraxiom/quantumharmony

13 / 13