Every number on the ledger is reconstructed from public on-chain data and can be independently verified. This page explains exactly how — and where the estimates have known limits.
After each refresh, the balance implied by a wallet's reconstructed history is compared to its actual on-chain balance. A mismatch first triggers a live balance re-read (to rule out a race with a trade landing mid-refresh); if the history still doesn't reconcile, the wallet's entire transfer history is re-fetched from scratch that same run. Each refresh also re-fetches the last hour of every wallet's transfers wholesale, so same-second trades can't be skipped and nothing is ever double-counted.
Net flow sums every tracked wallet's inbound minus outbound FRONG per hour. Transfers between two tracked wallets are tagged internal and excluded from the flow, the verdict's buyer/seller counts, the movers list, and realized PnL — internal shuffling can't fake a signal anywhere on the site.
No survivorship bias: "tracked" is not just today's top 50. A wallet that sells its way off the list stays tracked (the most recently active stay first, up to 80 total), so a whale's exit dump still counts in the flow, the verdict, and the movers list — it is labeled sold out of top 50 instead of silently disappearing.
Harvest events are detected as FRONG inflows to the protocol fee recipient, which pairs its share and re-deposits it into the pool with the resulting LP position sent to the burn address. "FRONG recycled" is the cumulative sum of those inflows — fees that became permanent liquidity instead of being extracted. (Verified on-chain: every harvested FRONG to date has ended at the Uniswap position manager, i.e. inside the pool.) To be precise about what "locked" means: the liquidity position is locked forever; the recycled FRONG inside it is still buyable like any pool token. Only burned FRONG is gone from the supply.
The buyback contract burns a fixed 500,000 FRONG per claim
(minCurrency1BurnAmount, immutable). Whoever fires a claim takes the queued
ETH and, in the same transaction, buys those 500,000 FRONG on the open market and sends
them to the dead address — so a claim is only worth making once the queued ETH covers
what 500,000 FRONG costs. That is the meter — on the site the queued ETH is called the fee pot:
fee pot ÷ (500,000 × FRONG price in ETH).
"Queued" is read live in your browser as amounts(409801) on all three
contracts the fees pass through — the fee vault where they accrue, the vesting contract
that releases them, and the buyback contract a claimer draws from. 409801 is FRONG's
fee-NFT id. The price leg is the FRONG/ETH rate from the deepest pool, so the bar moves
on price as well as on fees: the target is denominated in FRONG, not dollars, so a lower
price lowers the bar and a higher price raises it. If the RPC is unreachable the meter
falls back to the last value the 10-minute refresh recorded.
Two caveats. The bar can reach 100% without a burn happening immediately — firing it is permissionless and nobody is obliged to; in practice a searcher does it within hours. And it can fire slightly before 100%, because a claimer can harvest fresh fees inside the same transaction, adding to the pot the meter hasn't seen yet.
xfer-in). If a whale moved coins between their own wallets, their true
cost is older and usually lower than shown.partial where so.A pipeline recomputes everything every ~10 minutes and commits the result; every commit is a permanent, public, timestamped snapshot. The page you're reading always shows the latest baseline plus a live price layer on top.