$ROODFI

reading this pool's swap logs…

• · V4 depth is UNMEASURED, not zero: V4's PoolManager is a singleton holding every pool's tokens in one contract balance, so per-pool reserves cannot be read as balances. We say so rather than guess.
• · Volume is the 24h ETH leg the chainwide index attributed to each pool — a floor over what its per-tick budget could walk, never a lifetime total. Share divides by $ROODFI's 24h ETH across all 1 of its pools, not just the rows listed.

• · These strings were written into the token contract by whoever deployed it, and some of what is above came from our index rather than from this request — each part says which. Anyone can deploy a contract and write anything into it. A link here is not evidence that the account, site or person it points to has anything to do with $ROODFI — we do not check, we do not ask them, and we never follow the link to see where it lands.
• · Read them yourself: the contract on the explorer ↗

• · Every row is the account that SIGNED the swap transaction — never the router the trade was routed through. (Measured while building this: every swap-event “sender” in a live window was a contract; a board of those would be a list of routers.)
• · Totals cover ONLY the indexed window: 15 swaps attributed for $ROODFI between 2026-08-07 15:22Z and 2026-08-07 15:36Z — at least 60% of the 25 swaps our volume index counted over the same hours. Attribution is budgeted per tick and takes the highest-value blocks first, so every figure here is a floor over a stated period, never a lifetime total.
• · ETH in and ETH out are shown separately because net alone cannot tell “never sold” from “round-tripped”.
• · An account signing on others' behalf (a keeper, a relayer) appears as one signer. The “tokens” column is shown so bot- and infrastructure-shaped accounts are visible rather than silently ranked as people.

last 24h 0 ETH added over 0 events · 0 ETH left the pools over 0 movements (V3 collects and V2 burns — the two ways tokens actually leave a pool contract) · 1 V4 event carry a liquidity delta and no amounts, so they are counted here and add nothing to the ETH figures. Floors over the pools and blocks we walked, not a census.

No holder concentration is shown for $ROODFI: no Transfer events appear in the window we walked, and the token emitted no logs at all in the blocks we probed to check — so it looks quiet rather than clipped. No wallet could be nominated for a balance read.

· The read itself worked — this is what it found, not an outage. Candidate discovery covers the last 120,000 blocks (about 3.3 hours) of chain history, so a token whose transfers all predate that window is invisible to it.