Post Quantum
Scan a wallet
01 / Security research

Post Quantum

Tools for testing what comes after today's cryptography.

Measure public-key disclosure against Shor-class adversaries. Encapsulate with ML-KEM-768. Sign with ML-DSA-65. Every primitive runs client-side and self-tests on load.

Signature lab/KEM vault/Exposure scanner
pqc-selftest — pairwise consistencyRUNNING
$ pqc selftest --fips203 --fips204 --aead
FIPS 203 · 204 · 205NIST PQC standards: ML-KEM, ML-DSA, SLH-DSA
NIST Category 3ML-KEM-768 and ML-DSA-65 parameter sets
0 B egressKeys and plaintext never leave the client
3 chains · live RPCBitcoin, Ethereum and Solana disclosure analysis
BUILT ONNIST FIPS 203NIST FIPS 204noble-post-quantumWeb Crypto APImempool.spaceEthereum JSON-RPCSolana JSON-RPC
02 / Tools

Three tools. All live.

pqc://risk-scannerLive chain data

Exposure Scanner

Determines whether an address has disclosed its public key on-chain, the precondition for a Shor-class key-recovery attack, and quantifies the value at risk. Supports P2PKH, P2SH, P2WPKH, P2WSH, P2TR, Ethereum EOAs and Solana accounts.

TryGrading methodology
A

Runs on noble-post-quantum, an open-source implementation that hasn't been independently audited yet. Great for learning and everyday files; don't trust it with secrets you can't afford to lose.

pqc://kem-vaultML-KEM-768 · FIPS 203

KEM Vault

Encapsulate a fresh shared secret with ML-KEM-768, derive an AES-256-GCM key through HKDF-SHA256 and seal text or a file. Only the matching secret key can open it. Nothing leaves this page.

1 · KEYPAIR
No keypair yet.
2 · ENCRYPT
or
3 · DECRYPT
or
pqc://signature-labML-DSA-65 · FIPS 204 vs Ed25519

Signature Lab

Generate keys, sign and verify with a post-quantum signature next to a classical one. Compare sizes and timings, then flip a bit in the message to watch both signatures fail.

03 / Threat model

Harvest now, break later.

Public keys published today stay on-chain forever. They're safe against classical computers, but a large enough quantum computer could work backwards from them. This is the attack path we test for.

01Your public key lands on-chain

When you send from an address, or by design on Taproot and Solana.

02Shor's algorithm reverses it

A quantum computer derives the private key from the public one.

03The attacker signs as you

Funds move in a normal-looking transaction. Nothing on-chain can tell it apart.

6.9M BTC

already sit in addresses whose public keys are on-chain, mostly reused legacy addresses, by Google Quantum AI's March 2026 estimate.

No quantum computer can do this today. Keys exposed now will still be exposed when one can, which is why migration has to start early.
04 / Reference

Algorithm matrix.

The primitives securing today's chains, their hardness assumptions, and their security against classical and quantum adversaries. NIST categories are relative to AES key search.

PrimitiveDeployed inHardness assumptionClassical (bits)Quantum (bits)StatusNotes

Upgrades in progress: Bitcoin's BIP-360 (P2MR) is proposed, not active. Solana's Winternitz Vault is opt-in and live.

05 / Connector

Ask your AI.

POST QUANTUM also works as a connector for Claude and ChatGPT. Add it once, then ask "is my wallet quantum-safe?" and paste an address.

In Claude, add a custom connector in Settings and paste this. In ChatGPT, turn on developer mode and add it as a connector.

06 / Token

$PQC

The community token behind POST QUANTUM. Every tool here stays free, with or without it.

CA

$PQC is a standard Solana token. Like every Solana token, it isn't quantum-resistant itself.