THEORY
FEES ARE FUEL.
The analogy, and its limits
A combustion reaction needs three things: a fuel, something to sustain the reaction, and a path for the products to leave. The protocol is described here with those words because the shape of the process matches — an input that arrives from outside, a component that enables the transformation without being consumed by it, and a product that leaves the system permanently.
The analogy stops at the word “chemistry”. Nothing here is a chemical reaction, no element is real, and the periodic-table notation on the board is a way of labelling parts of a contract system, not a claim about matter. Chemistry is the metaphor. The contract is the mechanism.
Why fees are the natural input
A liquidity pool produces fees only when it is used. That makes fee flow an honest signal: it cannot be manufactured by announcement, and it scales with genuine activity rather than with intent. A mechanism fed by fees is therefore a mechanism whose intensity is set by the market rather than by a schedule.
F(t), the captured fee flow up to time t, is the only input this system consumes. Every other quantity on the board is downstream of it.
Why the hook is the catalyst
In Uniswap v3, a pool's behaviour was fixed at deployment. In Uniswap v4, all pools live inside one contract — the PoolManager — and a pool key may name a hook: an external contract the PoolManager calls at defined moments around initialization, liquidity changes, swaps and donations.
That is what makes the comparison to a catalyst exact enough to be useful. The hook sits in the path of the reaction and determines what happens there, but it is not the fuel and it is not the product. It is the component that decides what the reaction does.
A hook's permissions are not a promise. Uniswap v4 encodes them in the low fourteen bits of the hook's own address, and the PoolManager enforces exactly those bits. A hook whose address does not carry the beforeSwap flag will never have beforeSwap called, whatever its source code says.
Why the burn is the product
Supply reduction is the one outcome in this system that cannot be undone. A fee can be redirected, a buyback can be repriced, a parameter can be changed — but a token removed from circulation is removed. That asymmetry is why the burn, not the buyback, is treated as the reaction's product.
The supply model is written on the board as S(t+1) = S(t) − B(t): supply at the next step is supply now, less whatever was burned. It is a description, not a prediction. B(t) depends on F(t), which depends on how much the pool is used.
What this board will not do
It will not show a number it did not read. Fee percentages, burn totals, supply figures, callbacks and addresses are read from the configured chain, the deployed contracts and the indexer. Where a value is unavailable the board says DATA UNAVAILABLE, and where a deployment has not configured something it says NOT CONFIGURED.