AXION·OSSYSTEM.INFO AXN-01
DRIVERS
- ARK.SYS · key commitment
- SIGNER.SYS · lattice signatures
- ORACLE.SYS · threat level feed
- CANARY.SYS · ECDLP bounty ladder
- GUARD.SYS · contract lock builder
- BOARD.SYS · solver rankings
LEGEND
⚠ NOTICE
AXION OS will never ask for your seed phrase or wallet private key. Post-quantum keys are born inside your browser tab; only a 32-byte hash ever leaves it.
Pixel-grade quantum early warning
An operating console that watches elliptic-curve crypto for signs of a quantum break, and hands you post-quantum tools before you need them.
TBA · launching soon
MAINNET.FEED …
RUNG.LADDER live
MEMORY 128 cells
BSGS.TRACE
INTEGRATE
import "axion/AxionGuard.sol";
contract Treasury is AxionGuard {
constructor(IAxionOracle o)
AxionGuard(o, 2) {}
function pay(address to)
external quantumSafe { … }
}
01 › Every transaction you sign publishes a public key.
02 › A big enough quantum computer can walk it back to the private key.
03 › Nobody will announce that day in advance.
04 › AXION OS listens for it, and flips your switches first.
Five stages from signal to safety
Real cryptographic bounties measure attacker capability. That measurement becomes one number. Everything else reacts to that number.
Bounty keys on fourteen curves, from toy 16-bit up to secp256k1. Anyone can submit a solution; the server checks k·G = Q itself.
Each broken armed rung (192-bit and up) lifts the threat level by one step, from 0 to 4. Training rungs never move it.
Contracts that inherit AxionGuard freeze chosen functions once the level crosses the threshold you picked.
Commit the hash of an ML-DSA-44 public key now. Later, that key proves you are the owner, even if ECDSA is broken.
Subscribe once and get pinged the moment the level moves. Dashboards and bots can poll the public JSON API.
The first time an armed rung falls. It is stamped with a timestamp and every module switches to defense mode.
Six programs, one OS
Each app does real cryptography locally and ends with something useful: a key file, a signature, a contract, or a ready-to-send transaction.
ARK.EXE
Forge an ML-DSA-44 keypair, download the recovery kit, and register its 32-byte commitment.
OPEN ▶ PROTECTSIGNER.EXE
Sign any message with a lattice-based key and verify signatures, fully offline-capable.
OPEN ▶ MONITORORACLE.EXE
Live threat level, what each step means, and an on-chain reader for deployed oracles.
OPEN ▶ MONITORCANARY.EXE
Browse every bounty curve and crack training rungs up to 40 bits with an in-browser BSGS solver.
OPEN ▶ BUILDGUARD.EXE
Generate a Solidity contract that inherits AxionGuard and locks only the functions you choose.
OPEN ▶ BUILDSOURCE.EXE
Read the reference Solidity: canary ladder, oracle, guard, ark and an example vault.
OPEN ▶Who boots AXION OS
One wallet or a whole protocol: everyone gets a concrete action they can take today.
Old wallets that already signed transactions have exposed keys. Commit a PQ key for them now.
Wrap payouts in AxionGuard so a cracked signer key can't empty the vault overnight.
Read the threat level like any price feed and pause risky paths automatically.
Benchmark discrete-log attacks on a public ladder and climb the leaderboard.
Tech stack
Small, auditable building blocks. No black boxes.
| Component | Role | Reference |
|---|---|---|
| ML-DSA-44 | Post-quantum signatures for Ark & Signer | NIST FIPS 204 |
| @noble/post-quantum | Audited-style pure JS implementation, loaded in the browser | GitHub |
| keccak256 | Key commitments and function selectors | ethereum.org |
| SEC 2 / NIST curves | Armed rungs: P-192, P-224, P-256, secp256k1 | SEC 2 v2 |
| Baby-step giant-step | Web Worker solver for training rungs ≤ 40 bit | Shanks, 1971 |
| Vercel Functions | JSON API: status, rungs, claims, ark registry, alerts | Vercel docs |
| Upstash Redis (optional) | Durable storage for claims and registrations | Upstash |
Roadmap
A level only unlocks after the previous one is cleared and verified.
Console, API, canary ladder, Ark & Signer live.
Contracts on Sepolia, wallet flows, funded training bounties.
External review of contracts and curve math.
Deploy on Ethereum L1 and seed armed bounties.
On-chain ML-DSA verification via account abstraction.
FAQ
Can AXION OS stop a quantum computer?
No software can. AXION OS detects the capability the moment someone proves it, and triggers the protections you prepared ahead of time: frozen functions, a recovery key and alerts.
What if an attacker never claims a bounty?
Then the canary stays quiet. That is exactly why Ark and Guard should be set up early instead of after an alarm.
Do my keys ever leave the browser?
No. ML-DSA keys are generated and used in your tab. The server only ever sees a 32-byte keccak256 commitment, and the recovery kit is downloaded straight to your device.
Why can some rungs be cracked in a browser?
Training rungs (16–40 bit) are deliberately tiny so you can see the full flow end to end. They earn leaderboard points but never move the threat level.
Who knows the private keys of the armed rungs?
Nobody. Their target points are derived by hashing a public phrase onto the curve, so no one, including us, ever had the matching scalar.
Is it live on mainnet?
The console and API are live. Contracts are reference implementations awaiting testnet and audit; the app already builds correct calldata for them.
Ready before the
AXION Moment
Commit a post-quantum key in under a minute. Nothing leaves your machine except a hash.