ETH / BORDR
fee 88%- Swap ETH → BORDRnothing taken
- Swap BORDR → ETHnothing taken
- Add, then remove liquiditycame back whole
pool 0xf192020b2c388f5077d591ae95bf258440ddf67685a1e46f8c1d50ccd65afeeb
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
28 pools use this hook, the first one 53 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.
The pool fee stands at 88%. That is on top of anything the hook takes.
Owned by 0xa6400e4511D956bFEE6b088381F2677fDd61d889. Owner-style functions: claimFees, setDrainThresholds, claimAllFees, setHookFee, claimable, transferOwnership.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
28 pools over 53 days.
Measured at block 92,983,029. 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 0xf192020b2c388f5077d591ae95bf258440ddf67685a1e46f8c1d50ccd65afeeb
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.