NodeOps (NODE) — the network, measured

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

Fees & revenue — DefiLlama protocol data, as held

Protocol-level fees and revenue from DefiLlama's public summary API for the nodeops protocol. Fees rows verify against /summary/fees/nodeops; revenue rows against /summary/fees/nodeops?dataType=dailyRevenue — each row keeps its own verify_url. Every fee and revenue window held for NODE is currently non-zero upstream; values are published exactly as answered, never rounded for presentational comfort. Revenue is DefiLlama's dailyRevenue slice (fees kept by the protocol after provider payments) — a different measurement from fees, never netted against it on this page.

Ethereum-chain state — Blockscout, as held

Chain state for the Ethereum-mainnet token 0x2f714d7b…e37f43fb (catalog chains: binance-smart-chain,ethereum; this collector family reads the Ethereum deployment — the BSC deployment listed in the catalog is not read by this estate, and that absence is stated rather than papered over), from Ethereum Blockscout's public API: on-chain total supply, holder count, top-holder balance, and the transfer/contract counters. Counter series are sparse (11–13 rows each) — that is the archive's own shape, shown as held with row counts. top_holder_balance is a balance, not a concentration percentage. This is a different ledger object from the CoinGecko market reference; the two are never merged, and no ratio is derived between them.

GitHub dev telemetry — NodeOps-app org, as held

Development-activity counters from GitHub's public API: the NodeOps-app organisation's public-repository count (verify_url is the org endpoint) and the tracked repository's stars, forks, watchers, open issues and days-since-last-push (verify_url is the repo endpoint). These are single-repo and single-org counters as GitHub reports them — never aggregated, averaged, or extrapolated into a broader "developer activity" index on this page. The tracked repo's last-push age is shown as held at its latest read; the engines' Dev-Velocity grade below is computed from this family and published as computed, including when it is unflattering.

Full metric inventory — 43 measured series, each with provenance

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

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

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

Served by /v1/network/NODE — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The Dev-Velocity and Revenue grades are F and the data-coverage grade is D for this network; they are published exactly as computed, including the unflattering ones.

Engine narrative, verbatim: NODE (other): NQ=A(100%) Dil=ELEVATED Bot=C(85%) Dev=F Rev=F Data=D. Overall=D(40.3/100)

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; GitHub's unauthenticated quota is 60 req/hour per IP); command 5 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) Ethereum-mainnet token state (Blockscout public API), as of 2026-09-02T15:34:46Z:
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x2f714d7b9a035d4ce24af8d9b6091c07e37f43fb" | python3 -m json.tool | head -30
# 1b) Holders (same API family):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x2f714d7b9a035d4ce24af8d9b6091c07e37f43fb/holders" | python3 -m json.tool | head -30
# 1c) Transfer/contract counters (same API family):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0x2f714d7b9a035d4ce24af8d9b6091c07e37f43fb/counters" | python3 -m json.tool
# 2) Protocol fees (DefiLlama public API):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/nodeops" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total24h', d.get('total24h')); print('total30d', d.get('total30d'))"
# 2b) Protocol revenue (same family, revenue slice):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/nodeops?dataType=dailyRevenue" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total24h', d.get('total24h'))"
# 3) Market reference (CoinGecko public API):
# CoinGecko public markets API (the endpoint family our collector
# reads for the price/supply/cap rows). The browser coin page for
# this asset is /en/coins/node-2 (slug node-2 — CoinGecko's own
# disambiguation) and it 403s plain curl, so the programmatic
# endpoint is given:
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=node-2" | python3 -m json.tool
# 4) GitHub dev telemetry (GitHub public API; unauthenticated quota is
#    60 req/hour per IP — a 403 there is the rate limit, not a broken cell):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/NodeOps-app/atlas-operator" | python3 -c "import json,sys; d=json.load(sys.stdin); print('stars', d.get('stargazers_count')); print('pushed_at', d.get('pushed_at'))"
# 4b) The org's public-repo count (same API family):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/NodeOps-app" | python3 -c "import json,sys; d=json.load(sys.stdin); print('public_repos', d.get('public_repos'))"
# 5) This estate's public API row for NODE:
curl -s "https://kairossignal.com/v1/network/NODE" | 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_node.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 NODE-native network/market/on-chain/dev metrics with no cross-network concept; grading them would be fabrication, so they are labelled "node-native (unmapped)". THREE supply references are shown side by side as held, never summed, merged, or reconciled: CoinGecko's circulating/total/max supply, and Blockscout's on-chain token supply. 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 Blockscout counters stay raw cumulative counts as the endpoint reports them — never differenced into rates. The GitHub family stays single-repo/single-org counters — never aggregated into an index. 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: Blockscout Ethereum token API HTTP 200; Blockscout Ethereum holders API HTTP 200; Blockscout Ethereum counters API HTTP 200; DefiLlama fees API HTTP 200; DefiLlama revenue API HTTP 200; CoinGecko markets API HTTP 200; GitHub org API HTTP 200; GitHub repo API HTTP 200; estate /v1/network/NODE HTTP 200.