ETH / PONS FORUM
fee 0%- Swap ETH → PONS FORUMnothing taken
- Swap PONS FORUM → ETHhook takes 99%
- Add, then remove liquiditycame back whole
pool 0x8c1bf2250e2a1890923da2ab1017c3175b1b6750844657f964e3832b0a0e7af8
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
3 pools use this hook, the first one 46 d ago.
The address enables before swap returns delta, after swap returns delta. The hook is allowed to take; the next two checks measure whether it does.
It took 99% of a swap on top of the pool fee.
Liquidity added and removed in the same block came back whole.
A fixed fee of 0%, written in the pool key.
Owned by 0x24e052DCd41c60B488FeACb1b3c9E171a8747D74. Owner-style functions: setFactory, setTaxRecipient, transferOwnership.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
3 pools over 46 days.
Measured at block 93,361,072. A hook with an owner or a dynamic fee can behave differently later; scan again before a large trade.
A v4 hook's permissions are the last fourteen bits of its address. The PoolManager calls only what they switch on.
A small swap each way and a liquidity round trip, run through the PoolManager and this hook inside a call that is never sent. The pool fee is expected; anything else missing is the hook.
pool 0x8c1bf2250e2a1890923da2ab1017c3175b1b6750844657f964e3832b0a0e7af8
pool 0x6c4b10093642db618ad705c821f0a9b71587ba7fd967e43acd6c898d64eb5385
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.