SUBNET TRACKER · All subnets
SN55 · NIOME
Every Bittensor Daily mention of SN55 NIOME, newest first. Price changes are snapshots from each edition.
24h change −0.18%
- What happened
- Miners reported that SN55 (NIOME)'s top-ranked miners have been receiving scores with unusually rounded values since a round identified as 5f7cc0c7, the same point at which WandB logging for the subnet stopped. The subnet team subsequently paused the task generator and owner validator for a leaderboard update, saying both would return online soon.
- Community
- Multiple community members, including a miner and a validator, repeatedly asked the team to explain the rounded scores and to restore WandB logging, noting they could not audit miner performance without it. Several messages expressed frustration at what they described as a lack of response from the subnet owner.
- Official
- A team representative said WandB is currently unavailable due to a service issue, that the leaderboard is being updated, and that the team is investigating how top miners submit their results.
24h change +24.25%
- What happened
- Community members reviewing a validator's public Weights & Biases logs on SN55 (NIOME) found that submissions from all 256 uids were being skipped as "not found," while scores were still recorded for roughly 100 uids tied to 8 coldkeys. The team later confirmed validator-side submission and benchmarking problems, attributing them to new compression logic, and said a fix had been applied. The next competition phase went live on testnet, and validators were separately reported to have issued no tasks for about 15 hours. NIOME also announced a GENOME-to-NIOME token migration starting October 28, which it said could bring roughly 1,500-2,000 TAO into the ecosystem.
- Community
- Community members posted log excerpts questioning why scored uids matched those marked as having no submission, and one review raised concerns about whether duplicate-owner protections were properly enforced across multiple uids. Others reported submission uploads failing and asked why mainnet and testnet appeared to be down, with some waiting for the team's response.
- Official
- The team said it investigated the validator codebase after miner reports, identified and fixed submission and benchmarking issues caused by compression logic, and said v4 would be released on testnet before mainnet.