OriginTrail (TRAC) — the network, measured

Generated 2026-09-02T15:53:34Z from live ClickHouse queries against this estate's ledger. Held inventory: 8,154 observations · 32 distinct series · 4 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 15:49:30 · 8,154/8,154 rows carry a verify_url. 32 series refreshed in the last 24h (750 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.

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. This estate holds NO on-chain token telemetry for TRAC (the contract lives on Base/Ethereum; no EVM RPC reads are in the ledger), so the CoinGecko supply rows are the only supply figures on this page and are labelled as market-reference, not chain reads.

Substrate chain state — OriginTrail's own RPC, read hourly

Chain state read from https://astrosat-parachain-rpc.origin-trail.network — the OriginTrail network's own public Substrate JSON-RPC endpoint, which makes these genuine first-party reads even though the catalog lists no stats API (has_public_stats_api = 0). finalized_block_height comes from chain_getHeader and chain_health_peers from system_health. The collector writes a row only when a second confirmation read corroborates the first (block height must be advancing; peer count a sane non-negative integer) — rows that fail the gate are skipped, never invented. The peer figure is the RPC node's own libp2p peer count, not a network-wide total. The catalog's chains field (base,ethereum) describes the token contract's chains, not this parachain — both facts are shown as the estate holds them.

Dev velocity — GitHub, as held (repo migrated)

Raw GitHub API counters for the OriginTrail organisation and its tracked repos. dev_public_repos is an ORG-level counter (verify link points at /orgs/OriginTrail); the rest are repo-level. The tracked repo MOVED inside our archive: rows collected through 2026-08-23 carry /repos/OriginTrail/dkg-engine verify_urls and rows collected from 2026-09-02 carry /repos/OriginTrail/dkg-node. The table's per-metric verify link points at the repo of the LATEST row; the archived generation's link is listed below and in the buyer-verify commands. dev_days_since_push is a collector-computed staleness figure from the repo's pushed_at; the others are raw API counters, never differenced into rates.

Repo migration as held — each generation keeps its own verify_url:

First-party one-off — FROZEN row, as held

A single finalized_block_height row read ONCE from the same OriginTrail astrosat RPC on 2026-08-10T00:04:09Z (source family first_party_api). It is a single-day snapshot, not a flowing series, and it is superseded by the hourly substrate_rpc series of the same metric shown above. It is published exactly as held — the estate re-anchors its ledger rows daily into Bitcoin-anchored OpenTimestamps Merkle batches, which preserves integrity and point-in-time verifiability but does not make a frozen row fresh. No re-collection of this one-off is implied.

Full metric inventory — 32 measured series, each with provenance

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

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

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

Served by /v1/network/TRAC — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The engines read only third-party and chain-state series; the F grades on dev-velocity and revenue and the D on data coverage are shown exactly as the engines emitted them, unflattering parts included. The F on revenue reflects that this estate holds no fee or revenue series for this network (DefiLlama lists no OriginTrail protocol-fees entry) — an absence, published as an absence.

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 OriginTrail RPC commands replay the collector's real JSON-RPC methods; the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given); command 4 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) OriginTrail's own public Substrate RPC — peer count (system_health), as of 2026-09-02T15:53:34Z:
curl -s -H "User-Agent: kairos-check" "https://astrosat-parachain-rpc.origin-trail.network" -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"system_health","params":[]}' | python3 -m json.tool
# 1b) Same endpoint — finalized block header (chain_getHeader):
curl -s -H "User-Agent: kairos-check" "https://astrosat-parachain-rpc.origin-trail.network" -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"chain_getHeader","params":[]}' | python3 -m json.tool
# 2) Dev velocity — current tracked repo (GitHub public API):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/OriginTrail/dkg-node" | python3 -c "import json,sys; d=json.load(sys.stdin); print('stars', d.get('stargazers_count')); print('forks', d.get('forks_count')); print('pushed_at', d.get('pushed_at'))"
# 2b) Org-level repo counter (same API, org endpoint):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/OriginTrail" | python3 -c "import json,sys; d=json.load(sys.stdin); print('public_repos', d.get('public_repos'))"
# the archived generation of repo rows (through 2026-08-23) verifies against:
curl -s -o /dev/null -w "%{http_code}\n" -H "User-Agent: kairos-check" "https://api.github.com/repos/OriginTrail/dkg-engine"
# 3) 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=origintrail" | python3 -m json.tool
# 4) This estate's public API row for TRAC:
curl -s "https://kairossignal.com/v1/network/TRAC" | 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_trac.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 TRAC-native network/market/on-chain metrics with no cross-network concept; grading them would be fabrication, so they are labelled "trac-native (unmapped)". The CoinGecko change-column generation two (from 2026-08-22) is shown from its first held row, never back-filled; 24h staleness is computed live at generation, never remembered. The chain-state rows are read from the network's own RPC by a collector that dual-reads and gates every value before writing. The peer-count row is the RPC node's own peer set, published with that scope attached. The GitHub repo migration (dkg-engine → dkg-node, visible in the verify_urls across the archive) is shown as two held generations, never merged or rewritten. The frozen one-off first-party row stays frozen: re-anchored daily for integrity, never re-collected and never passed off as flowing. Where a section has no data — as with fees and revenue, which this estate holds no series for — it is absent; we do not publish zeros for gaps. Upstream probes run serially by this generator immediately before rendering: OriginTrail Substrate RPC (system_health) ok(json); GitHub repo API (dkg-node) 200; GitHub org API 200; CoinGecko markets API 200; estate /v1/network/TRAC 200.