QAIROS
0xe0bc2162104f64d0b399dede94aa72d0001a3fd1
Training rungs (16–96 bit) can be solved on ordinary hardware. They never move the threat level.
An account that has sent a transaction has published its public key.
Qairos never asks for a seed phrase or private key. Post-quantum keys are generated in your browser and only their hash goes on-chain.
All armed rungs (128-bit and up) are intact. Public quantum capability stands at 15 bits.
Migrating exposed EOAs before 2029 is still recommended.
// If a quantum computer grows large enough
Every exposed public key
Can be turned back into its private key
Qairos sounds the alarm before that happens //
Qairos measures quantum capability with real cryptographic bounties, publishes it as one on-chain number, and lets every contract and holder react automatically.
Twelve elliptic-curve keys from 16 to 256 bits carry bounties. The contract verifies any claimed key by itself.
Each broken armed key (128 bits and up) raises threatLevel() by one, from 0 to 5.
Contracts that inherit QairosGuard lock sensitive functions when the level reaches their threshold.
Holders who registered a post-quantum key beforehand recover funds with proof no attacker can forge.
Prediction markets and insurance settle straight from the oracle. No votes, no disputes.
Every tool runs real cryptography in your browser and ends in a ready-to-send Ethereum L1 transaction.
Generate an ML-DSA-44 post-quantum key and commit its hash on-chain. It proves ownership after the Qairos Moment.
Open in app → ProtectLoad your recovery kit and build the two-step transactions that move vault funds to a fresh address.
Open in app → ProtectCreate and verify lattice-based signatures under NIST FIPS 204, entirely in the browser.
Open in app → MonitorRead QairosOracle on L1 and follow a clear response guide for every level from 0 to 5.
Open in app → MonitorInspect every bounty curve and solve training rungs up to 40 bits in your browser, then build the claim.
Open in app → BuildGenerate a Solidity contract that inherits QairosGuard and locks the functions you choose.
Open in app →From a single wallet to a protocol treasury, each group gets a concrete action today.
Register a post-quantum key for accounts whose public key is already exposed.
Wrap treasury withdrawals in QairosGuard so a stolen ECDSA key cannot drain them.
Read threatLevel() like a price feed and pause risky paths automatically.
Insure exposed balances and keep pre-Moment ownership proofs for every client account.
Claim bounties and publish verifiable progress against elliptic-curve keys.
Every primitive Qairos uses is a published standard or an open-source library you can inspect.
| Component | Used for | Reference |
|---|---|---|
| ML-DSA-44 | Post-quantum keys and signatures in Ark and PQ Signer | NIST FIPS 204 |
| SEC 2 curves | Armed canary rungs: secp128r1, secp160k1, secp192k1, secp224k1, secp256k1 | 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 |
| noble-post-quantum | Minimal, auditable JS implementation of ML-DSA | GitHub |
| Solidity 0.8.28 · Foundry | Seven contracts, 23 tests, deploy script | Foundry |
| Ethereum PQ roadmap | Why account-level signature agility matters | ethereum.org |
| 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.
Contracts, 23 passing tests, local deployment, working app.
Public deployment, funded training bounties, wallet connection.
Full review of contracts and curve math.
Deploy on L1, seed armed bounties, open markets.
On-chain ML-DSA or Falcon verification through account abstraction.
Short answers. The app has the full detail.
No. Qairos detects the capability as soon as someone proves it on-chain, then triggers the protections you set up in advance: locked contracts, a recovery path and insurance.
Then the canary stays silent. Qairos catches attackers who reveal capability for money. That is why the Ark and Guard should be set up early, not only when the alarm sounds.
No. Keys are generated and used inside 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 96 bits) to prove the mechanism end to end. They never move the threat level. Only armed rungs from 128 bits up do.
Not yet. The contracts are tested and the app already builds correct L1 transactions. Mainnet follows the testnet phase and an independent audit.
Register a post-quantum key in under a minute. Nothing leaves your browser except a hash.