AMD / A
fee dynamic, now 0%- Swap AMD → Ano liquidity at the current price
- Swap A → AMDno liquidity at the current price
- Add, then remove liquiditycame back whole
pool 0xf7ea6cd0c83d94530efb647cfa177249f5750485907182b6c43e7a6f093b1876
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 85 d ago.
None of the permissions that let a hook take from swaps or from LPs are switched on.
No pool with liquidity to swap through yet.
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 0% now and can change.
No owner() but it has setLaunchManager.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
3 pools over 84 days.
Measured at block 93,364,587. 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 0xf7ea6cd0c83d94530efb647cfa177249f5750485907182b6c43e7a6f093b1876
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.