ai.gist.rs · Explorer

KAT ledger explorer

explorer

the ledger, walkable — every number shows its source row, every page its commitment root

the KAT ledger, walkable
every number shows its source row — every page its commitment root
/explorer/katsupply, sinks, service columns, the RATIFIED genesis row, live params vs genesis
/explorer/account/<id>one account: balance, grant, burn watermark + event log, credit events, receipts, and the pre-event-log residual. A full 32-hex id or an 8-hex 4+4 prefix both work; an ambiguous prefix gets a pick list. Pages render only 4+4 — pseudonymous by construction.
/explorer/epoch/<n>the settle row, epoch split params (+ drift vs genesis), the committed telemetry row incl. stats_root, hourly burn-settle buckets
/explorer/stake/<id>one staking position: USDC/KAT tranches with unlock dates, unstake requests (escrow + vent schedule), KAT redeems, accrued, the per-epoch distribution markers
/explorer/gov[/<id>]governance: the proposal list (kind, state, timeline ticks, tally), per-proposal votes, applied param intents, ban rows; <id> opens one proposal's detail
/explorer/nftthe item shop's catalog (prices, stock, editions, denominations) + the art listings (owner, creator royalty, sale trail) + the shop's burned-total stats
/explorer/miningthe mining reward LEDGER half: proven reward rows by epoch (weight, paid), the unpaid queue; the ingest/queue half links out to /mining/*
/explorer/fixstatsthe committed work-stats fold: per-epoch stats_root commitments + the verify links; live counters link to /mining/fixstats
/explorer/payreq/<32hex>one payment request: kind, state timeline, pinned amount, the settled invoice when the KAT rail settled it
/explorer/livethe recent-events feed: an honest MERGE of the globally orderable sources (deposits, burn-settle buckets, governance proposals, mint receipts, epoch boundaries) — labeled per plane, capped, and explicit about the per-account logs it cannot see
/explorer/genesisgenesis vs live: the deployed kat:cfg:v1 row vs the compiled defaults (each row labeled NEVER-LEVER), the live EpochParams levers vs their governance bounds, the applied param intents, and the RATIFIED pointer
?format=csvthe table views export CSV: gov list, NFT catalog, mining rewards — same rows as the JSON twin, header row, RFC-4180 quoting, 4+4 ids
/explorer/search?q=one box: account (8-hex 4+4 prefix, full 32-hex service id, or the client's full 64-hex local id — the ledger keys its first 32 hex), receipt id, epoch number, acct:seq

Every page has a JSON twin: ?format=json (or any non-www host). Amounts are integer micro + the rendered KAT string. The traceability chain: genesis → grant → burn report → watermark → hourly settle → epoch split → receipt → vest → spend.

Words on this page
KAT
The network’s metered service credit. No cash value and no redemption right.
TUNA
Free trial credit, one grant per account, spent before KAT.
epoch
The network’s one-week accounting period.
settle
The once-per-epoch accounting pass that fixes each miner’s share of that epoch’s pool.
burn
Credit spent on a run. Each KAT burn is split by the network’s published parameters, mostly into the next epoch’s mining pool — the live split is on the KAT page.
mint receipt
The ledger’s record of one miner’s claim in one epoch: its rows, weight, amount and release date.
4+4 id
An account shown by the first 4 and last 4 characters of its id — enough to recognise, not enough to identify.

verify: committed stats_root (epoch 2961) 2e9ed6bb… · /mining/statroot

Devnet: KAT carries no cash value and no redemption right. It is metered service credit.