Mysterium (MYST) — the network, measured

Generated 2026-09-02T16:45:52Z from live ClickHouse queries against this estate's ledger. Held inventory: 7,857 observations · 39 distinct series · 3 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 16:34:01 · 7,857/7,857 rows carry a verify_url. 25 series refreshed in the last 24h (715 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.

Network telemetry — Mysterium's own discovery API, as held

First-party telemetry read from the network's own public stats endpoint (discovery.mysterium.network/api/v4) — the endpoint the catalog names as this network's public stats API. nodes_total and countries_covered verify against /api/v4/countries; the proposal-family series and distinct_providers verify against /api/v4/proposals — each row keeps its own verify_url. The proposal-family series are a single-row snapshot in our archive (first held 2026-08-09): they are published from that first held row — never back-filled, never re-windowed. nodes_total and countries_covered carry dense daily histories over the 30-day window.

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. The circulating and total supply rows are different quantities (circulating vs total) and are never netted against each other; the estate holds no chain-read supply row for MYST, so there is no chain row to merge — absence, not zero.

Dev velocity — GitHub, as held

Raw GitHub API counters for the Mysterium repositories — dev_public_repos reads the mysteriumnetwork org account, the rest read the mysteriumnetwork/node repo. Each row keeps its own as-of stamp; counters are published raw, never differenced into rates.

Full metric inventory — 39 measured series, each with provenance

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

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

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

Served by /v1/network/MYST — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The overall grade is C and it is published as computed: node quality F alongside dev velocity B and data-coverage B, exactly as the engines emitted them. Node quality F and revenue F are the engines' own outputs as served — not derived from any series on this page, and not smoothed. The dilution-risk grade is MINIMAL, also as served.

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 (Mysterium's own public discovery API, one polite call each); command 3 hits the CoinGecko programmatic markets endpoint (the coingecko.com browser coin page 403s plain curl, so the programmatic endpoint is given, id mysterium); command 4 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) Mysterium's own discovery API — node-count/countries endpoint (as of 2026-09-02T16:45:52Z):
curl -s -H "User-Agent: kairos-check" "https://discovery.mysterium.network/api/v4/countries" | python3 -c "import json,sys; d=json.load(sys.stdin); print('countries', len(d) if isinstance(d, list) else list(d.keys())[:5])"
# 1b) Same API — proposals endpoint (proposals/provider-count family):
curl -s -H "User-Agent: kairos-check" "https://discovery.mysterium.network/api/v4/proposals" | python3 -c "import json,sys; d=json.load(sys.stdin); print('proposals', len(d) if isinstance(d, list) else list(d.keys())[:5])"
# 2) Market reference (CoinGecko public API, id mysterium):
# 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
# (note the id: mysterium):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=mysterium" | python3 -m json.tool
# 2b) Human-view check of the verify_url target (the browser coin page 403s plain curl — that is the documented 403, the programmatic command above is the verification path):
curl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/mysterium"
# 3) This estate's public API row for MYST:
curl -s "https://kairossignal.com/v1/network/MYST" | 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_myst.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: nodes_total maps to nodes_total (unit-verified) and total_supply maps to token_supply_total (question-verified). The remaining series are MYST-native market/telemetry metrics with no cross-network concept; grading them would be fabrication, so they are labelled "myst-native (unmapped)". The proposal-family series and distinct_providers are a single-row snapshot in our archive (first held 2026-08-09): they are published from first held row, never back-filled, never re-windowed. nodes_total and countries_covered carry dense daily histories and are shown from first held row across the 30-day window. The CoinGecko circulating and total supply rows are different quantities (circulating vs total) and are never netted; the estate holds no chain-read supply row for MYST, so no chain-vs-reference reconciliation exists or is implied — absence, not zero. The estate holds no DefiLlama fees, revenue, or TVL-bucket rows and no other first-party network counters beyond the discovery-API families shown — those sections are absent rather than zero-filled, and the queries rerun at every regeneration. The estate grades are published exactly as the engines served them, unflattering parts included; node quality F and revenue F are the engines' own outputs, not derived from any series on this page. 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: Mysterium discovery countries API HTTP 200; Mysterium discovery proposals API HTTP 200; CoinGecko markets API (mysterium) HTTP 200; estate /v1/network/MYST HTTP 200.