PONS / TEST 3
fee 1%- Swap PONS → TEST 3hook takes 1%
- Swap TEST 3 → PONShook takes 1%
- Add, then remove liquiditycame back whole
pool 0xbd7128ced13bc07acc6a92fb153b7e9c58e5da5e92fc9ee081c21e7e0cbc8f71
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
4 pools use this hook, the first one 42 d ago.
The address enables after swap returns delta. The hook is allowed to take; the next two checks measure whether it does.
It takes 2% of each swap on top of the pool fee.
Liquidity added and removed in the same block came back whole.
A fixed fee of 1%, written in the pool key.
Owned by 0x2D79A4626b9B7fE3104D6146Cf9c727719B907bE. Owner-style functions: setTwapWindow, setVault, transferOwnership, setLauncher.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
4 pools over 42 days.
Measured at block 93,295,358. 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 0xbd7128ced13bc07acc6a92fb153b7e9c58e5da5e92fc9ee081c21e7e0cbc8f71
pool 0x3670edea6f4c2ff13840657962510b09a01ec072bb7f685b925b8c4f0b086a45
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.