PKT (PKT) — the network, measured

Generated 2026-10-17T04:59:18Z from live ClickHouse queries against this estate's ledger. Held inventory: 43,659 observations · 57 distinct series · 5 upstream sources · first row 2026-08-08 23:21:30 · newest row 2026-10-17 04:51:55 · 43,659/43,659 rows carry a verify_url. 45 series refreshed in the last 24h (423 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 deeper change columns start 2026-08-22 in our archive and are shown from their first held row.

Base-chain state — Blockscout, as held

Chain state for the Base token 0x917f39bb33b2483dd19546b1e8d2f09ce481ee44 (catalog chains: base), read from Base Blockscout's public API: on-chain total supply, holder count, top-holder balance, and the transfer/contract counters. Counter series are sparse (10–25 rows each) — that is the archive's own shape, shown as held with row counts. This is a different ledger object from the CoinGecko market reference and the PKT chain's own explorer decomposition below; the three are never merged.

PKT-chain supply & airdrop — the PKT block explorer, as held

Read from the network's own public stats endpoint (explorer.pkt.cash/api/v1/stats) by the estate's deep-stats collector: the PKT chain's native supply decomposition (burned, circulating, lockbox, LP-locked, LP-unlocked, yieldable), the airdrop series, and the current daily yield. Units are token_base_units as upstream reports them — this estate applies no conversion and publishes no decimal factor. These are PKT-chain-native accounting figures, a different measurement from both the CoinGecko reference and the Base-chain token state above; held side by side, never summed or reconciled.

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

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

Full metric inventory — 54 measured series, each with provenance

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

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 PKT. 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; the PKT explorer's TLS certificate does not match its hostname — the same reason this estate's own collector reads it with verification disabled — so its command is given with -k and the mismatch is declared here rather than hidden); command 5 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) The network's own block explorer stats — keyless, as of 2026-10-17T04:59:18Z:
curl -sk -H "User-Agent: kairos-check" "https://explorer.pkt.cash/api/v1/stats" | python3 -m json.tool | head -40
# 2) Base-chain token state (Blockscout public API):
curl -s -H "User-Agent: kairos-check" "https://base.blockscout.com/api/v2/tokens/0x917f39bb33b2483dd19546b1e8d2f09ce481ee44" | python3 -m json.tool | head -30
# 2b) Base-chain holders (same API family):
curl -s -H "User-Agent: kairos-check" "https://base.blockscout.com/api/v2/tokens/0x917f39bb33b2483dd19546b1e8d2f09ce481ee44/holders" | python3 -m json.tool | head -30
# 2c) Base-chain transfer/contract counters (same API family):
curl -s -H "User-Agent: kairos-check" "https://base.blockscout.com/api/v2/addresses/0x917f39bb33b2483dd19546b1e8d2f09ce481ee44/counters" | python3 -m json.tool
# 3) Market reference (CoinGecko public API — 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=pkt" | python3 -m json.tool
# 4) Dev velocity, repo-level (GitHub public API):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/pkt-cash/pktd" | python3 -m json.tool | head -20
# 4b) Dev velocity, org-level (GitHub public API):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/pkt-cash" | python3 -m json.tool | head -20
# 5) This estate's public API row for PKT:
curl -s "https://kairossignal.com/v1/network/PKT" | 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_pkt.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 PKT-native network/market/on-chain metrics with no cross-network concept; grading them has no basis in the held data, so they are labelled "pkt-native (unmapped)". Three supply-side measurement families are shown side by side as held, never summed, merged, or reconciled: CoinGecko's coin-page reference, Blockscout's Base-chain token state, and the PKT explorer's chain-native decomposition (units token_base_units, no conversion applied, no decimal factor published). The CoinGecko change-column generation two (from 2026-08-22) is shown from its first held row, never back-filled; 24h staleness is computed live at generation, never remembered. GitHub repo-level and org-level dev metrics keep their separate verify targets. The PKT explorer's TLS certificate does not match its hostname (verified 2026-09-02); the estate's collector has always read it with verification disabled for that reason, and the buyer-verify command is published with -k — disclosed, not hidden. 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: PKT block explorer stats API (TLS verification skipped — cert/hostname mismatch, see above) HTTP 200; Blockscout Base token API HTTP 403; Blockscout Base holders API HTTP 403; Blockscout Base counters API HTTP 403; CoinGecko markets API HTTP 200; GitHub pkt-cash/pktd HTTP 200; GitHub orgs/pkt-cash HTTP 200; estate /v1/network/PKT HTTP 200.