AVLO / WOLF
fee 1%- Swap AVLO → WOLFhook takes 1%
- Swap WOLF → AVLOhook takes 1%
- Add, then remove liquiditycame back whole
pool 0x2335a47ccba9aabc9a70b133d738cfcfb23d3c73bb7a4aae9686fa62cc9a7dbb
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 63 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 1% 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 0x85228f9817798E97c599ec4B2BEd0F1104b51273. Owner-style functions: setAutoProcess, transferOwnership, setRegistrar.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
6 pools over 63 days.
Measured at block 93,146,546. 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 0x2335a47ccba9aabc9a70b133d738cfcfb23d3c73bb7a4aae9686fa62cc9a7dbb
pool 0xb724b955b9fc1c927cf1493d37c9c968031c3c6b1e491e68019051d6fe3db113
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.