TAO—Block—Subnets85 / 128active
Bittensor Subnet 11: verified agent work on open-weight models. Season 2: fusion policies over the Engy catalog; next: an open protocol for verifiable environments.
What miners actually race on — the mission definition, its tasks and scoring, and the mission-score board. Not the same thing as emission share.
The mission does not live in the registered repo. The chain points at https://github.com/trajectoryRL/trajectoryRL, but the race runs from trajectoryRL/trajrl-bench (scenarios). Follow that one — and the repo watch below tracks the registered repo only.
Read 4d ago from trajrl.com/api/miners. Mission scores are the subnet's own scoring; emission share is the on-chain payout — different numbers, different meanings.
What the validator network actually scored this epoch — read from the chain's Incentive vector, normalized on chain.
Winner-take-all right now: the whole incentive — and with it essentially all emission — lands on a single uid. That is why concentration views here show a ~100% top share: it's the payout structure of this race, not an anomaly.
These are each miner's normalized incentive from the chain's Incentive vector — the only race score Bittensor stores. It is a share of the validators' consensus weight: all rows sum to 1, so uid #56's 0.802 on Minos means it holds 80.2% of the validated weight — and since emission follows incentive exactly, it also takes ~80% of the miner-side payout. There is no absolute score (an “87/100”) on chain; numbers like that live in each subnet's own off-chain platform. Uids absent from the list received zero validated weight this epoch.
Absolute submission scores (an “87/100”) are computed by validators off chain and never published on chain — subtensor no longer even stores a pre-normalization Scores vector, so the incentive shares above are the only race score that exists on chain. When a subnet publishes scores through its own mission API, they appear in the mission panel above instead.
live chain reads
scores read 4d ago · block 9,485,339 · epoch 26,348
and what they can't
Incentive is the score the validator network converged on for each uid this epoch — it's what pays: emission follows it. It is normalized on chain to sum to 1, so it reads as a share of validated weight. Hidden per-validator test sets (e.g. a private eval split) are computed off chain and never published — the chain no longer even stores a pre-normalization Scores vector — so taonets shows exactly what the chain shows, no reconstruction.
did the race change? the head commit is the probe
The watch hasn't confirmed this repo in 4d ago — the head below may be behind GitHub. Treat the race as possibly moved until the watch is live again.
Burn all SN11 miner emission to owner UID 74; release 0.7.8 (#347)
The head commit is the atomic “did the race move” probe: any push to the default branch — new tasks, benchmark changes, scoring edits — lands here on the next watch pass. The confirmed-ago line above proves the watch is actually running.
archived per epoch since taonets started tracking (epoch 25,629)
| Epoch | Block | Time | Winner uid | Winner coldkey | Race score | Top incentive | Qualifier mean incentive | Qualifiers |
|---|---|---|---|---|---|---|---|---|
| Nov 11 | ||||||||
| 26,348 | 9,485,339 | Nov 11, 20:10 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,347 | 9,485,045 | Nov 11, 19:11 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,346 | 9,484,587 | Nov 11, 17:39 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,345 | 9,484,293 | Nov 11, 16:41 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,344 | 9,483,855 | Nov 11, 15:13 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,343 | 9,483,554 | Nov 11, 14:13 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,342 | 9,483,244 | Nov 11, 13:11 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,341 | 9,482,785 | Nov 11, 11:39 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,340 | 9,482,505 | Nov 11, 10:43 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,339 | 9,482,042 | Nov 11, 09:10 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,338 | 9,481,734 | Nov 11, 08:09 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,337 | 9,481,440 | Nov 11, 07:10 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,336 | 9,480,993 | Nov 11, 05:41 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,335 | 9,480,698 | Nov 11, 04:43 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,334 | 9,480,269 | Nov 11, 03:16 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,333 | 9,479,955 | Nov 11, 02:13 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,332 | 9,479,650 | Nov 11, 01:12 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| Nov 10 | ||||||||
| 26,331 | 9,479,190 | Nov 10, 23:40 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,330 | 9,478,914 | Nov 10, 22:45 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,329 | 9,478,491 | Nov 10, 21:20 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,328 | 9,478,163 | Nov 10, 20:15 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,327 | 9,477,829 | Nov 10, 19:08 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,326 | 9,477,407 | Nov 10, 17:44 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,325 | 9,477,012 | Nov 10, 16:25 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
| 26,324 | 9,476,988 | Nov 10, 19:26 | #74 | 5D2Jhtb…JP3uE | — | 1.000 | 1.000 | 1 |
The chain does not store past Incentive vectors — history begins when taonets started watching (last 720 epochs kept), and every epoch is archived from live reads only. Gap rows mark stretches the worker never saw — they are downtime, not data. Winner coldkeys read at archival are exact; ones marked current were resolved later from the present ownership map. Race scores are the mission's own published scores for the settled round covering each epoch — retrospective (unknown until the round closed), in the mission's own units, never incentive.
who held the top incentive each day — 90 days back to 2026-08-13
| Day (UTC) | Winner uid | Winner coldkey | Top incentive | Block |
|---|---|---|---|---|
| 2026-11-10 | #74 | 5D2Jhtb…JP3uE | 1.000 | 9,472,091 |
| 2026-11-09 | #74 | 5D2Jhtb…JP3uE | 1.000 | 9,469,715 |
| 2026-11-08 | #74 | 5D2Jhtb…JP3uE | 1.000 | 9,462,530 |
| 2026-11-07 | #157 | 5CXwYge…pTfzh | 1.000 | 9,455,345 |
| 2026-11-06 | #125 | 5FCbinb…9y1jW | 1.000 | 9,448,167 |
| 2026-11-05 | #125 | 5FCbinb…9y1jW | 1.000 | 9,440,986 |
| 2026-11-04 | #105 | 5GvZoHG…tVDkZ | 1.000 | 9,433,801 |
| 2026-11-03 | #1 | 5HBeTAH…pXgoz | 1.000 | 9,426,620 |
| 2026-11-02 | #238 | 5Esqkv3…hwYwP | 1.000 | 9,419,436 |
| 2026-11-01 | #129 | 5GTbLjE…VgPdK | 1.000 | 9,412,257 |
| 2026-10-31 | #155 | 5DUALFP…FhW1B | 1.000 | 9,405,075 |
| 2026-10-30 | #222 | 5DcQYZ1…AvZji | 1.000 | 9,397,895 |
| 2026-10-29 | #45 | 5HBeTAH…pXgoz | 1.000 | 9,390,716 |
| 2026-10-28 | #6 | 5GQYnzo…gp3FR | 1.000 | 9,383,531 |
| 2026-10-27 | #136 | 5ELEnMa…zS3H8 | 1.000 | 9,376,346 |
| 2026-10-26 | #31 | 5CXwYge…pTfzh | 1.000 | 9,369,171 |
| 2026-10-25 | #229 | 5FZM5Xa…xJaFG | 1.000 | 9,361,985 |
| 2026-10-24 | #231 | 5GunvBx…Sgfy5 | 1.000 | 9,354,801 |
| 2026-10-23 | #254 | 5DUALFP…FhW1B | 1.000 | 9,347,615 |
| 2026-10-22 | #59 | 5GCPfKT…f4phZ | 1.000 | 9,340,428 |
| 2026-10-21 | #162 | 5DUALFP…FhW1B | 1.000 | 9,333,255 |
| 2026-10-20 | #34 | 5DnbFoq…PAgHU | 1.000 | 9,326,080 |
| 2026-10-19 | #97 | 5DtF8SR…vXA6w | 1.000 | 9,318,902 |
| 2026-10-18 | #29 | 5HBeTAH…pXgoz | 1.000 | 9,311,737 |
| 2026-10-17 | #29 | 5HBeTAH…pXgoz | 1.000 | 9,304,550 |
| 2026-10-16 | #66 | 5D7smKp…MARQ5 | 1.000 | 9,297,371 |
| 2026-10-15 | #86 | 5DvkyhP…CCGby | 1.000 | 9,290,189 |
| 2026-10-14 | #58 | 5GqCnig…HPitf | 1.000 | 9,283,014 |
| 2026-10-13 | #21 | 5F3yojW…Y5rJv | 1.000 | 9,275,836 |
| 2026-10-12 | #173 | 5GvZoHG…tVDkZ | 1.000 | 9,268,655 |
| 2026-10-11 | #144 | 5EPcLUA…GoUK4 | 1.000 | 9,261,475 |
| 2026-10-10 | #83 | 5EyK8fs…UR534 | 1.000 | 9,254,295 |
| 2026-10-09 | #186 | 5Dff1qD…s42xe | 1.000 | 9,247,116 |
| 2026-10-08 | #190 | 5GmjbWg…yBdeW | 1.000 | 9,239,945 |
| 2026-10-07 | #78 | 5HNB3tE…BHF2X | 1.000 | 9,232,765 |
| 2026-10-06 | #127 | 5DUALFP…FhW1B | 1.000 | 9,225,770 |
| 2026-10-05 | #154 | 5FWdTpo…Mq2Rr | 1.000 | 9,218,595 |
| 2026-10-04 | #168 | 5DUzxve…2cb2m | 1.000 | 9,211,411 |
| 2026-10-03 | #190 | 5GmjbWg…yBdeW | 1.000 | 9,204,226 |
| 2026-10-02 | #198 | 5DUALFP…FhW1B | 1.000 | 9,197,050 |
| 2026-10-01 | #16 | 5Hp57T3…aj454 | 1.000 | 9,189,870 |
| 2026-09-30 | #66 | 5D7smKp…MARQ5 | 1.000 | 9,182,691 |
| 2026-09-29 | #2 | 5DcQYZ1…AvZji | 1.000 | 9,175,517 |
| 2026-09-28 | #76 | 5GTbLjE…VgPdK | 1.000 | 9,168,330 |
| 2026-09-27 | #76 | 5GTbLjE…VgPdK | 1.000 | 9,161,151 |
| 2026-09-26 | #246 | 5F1a352…U6Y41 | 1.000 | 9,153,971 |
| 2026-09-25 | #175 | 5CJySDk…TEWqV | 1.000 | 9,146,788 |
| 2026-09-24 | #175 | 5CJySDk…TEWqV | 1.000 | 9,139,614 |
| 2026-09-23 | #210 | 5G1d4Sr…tkq5V | 1.000 | 9,132,431 |
| 2026-09-22 | #210 | 5G1d4Sr…tkq5V | 1.000 | 9,125,261 |
| 2026-09-21 | #210 | 5G1d4Sr…tkq5V | 1.000 | 9,118,081 |
| 2026-09-20 | #32 | 5DLLQvH…2qR3n | 1.000 | 9,110,902 |
| 2026-09-19 | #17 | 5CJySDk…TEWqV | 1.000 | 9,103,731 |
| 2026-09-18 | #17 | 5CJySDk…TEWqV | 1.000 | 9,096,555 |
| 2026-09-17 | #17 | 5CJySDk…TEWqV | 1.000 | 9,089,372 |
| 2026-09-16 | #17 | 5CJySDk…TEWqV | 1.000 | 9,082,196 |
| 2026-09-15 | #97 | 5EWoiMU…DedXX | 1.000 | 9,075,215 |
| 2026-09-14 | #97 | 5EWoiMU…DedXX | 1.000 | 9,068,031 |
| 2026-09-13 | #97 | 5EWoiMU…DedXX | 1.000 | 9,060,852 |
| 2026-09-12 | #97 | 5EWoiMU…DedXX | 1.000 | 9,053,665 |
| 2026-09-11 | #97 | 5EWoiMU…DedXX | 1.000 | 9,046,480 |
| 2026-09-10 | #97 | 5EWoiMU…DedXX | 1.000 | 9,039,301 |
| 2026-09-09 | #97 | 5EWoiMU…DedXX | 1.000 | 9,032,120 |
| 2026-09-08 | #97 | 5EWoiMU…DedXX | 1.000 | 9,024,936 |
| 2026-09-07 | #98 | 5Dhi8Yx…5qaN7 | 1.000 | 9,017,752 |
| 2026-09-06 | #98 | 5Dhi8Yx…5qaN7 | 1.000 | 9,010,567 |
| 2026-09-05 | #98 | 5Dhi8Yx…5qaN7 | 1.000 | 9,003,380 |
| 2026-09-04 | #181 | 5Hg4qMX…ZphPp | 1.000 | 8,996,346 |
| 2026-09-03 | #181 | 5Hg4qMX…ZphPp | 1.000 | 8,989,167 |
| 2026-09-02 | #181 | 5Hg4qMX…ZphPp | 1.000 | 8,981,981 |
| 2026-09-01 | #181 | 5Hg4qMX…ZphPp | 1.000 | 8,974,801 |
| 2026-08-31 | #45 | 5GedYAn…2qxvc | 1.000 | 8,967,651 |
| 2026-08-30 | #45 | 5GedYAn…2qxvc | 1.000 | 8,960,466 |
| 2026-08-29 | #45 | 5GedYAn…2qxvc | 1.000 | 8,953,285 |
| 2026-08-28 | #124 | 5GedYAn…2qxvc | 1.000 | 8,946,100 |
| 2026-08-27 | #130 | 5CyadYi…o8JPD | 1.000 | 8,938,917 |
| 2026-08-26 | #130 | 5CyadYi…o8JPD | 1.000 | 8,931,751 |
| 2026-08-25 | #130 | 5CyadYi…o8JPD | 1.000 | 8,924,564 |
| 2026-08-24 | #53 | 5Hg4qMX…ZphPp | 1.000 | 8,917,380 |
| 2026-08-23 | #53 | 5Hg4qMX…ZphPp | 1.000 | 8,910,196 |
| 2026-08-22 | #53 | 5Hg4qMX…ZphPp | 1.000 | 8,903,009 |
| 2026-08-21 | #53 | 5Hg4qMX…ZphPp | 1.000 | 8,895,829 |
| 2026-08-20 | #53 | 5Hg4qMX…ZphPp | 1.000 | 8,888,660 |
| 2026-08-19 | #163 | 5ELosRT…1QhBB | 1.000 | 8,881,632 |
| 2026-08-18 | #163 | 5ELosRT…1QhBB | 1.000 | 8,874,451 |
| 2026-08-17 | #139 | 5DvMEyS…J5dkB | 1.000 | 8,867,271 |
| 2026-08-16 | #139 | 5DvMEyS…J5dkB | 1.000 | 8,860,086 |
| 2026-08-15 | #139 | 5DvMEyS…J5dkB | 1.000 | 8,845,720 |
| 2026-08-14 | #139 | 5DvMEyS…J5dkB | 1.000 | 8,838,535 |
| 2026-08-13 | #139 | 5DvMEyS…J5dkB | 1.000 | 8,831,356 |
Sampled one block per day from archived chain state — the block number is the verifiable anchor, the date is ±drift. Identity (hotkey + coldkey) is read at the sample block, so it names who actually won that day. Days the endpoint had already pruned are absent, never zero-filled.
The Emission map — what the scores converted into, live.
No emissions flow on chain right now — the race pays nothing until that changes.
Zero τ is flowing to this subnet right now (chain reads taoInPerBlock = 0) — the shares above are the score distribution that would convert if flow resumes.
what it costs to race here, live
Best-case frame: every key wins every epoch. Your real edge depends on the model you bring — check the scoreboard and winner history above, and the repo watch before committing.