One terminal, seven instruments

Paste any address to learn if the key behind it can already be rebuilt from chain data, with one answer per network.

• Signed before? An account that has sent even one transaction has published its public key. The scan counts those transactions per network.
• What is at stake. What the address holds in native coin, and whether code lives there instead of a key.
• A sober verdict. A revealed key is tomorrow's problem rather than today's breach. The report says so and lists the sensible next steps.
• Check words. Four words computed from the address. An address forged to resemble yours fails the comparison before you send.

Create post-quantum key pairs, derive shared secrets and sign or check messages with the standardized schemes.

• The real algorithms. ML-KEM, ML-DSA and SLH-DSA as specified in FIPS 203, 204 and 205. Outputs are shown byte for byte.
• Measured on your device. Each operation reports how long your own browser needed, beside the byte count of what it produced.
• Gone when you leave. Keys live in the page's memory until you export them. Closing the tab erases them.

Encrypt a message or a file to a post-quantum key in the browser, and open what was sealed to yours.

• Hybrid by design. Each seal gets a new 32-byte secret from ML-KEM-768, stretched by HKDF into an AES-256-GCM key that both hides and authenticates the content.
• To an address. Seal to anyone who published an ML-KEM key in the Lattice Book, found by their wallet address.
• An open format. The byte layout is published in the docs, so other software with ML-KEM and AES-GCM can open your seals even if this site disappears.

Keep a list of addresses and see, every time you look, whether one of them has just revealed its key.

• First-signature alert. Watch remembers each address's transaction count and flags the moment a quiet address signs for the first time.
• Balances in one place. Native ETH on the three EVM networks, re-read while the page stays open.
• Stays on this device. The list is kept in your browser only. Nothing about it is sent to a Kibora server.

One table for all of them: purpose, underlying problem, byte sizes and speed on the machine you are using.

• Classical next to post-quantum. ECDSA, Ed25519, X25519 and RSA beside ML-KEM, ML-DSA and SLH-DSA, with sizes in bytes.
• A live benchmark. One button runs every algorithm on your device and fills in the timings column.

The three NIST standards and the migration guidance in plain words, each linked to its primary source.

• What each standard fixes. Parameter sets, security categories and intended use for FIPS 203, 204 and 205.
• Dates that matter. When the standards were published and what NIST's draft transition plan says about 2030 and 2035.

Shared, on-chain pieces: a public book of post-quantum keys and Ward, a safe that makes every withdrawal wait.

• Lattice Book. Publish your ML-KEM or ML-DSA public key against your address, so others can seal to you or check your signatures.
• Ward. A personal safe on Robinhood Chain. Outgoing transfers sit in a queue for a period you set, and a second wallet of your choice can stop them or sweep everything to your haven.
• Check words. The four-word fingerprint of any address, to read aloud or compare across devices.