Verify a Challenge Coin.
Drop the file. The math does the rest: on your device, with nothing uploaded, no account, and no trust in the people who made it. Including us.
What just happened?
A Challenge Coin isn’t a screenshot of a result. Inside the file are the raw findings themselves, the verdict, and a cryptographic seal that binds every number together.
Each finding is hashed into a leaf, the leaves chain into one root fingerprint, and a challenge–response transcript locks the whole set. Your browser just rebuilt all of it from scratch.
The grade in the file has to open the sealed commitment built from the raw findings. Change one number, anywhere, and it stops opening. Whether that grade is the right grade for those findings is a separate check, and the terminal below does it.
The whole verdict is signed with ML-DSA-44, the NIST-standardized post-quantum signature (FIPS 204). It is the same class of cryptography the U.S. government is migrating to.
Under the hood: a transparent, hash-based binding proof: a SHA-384 Merkle commitment over the finding set with a Fiat-Shamir transcript, salted range and count openings, and an ML-DSA-44 origin seal. No trusted setup, nothing to subscribe to; verification is a deterministic replay of the derivation, and it fails closed on any mismatch. It is not a zero-knowledge proof (a zk prover is a patent-pending research direction). Details in the whitepaper.
What this page does and does not settle: it establishes integrity (the findings and the score are exactly what was sealed) and origin (which key sealed them), and it is kept byte-exact against the engine by golden test vectors. It does not recompute the score itself, because that needs the full scoring engine: algorithm risk weights, per-framework deadline urgency, asset criticality. pqcat coin verify does recompute it, and refuses a coin whose score does not follow from its own findings even when every seal is intact. So a coin that passes here is proven unaltered and attributable; for the stronger claim that its grade is the correct grade, run the pinned CLI. We would rather name that boundary than let a green check imply more than it checked.
Who sealed it: the verdict above proves the evidence was not altered; the seal key says who produced it. Coins minted by Soqucoin Labs are sealed by our published prover key, fingerprint 40e8cdb90683ad6f1ca0d46b. When a verified coin carries that key, the certificate says so; any other key means you should confirm the sender’s published key out of band before trusting the origin. An auditor who prefers a terminal pins the same key: export PQCAT_TRUSTED_SEAL_KEYS=<key> makes pqcat coin verify refuse any coin sealed by an unpinned signer, no browser involved.
The full published key (pin this)
d3b720f6375d67eee853529be05b698b57b65dad9a6a944eb0b8538fbc1f307a5c1b42c3355e6aca995177369e8849681ff03504852f8b27c08822973b816fcfa14b6a0c50d003fd1474b7b4816977b5ad13040ae943faab36aa7ed3968b9d53de2c55f2315cb372ae90b26f117edf13ce011d4639b2c270f0e61667f21bc3719d2a9a0866db2327fcff588bbcfc769a36d96ae1cbdb876ed2bf67086eb3d1bf306e117ee4bc7be313c18b788e929d124779253aabe37a5348ffce453bc5f96dd2bbc6b26d125f363c18bea9080e658be2634ec6315524fb12859a5c2aef93a3b786566ddf28de076e6b0279f857140fae4bca9e1e206a3196c86d0b8d76f6e20b3705f6fd24b9cc42ea0b61ffe1590eb45b4290965a46beee69a10c69d7ae9285c5a24f23f59689a8f210de2a5ced1101f35eb12595e8255a9b487b177424a1839b85abe259c9f20b48406ccd38f3d4131a338bbf50ec41e769eaa5db039e3c67426b0ddb7aefb6f6da00b258bb049b2f08d9e22202b62f2c3f749e5c071bb3eaa8f61d5b1acfb74576c891d0058c16194542ec316d2b34b331770addad589c299cd66f4dfaebf56c31c8e3524b0371175fed37077c083b9c4e680da11a9e3cfb56dafaf0d6d2708c2e23ffc1811f13acd210de0929cae237b2deb4d7f4d4444d40759d5353680d0b9db8cc5f32268f804f467a9281e559fccbd6c92599ceff0c57090ad2315c0626cc4d25a89af4248e4a5e1ebed7a5c23dc54ebf6afe6a4b5f4f77dc9dc957839f264a25bc0b99788d8e9acd0bfb9ba77ac15e9e06d8892061bd9890de4d7569dca218964b2a54ea54237d129a07b457826b1a6d4d687a2b30cdffb681ff6bf5599cc13d895d443302f2acedc0ef4eefa18054b3e0b76a480a1afb71e9a507a7e2fead11c2eaed7fea40d26cd097c770a0feb3e469d2ced02b2bc09b7e14005ae86fb495a6f595daed8646185adae5c305e5fdfcdd239dc4d13b7d90eec5a74c5327750a263e40ef5c1cf25b2def7d5c1adad60d6765716a5f0422f4de26afd3f86decd8ab5a5893bd0093b721f6cb694138a9a590827e1c622fb384ff79b4d30033fffedd2d254962aa0b67ebfaf838db356bb8d568db667829c2ea93bdc311a12725c5b63cd5da3f350953e3bbe63934cd0881727b7e959a3116401b702d07a519b69f5f43e0dc980f7ae5aa07e160d740d66339733db92c7a2c5c71dd50a355dcde8626e2a30a5b974c13b9f22c56d275389748055f2d02ea9f1ff4595cf519b120a073b24e28da6e3b3f805bcd5569873e7ef6b0163b863adbae901a1e24a56595f0128d837a76ea2bfbe451bb60fff6869721f51c970eba14405d5ebd54f77d74cb7c3583fc78329229834297cc731021534b4c1f3daa2e028f815bf60df9c4824a89abd04210d8f651a4fe349b5c5156c435c0fd851616a32757b6a903d6983e3c9f45d35bb29a7e5f573fe866422391352c0cef23fd075de97df89bf67053e3e4875bf0fcf737910a2c22c6713013f21e7369aa8bfcf45f32eb05f7a875971ef1651a5b60ce45bb2c4b116be03293c99a0ce52348af4e48c57fe57abf4f451309fc35d9471f33508aa855dd54187baa71958f1493d09d73209b933573837450d60bb3b6c62505cd156054c310d03f6f25041d2b1ed47657841a9f4e98082eed1b4122fdfc086b2d545f30d91c86fd34ed984434375e3618e0b95115091957c0e7365c43e35b306e0691c9dd372d1235c430a2e2325e446877a3c7f9d742bcac09e74daaecf212abc0ddd439d4616c910c9f69f1e58090f228c1afdb0f01646b42837c36b2411abbbd8899b4a68350d5fe26197324