SN97 kingship bugs fixed, architecture issues remain
Share
Two critical bugs were fixed: HumanEval+ scoring stuck at 0.0 for all miners (now producing real scores), and dethroned kings not being seated in subsequent rounds due to stale `king_uid` not being rewritten. Current king is UID 35. However, multiple structural issues persist including stale DQ flags, lost composites, ghost weights, and a regression where `recent_kings_max` was changed from 5 to 4, cutting UID 92's emission. Pod orchestrator issues and log persistence gaps also complicate debugging.
- •HumanEval+ axis fixed; UID 35 now legitimate king (0.4366 composite)
- •Dethrone persistence bug resolved; kings now correctly seated next round
- •`recent_kings_max` regressed from 5 to 4; UID 92 unfairly excluded from crown
- •Schema migration left UIDs 244, 214 without composites; UID 230 stuck DQ'd
- •Evaluated-but-no-composite limbo blocks new hotkey re-evaluations; 51+ UIDs trapped
Distilled from 85 team messages in the official Bittensor Discord. Generated by Claude Haiku 4.5.
View original messages
- Discord message 1505314621937160243
- Discord message 1505314852195930112
- Discord message 1505315065002328105
- Discord message 1505315446679670945
- Discord message 1505315624644120646
- Discord message 1505338723519430727
- Discord message 1505339712938836108
- Discord message 1505357152490098870
- Discord message 1505367826754703570
- Discord message 1505367828038160475
- Discord message 1505373934768361623
- Discord message 1505374318773796984
- Discord message 1505375282100568247
- Discord message 1505379754683924644