NodeOps (NODE) — the revision ledger

Generated 2026-10-17T05:34:58Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for NODE: 37,240 observations · 53 distinct series · 5 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 04:58:01 · every one of the 37,240 rows carries a verify_url · 42 series refreshed in the last 24h (692 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where NodeOps's archive comes from

5 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. NodeOps does not publish a first-party stats API — instead the estate collects four upstream families for it: CoinGecko's market series for NODE, DefiLlama's fees summary for nodeops (the all-time fees counter and its rolling windows), NodeOps-app GitHub activity, and Blockscout's counters for the NODE token contract itself (0x2f714d7b9a035d4ce24af8d9b6091c07e37f43fb on Ethereum, queried through eth.blockscout.com). The estate's own first-party collector re-snapshots the fee counters daily (depin_first_party).

Revision ledger — 4 backward revision(s) recorded for NODE

Backward revisions are values upstream later replaced for a date this estate had already archived. The before-value is retained alongside the replacement — both snapshot dates, both numbers — which is what no overwriting vendor keeps. /v1/revisions?symbol=NODE cross-check passed: the served API reports 4 row(s), matching the ledger count rendered on this page.

What the detector watches for NodeOps — the intersection, measured

The detector diffs every daily snapshot of every cumulative-by-construction series. Below is the live intersection of the estate detector's cumulative watchlist — imported directly from propintel/revision_ledger.py (11 declared names, so this page can never drift from the detector) — with what the daily archive holds for NODE. Five watched series are held and were fully diffed; none produced a backward pair. That is the structural content of the zero above: watchable counters exist, and they are clean.

The trails behind the zero — watched counters, end to end

These are the actual counter trails the detector diffed for NodeOps, rendered live from the archive. Each is a series that cannot decrease unless upstream rewrote history — which is exactly what makes their smooth monotonicity the proof behind the zero, and the same trails where a GRT/OVPP/EIGEN-style restatement would appear if it ever happened. The fee counters come from DefiLlama's fees summary for nodeops (the first_party_api family) re-snapshotted daily by the estate's own depin_first_party collector; the contract counters come from Blockscout's counters endpoint for the NODE token contract. A note on the fee counter's two spellings: DL_FEES_ALLTIME_USD (depin_first_party) and fees_alltime_usd (DefiLlama /overview/fees) are snapshots of the same upstream counter taken hours apart each day — the table below renders the value of whichever wrote last for each snapshot date, and the two agree on every overlapping snapshot date.

DL_FEES_ALLTIME_USD / fees_alltime_usd — the NodeOps lifetime protocol fees counter (USD, all-time):

token_transfers_total — the NODE token contract's lifetime transfer counter (Blockscout), the series class that produced real restatements for OVPP, AUKI, R1 and SOGNI elsewhere in the estate:

contract_transactions_total — transactions touching the NODE token contract (Blockscout):

contract_gas_used_total — cumulative gas used at the NODE token contract (Blockscout):

Gauges that moved backward — deliberately NOT revisions

These series fall outside the detector's cumulative-by-construction class (NOT_TRULY_CUMULATIVE and plain gauges in propintel/revision_ledger.py): a drop there is a real population or market change, not upstream rewriting history. Publishing them as "revisions" would be exactly the fake-metric behaviour this product exists to eliminate.

Same-timestamp conflicting values on record for NODE: none

The task-level conflict check, run live: any (metric, timestamp) family where this estate recorded two or more different values. The query ran at generation and returned 0 groups in both depin_onchain and depin_daily — every (metric, timestamp) pair the estate holds for NODE carries exactly one value. Zero here is the live query result, not a gap; the archive kept every write it made, and none of them disagree.

The ledger, live — every restatement recorded estate-wide (39 deduped events)

Deduped on revision identity exactly as /v1/revisions dedupes it. This is the same feed a subscriber polls; it is rendered live from ClickHouse at generation, not copied from a snapshot. Each row is an upstream source replacing the value of a (network, metric, date) it had already published — after this estate recorded the original. The superseded value is retained, never overwritten; that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards.

How detection works — and what it cannot see

The detector (propintel/revision_ledger.py) diffs every daily snapshot this estate holds of every cumulative-by-construction series — counters that cannot decrease unless upstream rewrote them (block heights, transaction and transfer counters, lifetime fees). A row enters default.depin_revision_ledger iff two snapshots disagree for an already-observed date; zero human judgement. Resolution rule: latest observation wins for current-state reads, the superseded value is retained, never overwritten. Population gauges (provider sets, node counts, prices, capacity) legitimately move both ways and are deliberately excluded — a drop there is a real population change, not a rewrite; the gauge table on this page is the worked example. Honest boundary: this catches value-history rewrites ex-post; identical-schema semantic drift with plausible values is what the hash-pinned derivation_replay layer is for. The detector's full classification is inspectable at /v1/revisions and frozen daily at /revision-ledger/REVISIONS_20260902.json.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–2 hit this estate's public API (the same rows this page queried — every row carries source / as_of / verify_url); commands 3–5 hit the upstream families the network-side rows came from; command 6 is the estate's graded network row; command 7 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for NODE — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=NODE" | python3 -m json.tool
# 2) The estate-wide feed (every network, both sides of every diff):
curl -s "https://kairossignal.com/v1/revisions" | python3 -m json.tool | head -80
# 3) DefiLlama's fees summary for nodeops (the fees counters' origin):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/nodeops" | python3 -m json.tool | head -40
# 4) Blockscout counters for the NODE token contract (on-chain counters' origin):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0x2f714d7b9a035d4ce24af8d9b6091c07e37f43fb/counters" | python3 -m json.tool | head -30
# 5) GitHub API for NodeOps-app/atlas-operator (the dev-velocity upstream family):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/NodeOps-app/atlas-operator" | python3 -m json.tool | head -30
# 6) This estate's public API row for NODE (grades + provenance):
curl -s "https://kairossignal.com/v1/network/NODE" | python3 -m json.tool | head -60
# 7) The public daily snapshot of the ledger (frozen copy):
curl -s -o /dev/null -w "%{http_code}\n" "https://kairossignal.com/revision-ledger/REVISIONS_20260902.json"

Method & honesty notes. All counts are queries against the live ledger at generation time, not restamped copy — this page is regenerated by gen_revision_page_node.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The NODE revision count is the live result of SELECT count() FROM default.depin_revision_ledger WHERE network='NODE'; the page refuses to ship if the served /v1/revisions?symbol=NODE disagrees with it. The 39 estate-wide events shown are deduped on revision identity (deterministic hash of network, metric, current_date, prior_date) exactly as the API dedupes them; detected_at is the first detection and never moves. Series absent from a section are absent, not zero: the daily-snapshot ledger for NODE is genuinely empty today — because every watched counter the archive holds proved monotonic under the detector's diff, a measured negative published as found, with the full trails rendered above — and this page says so instead of inventing restatements. The same-stamp conflict check is likewise the honest live answer: 0 groups in depin_onchain and 0 in depin_daily. Upstream probes ran serially by this generator immediately before rendering: api.llama.fi /summary/fees/nodeops (the fees upstream: the all-time fees counter and its rolling windows) HTTP 200; eth.blockscout.com counters for the NODE token contract (the evm_blockscout upstream: transactions / gas / transfers) HTTP 200; GitHub API NodeOps-app/atlas-operator (the github upstream family) HTTP 200; CoinGecko NODE page (browser-verified origin; 403 here is its bot wall) HTTP 403; estate /v1/revisions?symbol=NODE HTTP 200; estate /v1/network/NODE HTTP 200.