Phala Network (PHA) — the revision ledger

Generated 2026-10-17T05:41:33Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for Phala Network: 38,828 observations · 48 distinct series · 6 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 05:41:01 · every one of the 38,828 rows carries a verify_url · 39 series refreshed in the last 24h (730 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where Phala Network's archive comes from

6 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. PHA publishes no first-party stats API of its own in this catalog — the network-side families here are public chain infrastructure (Ethereum PublicNode RPC block/supply reads and Ethereum Blockscout token and address-counter endpoints for 0x6c5ba91642f10282b576d91922ae6448c9d52f4e), with CoinGecko's market series and Phala-Network GitHub activity alongside.

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

The ledger query ran during generation and returned 0 rows for PHA. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions?symbol=PHA (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=PHA 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 PHA — below, the live intersection shows the 0 cumulative-by-construction series the archive holds for this network, each fully diffed across its whole snapshot window, and each rendered here end to end so the monotone runs are visible raw. Nothing moved backward. That is the structural zero: the detector was watching, the counters were fully exposed to it, and upstream did not rewrite history for this network in the window this estate holds. 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 Phala Network — 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 PHA. All three held series come from the Ethereum Blockscout counter family for the PHA token contract.

Live query result: 0 watchlist series held for PHA. The intersection query ran during generation and returned an empty set — none of the 11 cumulative-by-construction metric families the detector watches appear in PHA's daily archive. This is the structural zero behind the ledger count above, published as the query found it.

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

These are the actual counter trails the detector diffed for PHA, rendered live from the archive. Each is a series that cannot decrease unless upstream rewrote history — and each is monotonic across its entire held window, which is exactly why the ledger above is empty. The raw runs are the evidence; the reader does not have to trust the summary.

contract_gas_used_total — the cumulative gas burned by the PHA token contract (Ethereum Blockscout):

contract_transactions_total — the lifetime transaction counter for the PHA token contract (Ethereum Blockscout):

token_transfers_total — the lifetime transfer counter for the PHA token contract on Ethereum (Ethereum Blockscout) — the series class that produced real restatements for OVPP, AUKI, R1 and SOGNI elsewhere in this estate; monotonic here across all its held snapshots:

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 PHA: 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 PHA 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.

The snapshot archive the detection runs over

PHA's slice of depin_daily: 1,869 rows over 69 snapshot days (2026-08-09 → 2026-10-16), from 3 source families. 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.

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–4 hit the upstream families the network-side rows came from; 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 PHA — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=PHA" | 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) Ethereum Blockscout token endpoint for the PHA contract (counter origins):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x6c5ba91642f10282b576d91922ae6448c9d52f4e" | python3 -m json.tool | head -30
# 4) Ethereum Blockscout address counters for the PHA contract:
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0x6c5ba91642f10282b576d91922ae6448c9d52f4e/counters" | python3 -m json.tool | head -30
# 5) This estate's public API row for PHA (grades + provenance):
curl -s "https://kairossignal.com/v1/network/PHA" | 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_pha.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The PHA revision count is the live result of SELECT count() FROM default.depin_revision_ledger WHERE network='PHA'; the page refuses to ship if the served /v1/revisions?symbol=PHA 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 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 PHA page (browser-verified origin; 403 here is its bot wall) HTTP 403; Ethereum PublicNode RPC (the deep_stats_eth_rpc block/supply upstream) HTTP 301; Ethereum Blockscout token endpoint for the PHA contract (the blockscout upstream family) HTTP 200; Ethereum Blockscout address counters for the PHA contract (transfer counters' origin) HTTP 200; GitHub API Phala-Network/phala-blockchain (the github upstream family) HTTP 200; estate /v1/revisions?symbol=PHA HTTP 200; estate /v1/network/PHA HTTP 200.