Jackal Protocol (JKL) — the network, measured

Generated 2026-10-12T04:48:15Z from live ClickHouse queries against this estate's ledger. Held inventory: 50,252 observations · 50 distinct series · 4 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-12 04:41:49 · 50,252/50,252 rows carry a verify_url. 49 series refreshed in the last 24h (1,026 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

4 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.

Supply & bond — the dual-denomination trap, declared

The same metric names arrive under two sources with different units: cosmos_lcd writes human-denom JKL rows from the live chain; first_party_api wrote the raw micro-denominator ujkl (1 ujkl = 1e-6 JKL) in its archived 2026-08-10 snapshot. The cosmos_lcd and first_party_api rows for the same metric are the same quantity in different denominations — shown side by side as held, never summed, merged, or silently converted. Chain reads from other endpoints (bank supply) stay in their own rows.

Market reference — CoinGecko coin page, as held

Market-data reference rows: price, supply, capitalisation, and the published change columns. These are the coin-page reference's own numbers — the estate does not model, smooth, or forward-fill them.

Chain & staking parameters — Jackal (Cosmos SDK), as held

Read from the chain's REST endpoints via rest.cosmos.directory (chain id jackal): staking pool, bonded / unbonded / unbonding validator sets, mint/inflation parameters, governance count, IBC channels, slashing parameters, signing infos, account count. Every row is a direct endpoint read with its own as-of stamp.

Archived first-party snapshot — raw ujkl, as held

The first_party_api collector's 2026-08-10 snapshot for JKL: the staking pool, inflation, and validator count in the chain's native micro-denominator (ujkl, 1 JKL = 1,000,000 ujkl). These are the same quantities as the cosmos_lcd rows above, captured in raw form; retained unconverted.

Full metric inventory — 49 measured series, each with provenance

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

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 JKL. 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–6 hit the same upstream endpoints our collectors do (the auth/accounts endpoint upstream answered 500 at generation time, so no curl is offered for that family); command 7 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) Staking pool (bonded/unbonded JKL) — keyless, as of 2026-10-12T04:48:15Z:
curl -s -H "User-Agent: kairos-check" "https://rest.cosmos.directory/jackal/cosmos/staking/v1beta1/pool" | python3 -m json.tool
# 2) Native total supply (bank, raw ujkl):
curl -s -H "User-Agent: kairos-check" "https://rest.cosmos.directory/jackal/cosmos/bank/v1beta1/supply/ujkl" | python3 -m json.tool
# 3) Governance — proposal count printed:
curl -s -H "User-Agent: kairos-check" "https://rpc.cosmos.directory/jackal/abci_query?path=%22/store/gov/key%22&data=0x03" | python3 -c "import json,sys; d=json.load(sys.stdin); print(d['pagination']['total'], 'proposals')"
# 4) IBC — channel count printed:
curl -s -H "User-Agent: kairos-check" "https://rest.cosmos.directory/jackal/ibc/core/channel/v1/channels?pagination.limit=1&pagination.count_total=true" | python3 -c "import json,sys; d=json.load(sys.stdin); print(d['pagination']['total'], 'ibc channels')"
# 5) Chain height (blocks/latest):
curl -s -H "User-Agent: kairos-check" "https://rest.cosmos.directory/jackal/cosmos/base/tendermint/v1beta1/blocks/latest" | python3 -m json.tool | head -30
# 6) Market reference (CoinGecko public API):
# CoinGecko public markets API (the endpoint family our collector
# reads for the price/supply/cap rows):
curl -s -H "User-Agent: kairos-check" "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=jackal-protocol" | python3 -m json.tool
# 7) This estate's public API row for JKL:
curl -s "https://kairossignal.com/v1/network/JKL" | 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_jkl.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: block_height maps to chain_height (question-verified), bonded_tokens to tokens_bonded (question-verified), bonded_validators to validators_bonded (question-verified), not_bonded_tokens to tokens_not_bonded (question-verified), total_supply to token_supply_total (question-verified), inflation to inflation_rate (question-verified). The remaining series are Jackal-native chain/market metrics with no cross-network concept; there is no cross-network concept to grade them against, so they are labelled "jkl-native (unmapped)". Human-denom and raw-ujkl rows for the same quantity are different denominations, never reconciled into one number. Where a section has no data, it is absent — we do not publish zeros for gaps.