How Topaz Stats are computed

Network coverage and share accounting

Topaz analytics cover BNB Chain (56), Robinhood Chain (4663), Base (8453), Ethereum (1) and Arc (5042). Protocol totals combine the selected networks; a network filter applies to the metrics, chart and pool list. Pool and token identities always include both chain ID and contract address.

Liquidity totals count indexed user pools, excluding the API’s pricing blacklist. Token exposure is not added to pool TVL: that would count the same liquidity twice. Bridged xTOPAZ supply, adapter custody, canonical backing and in-flight transfers are separate accounting quantities, not additional DEX liquidity.

Data sources

The Topaz API is the public read layer. /v1/chains describes network capabilities; /v1/protocol provides combined and per-network liquidity metrics; /v1/pools and /v1/tokens provide chain-qualified market observations.

The service indexes Topaz’s stable/volatile and concentrated pools and governance deployments. Prices include source, block and availability evidence. Use the API’s published pricing and valuation status; a raw subgraph reserve value or a current token price is not a substitute for a historical USD observation.

Observation times and history

Headline 24-hour and seven-day figures use the API’s rolling windows. Each network has its own indexed observation boundary; combined totals sum those independently observed windows. They are not a synchronized cross-chain block. No browser-side proration of yesterday’s totals is applied.

The stats chart explicitly requests alignment=utc. Daily volume and fees are period flows; daily TVL is the latest state observation within the requested period. TVL is not summed across time. The current day or a period with incomplete pricing/coverage is marked partial. Historical coverage depends on each network and metric; requests for 30 or 90 days do not imply those days are all available.

A missing value is not zero. A known subtotal is displayed with + when complete valuation or network coverage is unavailable. Charts mark partial periods and preserve gaps. Response generation and cache times are not the time the underlying chain state was observed.

Epoch timing

Epochs last seven days and align to Thursday 00:00 UTC. Voting opens one hour after epoch start and closes one hour before the next epoch. Gauges and reward funding are scoped to the requested chain and epoch.

Voter rewards describe notified fee and incentive funding for that epoch. They are distinct from rolling DEX trading fees and from gauge emissions paid to staked liquidity. Public voting displays may retain an explicitly stale same-epoch publication with its timestamp; transaction eligibility still uses its own chain-state checks.

Rates and fees

Fee APR annualizes the API’s trailing seven-day fees: (fees7dUsd × 365 / 7) / tvlUsd × 100. It is an observed pool rate for unstaked liquidity, not a guarantee of a personal return.

Emissions APR uses the gauge reward rate, reward-token price and staked liquidity. TOPAZ pays hub emissions; xTOPAZ pays spoke emissions. Concentrated pool listings use the API’s reference deposit and range scenario; personal positions use their actual liquidity and range. Fee APR and Emissions APR remain separate.

The dynamic-fee table shows the indexed observed fee and custom/dynamic flags from the selected networks. It does not quote a transaction’s execution fee or claim that an indexed fee is a fresh RPC read. Base and maximum settings are not supplied by this endpoint; for BNB Chain pools they come from the legacy BNB Stats service and appear beside each pool's observed fee in the same table.

Rate definitions explain the denominators, reward assets and observation periods.

Limits and compatibility data

Cumulative volume reads the API's stored volume from /v1/protocol/volume, for all networks or the selected one, and the by-network table shows each network's figure.

Foundation ownership, allocation, incentive history and ROI, TOPAZ supply/locked-share reporting, historical valuation ratios, and public veTOPAZ escrow/voting-power totals still use compatibility endpoints where an equivalent accepted /v1 observation is unavailable. These have their own timestamps and scope. Current TOPAZ price, TOPAZ pool metrics and protocol activity use /v1; market cap and FDV multiply that price by the separately reported supply.

Foundation KPI classifications indicate correlation, not causality. Missing prices, incomplete indexing, failed observations and unavailable periods must not be converted into zeroes or complete totals.

Cumulative volume is the USD volume the API has recorded on each network, summed across the networks shown.