Leoma requests commit metrics surfacing, emphasizes task coverage
Share
Team clarified that commit history and remaining slots are tracked on-chain and currently require subtensor client queries; requested feature to surface `commit_history_len` and `commits_remaining` on public miner endpoint to reduce friction. Emphasized that 80%+ task coverage is needed to stay competitive, with penalties for task dropouts, and that model development (first-frame fidelity and prompt adherence) should be the primary optimization focus alongside the six-aspect rubric.
- •Feature request: expose commit metrics on miner dashboard endpoint
- •80%+ task coverage required; task dropout incurs penalties
- •Model quality (first-frame fidelity, prompt adherence) is half the score
- •EMA-smoothed task coverage feeds validator consensus and emission weight
Distilled from 3 team messages in the official Bittensor Discord. Generated by Claude Haiku 4.5.