THECHAINOBSERVER / OBSERVATORY

Methodology.

Sources, definitions & collection health

What Observatory measures

TheChainObserver combines source-linked announcements, published software releases, selected network indicators and token-market observations. These datasets answer different questions. An announcement date is not necessarily an event date; a release count is not a developer count; a token price is not a measure of network adoption.

Our market pages are maintained automatically from DEX Screener observations. The summaries use transparent calculation rules, not generated predictions. Editorial choices about the initial watchlist and the meaning of each metric are recorded in the coverage below.

Market collection health

Provider: DEX Screener public API
Latest attempt: 16 Sep 2026 18:15 UTC
Latest successful collection: 16 Sep 2026 18:15 UTC
Collection result: partial
Fresh coverage: 9 / 10 selected assets
Observations started: 16 Sep 2026 17:23 UTC

Coverage and identity

The initial market watchlist covers ten contracts on Ethereum: AAVE, COMP, DAI, LDO, LINK, UNI, USDC, USDT, WBTC and WETH. It is a selected editorial sample, not a top-ten ranking or a complete market index.

Contracts were cross-checked against the Uniswap Labs default list on 16 September 2026. Symbols alone are never used to identify a token. Wrapped BTC and ETH are labelled separately from their native assets. We do not substitute them for Bitcoin or Ethereum network statistics.

How pairs and observations are selected

Discover pairs for approved contracts daily, resolving up to two missing assets through contract-specific pool lists. Refresh the selected pairs together every 15 minutes.
Accept only the expected chain and base-token contract, valid pair addresses, a positive price and at least $10,000 in reported pool liquidity.
Select the highest reported liquidity among eligible returned pairs for each asset. This does not prove that all pools or all venues were returned. Pair selection is refreshed daily; intervening observations use those selected pairs.
Save normalized observations with provider, dataset, entity, pair and reception time. Do not retain arbitrary provider descriptions, promotional images or raw responses.
Serve local observations to readers. Visits do not trigger provider requests.

The liquidity threshold is a publication filter, not a safety assessment. A different pair can be selected later; charts restart at the current pair’s uninterrupted observation sequence instead of joining unrelated markets.

Dates, history and missing values

“Received” is the time our collector obtained the response, not the timestamp of the latest trade. Observations older than one hour are labelled delayed. A failed request preserves the last valid data and schedules an automatic retry with increasing delays.

We keep 15-minute observations for 90 days and the last received observation of each UTC day for up to two years. Daily records are snapshots, not OHLC candles or daily volume totals. History begins at collection; we do not fabricate earlier points. Charts use up to 96 recent observations for the currently selected pair.

Missing values remain unavailable. Partial responses do not erase an asset’s previous observation. Each asset carries its own reception time.

Understanding the numbers

Price: USD price reported for the selected pair; not a consolidated exchange price.
Liquidity: Reported USD value in that pool; different from executable depth.
24-hour volume: A rolling window reported by the provider. Overlapping observations must not be added together.
Volume / liquidity: Rolling volume divided by observed liquidity. A descriptive ratio, not a forecast.
Transactions: Buy/sell counts for the pair; not counts of unique people.

Sources and corrections

Market observations link to their selected DEX Screener pair. The integration follows the provider’s API conditions; Observatory is an editorial context service and does not resell a bulk market-data API. Advertising boosts are not used to rank projects.

Other Observatory modules maintain their own source scope: publication sources and status, explicit dated deadlines, selected software repositories and network indicators. Their figures should not be combined without checking units and methodology.

Use the source links to check a discrepancy. These pages describe observed data, not buy or sell recommendations.

Publication sources, update status & coverage →