SUSD / NVDA
fee 0%- Swap SUSD → NVDAhook adds 0.01%
- Swap NVDA → SUSDhook takes 99%
- Add, then remove liquiditycame back whole
pool 0x148740517b90172ad528d6778e5495b320e9e8bc6ae24d83022a3dbcd6f1ebb1
Reading the hook.
The address, the bytecode, then a swap each way through its pool. A few seconds.
12 pools use this hook, the first one 3 d ago.
The address enables before swap returns delta. The hook is allowed to take; the next two checks measure whether it does.
It took 99.00% of a swap 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 0xa307B4C7AD1eb1CC8656Ba15Ab7C07C3Fe88fEFf. Owner-style functions: setOwner, setAllowlistBatch, setOperator, setAllowlist.
Not a proxy, no DELEGATECALL, no SELFDESTRUCT.
Each callback refused a call that did not come from the PoolManager.
12 pools, first seen 3 days ago.
Measured at block 93,032,305. 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 0x148740517b90172ad528d6778e5495b320e9e8bc6ae24d83022a3dbcd6f1ebb1
pool 0x740c49deb1207ee2de56dcce2f2407f56d54c414f3c078a968ef2a96d35e5dc0
Selectors found in the dispatcher, named from the public signature database. Red ones are what an owner usually keeps for itself.