NECTB / H2O
fee dynamic, now 2%- Swap NECTB → H2Onothing taken
- Swap H2O → NECTBnothing taken
- Add, then remove liquiditycame back whole
pool 0x8877d0094e135ab3bdf8646765b8c34b5a51f569dcfcb1261ecc07feac721f44
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
578 pools use this hook, the first one 40 d ago.
None of the permissions that let a hook take from swaps or from LPs are switched on.
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. It stands at 2% now and can change.
No owner() but it has setPoolFee.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
578 pools over 39 days.
Measured at block 92,892,614. 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 0x8877d0094e135ab3bdf8646765b8c34b5a51f569dcfcb1261ecc07feac721f44
pool 0x5f8b7d22359d5d73a837b01916e5c37c0bdd110f007630741cb1b523ca1e221e
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.