← 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 1. Part of the pool's key in v4, so unlike v3 it needs no separate contract call.
0x4440854b2d02c57a0dc5c58b7a884562d875c0c4
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.
Uniswap v4 · Ethereum mainnet · 0.0001% fee on every swap
0x3b1bd35a555160a9b60c7524db56029c2025ab93b69d97d33ca3f1c23b6494ad
Where a position in this pool would be active, as the price of one USDC in USDT.
0.9991 – 1.0014 USDT per USDC
0.11% below and 0.12% above the current price.
Current price 1 USDC = 1.00024 USDT
The current price is inside this range. A position opened here would be active straight away.
Between these two prices a position earns its share of the pool's swap fees. Outside them it holds a single token and earns nothing until the price comes back.
If the price falls below the range, the position ends up holding only USDC; if it rises above it, only USDT.
From how much the price of USDC actually moved over the last 30 completed days — not from a forecast of where it goes next.
The standard deviation of one day's price change, over the window.
The same movement stretched over the horizon chosen below: one standard deviation, either way.
Chosen below. A wider range is left less often, and the same deposit spread over it is thinner at any one price.
29 daily changes went into it.
The range is centred on today's price and drawn the same distance up and down in ratio terms — halving and doubling are the same move — which is why the two percentages differ. It describes how far the price has moved, not where it will go: it is not a forecast, and the width is not a confidence level. Nothing here sizes a position or says how much of either token to deposit.
The same method at each width the form offers, so the trade-off can be seen rather than told: a wider range holds more of the days, and spreads the same deposit over more prices — which is the last column, and it is the arithmetic of the protocol rather than an estimate.
| Width | Range | Inside, of the last 30 days | Inside, on days it never saw | Fee share while inside |
|---|---|---|---|---|
| Tight (1σ) · shown above | 0.9991 – 1.0014 USDT | 30 of 30 | 26 of 29 | 1× |
| Medium (1.5σ) | 0.998601 – 1.0019 USDT | 30 of 30 | 29 of 29 | 0.7× |
| Wide (2σ) | 0.998002 – 1.0024 USDT | 30 of 30 | 29 of 29 | 0.52× |
| Very wide (3σ) | 0.997005 – 1.00351 USDT | 30 of 30 | 29 of 29 | 0.35× |
The first count is over the days each range was drawn from, so it says how that width was fitted, not how it held. The second is the check above, run for each width: the method stepped back a horizon and laid over the days that followed.
The last column is what the same deposit would take of the fees charged on a day the price stays inside that range, against the width shown above — so that one reads as one. It is the protocol's own position arithmetic rather than an estimate: a narrower range turns the same money into more liquidity over fewer prices. It assumes the rest of the pool's liquidity is unchanged, which a deposit large enough to move it would not leave true, and it says nothing about the days price spends outside.
The whole pool's, shared among everyone whose liquidity was active.
This pool's hook is permitted to take a share of a swap, and nothing in the source separates the hook's share from the liquidity providers'. The fees above are what the pool charged, which is a fact; tying a portion of them to this range would be a claim about a position nobody can check.
Of the last 30 days, 30 stayed entirely inside this range, 0 sat entirely outside it, and 0 crossed an edge.
These are the same days the range was drawn from, so they show how it was fitted rather than testing how it holds up — and the range is centred on today's price, which nobody could have opened a month ago. Read them as how the pool's recent movement sits against the range, not as a backtest.
None of this is what a position would earn: it is what the whole pool charged. What a deposit would have taken of it — its share of the liquidity active while the swaps happened — is the panel directly below, and even that is fees and nothing else.
Not shown for this pool
For the same reason as the figure above it: a hook here may take a share of the swap, and nothing in the source separates its share from the providers'. A fraction of a total that cannot be attributed to this range cannot be attributed to a deposit in it either.
These agree on every measured day. The declared rate is the rate that was charged.
The window's fees over the window's volume, so a busy day counts for more than a quiet one.
The fee the pool states is one number. This is what swappers actually paid, divided back out of the same days as the figures above: a day's fees over that day's volume. It needs no extra request and nothing from the hook.
None of this is what reaches a liquidity provider. This pool's hook is permitted to take a share of a swap, and the source does not separate the hook's share from the providers'. What these figures say is what a swap cost, not who received it.
Across 1 folds, 26 of 29 days stayed entirely inside the band this method would have drawn.
Every figure above is fitted to the days it describes. These are not. The method was stepped back 30 days, run again on the prices before that point only, and centred on the price at that point — one somebody standing there would actually have seen. Then it was laid over the days that followed, and the whole thing repeated back through the history as many times as it had room for.
How many times the history had room to fit a band and then test it.
| Days checked | Fitted volatility | In / out / crossed |
|---|---|---|
| 2026-08-23 → 2026-09-22 | 0.19% | 26 / 0 / 3 |
Each row is one fold: the days it was checked over, the volatility its own fit measured — not the figure above — and how those days sat against the band that fit produced.
Nobody held these bands. Each is what the method would have suggested at that moment, laid over prices that then happened — and the days above, which the suggested range was drawn from, are not these days.
A few folds on one pool are not a measure of how often the method holds, and say nothing about what happens next. Consecutive fits overlap, too — a 31-close fit is longer than a step of one horizon — so the folds are not independent of each other.
What a position in this range would be worth compared with simply holding the two tokens, at each price. Exact arithmetic rather than an estimate — but it counts price movement and nothing else. It says nothing about the fees a position would earn, and fees are precisely what a liquidity provider is paid for this difference.
| Price of USDC | Position against holding |
|---|---|
| 0.9991 USDT | -0.03% |
| 0.999672 USDT | -0.01% |
| 1.00024 USDT | 0.00% |
| 1.00082 USDT | -0.01% |
| 1.0014 USDT | -0.03% |
The price this is measured from — the pool's current price.
This is what is usually called impermanent loss. It is only impermanent if price comes back: a position closed at a price other than the one it opened at has realised it.
The range above is two-sided: money on both sides of the price, earning fees for as long as the price stays between them. Split it at the price and each half is a different instrument. A position sitting entirely above the price holds one token and nothing else, and the pool sells that token for the other as the price rises through the band. Below the price it does the reverse. That is what a range order is, and both halves of this range are one.
Where the position sits. Its inner edge is the first price step past the one the price is in, so it starts out holding none of what it is converting into.
What the conversion works out at, if the price crosses the whole band.
Where the position sits. Its inner edge is the first price step past the one the price is in, so it starts out holding none of what it is converting into.
What the conversion works out at, if the price crosses the whole band.
That average is the geometric mean of the two bounds — exactly, and whichever way round the prices are written. It follows from the protocol's own formulas for what a position holds at each end of its band, and the amount put in cancels out of it: a hundred dollars and a million convert at the same price.
And only if the price crosses the whole band. One that turns back inside leaves the position holding some of each, at no single price at all — which is the same thing the range above it is for, arrived at by accident.
Everything above is about providing liquidity. This is about using it. A pool's liquidity is constant between the price steps it is built on, so a swap that stays inside the step the price is in can be priced from the protocol's own formulas with nothing assumed — and one step further cannot, because another position's liquidity may begin there and this application does not read the liquidity at every price.
What goes in before the price reaches the end of the step it is in. Not a limit: a larger swap works, and this page cannot say what it costs.
How far the swap's average sits from the price on the screen.
What goes in before the price reaches the end of the step it is in. Not a limit: a larger swap works, and this page cannot say what it costs.
How far the swap's average sits from the price on the screen.
That average is the geometric mean of the price now and the price the swap ends at — the same identity the one-sided positions above rest on, seen from the other side of the trade. A swap crossing a band pays it; a position sitting in that band receives it.
The two directions are not the same size because the price sits somewhere inside its step rather than in the middle of it. What is worth comparing between pools is the size itself: it is what this market absorbs before it moves, and it is the reason anybody breaks a large order into small ones instead of sending it at once.
The ticks, blocks and figures the page above is checked against.
Source reported 2.
A price step of 0.01% between usable edges.
USDT per USDC
Before snapping to the tick grid, in the pool's own direction.
Sample standard deviation of daily log returns, scaled by sqrt(365).
How much of the window had consecutive daily prices behind it.
2026-09-22 10:03 UTC
When the response arrived, not what it describes.
Writing the explanation…
None of these is a recommendation. A narrower range takes a larger share on the days it holds and nothing at all on the days it does not, and which of those matters more depends on what the position is for — which nothing here knows.
Nothing here schedules the conversion and nothing guarantees it. This is not an order book: an order the price never reaches is the ordinary outcome rather than a failure, and there is no queue and no counterparty waiting. What there is instead is that the position collects the pool's fees while the price is inside the band, rather than paying them.
The suggested range runs from the lower price shown above to the upper price shown above, quoted as USDT for each USDC. The current price is inside it and sits close to the middle, with a slightly shorter move to the lower edge than to the upper edge. This is a concentrated-liquidity band: while price remains inside, the position supplies liquidity across that band rather than across every possible price. The range was drawn from recent movement, not from a view about where price will go. A v4 hook is attached to this pool. The protocol permits it to act before and after swaps, refuse a swap, change what a swap pays when the fee is dynamic, and take a share of a swap after pricing. It cannot refuse or take a share of a withdrawal. The rate actually charged has matched the pool's stated swap rate throughout the measured period.
Still being written…
Still being written…
Still being written…
If price falls below the lower edge, the position holds only USDC. If price rises above the upper edge, it holds only USDT. There is no order book and no scheduled conversion: these outcomes result from the liquidity formulas as price moves through the band. If price turns back before crossing the whole range, the position can hold some of each token instead. The one-sided averages shown above describe the protocol's exact end-of-band formulas, not a promise that either edge will be reached. Against simply holding the two tokens, the comparison shows a small loss at either edge and no difference at the starting price, because it counts price movement only.
The recent typical daily move was small, and the movement accumulated across the displayed horizon produced the band shown above. The suggested band contained every observed day in the fitting window. Widening the band buys more days inside in the comparisons shown, but gives a smaller share of the fees charged on each day inside. The recent activity figures show substantial variation in trading volume across the displayed periods, while the pool's measured fee charge remained at the stated level. The volatility calculation uses only days for which a price was reported; missing days were skipped rather than estimated. The same method was also checked on days the fit never saw, and the checked stretch stayed inside the band for most of those days.
This analysis does not include liquidity-provider fees earned by a particular deposit, gas costs, or whether the pool or its tokens are trustworthy. The hook may take a share of swaps, and the available data does not separate that share from the pool's reported fees. The pool-wide fee figures are not an individual's earnings, and no position-specific deposit is available here. The comparison with simply holding is exact for price movement, but it omits fees, so it is only half of that comparison. The swap examples show how much this market absorbs before the displayed price moves over the part of the pool that was read; they are not limits or capacity figures, because liquidity at the next price step was not read.
Written by gpt-5.6-luna. The figures above were not.
The v4 pools that trade USDC / USDT — the same two contracts. A v4 pair can be many pools: the fee is any number, the price step is free, and every hook makes another.
Depth at the current price ≈ 16,628,200 ETH
hook 0x0000113dcf4add69999fad8f20f2b63f979bfcc0 · may change what a swap costs
Depth at the current price ≈ 10,578,400 ETH
no hook
Depth at the current price ≈ 6,754,230 ETH
no hook
Depth at the current price ≈ 3,825,350 ETH
no hook
Depth at the current price ≈ 169,443 ETH
no hook
Depth at the current price ≈ 7,710.65 ETH
no hook
Depth at the current price ≈ 2,825.62 ETH
no hook
Depth at the current price ≈ 741.495 ETH
no hook
Depth at the current price ≈ 0.850789 ETH
no hook
Depth at the current price ≈ 0.620507 ETH
hook 0x38fdc1b79148abe3c621467e3cc6556453b0f6c0 · may change what a swap costs
Depth at the current price ≈ 0.608465 ETH
no hook
Depth at the current price ≈ 0.145701 ETH
hook 0x4440854b2d02c57a0dc5c58b7a884562d875c0c4 · may change what a swap costs
38 more are not shown; they are shallower than these.
Ordered by depth at the current price — the pool's active liquidity and price, read from the PoolManager's storage — because a v4 pair is mostly pools somebody initialised and left, and depth is what tells those apart. It says how much a swap can draw on, and nothing about which pool is better: a deeper pool is a larger crowd sharing the same fees.
The v3 pools that trade USDC / USDT — the same two token contracts, at each fee tier.
Holds 21,609,798.1412 USDC + 12,700,854.3438 USDT
Holds 312,578.7236 USDC + 294,258.9124 USDT
Holds 30,730.3304 USDC + 31,275.3702 USDT
Holds 633.984 USDC + 761.5102 USDT
A tier holding more liquidity is a larger crowd sharing the same swap fees, not a better place to be. Which one suits a position depends on how far the price moves and how often, and that is measured per pool — so the honest way to compare them is to open each and read its own figures. The horizon and multiplier you chose travel with the link.
These are the balances the two token contracts report for each pool, read from the chain rather than from an indexer. The indexer's own figure was measured against them and overstates what is there by between 1.3 and 13 times, so it is not shown. Two token amounts rather than one dollar figure, because every tier here holds the same two tokens and nothing has to be priced to compare them.