Post-quantum ready from Block 0.
Kyberpad is two things. Readiness tools that show you, in bytes and milliseconds, what post-quantum cryptography costs on Solana. And a pump.fun launchpad where each coin's dev wallet is bound to an ML-DSA-65 key in the transaction that creates it.
Two keys that vouch for each other
Ed25519 signs the transaction, as it must today. ML-DSA-65 signs the same facts, so the record still means something after Ed25519 stops being enough.
- 011,952 B public key
Key
Your browser makes an ML-DSA-65 key pair. You download its 32-byte seed. It never leaves your machine and we can't recover it.
- 023,309 B signature
Cross-sign
The post-quantum key signs your wallet and the new mint. Your wallet signs that record's digest as a memo in the same transaction as the coin.
- 0381 B memo on chain
Launch
One pump.fun create_v2 transaction. After it confirms we read the mint back and record every authority slot. pump.fun leaves them all empty.
- 04ML-DSA-65 sealed
Receipt
Kyberpad seals receipt #1 of the coin's chain. Later dev notes, signed with the same post-quantum key, join it. Anyone can verify it in a browser.
Launch, scan, verify
Launch
Launch a coin with your wallet and a fresh ML-DSA-65 key bound together from the first transaction.
OpenScan
Paste any token address. See every authority key that is still live, and what its holder could do on Q-day.
OpenCoins
Every coin launched here, its key id, its receipt chain and the dev notes signed since.
OpenKnow the bytes before you need them
Primer
What Shor and Grover actually threaten, what the NIST replacements weigh, how Solana checks a signature, and how to plan the swap.
OpenLab
Ed25519, ML-DSA-44/65/87 and SLH-DSA signing side by side, X25519 beside ML-KEM-768, with real sizes and timings from your machine.
OpenReadiness check
Five areas from where you sign to who owns the plan. A score with its formula shown, next steps and a JSON export.
OpenWhat each signature costs
The smallest possible transfer, signed with each scheme, against the 1,232 B legacy cap and the 4,096 B v1 cap.
| Scheme | Family | Standard | Pubkey | Signature | Sig vs Ed25519 | Min transfer | Fits |
|---|---|---|---|---|---|---|---|
| Ed25519 | Classical | RFC 8032 | 32 B | 64 B | baseline | 183 B | legacy + v1 |
| ML-DSA-44 | Lattice | FIPS 204 (Dilithium) | 1,312 B | 2,420 B | 37.8× | 3,819 B | v1 only |
| ML-DSA-65binds off-chain here | Lattice | FIPS 204 (Dilithium) | 1,952 B | 3,309 B | 51.7× | 5,348 B | neither |
| ML-DSA-87 | Lattice | FIPS 204 (Dilithium) | 2,592 B | 4,627 B | 72.3× | 7,306 B | neither |
| SLH-DSA-SHA2-128f | Hash-based | FIPS 205 (SPHINCS+) | 32 B | 17,088 B | 267.0× | 17,207 B | neither |
| Falcon-512 | Lattice | FIPS 206 (draft) | 897 B | 666 B | 10.4× | 1,650 B | v1 only |
Sizes from FIPS 204, FIPS 205, the FIPS 206 draft and RFC 8032. Min transfer = a real 183-byte Ed25519 self-transfer with the signature and the full public key swapped in.
Already in play
Ciphertext captured today can be opened once key exchange breaks. Anything that must stay secret for years is exposed now.
Your address is your key
A Solana address is the Ed25519 public key itself. On Q-day, any authority still set on a mint is a key someone can recover from chain data.
3,819 bytes
3.1× the 1,232-byte legacy cap. v1 transactions allow 4,096, so it now fits, with little room left for anything else.
$KYBER
This panel is the only source of official Kyberpad addresses. Compare every character before you trust an address.
What Kyberpad is not. It is not a security certification, and a bound ML-DSA-65 key does not make a coin, a wallet or Solana itself quantum-resistant: transactions are still signed with Ed25519 today. The binding is a public, signed record of who the dev is that survives that changing. Coins launched here are ordinary pump.fun coins; nothing here is investment advice.