Open-source project guide · Experimental public-alpha

ML-DSA-65 and Hybrid-Signature Research

QRun includes real post-quantum signature verification work in Rust, but the whole blockchain is not being advertised as quantum-resistant. The distinction between a tested verifier and a fully integrated security profile is essential.

What is implemented in the research tree?

The Rust source includes a Libcrux ML-DSA-65 verification adapter and tests against a selected hash-pinned C2SP/Wycheproof fixture. The documented fixture has 53 cases: 48 expected-valid and 5 expected-invalid. The test work checks acceptance/rejection outcomes and selected mutation, tampering and wrong-digest cases.

Real verification code

This is more than a roadmap-only mention: the adapter calls a real implementation for ML-DSA-65 verification in candidate code paths.

Hybrid identity candidate

V4 research formats carry both Ed25519 and ML-DSA-65 identity/signature material. The selected path is not yet fully activated across the production node, wallet and every transaction type.

Independent qualification remains

The full key policy, transaction migration, peer identity, signing UX, release builds and end-to-end protocol path require consolidation and independent review.

What the 53 cases do—and do not—mean

The 53 cases refer to one selected external signature-verification fixture, not all project tests and not all protocol vectors. QRun has additional protocol/state fixtures and regression tests. Counting test vectors is not the same as proving production security.

ML-DSA-65 verification tests do not prove that consensus, network handshakes, wallets, transaction signing, storage recovery, or the whole chain are quantum-resistant. This page deliberately does not make that claim.

Recommended review

  1. Reproduce the selected fixture tests from the exact branch and pinned dependencies.
  2. Review public-key and signature parsing, domain separation, wrong-network rejection and downgrade behavior.
  3. Exercise the selected policy through wallet construction, transaction admission, peer authentication, reorg/replay and independent release builds.
  4. Publish reviewer findings and resolve critical/high issues before activating a production profile.

Source evidence: technical test report, selected 53-case fixture, and current release gate.

Project status: QRun is experimental public-alpha, not production Mainnet. No public native QZXB market or price is claimed.

See the current release gates · Contribute or propose a funded milestone.