FRIES / FRIES
fee dynamic, now 2%- Swap FRIES → FRIESnothing taken
- Swap FRIES → FRIESnothing taken
- Add, then remove liquiditycame back whole
pool 0x9919cefab3f645582e6871fe39de299ded086e72a9ce5c5b59a44c4220b6efa8
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
9 pools use this hook, the first one 42 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.
9 pools over 42 days.
Measured at block 93,086,664. 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 0x9919cefab3f645582e6871fe39de299ded086e72a9ce5c5b59a44c4220b6efa8
pool 0xa1b4799788722dcb73b564efe672ea78c0ff342f1c5361b74214a2262e93e655
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.