The dev writes the promise. The agent keeps it.
Write your fee plan in plain English. At launch it's sealed with ML-DSA-65 and handed to an agent that runs your creator fees on a schedule and refuses anything outside it. Every buyback, burn and airdrop comes with a receipt anyone can verify.
From one sentence to an agent you can audit.
The agent only gets the coin's fee vault and the sealed policy. It can't edit the mandate, and neither can the dev.
Say it plainly
"40% of fees buy back daily, burn half." Claude compiles it into strict rules and shows you exactly what will be enforced.
Sign the mandate
The policy is hashed. You sign mandate:v1:<digest> as a memo inside the pump.fun create transaction.
Vault as creator
The coin's pump.fun creator is the agent's vault, so every creator fee lands where only the mandate can spend it.
Agent executes
Claims, buybacks, burns, airdrops and dev payouts on schedule. Each one is an ML-DSA-65 receipt chained to the last.
Meet OPERATOR. One agent per coin, bound to its mandate.
It holds one key, the coin's fee vault, checks every move against the sealed policy before signing, and writes a receipt for everything it does or refuses. Holders can question it on the coin page.
- Claim the coin's pump.fun creator fees
- Buy back inside the size and price-impact caps
- Burn, airdrop to top holders, pay the dev share
- Cut the dev share if the dev breaks the sell lock
- Answer holders, citing receipts
- Change or re-sign the mandate
- Move fees anywhere the mandate doesn't name
- Take orders from the dev or holders
- Sell the tokens it holds
- Act without sealing a receipt
Type your promise. See what the agent will hold you to.
Claude reads it and turns it into rules. The clauses are generated from those rules, so the text that gets sealed is exactly what the agent runs. Anything vague is flagged before launch.
Every coin, its mandate, and what its agent did.
Open a coin to see its sealed clauses, its full receipt chain, and to ask its agent anything.
| Coin | Mandate | Lock | Receipts | Bought back | Last action |
|---|---|---|---|---|---|
Loading coins… | |||||
Receipts that outlive the keys that made them.
Solana signs with Ed25519, which a large enough quantum computer can forge. A receipt only matters if nobody can fake one later, so MANDATE seals each one with ML-DSA-65, the lattice signature NIST standardized in FIPS 204. The receipts are hash-chained, so one can't be edited or dropped without breaking every receipt after it. Every agent transaction also pins the chain tip on Solana in a memo.
The verify page re-checks every digest, signature and chain link in your browser. Nothing has to be trusted.
When the dev asks the agent to break the mandate, the refusal is sealed into the chain and shown to holders.
If the dev wallet sells during its lock, the agent seals a penalty and the dev's fee share goes to buybacks for good.