Scope
CoinVerum covers supported decentralized exchanges on Ethereum mainnet. Current venue pages include Uniswap, PancakeSwap, Curve and SushiSwap when their data sources are configured and qualifying pools are available. Coverage is not a complete record of every Ethereum pool or transaction.
The core market views do not use centralized-exchange price feeds. Pool discovery uses supported protocol subgraphs and public protocol data, while trading activity comes from indexed Ethereum swaps.
Metric definitions
Price
The token table uses the most recent valid USD-denominated observed swap price for the asset. It is a market reference, not a guaranteed executable quote.
TVL and token liquidity
Pool TVL is the current USD value attributed to a qualifying pool. Token liquidity aggregates qualifying pools containing that asset. Concentrated liquidity and token composition can make two pools with similar TVL behave differently.
Volume and trades
Volume is the sum of indexed swap values in USD during the stated rolling window. Trade count is the number of indexed swaps in that window.
Active addresses
Active addresses are distinct observed transaction senders. The measure should not be described as a count of people because routers, aggregators and smart accounts can act for multiple users.
Pool inclusion and ranking
Pool rankings require active status and more than $50,000 in USD TVL. Non-Curve pools must also have produced a valid USD-priced indexed swap before their liquidity is counted. This reduces the influence of inactive and obviously manipulated pools, but it cannot remove every token, smart-contract or data-quality risk.
Rankings default to descending liquidity. DEX pages aggregate trusted pools by venue; version-level breakdowns remain visible where multiple implementations are tracked.
Freshness and timestamps
- Token and pool market views generally revalidate every 30 seconds.
- DEX analytics generally revalidate every 60 seconds.
- Category membership and external token metadata update less frequently.
- API responses expose update timestamps where the underlying metric supports one.
Anyone quoting a live value should retrieve the current page or JSON response and include its timestamp. Historical values may be incomplete during RPC interruptions, indexing gaps or backfill periods.
Data limitations
- Only supported and tracked Ethereum mainnet pools are represented.
- A displayed price can have limited executable depth.
- Address history begins when sender tracking is enabled.
- Category labels do not verify reserves, legal rights or project claims.
- External protocol metadata can contain errors or change independently.
Frequently asked questions
Does CoinVerum use centralized exchange prices?
No. Core CoinVerum prices and market activity are derived from qualifying Ethereum decentralized-exchange pools and indexed swaps.
Are active addresses the same as users?
No. Active addresses count distinct observed transaction senders. Routers, aggregators and smart accounts can represent activity from multiple underlying users.
Does a displayed price guarantee execution?
No. A price is an observed market reference. Available liquidity, pool concentration, fees and trade size determine the executable result.
How frequently does the data update?
Most live market views revalidate every 30 to 60 seconds. External metadata, category assignments and historical backfills update less frequently.
Reproducibility and access
Read the public Data API reference, download the machine-readable OpenAPI document, or inspect the open-source implementation on GitHub. For correction requests, use the Contact page.