$2.28M or $28.37M? Volume Differs 12x by Scope
- Board scope $54.68M vs token-wide $185.27M — a 3.39x gap
- $AI volume differs 12.44x; $ROBIN liquidity differs 15.87x
- Single pool for execution, aggregate for activity, same scope for comparison
One site says $AI did $2.28M in 24-hour volume on Robinhood Chain. Another says $28.37M. Neither is lying — they are measuring different things. One reports the main pool; the other aggregates every pool under the token.
I pulled every pool under all twelve tokens on today's hot board and added them up. Main-pool volume totals $54.68M. Token-wide volume totals $185.27M — 3.39x higher. This is which number to use when, and what goes wrong if you mix them.
Snapshot: 2026-09-09 00:09 UTC.
The size of the gap
| Token | Pools | Main-pool liq | Token-wide liq | × | Main-pool vol | Token-wide vol | × |
|---|---|---|---|---|---|---|---|
| PONS | 20+ | $8,607,787 | $36,133,042 | 4.20x | $27,823,651 | $116,117,903 | 4.17x |
| AI | 20+ | $22,683,038 | $36,364,946 | 1.60x | $2,280,519 | $28,365,909 | 12.44x |
| CASHCAT | 20+ | $3,403,328 | $14,066,731 | 4.13x | $13,670,663 | $24,007,790 | 1.76x |
| PAIR | 20+ | $1,090,384 | $2,653,223 | 2.43x | $1,267,390 | $5,644,613 | 4.45x |
| ROBIN | 20+ | $192,993 | $3,063,604 | 15.87x | $1,138,418 | $1,777,426 | 1.56x |
| DELTA | 20+ | $1,146,058 | $1,871,690 | 1.63x | $2,345,680 | $2,980,353 | 1.27x |
| SIRIUS | 20+ | $77,566 | $261,938 | 3.38x | $462,013 | $563,258 | 1.22x |
| CHUMP | 20+ | $1,163,709 | $1,211,549 | 1.04x | $2,679,614 | $2,755,828 | 1.03x |
| ASHIBA | 11 | $132,005 | $142,021 | 1.08x | $934,392 | $950,514 | 1.02x |
| AP | 11 | $102,695 | $113,146 | 1.10x | $713,372 | $728,607 | 1.02x |
| RUBEN | 8 | $6,099 | $7,485 | 1.23x | $773,010 | $784,686 | 1.02x |
| WORKS | 7 | $7,057 | $7,225 | 1.02x | $587,400 | $598,072 | 1.02x |
The API returns at most 20 pools per token, so every "20+" row is a lower bound.
Where $AI's 12.44x comes from
$AI (Artificial Inu) is the clearest case on the board. It has at least 20 pools. The four largest by volume:
| Pool | Created | Liquidity | 24h volume | Turnover | 24h buys / sells |
|---|---|---|---|---|---|
| AI / NVDA (main) | 2026-07-14 | $22,599,018 | $2,275,951 | 0.10x | 1,743 / 3,636 |
| AI / USDG 0.23% | 2026-09-03 | $814,661 | $9,031,764 | 11.1x | 6,105 / 7,159 |
| AI / WETH 1% | 2026-07-22 | $2,784,686 | $5,288,147 | 1.9x | 1,002 / 993 |
| AI / BONER 0.9% | 2026-08-21 | $1,996,729 | $2,280,188 | 1.1x | 1,015 / 727 |
The structure is inverted: $AI's liquidity is in the NVDA pool ($22.6M), but its trading is in the USDG pool ($9.03M on $814,661 of depth). The main pool turns over 0.10x — a $22.6M pool that did $2.28M in a day.
Read only the main pool and you conclude: "$AI is dead, nobody trades it." The token-wide figure is $28.37M. $AI is not dead — the trading is happening in the pool you were not looking at.
Read only the token-wide figure and you make the opposite mistake: assuming you can size a position against $36.4M of depth. Your order routes through one specific pool, and your slippage comes from that pool's depth, not from the sum. $AI trading page.
$ROBIN, the reverse case: 15.87x on liquidity
$ROBIN's main pool (ROBIN / USDG 1%) holds $192,993. Token-wide it holds $3,063,604 — 15.87x more.
Compute its market-cap-to-liquidity ratio on the main pool and you get 28.7x, which reads as a badly inflated paper valuation. Compute it token-wide and you get 1.8x, which reads as conservatively backed.
Both are correct. They answer different questions.
- "How much will my order slip?" → the depth of the pool you actually trade in.
- "How much capital stands behind this token overall?" → the token-wide sum.
- "How easily can the price be pushed?" → the main pool, because that is where price discovery happens.
Three rules
Rule 1: for slippage and position size, use the pool you trade in
$ASHIBA is token-wide $142,021 with 93.7% in one pool, so the two numbers are interchangeable. $ROBIN's liquidity is spread across 20+ pools — sizing off the sum would badly overstate what a single order can absorb.
Rule 2: for "is anyone still here", use the token-wide sum
$AI's 0.10x main-pool turnover is misleading. Token-wide it did $28.37M in 24 hours, second only to $PONS's $116.12M.
Rule 3: when comparing tokens, both sides must use the same scope
This is where people get hurt. Compare $AI's main-pool volume ($2.28M) against $PONS's token-wide volume ($116.12M) and you conclude $PONS is 51x more active. Same-scope, the main-pool ratio is 12.2x and the token-wide ratio is 4.1x. Three numbers spanning an order of magnitude, three different conclusions.
A note on our own board
Our daily hot-tokens report uses main-pool scope, because it corresponds to the depth you actually face when you place an order — the more conservative, more actionable number. Today's board totals ($54.68M volume, $38.61M liquidity) are all main-pool.
Two consequences to keep in mind:
- The board understates real activity. Token-wide, those twelve tokens did $185.27M, not $54.68M. Chain-wide, GeckoTerminal shows $2.06B across 8,016,535 transactions today.
- The turnover column is main-pool turnover too. $AI reads 0.1x; token-wide it is 0.78x. Worth remembering when judging whether something is a dead pool.
Checking a token's pool structure in 60 seconds
- Open it on the BigPump trading page and identify the main pool and its quote asset.
- Check whether liquidity is concentrated (one pool over 90% — easy to reason about) or spread across five or six pools (each needs its own read).
- Read the fee tag on each pool. Today's board carries 22 pools with fees at or above 20%, topping out at 90%. Volume in those pools should be excluded from any aggregate — it is a warning sign, not activity.
- Compute turnover for the pool you will actually trade in, not from the aggregate.
FAQ
Why does one token have so many pools?
A DEX lets any address create a pool for any pair with any fee, without the project's involvement. $AI has at least 20, quoted against NVDA, USDG, WETH, BONER and others.
Which scope is more "true"?
Neither. Single pool for execution, aggregate for activity, same scope for comparison.
Does the token-wide figure include wash trading?
It can. Pools holding a few hundred dollars with 80%+ fees distort aggregates badly. Today $ASHIBA has a pool with $0 liquidity that recorded $9,974.99 of volume — that kind of row has to be excluded manually.
What structure do BigPump tokens have?
During the curve phase there is no DEX pool at all — only the bonding curve, at a 1% pool fee. At 4 ETH of cumulative real ETH the token graduates and the contract creates a single Uniswap V2 pool with LP tokens burned. So a freshly graduated token has a clean single-pool structure — after which anyone can add more pools, exactly as on any other token. See the BigPump docs or launch a token.
Which token has the biggest gap today?
On volume, $AI at 12.44x. On liquidity, $ROBIN at 15.87x. The smallest gap is $CHUMP at 1.03x / 1.04x — almost everything it has sits in the main pool.
Data from Robinhood Chain per-token pool listings, 2026-09-09 00:09 UTC; the API returns at most 20 pools per token, so aggregates are lower bounds. Not investment advice — memecoins can go to zero.
Disclaimer: memecoins are extremely volatile and most go to zero. This article is not financial advice. Do your own research and only spend what you can afford to lose.