Public test labs and live endpoints for inspecting Quantova's consensus and confirming it exhibits a post-quantum structure. Point the labs at a Quantova node (the public testnet, or your own) and they check — over the q_ JSON-RPC surface — that signatures are post-quantum, that there is no elliptic-curve recovery path, that slot leadership is deterministic with no VRF, and that hashing is SHA3-256.

This is a hands-on companion to the consensus-specs repository. The specs say how consensus works; these labs let anyone verify a running node behaves that way.

These labs are an inspection harness, not a security proof. Read what-the-labs-prove.md before drawing conclusions.

• They confirm a node exhibits the expected post-quantum structure: post-quantum signature schemes and sizes, no ecrecover/secp256k1 path, deterministic no-VRF leadership, SHA3-256 hashing, and deterministic finality.
• They do not prove the cryptography is unbreakable, that the implementation is free of side-channels, or that there is no fallback elsewhere. Those are established by the NIST standardization of the underlying schemes and by independent audit — not by a connectivity test. The labs are evidence, not a substitute for audit.

Free TQTOV for testnet is available from the faucet (see https://quantova.org). The full endpoint and method reference is in docs/endpoints.md.

--- # Consensus

git clone https://github.com/Quantova/consensus-spec-test.git
cd consensus-spec-test
npm install # only Node's built-in test runner is required to run the offline labs
# point the labs at a node
cp .env.example .env
# set QUANTOVA_RPC_URL=https://testnet.quantova.io (or your node)
# run every lab
npm test
# or run one lab
npm run lab:signature

Labs that need a node skip cleanly when QUANTOVA_RPC_URL is unset, so npm test passes offline and runs the self-verifying checks (for example, the SHA3-256 known-answer tests). Set the endpoint to run the live checks.

Shared helpers live in lib/: a q_ JSON-RPC client and the post-quantum scheme reference.

The labs are written against the documented Quantova RPC surface, but the exact field names and byte layout in a node's responses are confirmed against the running node. Where a lab depends on a specific response shape (for example, where a block records its slot, author, or signature), that point is marked in the code with a // ADAPT: comment. Confirm those against the node you test, then the live checks run.

© 2026 Quantova Inc. See LICENSE.md. These labs are provided for inspection and educational use and are not a security audit, a guarantee, or financial advice.