Roadmap (design)
On-chain architecture
What runs where today, Token-2022 transfer hooks, and the gap to on-chain mechanics.
What runs today, and where#
| Piece | Runs on |
|---|---|
| The curve, graduation, the pool, trading fees | pump.fun's programs on Solana |
| Creator fees | pump.fun pays them to the vault |
| Mechanics | The vault's fee rounds: a scheduled job that signs ordinary transactions |
| Terms, sites, the holder gate, the desk | EVERYNTH's own server and database |
That is an honest division: nothing on chain enforces the mechanics; the vault's published rounds do, and anyone can check them against the chain. Moving enforcement on chain is the next step, and it is harder than it looks.
The foundation for on-chain hooks#
Solana's Token-2022 program has a transfer hook extension: a mint can name a program that must run on every transfer. If the hook fails, the transfer fails. That is the whole security model in one sentence, and it cuts both ways.
The gap#
| Needed for | Uniswap v4 hook | Token-2022 transfer hook |
|---|---|---|
| Knowing a transfer is a buy or a sell | Given by the callback | Not given — a transfer is a transfer |
| Reacting to liquidity changes | Given | Not visible |
| Reading the price of the swap | Given | Not available in the hook |
| Allow and deny lists, caps, cooldowns | Possible | Possible, and natural |
Half the catalogue — transfer rules, access rules, caps, cooldowns, burns on transfer — maps onto Token-2022 directly. The other half needs a router that knows a swap from a transfer, and a runtime that meters hooks and isolates failures. Reward hooks must never run inline: a payout failing must not stop someone moving their own coins.
Next