ETH / AMBW
fee dynamic, now 3%- Swap ETH → AMBWnothing taken
- Swap AMBW → ETHnothing taken
- Add, then remove liquiditycame back whole
pool 0x59f75435995fd209e462d3b2b9960ffcf4f301492d9d4a0c3bde73e8bf0e1683
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 18 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.
A swap through it pays the pool fee and nothing else.
Liquidity added and removed in the same block came back whole.
Its pools use a dynamic fee that the hook sets before every swap. It stands at 3% now and can change.
No owner() but it has claim, claimFor, claimable.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
3 pools over 17 days.
Measured at block 93,419,519. 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 0x59f75435995fd209e462d3b2b9960ffcf4f301492d9d4a0c3bde73e8bf0e1683
pool 0x13b0d8f5b7a7ef7861ff64dba98c35b61aaeafb7b19b780f188d27a8d6d138e1
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.