GEOD (Geodnet) — the network, measured

Generated 2026-09-02T17:28:14Z from live ClickHouse queries against this estate's ledger. Held inventory: 9,849 observations · 41 distinct series · 4 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 16:58:01 · 9,849/9,849 rows carry a verify_url. 40 series refreshed in the last 24h (858 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

4 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 self-telemetry — GEOD's own miner-statistics API, as held (first-party)

First-party reads of GEOD's OWN public miner-statistics API (websiteapi.geodnet.com/api/front/getMinerStatistics, keyless GET) by this estate's collectors: the network's own counts of satellite miners, cities, and countries, plus its cumulative usage-revenue counter. This is the network's self-reported supply-side telemetry — the strongest provenance class in the ledger: the upstream is the network itself, and each row's verify_url re-executes the same keyless GET the collector ran (the endpoint answers one JSON object — total_miner / total_city / total_country / total_usage_revenue — so every verify command on this page re-runs exactly that GET, probe-verified HTTP 200 before this page shipped). The three coverage counters flow near-daily in the archive (~570 rows each); total_usage_revenue was collected 2026-08-09 and has exactly 1 row held — newer rows are absent from the ledger and that absence is shown, not smoothed.

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/max supply rows are different quantities (circulating vs total vs cap) and are never netted against each other.

Protocol fees & revenue — DefiLlama fees dimension, as held

DefiLlama's fees dimension for Geodnet (api.llama.fi /summary/fees/geodnet). Upstream's OWN published methodology for this protocol: fees are INFERRED FROM GEOD BURNS — burns represent 80% of total fees, so total = burns / 0.8 — and Revenue equals the same station-access fees (80% of fees buy back and burn GEOD, 20% supports the foundation). These are therefore burn-derived estimates by DefiLlama's own published definition, held and shown as such. The fees_24h/7d/30d/1y/alltime and revenue_24h/30d series are different windows of that same derivation — the fees_* and revenue_* pairs carry the same figures at generation and are never netted, differenced, or merged with each other, with the first-party usage counter, or with any market row. Cumulative counters are published raw — never differenced into rates.

Dev velocity — GitHub, as held

Raw GitHub API counters for the geodnet org — repo-level (geodnet/whitepaper) and one org-level row (public_repos via api.github.com/orgs/geodnet, a different measurement from the repo rows; each keeps its own verify_url). Counters are published raw, never differenced into rates; dev_days_since_push is a raw time delta from the repo's real pushed_at timestamp. Honesty note: the held repo is a whitepaper repository whose last push is 2022-10-18 — the counters are held as measured and are not smoothed, re-based, or swapped for a more flattering repository.

Full metric inventory — 41 measured series, each with provenance

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

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

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

Served by /v1/network/GEOD — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The unflattering grades (if any) are published exactly as computed: the estate's engines score GEOD against their own windows and inputs, and the measured-series count this page derives is the coverage engine's input — the unflattering parts ship with the flattering ones, unsmoothed.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–4 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 geodnet); command 5 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) GEOD's OWN miner-statistics API — the network's self-reported supply-side counts (keyless, as of 2026-09-02T17:28:14Z):\ncurl -s "https://websiteapi.geodnet.com/api/front/getMinerStatistics" | python3 -m json.tool
# 1b) Same endpoint (the single GET answers miners, cities, countries and usage revenue at once; shown twice for direct comparison with the rows above):\ncurl -s "https://websiteapi.geodnet.com/api/front/getMinerStatistics" | python3 -m json.tool
# 2) Protocol fees (DefiLlama public API — burn-inferred per upstream methodology):\ncurl -s "https://api.llama.fi/summary/fees/geodnet" | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('total24h'), d.get('total30d'), d.get('totalAllTime'))"
# 2b) Protocol revenue (DefiLlama dailyRevenue):\ncurl -s "https://api.llama.fi/summary/fees/geodnet?dataType=dailyRevenue" | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('total24h'), d.get('total30d'))"
# 3) Market reference (CoinGecko public API — the coingecko.com browser\n#    coin page 403s plain curl, so the programmatic endpoint is given):\n# 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
# (id: geodnet):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=geodnet" | python3 -m json.tool
# 3b) 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):\ncurl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/geodnet"
# 4) Dev velocity, repo-level (GitHub public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/geodnet/whitepaper" | python3 -m json.tool | head -20
# 4b) Dev velocity, org-level (GitHub public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/geodnet" | python3 -c "import json,sys; print('public_repos', json.load(sys.stdin).get('public_repos'))"
# 5) This estate's public API row for GEOD:\ncurl -s "https://kairossignal.com/v1/network/GEOD" | 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_geod.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_miners maps to providers_total (unit-verified), total_countries maps to countries_covered (question-verified), and total_supply maps to token_supply_total (question-verified). The remaining series are GEOD-native market/telemetry metrics with no cross-network concept; grading them would be fabrication, so they are labelled "geod-native (unmapped)". No chain-side rows: the catalog lists GEOD's chains as polygon-pos,solana, but the estate holds no EVM or Solana on-chain telemetry for GEOD — no token-holder, transfer, or contract counters exist in the ledger, no such section exists on this page, and that is absence, not zero. The first-party family reads GEOD's own miner-statistics API — the network's self-reported counts, labelled as such and never merged with the market-reference or fees rows. The DefiLlama fees and revenue rows are burn-inferred by upstream's own published methodology (burns = 80% of fees; total = burns / 0.8; revenue = the same fees) and are labelled as such wherever they appear; the fees_*/revenue_* pairs carry the same figures at generation and are never netted or merged. The first-party total_usage_revenue counter (1 archived row) is a different measurement from the DefiLlama windows — network's own cumulative counter vs burn-inferred windows — shown side by side, never reconciled into one number. GitHub rows mix repo-level and org-level counters; both are labelled with their own provenance and never combined, and dev_days_since_push is a raw time delta from a real timestamp. The estate grades are published exactly as the engines served them, unflattering parts included; they 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: GEOD miner-statistics API (keyless GET) HTTP 200; CoinGecko markets API (geodnet) HTTP 200; DefiLlama fees summary (geodnet) HTTP 200; DefiLlama dailyRevenue summary (geodnet) HTTP 200; GitHub geodnet/whitepaper HTTP 200; GitHub orgs/geodnet HTTP 200; estate /v1/network/GEOD HTTP 200.