peaq (PEAQ) — the network, measured

Generated 2026-09-02T15:02:51Z from live ClickHouse queries against this estate's ledger. Held inventory: 8,814 observations · 42 distinct series · 8 upstream sources · first row 2026-08-09 23:24:18 · newest row 2026-09-02 14:58:01 · 8,814/8,814 rows carry a verify_url. 42 series refreshed in the last 24h (870 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

8 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, 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. All 24 market series start 2026-08-22 in this archive (coingecko id peaq-2) and are shown from their first held row. The coingecko.com browser coin page 403s plain curl — verify through the programmatic markets endpoint given in the commands section.

Chain telemetry — Substrate JSON-RPC (substrate_rpc), as held

Read from peaq's public Substrate JSON-RPC (peaq.api.onfinality.io/public) by the estate's substrate_rpc collector with a double-read gate: every value written must come from that run's live read and a second confirmation read must corroborate it (block height must be ≥ the captured height — the chain is live and advancing; peer count must be a sane non-negative int). Rows that fail the gate are skipped, never invented, never back-filled. chain_health_peers is one node's own libp2p peer count at read time — a snapshot, not a network total. Both series flow fresh every ~10 minutes.

Single-observation seed metrics — held as read, never refreshed

Series exist as exactly one observation each, stamped 2026-08-10 by the estate's original first-party seeding run (the first_party_api family). They are published exactly as held — with the single-read caveat attached, never presented as flowing, and never back-filled or re-derived. The flowing substrate_rpc family now holds a series of the same name that has advanced past the seed value; the two families are kept separate and never merged or averaged.

Fees & revenue — DefiLlama protocol data, as held

Protocol-level fees and revenue from DefiLlama's public summary API. Fees rows verify against /summary/fees/peaq; revenue rows against /summary/fees/peaq?dataType=dailyRevenue — each row keeps its own verify_url. The near-zero and zero values are the live upstream answers, published exactly as answered — fees_24h $0.00, fees_7d $0.11, fees_30d $0.65, and fees_1y equal to fees_alltime upstream at generation. Zero is a measurement here, not a gap: the estate never smooths, rounds up, or hides an upstream zero, and the estate's own Revenue grade reads these same values.

On-chain activity — DefiLlama chain family, as held

Three different DefiLlama endpoints, three different verify paths, never merged into one "DefiLlama" object: DEX volume verifies against /overview/dexs/peaq; chain TVL against /v2/chains; stablecoin supply against stablecoins.llama.fi/stablecoinchains. The upstream chain object is named Peaq (capital A) — the verify commands filter case-insensitively. Each metric below carries its own origin link.

Dev velocity — GitHub, as held (repo + org provenance)

Public activity for peaq's peaqnetwork/peaq-network-node repo — the network's principal node implementation. Repo-level metrics (stars, forks, open issues, watchers, days since push) verify against repos/peaqnetwork/peaq-network-node; the public-repos count is an org-level metric and verifies against orgs/peaqnetwork. Each metric keeps its own verify_url — the page does not pretend they share one source object.

Full metric inventory — 42 measured series, each with provenance

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

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

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

Served by /v1/network/PEAQ — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The revenue grade reflects what the engines read from the held fee/revenue series — near-zero upstream activity grades F; it is published exactly as computed.

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 onfinality calls are Substrate JSON-RPC POSTs (the endpoint answers HTTP 405 to plain GETs, so plain GETs will not work). 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) peaq's own Substrate JSON-RPC (onfinality gateway) — keyless, POST-only, as of 2026-09-02T15:02:51Z:
#    (finalized block height) curl -s -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"chain_getHeader","params":[]}' https://peaq.api.onfinality.io/public | python3 -c "import sys,json; print(int(json.load(sys.stdin)['result']['number'], 16))"
#    (node peer count) curl -s -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"system_health","params":[]}' https://peaq.api.onfinality.io/public | python3 -c "import sys,json; print(json.load(sys.stdin)['result']['peers'])"
# 2) Protocol fees (DefiLlama public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/peaq" | python3 -m json.tool | head -30
# 2b) Protocol revenue (same family, revenue slice):\ncurl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/peaq?dataType=dailyRevenue" | python3 -m json.tool | head -30
# 2c) DEX volume (DefiLlama overview/dexs):\ncurl -s -H "User-Agent: kairos-check" "https://api.llama.fi/overview/dexs/peaq" | python3 -m json.tool | head -20
# 2d) Chain TVL (DefiLlama v2/chains — upstream names the chain "Peaq"):\ncurl -s -H "User-Agent: kairos-check" "https://api.llama.fi/v2/chains" | python3 -c "import sys,json; print([c for c in json.load(sys.stdin) if c.get('name','').lower()=='peaq'][:1])"
# 2e) Stablecoin supply (stablecoins.llama.fi):\ncurl -s -H "User-Agent: kairos-check" "https://stablecoins.llama.fi/stablecoinchains" | python3 -c "import sys,json; print([c for c in json.load(sys.stdin) if c.get('name','').lower()=='peaq'][:1])"
# 3) Market reference (CoinGecko public API — the coingecko.com browser\n#    coin page 403s plain curl, so the programmatic endpoint is given):\ncurl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=peaq-2" | python3 -m json.tool
# 4) Dev velocity, repo-level (GitHub public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/peaqnetwork/peaq-network-node" | python3 -m json.tool | head -20
# 4b) Dev velocity, org-level (GitHub public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/peaqnetwork" | python3 -m json.tool | head -20
# 5) This estate's public API row for PEAQ:\ncurl -s "https://kairossignal.com/v1/network/PEAQ" | 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_peaq.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 PEAQ-native network/market telemetry with no cross-network concept; grading them would be fabrication, so they are labelled "peaq-native (unmapped)". This estate holds no device count, machine inventory, capacity or staking series for PEAQ — no such figure appears on this page and none is implied. The two finalized_block_height families (the flowing gated substrate_rpc series and the single-observation first_party_api seed row) are different collectors with different stamps; they are shown side by side and never summed, merged, or reconciled. CoinGecko series start 2026-08-22 in this archive and are shown from their first held row, never back-filled. DefiLlama fees, revenue, DEX, TVL and stablecoin rows carry different verify_urls and each keeps its own; the fees family's near-zero values are upstream answers, not gaps. GitHub repo-level and org-level dev metrics keep their separate verify targets. 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: onfinality peaq RPC (chain_getHeader POST) HTTP 200; onfinality peaq RPC (system_health POST) HTTP 200; DefiLlama fees API HTTP 200; DefiLlama revenue API HTTP 200; DefiLlama dexs API HTTP 200; DefiLlama v2/chains API HTTP 200; DefiLlama stablecoinchains API HTTP 200; CoinGecko markets API HTTP 200; CoinGecko browser coin page (expected 403) HTTP 403; GitHub peaqnetwork/peaq-network-node HTTP 200; GitHub orgs/peaqnetwork HTTP 200; estate /v1/network/PEAQ HTTP 200.