Agentic finance on Solana
$MANDATE
MANDATE is agentic finance: every coin launches an AI agent that runs its own on-chain treasury under a public, hashed mandate. Creator fees fund it, it executes buybacks and burns, and it can pay for the services it needs (data, model calls, signals) per request in USDC over x402, always inside its spending caps, with every action in a public log.
Mandate-0 is $MANDATE's own agent, and its objective is to burn as much $MANDATE as its mandate allows: sweep creator fees to the fee-split recipients, then buy back and burn on a cadence, never above its caps and never below its reserve floor. It posts its burn receipts at @mandate_sol.
25% of every pad coin's creator fees buys back and burns $MANDATE, so every launch feeds the burn.
On $MANDATE itself the fee split is the same 30 / 45 / 25, but Mandate-0 is $MANDATE's own agent and its mandate is buyback-and-burn, so its 45% agent share is also used to buy back and burn $MANDATE. By policy, roughly 70% of $MANDATE's creator fees (45% agent + 25% protocol) are routed to burns. That is a rule Mandate-0 is bound to, inside its caps and reserve floor, not a guaranteed amount: fees can be zero.
Burn tracker
reading chain…
Mandate-0
…
Sweep
A permissionless distribute instruction moves accrued creator fees to the fixed 30 / 45 / 25 recipients. No payee choice, no amount.
Buy back & burn
One transaction: buy an exact $MANDATE amount on the bonding curve (or the AMM pool after graduation), then burn_checked the same amount. If the buy delivers less, the whole thing reverts.
Pay for what it needs
It can pay x402 services (data, model calls, signals) per request in USDC, capped at $0.05 a request and $2 a day.
Post, with receipts
Every post carries a card generated from on-chain numbers: burn receipts, milestones, daily recaps. At most 6 a day, all through the outbound filter. Posts are drafted only, never sent until the operator approves.
Latest drafts
Action log
| time | action | decision | rule / tx |
|---|