← LiquidityWise
Ethereum mainnetWhat this pool is, read from its own key. A v4 pool is not a contract of its own: it lives inside one PoolManager and is named by a hash of the five things that define it — the two currencies, the fee, the price step, and the hook.
Read from the pool's own key on the chain. The protocol takes nothing on top, so this is what a swap pays.
Taken by the protocol on top of the pool's fee, on every swap. Set by governance, and read from the pool's state on the chain.
The finest step at which a position's edges can be placed in this pool — its tick spacing of 200. Part of the pool's key in v4, so unlike v3 it needs no separate contract call.
The zero address here is not a missing field. v4 lets a pool hold the chain's own ether rather than a wrapped token, and that is what this is.
0xbac4827c28ab5871a830671df53bd94589d3c0cc
This hook is permitted to change what a swap costs or pays. Any figure drawn from price history — a suggested range, a fee tier, a comparison against simply holding — assumes the pool charges what it says and pays what the curve says. Neither assumption is safe here, and none of it is visible in a price series.
These are read out of the hook's own address. v4 stores a hook's permissions nowhere: a hook is deployed to an address whose last fourteen bits spell out which callbacks the PoolManager will invoke, and the PoolManager checks those bits rather than asking the contract. So this says what the hook may do, never what it does — one permitted to rewrite the fee on every swap may always return the same fee, and that is not knowable from here.
Below is the range analysis. The range comes from prices that already happened, so it holds here exactly as it does for a pool with no hook — a hook cannot retroactively change where price went. What a hook can change is what a swap costs, so the rate this pool charged is measured from what it collected rather than taken from the fee above.
This stopped while reading the pool's daily price history.
This pool does not have enough completed daily price history to analyse yet.
0xdd14a7c2bd78ccf9bf0e2b195037b199f0550c687d5dd6c8125f45412a7eb8b7 · insufficient-data