PAAL AI (PAAL) — the network, measured

Generated 2026-09-02T17:47:17Z from live ClickHouse queries against this estate's ledger. Held inventory: 7,645 observations · 37 distinct series · 5 upstream sources · first row 2026-08-17 23:01:56 · newest row 2026-09-02 16:58:01 · 7,645/7,645 rows carry a verify_url. 37 series refreshed in the last 24h (818 fresh rows). Nothing on this page is cached, estimated, or remembered.

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

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 change columns / rank / ATH-ATL / high-low series start later in the archive than the price rows (each metric's caveat in the full inventory states its own first-held row) and are shown from their first held row. The circulating and total/max supply rows are different quantities (circulating vs total vs cap) and are never netted against each other or against the Ethereum-RPC onchain_total_supply read in the chain-state section below — different measurements from different endpoints, shown side by side.

Fees & revenue — DefiLlama protocol data, as held

Protocol-level fees and revenue from DefiLlama's public summary API. Fees rows verify against /summary/fees/paal-ai; revenue rows against /summary/fees/paal-ai?dataType=dailyRevenue — each row keeps its own verify_url. Revenue is DefiLlama's dailyRevenue slice (fees kept by the protocol after contributor payments) — a different measurement from fees, never netted against it on this page. The recent-window fee rows read 0 as DefiLlama publishes them while the 1-year (245,873) and all-time (14,267,513) rows are non-zero — the zeros are the upstream's live answer, not a gap in our collection; our ledger's own 30-day daily shape for fees_24h_usd reads 0 on every held day, matching the upstream. Published exactly as answered, never smoothed.

TVL — DefiLlama protocol page, as held

Two buckets of the same DefiLlama /protocol/paal-ai response: the protocol-page TVL (tvl[] series' last totalLiquidityUSD) and the staking bucket (currentChainTvls.staking). They are different measurements — the general TVL bucket currently reads 0 as DefiLlama reports it while the staking bucket reads non-zero — and both are published exactly as answered, never netted, summed, or reconciled against each other. A zero here is the upstream's live answer, not a gap (the history table shows the staking series' 30-day shape).

Ethereum-chain state — RPC reads, as held

Chain state for the Ethereum-mainnet contract 0x14fee680690900ba0cccfc76ad70fd1b95d10e16 (catalog chains field, verbatim: Ethereum), read from public Ethereum nodes via eth_call (totalSupply() for on-chain total supply, balanceOf(0x…dEaD) for the burn-sink balance). The catalog's token_address field is empty for PAAL; the contract above is the one the estate's chain-read collector (evm_rpc_firstparty) is configured to read for the PAAL symbol, and every verify_url in this family points at etherscan.io for that same contract. onchain_total_supply is a different measurement family from the CoinGecko market reference; the two are never merged, and no ratio is derived between them. The burn row is the dEaD-sink balance only — an effective-supply input, not "total burned": many projects burn via other sinks or supply-reduction calls.

Token adoption counters — Blockscout, as held

Holders and transfer counts from the public Blockscout v2 token API for the Ethereum-mainnet contract 0x14fee680690900ba0cccfc76ad70fd1b95d10e16. This source is deliberately distinct from the RPC family so its freshness identity stays untouched. Polled roughly once per day; counters are published raw, never differenced into rates, never extrapolated.

Full metric inventory — 37 measured series, each with provenance

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

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

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

Served by /v1/network/PAAL — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The overall grade is middling and it is published as computed: the catalog lists no public stats API and the estate holds no first-party node telemetry for this network, so the engines grade on third-party and chain-state series alone — the revenue and data-coverage F grades are shown 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–3 hit the same upstream endpoints our collectors do (the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given; the RPC commands use the publicnode Ethereum endpoint the collector rotates through); command 4 hits this estate's public API, where every row carries the same source / as_of / verify_url fields. One polite call per endpoint, no hammering.

# 1) Ethereum-mainnet token supply (totalSupply() via public RPC — the collector's method), as of 2026-09-02T17:47:17Z:
curl -s -H "User-Agent: kairos-check" "https://ethereum-rpc.publicnode.com" -X POST -H "Content-Type: application/json" -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"eth_call\",\"params\":[{\"to\":\"0x14fee680690900ba0cccfc76ad70fd1b95d10e16\",\"data\":\"0x18160ddd\"},\"latest\"]}'
# 1b) Burn-sink balance (balanceOf(0x…dEaD) on the token contract):
curl -s -H "User-Agent: kairos-check" "https://ethereum-rpc.publicnode.com" -X POST -H "Content-Type: application/json" -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"eth_call\",\"params\":[{\"to\":\"0x14fee680690900ba0cccfc76ad70fd1b95d10e16\",\"data\":\"0x70a0823100000000000000000000000000000000000000000000000000000000000000dEaD\"},\"latest\"]}'
# 1c) Holders + transfers (public Blockscout v2 token API):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x14fee680690900ba0cccfc76ad70fd1b95d10e16" | python3 -c "import json,sys; d=json.load(sys.stdin); print('holders', d.get('holders')); print('transfers', d.get('transfers'))"
# 1d) The per-token page our verify_url points at (human view):
curl -s -o /dev/null -w "%{http_code}\n" "https://etherscan.io/token/0x14fee680690900ba0cccfc76ad70fd1b95d10e16"
# 2) Protocol fees (DefiLlama public API):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/paal-ai" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total24h', d.get('total24h')); print('total30d', d.get('total30d')); print('total1y', d.get('total1y')); print('totalAllTime', d.get('totalAllTime'))"
# 2b) Protocol revenue (same family, revenue slice):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/paal-ai?dataType=dailyRevenue" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total24h', d.get('total24h'))"
# 2c) Protocol TVL + staking bucket (same /protocol response the rows read):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/protocol/paal-ai " | python3 -c "import json,sys; d=json.load(sys.stdin); t=(d.get('tvl') or [{}]); print('tvl_usd', (t[-1] if t else {}).get('totalLiquidityUSD')); print('staking', (d.get('currentChainTvls') or {}).get('staking'))"
# 3) Market reference (CoinGecko public API):
# 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=paal-ai" | python3 -m json.tool
# 4) This estate's public API row for PAAL:
curl -s "https://kairossignal.com/v1/network/PAAL" | 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_paal.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 PAAL-native market/on-chain metrics with no cross-network concept; grading them would be fabrication, so they are labelled "paal-native (unmapped)". FOUR supply references are shown side by side as held, never summed, merged, or reconciled: CoinGecko's circulating, total and max supply, and the Ethereum-RPC on-chain token supply. The CoinGecko circulating_supply row is a different quantity (circulating vs total) and is never netted against the other reads. The currently-zero DefiLlama general TVL bucket and the recent-window fee rows are DefiLlama's live answers, published as answered with their shape shown; they are never silently replaced or smoothed, and the non-zero staking bucket is a different bucket, never summed with the TVL one. The burn row stays the raw dEaD-sink balance as the RPC reports it — an effective-supply input, never relabelled as total burned, never presented as investment advice. The Blockscout counters are ~daily polls, published as answered. The catalog's token_address field is empty for PAAL; the chain-read families above read the contract the estate's collector (evm_rpc_firstparty) is configured to read for this symbol on Ethereum mainnet, and every verify_url in those families points at etherscan.io / eth.blockscout.com for that same contract. The estate holds no GitHub and no first-party snapshot rows for PAAL — those sections are absent rather than zero-filled, and the queries rerun at every regeneration. Where a section has no data, it is absent — we do not publish zeros for gaps. Upstream probes ran serially by this generator immediately before rendering: Ethereum public RPC (totalSupply) HTTP 200; DefiLlama fees API (paal-ai) HTTP 200; DefiLlama revenue API (paal-ai) HTTP 200; DefiLlama protocol API (paal-ai) HTTP 200; CoinGecko markets API (paal-ai) HTTP 200; Blockscout token API HTTP 200; estate /v1/network/PAAL HTTP 200.