Onocoy (ONO) — the network, measured

Generated 2026-09-02T15:17:26Z from live ClickHouse queries against this estate's ledger. Held inventory: 8,580 observations · 29 distinct series · 3 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 14:49:20 · 8,580/8,580 rows carry a verify_url. 28 series refreshed in the last 24h (792 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 deeper change columns start 2026-08-22 in our archive (each metric's caveat in the full inventory states its own first-held row) and are shown from their first held row.

Station telemetry — Onocoy's own explorer API, as held

Read from the network's own public endpoint (api.onocoy.com/api/v1/explorer): the full GNSS reference-station list with each station's status. At generation, 3 series flow fresh (station_count, stations_online, stations_validated); 1 — the stations_offline category count — survives only as an archived single row stamped 2026-08-09 23:52:30 from the collector's first generation, shown exactly as held and never merged with stations_online. Each row's label states which it is. All counts are raw category counts over one fetch of the station list, exactly as the endpoint reports them; nothing is re-derived or presented as flowing when it is not.

Station liveness — computed by the estate's utilisation engine

STATION_LIVENESS_PCT is the one ratio this estate derives: stations with status.is_up = true divided by stations listed, from a single fetch of Onocoy's own explorer endpoint (one population — the up-set is a subset of the listed set by construction; the engine refuses to publish if subset ordering inverts). Per the 2026-08-13 canonical-metric correction this is liveness — what fraction of deployed hardware is switched on — not utilisation; stations have no divisible capacity. The component counts it is derived from are published raw in the section above; the ratio itself is the only estate-computed figure on this page, and it is labelled as such.

Full metric inventory — 29 measured series, each with provenance

Every series held for ONO 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 ONO

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 ONO. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions.

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

Served by /v1/network/ONO — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The dilution, revenue and data-coverage grades are poor because the engines read the held series (no fee rows exist for ONO; the token has a high float-over-time schedule); they are published exactly as computed, including the unflattering ones.

Verify any cell yourself — the exact commands

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

# 1) The network's own explorer endpoint — keyless, as of 2026-09-02T15:17:26Z:
#    (prints: stations listed, stations up — the halves behind
#    station_count / stations_online / STATION_LIVENESS_PCT)
curl -s -H "User-Agent: kairos-check" "https://api.onocoy.com/api/v1/explorer" | python3 -c "import json,sys; d=json.load(sys.stdin); print(len(d), 'stations listed'); print(sum(1 for s in d if s.get('status',{}).get('is_up') is True), 'up')"
# 2) Market reference (CoinGecko public API):
# 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=onocoy-token" | python3 -m json.tool
# 3) This estate's public API row for ONO:
curl -s "https://kairossignal.com/v1/network/ONO" | 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_ono.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 ONO-native network/market metrics with no cross-network concept; grading them would be fabrication, so they are labelled "ono-native (unmapped)". Collection generations (fresh-flowing vs the archived single stations_offline row) are derived from row counts at generation and shown side by side as held, never summed, merged, or reconciled. STATION_LIVENESS_PCT is the only estate-computed ratio on the page and is labelled as such; it is liveness (up / listed), not utilisation, per the 2026-08-13 canonical-metric correction. The explorer counts stay raw category counts as Onocoy's explorer endpoint reports them — never differenced into rates. Where a section has no data, it is absent — we do not publish zeros for gaps. Upstream probes run serially by this generator immediately before rendering: Onocoy explorer station list HTTP 200; CoinGecko markets API HTTP 200; estate /v1/network/ONO HTTP 200.