Phala (PHA) — the network, measured

Generated 2026-10-17T04:58:52Z from live ClickHouse queries against this estate's ledger. Held inventory: 38,823 observations · 48 distinct series · 6 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 04:51:55 · 38,823/38,823 rows carry a verify_url. 39 series refreshed in the last 24h (730 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number 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.

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 CoinGecko circulating_supply / total_supply rows and the chain reads are separate measurements from separate endpoints, shown side by side and never merged.

On-chain reads — Ethereum (RPC + Blockscout), as held

Chain reads for the PHA ERC-20 token (0x6c5ba916…, 18 decimals): total supply, holder count, transfer count, the largest single holder's balance, and the token contract's gas/transaction counters. The Phala/Khala native-chain endpoints were unreachable from this estate when probed (2026-08-25), so the ERC-20 token ledger on Ethereum is the on-chain read we hold. Dual-source series (publicnode RPC, deep_stats_eth_blockscout, evm_blockscout) are separate rows with their own stamps — the value and stamp gaps are shown, not smoothed. At generation the top-holder read is 298,951,548.563 tokens — 29.90% of the chain total-supply read (1,000,000,000), a live ratio of the two held values, not a new source. A balance of that size is typically an exchange, treasury or staking contract; it is a raw read and is never labelled as owner concentration.

Dev velocity — GitHub, as held

Public repo activity for Phala Network: the Phala-Network/phala-blockchain repo for stars, forks, issues, watchers and days-since-push, plus the org-level public-repo count. Daily snapshots; each row keeps its own as-of stamp.

Full metric inventory — 48 measured series, each with provenance

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

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

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); command 5 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) Market reference (CoinGecko public API) — keyless, as of 2026-10-17T04:58:52Z:
# 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=pha" | python3 -m json.tool
# 2) On-chain supply (Ethereum public RPC, eth_call):
# On-chain supply (Ethereum public RPC — eth_call totalSupply on
# the PHA ERC-20 token contract; this is the deep_stats_eth_rpc path):
curl -s -X POST "https://ethereum-rpc.publicnode.com" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x6c5ba91642f10282b576d91922ae6448c9d52f4e","data":"0x18160ddd"},"latest"]}' | python3 -m json.tool
# 3) Token stats (Blockscout public API):
# Blockscout token stats (holders_count, token_transfers_total,
# evm_blockscout supply read — the exact endpoint the rows cite):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x6c5ba91642f10282b576d91922ae6448c9d52f4e" | python3 -m json.tool | head -25
# 3b) Token contract counters (Blockscout address counters):
# Blockscout address counters (contract_transactions_total,
# contract_gas_used_total — the PHA token contract on Ethereum):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0x6c5ba91642f10282b576d91922ae6448c9d52f4e/counters" | python3 -m json.tool | head -20
# 3c) Top holders (Blockscout holders endpoint):
# Blockscout top holders (top_holder_balance — the source of
# the largest-single-holder row):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x6c5ba91642f10282b576d91922ae6448c9d52f4e/holders" | python3 -m json.tool | head -30
# 4) Dev velocity (GitHub public API):
# GitHub public API — the repo our dev-velocity series reads:
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/Phala-Network/phala-blockchain" | python3 -m json.tool | head -20
# 4b) Org-level repo counter (same API, org endpoint):
# Org-level public-repo counter (same API, org endpoint):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/Phala-Network" | 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 PHA:
curl -s "https://kairossignal.com/v1/network/PHA" | 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_pha.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 PHA-native chain/market metrics with no cross-network concept; grading them would be fabrication, so they are labelled "pha-native (unmapped)". The estate holds no DefiLlama fees, revenue or TVL rows for PHA — no such section exists on this page; that is absence, not zero, and the DefiLlama queries rerun at every regeneration so a section would appear the day rows exist. Dual-source series (chain supply, holders, transfers) are published as separate rows with their own stamps, never merged; the day-ago gaps between the two Blockscout generations are stated, not smoothed. The supply reads (RPC chain, Blockscout, CoinGecko total) are published side by side, never merged; the two chain reads and the CoinGecko total-supply reference all read the same value at generation — shown side by side, never merged. The CoinGecko circulating_supply row is a different quantity and is never netted against the chain reads. ethereum_block_height and ethereum_gas_price_gwei are Ethereum host-chain context for the ERC-20 read, never presented as Phala network telemetry. The top-holder percentage is a live ratio of two held reads, labelled as such; the underlying balance may be an exchange, treasury or staking contract and is never relabelled as owner concentration. 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: CoinGecko markets API HTTP 200; Publicnode Ethereum RPC HTTP 200; Blockscout token API HTTP 200; Blockscout address counters API HTTP 200; GitHub Phala-Network/phala-blockchain HTTP 200; estate /v1/network/PHA HTTP 200.