Post-quantum launchpad · pump.fun
Seal the
promise.
Watch the
dev.
Launch on pump.fun with a covenant: a share of creator fees bought back and burned, and a dev sell lock. KEPT seals it with ML-DSA-65, binds it to the create transaction, then seals every move the creator wallet makes after. Break it and the chain shows it.
Published at /api/seal
Per receipt, per tree head
NIST level 3, lattice-based
…
Leaves in the Merkle log
no anchor yet
Two promises, written down before the coin exists.
You pick the terms when you launch. They are sealed into the launch receipt, and their digest rides in a memo inside the pump.fun create transaction your wallet signs, so the promise and the launch are the same transaction.
A share of every fee claim buys the coin back.
Pick 0-100% in 5% steps. Each time the creator claims pump.fun creator fees, that share of the claim is owed as buyback, due within 24, 48 or 72 hours.
Everything bought back gets burned.
With a buyback covenant, tokens the creator wallet buys after launch count as buyback and must be burned by the deadline. Selling them back is not a buyback.
The dev wallet can't sell or move tokens.
Pick 0-90 days. Any sale or transfer of the coin out of the creator wallet inside the lock is sealed as a breach within minutes of landing.
Every coin. Every promise. One verdict.
The watcher reads each creator wallet every couple of minutes. Fee claims, buybacks, burns, sales and transfers each become a receipt in that coin's chain, and the verdict follows from the rules.
| Coin | Covenant | Ledger | Receipts | Verdict |
|---|
Seal a covenant. Then try to fake it.
This sandbox makes an ML-DSA-65 key in your tab and seals as you move the sliders. Change one byte of the received copy and every check fails. Real receipts are sealed the same way by the KEPT key.
- Keygen
- …
- Sign
- …
- Verify
- …
Making an ML-DSA-65 key…
- Key id
- …
- Body sha256
- …
- Signature
- …
- ABody matches digest—SHA-256 of the body, recomputed
- BML-DSA-65 signature—FIPS 204, context kept/sandbox/v1
- CIn a Merkle log—Leaf 8 of a local 8-leaf RFC 9162 tree
Append-only. Signed. Anchored.
All receipts from all coins go into one Merkle tree, hashed as in Certificate Transparency (RFC 9162). Heads are sealed and anchored on Solana, so nothing can be dropped or reordered quietly.
- 0x0Append
Every receipt digest becomes the next leaf. Leaves are never edited or removed.
- 0x1Sign the head
Root and size sealed with ML-DSA-65. No head yet.
- 0x2Anchor
New heads go into a Solana memo from the anchor wallet, so a rewritten log stops matching the chain. Not anchored yet.
- 0x3Monitor
Anyone can pull every leaf and consistency proofs between heads, and check each head extends the last one.
Paste any receipt into the verifier. It checks the digest and the ML-DSA-65 seal in your browser, proves the receipt is in a signed tree head, and reads the anchor memo off Solana.