How it works

Creator authority, handed to a contract.

01

The creator is a program, not a person

When VOTE mints a token on pump.fun, it sets the creator field to a program-derived address (a PDA). The creator field is just a pubkey set at mint - and pump.fun's own takeover instruction is admin-gated, so it can never be reassigned to a human afterwards. The fee owner is the code.

02

Fees land in a per-token sub-treasury

Creator fees accrue to a vault keyed by that PDA - pre-graduation in SOL, post-graduation in WSOL on PumpSwap. A permissionless crank claims them into the token's isolated treasury. No shared pot; each token's holders govern only their own fees.

03

Holders vote, weighted by a snapshot

At the start of an epoch, holder balances are snapshotted at a fixed slot and committed on-chain as a merkle root. Because the snapshot precedes the voting window, flash-loaned balances can't vote. You vote with a merkle proof; weight equals balance.

04

The winning mode executes on-chain

After quorum, the crank executes the chosen mode through PumpSwap - TWAP-sliced buybacks with a hard slippage cap, then liquidity, a community airdrop, or an airdrop to $ANSEM holders. Every action emits an on-chain event you can verify.

05

Nothing leaks to the deployer

There is simply no instruction that lets any human move fees out of a treasury. The only outflows are the voted execution paths. Rent on bookkeeping accounts is always recoverable; the program itself is closeable. The guarantee is structural, not a promise.