OVR (Ovr) — the network, measured

Generated 2026-09-02T18:07:23Z from live ClickHouse queries against this estate's ledger. Held inventory: 7,355 observations · 32 distinct series · 3 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 17:49:30 · 7,355/7,355 rows carry a verify_url. 32 series refreshed in the last 24h (726 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

3 source families feed this network's ledger. Every row they wrote carries its own source, as_of and verify_url; this table is the live rollup of that.

30-day history — headline series (daily last-value, live)

One row per series: latest value, a 30-day sparkline of daily last-known values (scaled to the series' own min→max), day count, and window change. Series absent from the 30-day window are omitted from this table, not zero-filled.

Market reference — CoinGecko coin page, as held

Market-data reference rows: price, supply, capitalisation, diluted valuation, and the published change columns including ATH/ATL. These are the coin-page reference's own numbers — the estate does not model, smooth, or forward-fill them. The change columns / rank / ATH-ATL / high-low series start later in the archive than the price rows (each metric's caveat in the full inventory states its own first-held row) and are shown from their first held row. OVR is a low-cap asset (2,755,244 market cap, 73,641 24h volume at generation) — every quote on a thin book is noisier; that is the reference's data, held as published, and the 30-day sparklines are daily last-values for exactly this reason. The circulating and total/max supply rows are different quantities (circulating vs total vs cap) and are never netted against each other or against the chain-read supply below.

Protocol TVL & staking — DefiLlama /protocols, as held

The DefiLlama /protocols family for OVR: tvl_usd and staking_tvl_usd — two dimensions of the same upstream protocol record. These are upstream's own published quantities, shown side by side and never summed, netted, or reconciled with each other or with any market row. The headline TVL is 0 because upstream answers 0: DefiLlama's own OVR series (api.llama.fi/protocol/ovr) ends at totalLiquidityUSD = 0 across its recent history while the staking dimension of the same record reads ~$967 — the collector copied the zero faithfully, and this page publishes it as upstream's answer, never as a gap and never smoothed into the staking figure. At generation this page re-fetched upstream's own answer: the last point of the OVR tvl series on api.llama.fi reads 0 totalLiquidityUSD while the staking bucket reads 966.91072 — the held rows below mirror those answers, held as published. The rows keep their own verify_url (https://defillama.com/protocol/ovr).

Chain-side telemetry — Ethereum mainnet, token 0x21bfbda47a0b4b5b1248c767ee49f7caa9b23697, as held

The estate's evm_blockscout family reads this token contract directly on Ethereum mainnet via keyless eth.blockscout.com endpoints (the token endpoint, the token counters endpoint, and the ADDRESS counters endpoint — each row's verify_url re-executes the same keyless GET the collector ran). These are the raw on-chain quantities for the contract — the strongest provenance class on this page, standing in where a first-party family is absent: the estate holds NO first-party self-telemetry family for OVR (has_public_stats_api = 0 in the catalog; the ledger holds zero first_party_api rows), and no such section exists here — absence, not zero. The catalog lists OVR on base, binance-smart-chain, ethereum and polygon-pos; this estate's chain-side family reads ONLY the Ethereum-mainnet contract (the collector's single Blockscout endpoint) — no Base/BSC/Polygon chain reads are held, and none are implied. The on-chain supply is a separate measurement from the CoinGecko total/max supply references above; at generation all three read the same figure (~89.89M tokens), shown side by side, never merged. OVR is NOT in the collector's supply-override registry (unlike ALTHEA's bridged subset or RENDER's migrated legacy contract), so this supply is the plain, un-renamed chain read. Balances and counters are published raw — never differenced into rates.

Full metric inventory — 32 measured series, each with provenance

Every series held for OVR with rows in the last 30 days: latest value, when it was observed, which source observed it, how many rows we hold, how many of the last 30 days it reported, its comparability grade, and the origin link. "days/30" counts distinct dates with at least one row in the window.

Revision ledger — 0 backward revision(s) recorded for OVR

Backward revisions are values upstream later replaced for a date we had already archived. The before-value is retained — that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards.

The ledger query ran during generation and returned 0 rows for OVR. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions.

Estate grades for OVR (graded 2026-08-20 13:54:15.000)

Served by /v1/network/OVR — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The split is published exactly as computed: node quality A and dev velocity A sit next to a revenue F (the engines see no protocol fee telemetry in the estate) and a data-coverage D — the unflattering grades ship with the flattering ones, unsmoothed.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–3 hit the same upstream endpoints our collectors do (the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given, id ovr); command 4 hits this estate's public API, where every row carries the same source / as_of / verify_url fields. One polite call per endpoint, no hammering.

# 1) Market reference (CoinGecko public API — the coingecko.com browser
#    coin page 403s plain curl, so the programmatic endpoint is given):
# CoinGecko public markets API (the endpoint family our collector
# reads for the price/supply/cap rows) — the coingecko.com browser
# coin page 403s plain curl, so the programmatic endpoint is given:
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=ovr" | python3 -m json.tool
# 1b) Human-view check of the verify_url target (documented 403 on plain curl):
curl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/ovr"
# 2) Protocol TVL + staking (DefiLlama protocols API — the same GET
#    the collector runs; the last tvl point and the staking bucket
#    are the two numbers the section above holds):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/protocol/ovr" | python3 -c "import json,sys; d=json.load(sys.stdin); s=(d.get(chr(39)+tvl+chr(39)) or []); print('tvl_last', s[-1] if s else None); print('staking', (d.get('currentChainTvls') or {}).get('staking'))"
# 3) Chain-side token endpoint (Blockscout keyless JSON — supply + holders):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x21bfbda47a0b4b5b1248c767ee49f7caa9b23697" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total_supply', d.get('totalSupply')); print('holders', d.get('holders'))"
# 3b) Chain-side transfers counter (Blockscout keyless JSON):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x21bfbda47a0b4b5b1248c767ee49f7caa9b23697/counters" | python3 -c "import json,sys; d=json.load(sys.stdin); print('transfers', d.get('transfers_count'))"
# 3c) Chain-side contract-address counters (Blockscout keyless JSON):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0x21bfbda47a0b4b5b1248c767ee49f7caa9b23697/counters" | python3 -c "import json,sys; d=json.load(sys.stdin); print('transactions', d.get('transactions_count')); print('gas_used', d.get('gas_used'))"
# 3d) Chain-side holders rows (Blockscout keyless JSON):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x21bfbda47a0b4b5b1248c767ee49f7caa9b23697/holders" | python3 -c "import json,sys; d=json.load(sys.stdin); items=d.get('items') or []; print('holder_rows', len(items), items[0].get('value') if items else None)"
# 4) This estate's public API row for OVR:
curl -s "https://kairossignal.com/v1/network/OVR" | python3 -m json.tool | head -60

Method & honesty notes. All counts are queries against the live ledger at generation time, not restamped copy — this page is regenerated by gen_deep_dive_ovr.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. Comparability grades come from the served canonical-metric system via its own resolver: total_supply maps to token_supply_total (question-verified). The remaining series are OVR-native market/chain metrics with no cross-network concept; grading them would be fabrication, so they are labelled "ovr-native (unmapped)". No first-party family: the catalog lists has_public_stats_api = 0 for OVR, the ledger holds zero first_party_api rows for this symbol, and no self-reported-telemetry section exists on this page — that is absence, not zero. No github family: the ledger holds zero github rows for this symbol; none are fabricated. The chain-side family reads token 0x21bfbda47a0b4b5b1248c767ee49f7caa9b23697 on Ethereum mainnet via eth.blockscout.com's public API — the catalog's own token_address, verified against the collector's TOKENS entry before build; OVR is not in the collector's supply-override registry, so its supply rows are the plain un-renamed chain reads. The on-chain total supply is a separate measurement from the CoinGecko total/max supply references — at generation all three read the same figure (~89.89M tokens), shown side by side, never merged. The DefiLlama TVL and staking rows are upstream's own published quantities, labelled as such wherever they appear, kept as two separate dimensions, and never summed, netted, or reconciled. The headline TVL series for OVR answers 0 upstream — that zero is upstream's data, held as published, never relabelled a gap and never smoothed into the staking figure; the generation-time re-fetch of upstream's answer is quoted in the TVL section above. Chain-side balances and counters are published raw, never differenced into rates. The estate grades section (if present) was fetched live from the estate's own API during this generating process; on any fetch failure the section is omitted rather than cached. Where a section has no data, it is absent — we do not publish zeros for gaps (the one zero PUBLISHED on this page — tvl_usd — is upstream's own answered zero, explicitly caveated, not a gap-fill). Upstream probes ran serially by this generator immediately before rendering: CoinGecko markets API (ovr) HTTP 200; DefiLlama protocols API (ovr) HTTP 200; Blockscout token API (OVR ERC-20) HTTP 200; Blockscout token counters API (OVR) HTTP 200; Blockscout address counters API (OVR) HTTP 200; estate /v1/network/OVR HTTP 200.