Read-only monitoring of the live four-contract deployment. No wallet key is used.
Quantum dashboard
Watch the on-chain canary, read the live threat level, and get your account protected before the Quanthood Moment. Monitoring alone protects nobody — registration takes a minute.
Start here
Register a post-quantum key
Create an ML-DSA-44 key in your browser and commit its hash to QuanthoodArk. After the Moment, that hash is what proves the account is yours.
2Try the canary
Solve a 16-bit training rung right here and watch the contract verify it. No quantum hardware needed for the small ones.
3Guard your contracts
Build a contract that locks itself the moment the threat level rises. Pick the threshold; the wizard writes the code.
Progress is stored only in this browser.
How Quanthood works
The Quanthood Moment is the first time an armed canary key breaks. It is recorded on-chain, and every module reacts to it from that instant.
Twelve curve keys from 16 to 192 bits hold bounties. Breaking an armed one proves quantum capability.
Each armed break raises threatLevel() by one, from 0 to 5. It never goes back down.
Contracts built with QuanthoodGuard lock their critical functions at a level you choose.
Accounts with a registered PQ key keep a recovery path no quantum attacker can forge.
Bounties sit in the canary contract itself. The contract verifies every claimed break and pays the solver.
Register a post-quantum key
Every ECDSA public key that has ever sent a transaction will be readable back into a private key by a big enough quantum computer. Register a post-quantum key now — after the Quanthood Moment, it is the only proof of ownership that still works.
ML-DSA-44 (NIST FIPS 204). The key is generated and stays in this browser — only a 32-byte hash of it ever reaches the chain.
A small file with your PQ public key and salt. Whoever holds it can prove this account's ownership after the Moment. Keep it offline — a USB stick or printed paper.
Lattice problems (Module-LWE) are believed hard for quantum computers — Shor's algorithm does not apply to them. An attacker who breaks your ECDSA key still cannot produce a valid ML-DSA signature for the account you registered. The commitment hash on-chain binds that ML-DSA key to your address, timestamped before the Moment.
PQ Signer
Generate an ML-DSA-44 signature entirely in your browser and verify it against the public key you registered. Useful as a dry run of the recovery flow before you actually need it.
Threat level
QuanthoodOracle exposes one number, 0 to 5. It rises by one each time an armed canary key is broken, and it never comes back down. Read it live from the chain, then use the guide to decide what to do.
This event fires whenever an armed rung is verified broken. Index it from your own contracts to react without polling.
| Level | State | Meaning | Recommended action |
|---|---|---|---|
| 0 | Nominal | No armed key broken | Register a PQ key. Keep monitoring. |
| 1 | Watch | 128-bit key broken | Move funds out of exposed accounts. Default guards trip. |
| 2 | Watch | 144-bit key broken | Stop using ECDSA-only accounts for anything valuable. |
| 3 | Critical | 160-bit key broken | Recover vault balances via Ark. |
| 4 | Critical | 176-bit key broken | Treat every exposed key as compromised. |
| 5 | Critical | 192-bit rung broken | All exposed ECDSA keys are breakable. Recover everything now. |
Canary ladder
Twelve elliptic-curve challenges from 16 to 192 bits. Solve the training rungs right here in your browser, then submit the claim — the contract verifies it and pays the bounty if you funded it. Armed rungs (128+) are the real quantum watch; nobody has broken one yet.
| # | Rung | Tier | Bounty | Status |
|---|
Click a rung to load it into the solver. Training rungs (16–112 bit) can be solved here; armed rungs open the verification panel instead.
The claim transaction passes your private key to the contract. It derives the public key on-chain and compares it against the rung. If it matches, the rung is marked broken and the bounty moves to you.
| When | Event | Who | Amount | Proof |
|---|---|---|---|---|
| Pick a rung to load its history. | ||||
How it works
Quanthood watches one thing: can a quantum computer break the keys that protect your money? Instead of guessing, we put a price on the answer and let the whole world try.
Every Bitcoin, every ETH account, every exchange wallet today is protected by elliptic-curve keys (ECDSA). A large quantum computer running Shor's algorithm can break those keys. Nobody knows when that day comes — so we measure it live.
We published 12 public keys that get harder to break step by step (16 bit up to 192 bit). Each one has a bounty locked on-chain. If anyone on Earth can break a key, they claim the bounty with one transaction — and the whole world sees it.
The moment a 128-bit or higher key falls, every Quanthood-protected contract on Robinhood Chain locks itself automatically. That is the early warning system: proven, not promised.
- Pick a rung on the canary ladder — start with the 16-bit one, it takes seconds.
- Solve it in your browser — the solver runs locally, no data leaves your machine.
- Claim the bounty — connect your wallet, send the claim, the contract verifies your proof.
- Get paid — the bounty moves to your wallet instantly. Your break appears on the Wall of breaks with the transaction link.
Bounties sit in the canary contract itself — nobody can take them except a solver with real proof. Funds are locked for 180 days, then refundable if nobody breaks the rung.
The 16-bit rung pays right now and takes about a second on any laptop. No account, no signup — just a browser and a wallet.
Wall of breaks
Every break proven on-chain: the solver address, the bounty paid and the exact transaction. No screenshots, no claims — each row links to a verified transaction on Robinhood Chain.
| When | Rung | Bits | Tier | Solver | Reward | Proof |
|---|---|---|---|---|---|---|
| Loading on-chain events… | ||||||
Live feed — this table updates automatically when a new break is verified. Armed-rung breaks also raise the global threat level.
Guard builder
Assemble a Quanthood-protected contract the way you would in the OpenZeppelin Wizard. Pick a type, a lock threshold and the functions to protect; the wizard writes the Solidity and a Foundry test.
Setup guide
- Copy the contract into a Foundry project (
forge init). - Run
forge build— it compiles against the QuanthoodOracle interface, which is inlined. - Deploy to Robinhood Chain (chain 4663) with the oracle address 0x95e294817114673D33B7ba6463EB245cA7cC8930.
- Move funds in. From then on, withdrawals lock automatically when the oracle level reaches the threshold you picked.
ABI & calldata
Function selectors and calldata for every contract in the suite. Copy them straight into cast, your scripts, or a hardware-wallet signer.
Contracts
Four contracts, live on Robinhood Chain (4663), verified on Blockscout. Ten Foundry tests cover claim flow, oracle levels, the Moment, Ark commits and guard locking.
Settings
Network endpoints for reads. Writes always go through your own wallet at your own confirmation.
This app stores your checklist progress and generated keys in this browser only (localStorage). No analytics, no tracking, no server-side storage. Clearing site data wipes everything — including any PQ key you have not saved yet.