Gauge Measured

Put a pool on the bench.

Give it any Uniswap V3-style pool address on Base and it reads the chain from your browser and reports the number no vault page prints: how long you would have to hold before that pool’s own average describes what it paid you.

GAUGE / LIVEBase · no key · no wallet · no server of ours

How to read it

The headline is a holding time

The number of blocks you would have to hold before the fee income you have collected is within ten per cent of the pool’s own mean, ninety per cent of the time — computed from that pool’s measured distribution rather than a rule of thumb. If it comes back longer than the window it was measured over, it is a floor: the window did not contain enough of the rare, large blocks to pin it down. That is not a defect of the tool. It is the finding.

Three things it will tell you it cannot do

  • It cannot name every factory. The same Swap event is emitted by every fork of Uniswap V3. If the factory is one this site cannot name, the fee arithmetic is assumed rather than known, and the log says so.
  • It cannot price a pool with no major on either side. Fees are then counted in the pool’s own token0, whose value moves during the window. Ratios survive that; the total does not.
  • It cannot see whose liquidity was in range. This is the pool’s income — the numerator of every APY quoted against it. A narrower range gets a burstier version, so every number here is a floor.

Same js/chain.js and js/stats.js as the published scan, so the tool and the finding cannot be two different programs.