Anyone can say they're post-quantum ready. PQ-Verified gives customers, regulators, and auditors a portable artifact they can verify themselves.
First attestation ceremony currently underway.
No H33 service in the loop. No vendor trust. Three commands, one PASS.
Disconnect from the internet. Run it again. Still passes. That is the entire architectural claim.
| Layer | Algorithm | Standard | Family |
|---|---|---|---|
| Primary signature | ML-DSA-65 | FIPS 204 | MLWE lattice |
| Compact alternative | FALCON-512 | Draft FIPS 206 | NTRU lattice |
| Belt-and-suspenders | SLH-DSA-SHA2-128f | FIPS 205 | Hash-based |
| Content commitment | SHA3-256 | FIPS 202 | Keccak-f1600 |
| Substrate format | 58-byte canonical | H33-74 standard | Deterministic |
The 2-of-3 threshold means PQ Verified passes if any two of {ML-DSA, FALCON, SLH-DSA} verify. A single algorithm family theoretically broken does not invalidate historical artifacts — the other two still hold.
Most vendors ship one signature algorithm. ML-DSA is currently the post-quantum default. If a future cryptanalysis attack breaks ML-DSA, every historical signature anywhere becomes worthless overnight. PQ Verified uses three independent mathematical foundations:
For all three to fall simultaneously requires a mathematical breakthrough that invalidates the entire post-quantum field. A 30-year-old PQ Verified artifact still verifies even after the first family falls.
Three views of the same product. What you get. What you'll pair it with. What runs underneath.
When a regulator, customer, or insurer asks "are you post-quantum compliant?" — you don't write a memo. You hand them a receipt. They verify it themselves. Done.
H33-74 receipts · Verifier Suite (vendor-independent) · Q-Sign threshold signing · NIST FIPS 203/204/205 alignment · Conformance corpus