KAT · epoch 2965
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.
tiers & installs: refine.gist.rs — this board is leader stats only. Per-lane detail sits at the bottom of this page.
| rank | contributor | tier | mining | mined | minted | contribution | status |
|---|---|---|---|---|---|---|---|
| #1 | d54e…55a0 | pro | 0 | 406 | 66.866068 | minted | |
| #2 | 4f46…c6cc | pro | 0 | 318 | 47.574989 | minted | |
| #3 | 518a…8176 | pro | 0 | 2 | 5.25947 | minted | |
| #4 | 863f…667d | pro | 0 | 1 | 0.000031 | grant unclaimed minted | |
| #5 | 8f5a…a427 | pro | 0 | 3 | 0.000014 | minted |
Newest mint receipts
| epoch | contributor | state | rows | locked KAT | |
|---|---|---|---|---|---|
| 2961 | d54e…55a0 | minted (spendable) | 153/153 | 0 | receipt → |
| 2961 | 8f5a…a427 | minted (spendable) | 3/3 | 0 | receipt → |
| 2961 | 4f46…c6cc | minted (spendable) | 3/3 | 0 | receipt → |
| 2960 | d54e…55a0 | minted (spendable) | 14/14 | 0 | receipt → |
| 2960 | 4f46…c6cc | minted (spendable) | 11/11 | 0 | receipt → |
| 2959 | d54e…55a0 | minted (spendable) | 50/50 | 0 | receipt → |
| 2959 | 518a…8176 | minted (spendable) | 2/2 | 0 | receipt → |
| 2959 | 4f46…c6cc | minted (spendable) | 31/31 | 0 | receipt → |
| 2958 | d54e…55a0 | minted (spendable) | 178/178 | 0 | receipt → |
| 2958 | 4f46…c6cc | minted (spendable) | 242/242 | 0 | receipt → |
The contribution lanes — where each role’s numbers live
| coder | heals your own code. This epoch (2962): 200 fixes shared by 2 coders over 30 runs — the consent-gated, stats-only lane (what was fixed, never the code; cargo refine --stats on to share). Top: doc_markdown ×91 · doc_lazy_continuation ×54 · chunks_exact_to_as_chunks ×13 · entry-vs-contains-insert ×4 · identity_op ×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 0 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.