What to know first
A TON market figure needs an asset identity, source, coverage, and observation time. Market cap uses circulating supply; FDV uses a broader supply basis. Global coin volume and covered pool volume measure different markets. A recent pool does not prove a new token, and missing data should remain unavailable rather than becoming zero.
Key takeaways
- Use provider valuation labels as estimates unless their supply basis is verified.
- Compare like scopes and time windows before adding or ranking market figures.
- Wallet addresses, transactions, pool age, and token age are separate observations.
Practical checks
- Match the chain, native asset or token master, and pair or pool address to the intended asset.
- For valuation, find the circulating, total, or maximum supply basis and whether the provider verified it.
- For volume and liquidity, read the venues, pool coverage, currency, and time window.
- Compare the observation timestamp with the fetch time and the current executable quote.
- Keep missing values unavailable and distinguish pair creation, token-contract evidence, and first discovery by a tool.
Market cap versus FDV
Market capitalization is price multiplied by circulating supply. Circulating supply is the provider's estimate of units in public circulation, with exclusions defined by its methodology. Total supply generally counts minted units less burned units; maximum supply is a cap where the token has one.
Fully diluted valuation applies price to a broader supply basis, commonly total supply or sometimes maximum supply. Check which basis the provider actually uses. Neither valuation is cash deposited into the token, nor a promise that all units could be sold at that price.
CoinGecko's GeckoTerminal-powered pool documentation warns that market cap can be null when it is not verified. A value shown elsewhere may resemble FDV rather than verified circulating-supply market cap. Keep the provider's qualification instead of silently relabelling one as the other.
Global coin volume versus covered pool volume
A coin's global reported trading volume aggregates the markets covered by that provider, potentially across centralized exchanges and DEXs. A TON pool's volume covers trading in that particular pair and interval. A covered-pool total is limited to the distinct pools included in the dataset.
These figures can overlap. Adding a global GRAM volume figure to TON pool volumes does not create a clean TON DEX total. Compare the same period, asset units, and market coverage, and count each pool once. Provider-wide coin volume is not evidence of activity in a particular TON contract.
Liquidity is a snapshot, not an exit guarantee
Pool liquidity describes inventory or reserve value observed for that pool. Trading volume describes past turnover. A busy pool can have limited inventory for the next order, and a large USD reserve figure does not specify the output for every trade size.
The pool's assets, pricing curve, fees, and current route affect an executable quote. Check the liquidity guide for minimum output and slippage; this page does not define a suitable order size or trading threshold.
Wallets and transactions are not people
A wallet or account count records blockchain addresses meeting a stated rule. One person can control several addresses, while a service can represent many customers through its own accounts. The inference is that an address count alone cannot establish a unique-person count.
Read what active means: sending a message, receiving funds, executing a successful operation, or another query condition. A transaction count records chain activity; a swap can involve several transactions. Neither figure alone measures unique traders or user growth.
Missing values and price freshness
If no source supplies a value, display it as unavailable, such as N/A or a dash. Zero is a measured value and should be used only when the evidence actually establishes zero. A missing 24-hour change is not proof that price was flat, and missing liquidity is not a measured empty pool.
Record when the provider observed the price separately from when the page fetched or published it. CoinGecko's simple-price API exposes a last-updated timestamp. A newly built page can still contain an older observation, and a chart price can differ from a later amount-specific swap quote.
Recent pool versus new token
DEX Screener exposes pairCreatedAt; GeckoTerminal-powered data exposes pool_created_at. Those fields describe the pair or pool. An existing token can gain another pool months after its original deployment.
Token-contract deployment, first recorded contract activity, a new trading pair, and first discovery by Gramium are different dates. If only pool evidence is available, describe a recent pool. Do not claim that the token itself is new without the corresponding contract evidence.
One hypothetical example
Illustration only, not current market data or a recommendation: imagine a token priced at $2, with 1 million verified circulating units and 10 million total units. Its market cap would be $2 million and its total-supply FDV $20 million. If circulating supply were unknown, market cap would remain unavailable even if an FDV estimate could be calculated.
Suppose its provider reports $500,000 of global 24-hour volume and two covered TON pools report $12,000 and $8,000 over the same period. Covered pool volume would be $20,000 after checking that the pools are distinct. Adding $500,000 would mix overlapping scopes. A $15,000 liquidity snapshot would still need a current quote for any specific trade.
If one of those pools was created yesterday, that dates the pool only. A count of 100 active addresses would not establish 100 people, and a price observed at 10:00 would not become a 12:00 price merely because the page refreshed at noon.
Sources and review
Reviewed . Sources support the definitions below; market observations and product availability keep their own dates.
- CoinGecko: methodology
Price, circulating supply, market capitalization, and provider trading-volume methodology.
- CoinGecko: supply and valuation definitions
Circulating supply versus total or maximum supply and the market-cap/FDV distinction.
- CoinGecko: GeckoTerminal-powered pool data
Pool reserves, period volumes, pool_created_at, and unverified or null market-cap caveats.
- DEX Screener: pair API reference
Pair-level volume, liquidity, valuation fields, transaction counts, and pairCreatedAt.
- CoinGecko: price freshness
last_updated_at and the distinction between current retrieval and price observation.
- TON Docs: explorers and account activity
Account, transaction, message, and trace definitions; no unique-person count is established.
FAQ
Why can market cap be missing while FDV is shown?
Circulating supply may not be verified even when the provider can estimate a broader supply and price. Keep market cap unavailable and retain the provider's FDV qualification rather than substituting the estimate.
Can global GRAM volume be added to TON pool volume?
Not as a homogeneous TON DEX total. Global coin volume and local pool volume have different coverage and may overlap. Label and compare them separately.
Does a recent TON pool prove a new token?
No. Pair or pool creation dates describe that market. Token deployment or first-activity evidence is needed to support a separate token-age claim.
Should missing market figures be displayed as zero?
No. Show them as unavailable. A measured zero, an absent observation, and a stale observation have different meanings.