Acurast (ACU) — the revision ledger

Generated 2026-09-02T20:12:52Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for Acurast: 7,675 observations · 32 distinct series · 3 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 19:49:20 · every one of the 7,675 rows carries a verify_url · 24 series refreshed in the last 24h (664 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where Acurast's archive 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. ACU (the catalog name here is Acurast, category compute; the token trades on base, binance-smart-chain, ethereum under contract 0x216b3643ff8b7bb30d8a48e9f1bd550126202add) publishes a first-party processor-management stats API (processor-management.acurast.com) that this estate polls directly — the cached device/processor counts and the cache-size family — plus GitHub repo telemetry and CoinGecko's market series alongside.

Revision ledger — 0 backward revision(s) recorded for ACU

The ledger query ran during generation and returned 0 rows for ACU. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions?symbol=ACU (the same query this page ran, served live), and a restatement would appear on this page the day the detector records one. /v1/revisions?symbol=ACU cross-check passed: the served API reports 0 row(s), matching the ledger count rendered on this page.

Why zero is the interesting answer. The detector does not skip ACU — below, the live intersection shows exactly which cumulative-by-construction series the archive holds for this network and which it does not, the fleet gauges that dominate ACU's archive are shown raw end to end, and the gauge table proves they are excluded by construction, not by neglect. Acurast's published series are fleet-state gauges — device counts, processor counts, cache sizes — which legitimately move both ways as processors join and leave the fleet. None of them is a cumulative counter, so nothing entered the ledger. Publishing an empty ledger as a live query result — instead of padding it with gauge noise — is the same retention discipline the ledger exists to sell.

What the detector watches for Acurast — 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 (75 declared names, so this page can never drift from the detector) — with what the daily archive holds for ACU.

Live query result: 0 watchlist series held for ACU. The intersection query ran during generation and returned an empty set — none of the 75 cumulative-by-construction metric families the detector watches appear in ACU's daily archive. This is the structural zero behind the ledger count above, published as the query found it: Acurast's series in this estate are fleet-state gauges, not monotone counters.

The gauges behind the ledger — ACU's fleet series, end to end

These are the actual series the daily archive holds for ACU, rendered live. Each is a fleet-state gauge that cannot be a revision signal by construction — processors join and leave the fleet, so the counts legitimately move both ways — and the monotonicity verdict beside each table is computed in this process from the same rows shown, so the summary cannot drift from the data. The raw runs are the evidence; the reader does not have to trust the summary.

BATTERY_HEALTH_CACHE_SIZE — 27 snapshot day(s). Live verdict from the rows below: NOT monotone — see the raw rows below.

DEVICE_STATUS_CACHE_SIZE — 27 snapshot day(s). Live verdict from the rows below: NOT monotone — see the raw rows below.

NETWORK_TYPE_CACHE_SIZE — 27 snapshot day(s). Live verdict from the rows below: flat across its entire held window — every snapshot holds the identical value.

PROCESSOR_CACHE_CAPACITY — 27 snapshot day(s). Live verdict from the rows below: flat across its entire held window — every snapshot holds the identical value.

PROCESSOR_CACHE_SIZE — 27 snapshot day(s). Live verdict from the rows below: NOT monotone — see the raw rows below.

cached_devices — 24 snapshot day(s). Live verdict from the rows below: NOT monotone — see the raw rows below.

cached_processors — 24 snapshot day(s). Live verdict from the rows below: NOT monotone — see the raw rows below.

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 fleet or market change, not upstream rewriting history. The cache gauges (device counts, processor counts, cache sizes) and the CoinGecko price, market-cap and rank classes dominate this table for ACU — a smaller device count is processors leaving the fleet, not a rewrite. Publishing them as "revisions" would be exactly the fake-metric behaviour this product exists to eliminate.

Same-timestamp conflicting values on record for ACU: 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 ACU 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 (18 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 deleted; 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 deleted. Population gauges (provider sets, node counts, prices, capacity, rolling windows) legitimately move both ways and are deliberately excluded — a drop there is a real 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.

The snapshot archive the detection runs over

ACU's slice of depin_daily: 457 rows over 27 snapshot days (2026-08-06 → 2026-09-01), from 3 source family. Each snapshot is a same-day capture of every series the collectors touched; the detector diffs consecutive snapshots of cumulative series across this window. This is the substrate the zero above is measured over — not an assumption, a measured archive.

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

Served by /v1/network/ACU — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, published exactly as the engines emitted them, unflattering parts included.

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); command 3 hits Acurast's own processor-management API the fleet rows came from; command 4 is the CoinGecko origin page; command 5 is the estate's graded network row; command 6 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for ACU — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=ACU" | 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) Acurast's own processor-management stats API (the first_party_api origin):
curl -s -H "User-Agent: kairos-check" "https://processor-management.acurast.com/processor/debug/cache/status" | python3 -m json.tool | head -40
# 4) CoinGecko ACU page (the market-series origin; browser-verified, bot-walled to curl):
curl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/acurast"
# 5) This estate's public API row for ACU (grades + provenance):
curl -s "https://kairossignal.com/v1/network/ACU" | python3 -m json.tool | head -60
# 6) 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_acu.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The ACU revision count is the live result of SELECT count() FROM default.depin_revision_ledger WHERE network='ACU'; the page refuses to ship if the served /v1/revisions?symbol=ACU disagrees with it. The 18 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 same-stamp conflict check is the honest live answer: 0 groups in depin_onchain and 0 in depin_daily. Upstream probes ran serially by this generator immediately before rendering: CoinGecko ACU page (browser-verified origin; 403 here is its bot wall) HTTP 403; Acurast's own processor-management stats API (the first_party_api origin) HTTP 200; estate /v1/revisions?symbol=ACU HTTP 429; estate /v1/network/ACU HTTP 429.