0x5a287eB723171869889169C2e0Fcadb406B6D9B1
Training rungs (16–112 bit) are solvable on a laptop. Breaking one never moves the threat level.
The canary keys are generated from a public formula. Nobody — including us — holds their private keys.
Quanthood never asks for a seed phrase or a private key. Post-quantum keys are generated in your browser, and only their hash ever goes on-chain.
All armed rungs (128-bit and up) are intact. Public quantum capability stands at 15 bits.
Migrating exposed accounts before 2029 is still the smart move.
// When a quantum computer gets big enough
Every public key that has been exposed
Can be walked back to its private key
Quanthood sounds the alarm before that day arrives //
Quanthood measures real quantum capability with cryptographic bounties anyone can fund, compresses the result into one on-chain number, and lets every contract and holder react to it automatically.
Twelve elliptic-curve keys from 16 to 192 bits sit on-chain with bounties attached. The contract checks any claimed key itself — no committee, no trust needed.
Every armed key that gets broken (128 bits and up) pushes threatLevel() up by one, from 0 to 5. It never comes back down.
Any contract that inherits QuanthoodGuard can lock its sensitive functions the moment the level hits the threshold it chose.
Accounts that registered a post-quantum key before the Moment keep a recovery path no quantum attacker can forge.
Bounties sit in public escrow on the canary contract itself. Anyone can fund a rung; the contract pays the solver directly.
Every tool runs real cryptography in your browser and ends in a ready-to-send Robinhood Chain transaction. The contracts are live today.
Read QuanthoodOracle on-chain and follow a clear response guide for every level from 0 to 5.
Open in app → MonitorInspect every rung and its bounty. Training rungs up to 40 bits can be solved in your browser, then claimed.
Open in app → ProtectGenerate an ML-DSA-44 post-quantum key and commit its hash on-chain before the Moment. It proves ownership afterwards.
Open in app → BuildGenerate a Solidity contract that inherits QuanthoodGuard and locks the functions you choose, at the level you choose.
Open in app → FundPut real money behind a rung. The contract holds it, verifies the break, and pays the solver — no middleman.
Open in app → ProtectA self-rescuing vault: when the threat level trips your threshold, your ETH sweeps itself to your pre-registered recovery address.
Open in app → PredictBet on Quanthood's own outcomes — threat levels and canary breaks, settled trustlessly from on-chain data.
Open in app → InsureParametric cover against the first armed break. If a quantum computer proves itself in your term, you get paid — automatically.
Open in app → VerifyEvery contract is verified on Blockscout. Read the source, check the state, don't take our word for any of it.
Open explorer →From a single wallet to a protocol treasury, each group gets something concrete to do today.
Register a post-quantum key for accounts whose public key is already exposed. It takes a minute.
Wrap treasury withdrawals in QuanthoodGuard so a stolen ECDSA key cannot drain them after the Moment.
Read threatLevel() like a price feed and pause risky paths automatically when the level rises.
Keep pre-Moment ownership proofs for every client account, ready before they are needed.
Break training rungs on ordinary hardware, claim bounties, and publish verifiable progress against armed ones.
Every primitive Quanthood uses is a published standard or an open-source library you can inspect yourself.
| Component | Used for | Reference |
|---|---|---|
| ML-DSA-44 | Post-quantum keys and signatures in Ark and PQ Signer | NIST FIPS 204 |
| secp256k1 | The canary ladder and every exposed account key | SECG SEC 2 v2 |
| keccak256 | Commitments, function selectors, event topics | Ethereum docs |
| Baby-step giant-step | In-browser solver for training rungs up to 40 bits | Shanks, 1971 |
| NUMS derivation | Canary keys from SHA256 — nobody holds the private keys | On-chain proof |
| Solidity 0.8.36 · Foundry | Four contracts, 10 tests, verified deploy | Foundry |
| Quantum ECC record | 15-bit key broken on public quantum hardware, April 2026 | Project Eleven |
Each phase ships only when the previous one is verified on-chain.
Canary, Oracle and Ark deployed and verified on Robinhood Chain. 10/10 tests pass.
Browser tools: canary solver, Ark registration, guard builder — connected to the live contracts.
Public escrow funded on the armed rungs. Anyone can add to the pot.
Robinhood Chain protocols wire their critical functions to the oracle.
On-chain ML-DSA verification through account abstraction.
Short answers. The contracts hold the full detail.
No. Nothing can. What it does is detect the capability the moment someone proves it on-chain, and trigger the protections you set up in advance: locked contracts, a recovery path, funded bounties. Preparation, not prevention.
Then the canary stays silent — that is its honest limit. It catches attackers who reveal capability for money. Which is exactly why Ark and Guard should be set up early, not after the alarm sounds.
No. Post-quantum keys are generated and used entirely in your browser. Only a 32-byte hash goes on-chain. The recovery kit is saved only when you choose to download it.
They are small on purpose — 16 to 112 bits — to prove the mechanism end to end. Breaking them never moves the threat level. Only armed rungs from 128 bits up do, and those need hardware nobody has yet.
No. Each key is derived from a public formula: SHA256 of a fixed string, mapped onto the curve. Anyone can recompute the keys from that formula. Nobody — including the Quanthood team — can know the matching private keys.
Register a post-quantum key in under a minute. Nothing leaves your browser except a hash.