Scope
CoinVerum covers supported decentralized exchanges on Ethereum mainnet. Current venue pages include supported versions of Uniswap, PancakeSwap, Curve, SushiSwap, Balancer, ShibaSwap and Fraxswap 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 registries. Those sources provide addresses and token metadata only: TVL balances and trading activity come from Ethereum.
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. Price freshness is evaluated per token from that token's latest observation. USD anchors use a fresh Chainlink ETH/USD reference and observed stablecoin cross-rates; a $1 stablecoin value is used only when no market-derived cross-rate is available.
TVL and token liquidity
Pool TVL is calculated from token balances or canonical protocol liquidity state read at one explicit Ethereum block. Uniswap V4 principal is reconstructed from the PoolManager liquidity curve through the official ReservesLens. Balances are valued using the median of recent USD prices derived from indexed on-chain swaps. Every counted coin must have both a successful balance read and a valid price; CoinVerum does not publish a partial pool value as complete TVL. Internal Curve LP claims held by another Curve pool are excluded from venue totals to avoid counting the same underlying assets twice. The token-level “associated pool TVL” metric sums the full TVL of qualifying pools containing that token. It is neither token-side reserves nor executable depth and is not additive across tokens.
Volume and trades
Volume is the sum of indexed swap values in USD during the stated rolling window, ending at the latest indexed swap. Trade count is the number of indexed swaps in that window. When indexing is delayed, the UI identifies the last indexed time rather than presenting the window as live.
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, complete on-chain balance and price coverage, and more than $50,000 in USD TVL. The same rule applies across supported venues. Protocol API or subgraph TVL fields are ignored.
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.
- On-chain TVL snapshots run every six hours at one recorded Ethereum block.
- Category membership and external token metadata update less frequently.
- API responses expose update timestamps where the underlying metric supports one.
- A 24-hour price change is published only when indexing is current and a valid price observation exists close to the point exactly 24 hours before the latest price.
- Each token is marked stale when its own latest valid price observation is older than five minutes.
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.
- Price-impact figures use constant-product estimates for supported V2-style pools and on-chain get_dy calls for supported Curve pools. They exclude concentrated-liquidity V3/V4 and Balancer execution and are not router quotes.
- Projected Aave liquidation levels cover at most 500 positions and do not model borrower-specific eMode. Market liquidation totals cover only the explicitly named sources.
- 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.
- Only protocol versions currently discovered by CoinVerum are represented.
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.