Quantum breaks today's locks.
Try tomorrow's.
A large quantum computer will open the public-key cryptography behind today's data, logins and wallets. Halite builds the replacement on NIST's lattice standards, and you can test it here, in your browser.
- StandardsFIPS 203 · 204 · 205
- Tools6, no account
- Your keysnever leave this tab
Shor's algorithm breaks the math under RSA and elliptic curves.
Secure connections, software updates, certificates and crypto wallets rely on two problems: factoring large numbers and computing discrete logarithms. A large, error-corrected quantum computer solves both efficiently. Symmetric ciphers and hashes survive, but lose about half their strength to Grover's algorithm.
Classical strength from NIST SP 800-57 Part 1. Grover figures are the theoretical upper bound; in practice the attack parallelises poorly.
Traffic recorded today can be opened later.
An attacker does not need a quantum computer yet. They only need to store your encrypted traffic until one exists. If the years your data must stay secret (x) plus the years your migration takes (y) exceed the years until a quantum attacker arrives (z), that data is already exposed.
These are your own assumptions. Nobody can give z with confidence; the roadmap below shows what is known.
What a quantum attacker can reach.
Halite's work is organised around the three things public-key cryptography protects. Open a drawer to see what breaks and what Halite does about it.
-
- Relies on
- RSA or elliptic-curve key exchange (ECDH) to agree on the symmetric key.
- What breaks
- Recover the key exchange and every recorded session opens. This is the harvest-now risk above.
- Halite's answer
- Hybrid key encapsulation (ML-KEM-768 + X25519) feeding AES-256-GCM. Try it in the Vault.
-
- Relies on
- RSA, ECDSA and Ed25519 signatures in TLS certificates, code signing, passkeys and documents.
- What breaks
- Derive a private key from its public key and you can sign as that person, server or vendor.
- Halite's answer
- ML-DSA signatures (FIPS 204). Sign and tamper with a message in Signatures, or check a certificate in the Scanner.
-
- Relies on
- ECDSA (secp256k1), Schnorr and Ed25519 signatures that prove who may move funds.
- What breaks
- A Solana address is its own public key, and many other chains reveal the key on the first spend. From then on, Shor's algorithm could recover the key that controls the funds.
- Halite's answer
- See what any Solana address holds with the wallet check. Tooling to move holdings to post-quantum signatures follows as chains adopt them: see the roadmap.
Hybrid by default. An attacker has to break both.
ML-KEM is young. X25519 is well studied but falls to a quantum computer. Halite combines them, the same way Chrome, Signal and OpenSSH now do, so a flaw in either one alone does not expose your key. Select a step to see what it does.
Six working tools on one bench.
No account, no install. Keys exist only in your browser tab and disappear when you close it. Pick a tool to jump straight in.
Open the Lab- L·01VaultSeal text or files to a hybrid post-quantum key.X-Wing · AES-256-GCM
- L·02SignaturesSign, tamper, and watch verification fail.ML-DSA-65
- L·03HandshakeStep through a key exchange with an eavesdropper.ML-KEM-768
- L·04ScannerCheck a certificate or key for quantum risk.X.509 · SSH · JWK
- L·05ExposureSee what a Solana address holds, and why it is exposed.Ed25519 · Solana
- L·06BenchmarkTime the algorithms on your own device.ML-KEM · ML-DSA · SLH-DSA
The quantum clock, and what Halite does at each mark.
Read it like a core sample: published research, standards and deadlines above the line, each with its source; Halite's plan below it. Plans are targets and can change.
One coin. One official address.
$HALITE is the project's coin. The Lab is free and works without it: no tool asks for a wallet signature or a payment.
Tokens can go to zero. Nothing on this site is financial advice. Copycat coins appear around every launch: trust only the address shown in this box.
What people ask before they trust a new lock.
Start with one file.
Seal something you care about with a hybrid post-quantum key, keep the key file, and open it again. It takes under a minute.