Tokenomics on autopilot
Buyback, burn, compound and revenue share as properties of trading — no team required to run them.
Every mechanism in this book — the pot, pump, shield, the burn cascade, the fee split, the compound engine — shares one design constraint: none of it needs a human to run. Put together, they turn a Uniswap pool into something new: an LP whose tokenomics are a property of its own trading, not an activity someone performs on its behalf. This chapter is about that independence — what it replaces, how far it goes, and why it survives the team that launched it.
Tokenomics as an activity vs tokenomics as a property
Almost every tokenomic promise in the market today is an activity: someone at the project signs the buyback, someone funds the bot, someone remembers to compound the LP, someone runs the keeper that harvests the fees. Activities depend on people — on their keys, their attention, their funding, and their continued existence. The moment the person stops, the tokenomics stop, and holders usually find out from the chart.
A hooked pool inverts this. The buyback fires inside the buy that would have benefited from it. The harvest fires inside the swap that generated the fees. The compound re-mints those fees into the pool's own position in the same breath. The burn happens on delivery, through a cascade that cannot fail a trade. Nothing on that list has an operator — the operator is the traffic.
| job | who does it, classically | who does it here |
|---|---|---|
| buy the token back | treasury signer, market-maker mandate, buyback bot | the pot, inside the buy — Pump |
| defend a sell-off | market maker on a retainer, team bids | the pot, inside the sell — Shield |
| burn supply | manual burns, announced and trusted | the cascade, on every delivery — Burn & delivery |
| collect LP fees | a keeper network or a weekly multisig call | the in-swap auto-harvest — Auto-harvest |
| compound the position | a vault protocol charging a performance fee | the compound engine, natively — Autocompound |
| route revenue share | spreadsheet + payout script | the recipient legs, to the wei — The recipients |
The loop, closed
The reason the machine needs nobody is that its output is its own input. Follow one unit of volume around the circle:
Every arrow in that loop is enforced code. There is no step where a human signs, funds, schedules, or approves — and therefore no step where a human can be late, wrong, out of gas, or gone.
How far the independence goes
The two human roles — pot admin and program operator — exist to set policy, not to run the machine. Both can be transferred, and both can be surrendered forever. A program whose operator is address(0) is an immutable promise: the split, the recipients, the burn share — frozen. The pool keeps buying, burning and compounding on the same terms whether the team is shipping, sleeping, or dissolved.
Nothing here waits for an external actor to find it profitable. A keeperless harvest costs the triggering swap a bounded slice of gas; the buyback executes at the pool's own curve rather than needing an arbitrageur to close a gap; the compound mints at the live price with the carry absorbing what doesn't fit. No bounty is paid, no spread is leaked, no third party takes a cut for keeping the lights on.
This is the deepest version of the promise: a team can launch a pool, set the program, seed the pot, surrender both roles — and walk away leaving a market that defends itself, burns its own supply and compounds its own liquidity for as long as anyone trades it. Holders stop trusting a roadmap and start reading a contract.
What still touches the machine — and why that's fine
Autonomy doesn't mean sealed. Anyone can fuel the pot with a donation; anyone can trigger the public quote-and-donate integration paths; a live operator can still tune the split; a heavy pool can be harvested manually with full gas. But notice the shape of every one of these: they are inputs and policy, never dependencies. The machine accepts help; it does not require it. Withdraw all of it and the loop above still turns.
The two engines, taken apart
FAQ
Does the pool literally run with zero human involvement?+
Once launched, yes — every engine (harvest, compound, buyback, burn, payouts) is triggered by swaps themselves. Humans only exist at the policy layer: setting the split, fueling the pot, optionally running a manual harvest. All of those are inputs, not dependencies.
What happens to the machine if the team abandons the project?+
Nothing. The trigger is trading, not the team: as long as anyone swaps, fees harvest, the position compounds, the pot pumps and shields, and supply burns. If the roles were surrendered, even the policy is frozen and runs unchanged forever.
Is this the same as renouncing a token contract?+
Stronger. Renouncing usually just removes a mint key. Surrendering the hook's roles freezes an active machine — a buyback, burn and compounding program that keeps executing on immutable terms, not just a promise to do nothing bad.
If no keeper is paid, who pays the gas for all this?+
The triggering swap carries a bounded slice of gas for the auto-harvest, controlled by the minimums the operator sets — so it only fires when the harvest is worth far more than the overhead. Pumps and shields ride the swaps that trigger them. Heavy work can always go through the optional manual path with the caller's own gas.
Can autonomy ever hurt a trader?+
No — that's the design's hard line. Every autonomous action is wrapped in fault tolerance: if anything about the hook's state or settings would fail, the action is skipped and the swap completes exactly as a vanilla pool. Sellers always receive the pool's exact output.