ETH / FWS
fee 0.30%- Swap ETH → FWShook takes 2%
- Swap FWS → ETHhook takes 2%
- Add, then remove liquiditycame back whole
pool 0x1b5a8261dd08653339174452b7fd14ab0f0a3553f9fbe6cdfce3083b0b288674
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
6 pools use this hook, the first one 71 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 0.30%, written in the pool key.
No owner() but it has claim, setPoolConfig, setInitializer, setCreator, BURN_ADDRESS.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
6 pools over 71 days.
Measured at block 93,145,465. 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 0x1b5a8261dd08653339174452b7fd14ab0f0a3553f9fbe6cdfce3083b0b288674
pool 0xf9935a0b38b9b1556c11f50cd4e58d48a3a95b2fb4b22c126cacd1f4471a1cf7
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.