NVDA / AI
fee 0%- Swap NVDA → AIhook takes 1.00%
- Swap AI → NVDAno liquidity above the price
- Add, then remove liquiditycame back whole
pool 0xf2c1065844904275a1294fd2c161f3ceae11271060fc460e2408dc4eaaba9087
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 81 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.
It takes 1.00% on top of the pool fee.
Liquidity added and removed in the same block came back whole.
A fixed fee of 0%, written in the pool key.
Owned by 0x0CD3795c56a4cd245001bbC8F66Abd436C083ce1. Owner-style functions: transferOwnership, setFeeAllowed, setTokenFee, setFactory, setRenouncedFee.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
3 pools over 80 days.
Measured at block 93,418,925. 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 0xf2c1065844904275a1294fd2c161f3ceae11271060fc460e2408dc4eaaba9087
pool 0x5e6e91f39c1d55eb7e09845e9867b9385788562daed00cba4da0ddfee5f1cc4e
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.