Refine · Leaderboard

KAT · epoch 2961

KAT contribution leaderboard

Ranked by KAT minted for accepted fixes, then rows mined, then claims still in flight. Re-rendered every 30 s.

Pseudonymous by construction

4+4 key prefixes, never full ids; a read projection of BLAKE3-committed ledger state, re-rendered every 30 s.

Words on this page
KAT
The network’s metered service credit. No cash value and no redemption right.
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.
mining
Opting in to share records of your own runs. Records that pass verification earn KAT at the settle.
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.
vest
The lock on newly earned KAT before it can be spent.
4+4 id
An account shown by the first 4 and last 4 characters of its id — enough to recognise, not enough to identify.
1,404.699993
KAT in circulation
7
accounts on the board
2
accounts minted (last settle)
2,960
last settled epoch
177
mining — epoch 2961 settle (Oct 8, in 1d 8h) + 1d vest
1.400007
pool backing them — grows with every burn

tiers & installs: refine.gist.rs — this board is leader stats only. Per-lane detail sits at the bottom of this page.

rankcontributortierminingminedmintedcontributionstatus
#1c79c…5345pro15324266.865579pays in 1d 8h minted
#27161…bd29pro328447.574944pays in 1d 8h minted
#3518a…8176pro025.25947minted
#4022d…c589pro600pays in 1d 8h grant unclaimed
#51599…b656pro600pays in 1d 8h grant unclaimed
#629c6…ffefpro600pays in 1d 8h grant unclaimed
#78f5a…a427pro300pays in 1d 8h grant unclaimed

Newest mint receipts

epochcontributorstaterowslocked KAT
2961c79c…5345allocated (locked, vesting)0/1530receipt →
29618f5a…a427allocated (locked, vesting)0/30receipt →
29617161…bd29allocated (locked, vesting)0/30receipt →
2960c79c…5345minted (spendable)14/140receipt →
29607161…bd29minted (spendable)11/110receipt →
2959c79c…5345minted (spendable)50/500receipt →
29597161…bd29minted (spendable)31/310receipt →
2959518a…8176minted (spendable)2/20receipt →
2958c79c…5345minted (spendable)178/1780receipt →
29587161…bd29minted (spendable)242/2420receipt →

The contribution lanes — where each role’s numbers live

coder heals your own code. This epoch (2961): 47 fixes shared by 2 coders over 19 runs — the consent-gated, stats-only lane (what was fixed, never the code; cargo refine --stats on to share). Top: doc_lazy_continuation ×9 · chunks_exact_to_as_chunks ×7 · match_bool ×7 · shrink-to-fit-after-build ×6 · unreadable_literal ×4. Per-rule detail: /mining/fixstats.
miner live the only class that settles today — every row in the table above is a miner. A fixer node's KAT total IS its miner row (same account).
fixer live · ours the operator's nodes drain the unproven queue; accepted work settles through the miner rows above. Per-machine work volume (pushed / earned / dup / unproven): the adoption card on refine.gist.rs · /mining/adoption (JSON). Designed next: replay verification — re-run a leased fix on your own rig (does it compile? does the finding reproduce under the clippy oracle?) and agree with a second independent verifier; both then share a bounded cut of that row's reward. Nothing records until a deployment arms the lane, and the split stays 0 until owner ratification.
trainer ours only the training window runs on our replicas at launch; it joins the board when third-party installs open.

free trial grant 100 TUNA (30-day expiry), once per account · mining reward 1,000 KAT/epoch decaying 9,900 bp · mining emission cap 100,000 KAT · registration supply cap 1,000,000,000,000 KAT · every KAT burn splits 70% mining reward pool · 20% treasury (operator) · 10% destroyed (this epoch’s live parameters) · pool backing now 1.400007 KAT

Devnet: KAT carries no cash value and no redemption right. It is metered service credit — fixing burns 1 KAT per million code-word tokens (a code-word token is one whitespace-separated word of code), and every burn funds the next epoch’s mining pool. What the credit is — and is not: token & staking risk.