SUBNET TRACKER · All subnets
SN61 · RedTeam
Every Bittensor Daily mention of SN61 RedTeam, newest first. Price changes are snapshots from each edition.
24h change −18.53%
- What happened
- SN61 (RedTeam)'s alpha token fell sharply on a large outflow, including an 18% move in 10 minutes on Oct 29, with no team announcement, code release, or on-chain change identified as a cause. Separately, miners working on the BEX challenge reported unclear rejection messages such as "Invalid submission" and high comparison scores, and asked the team to clarify what counts as meaningful extension detection and whether null validation results indicate a service error.
- Community
- Community members asked what was happening as the price dropped and referenced the outflow figures reported in a third-party post. Several miners said they had been unable to reduce their comparison scores despite repeated submissions and pressed for clearer guidance on validation rules.
- Official
- The team said it was compiling an update on commercial traction, including a banking partnership it described as progressing faster than originally expected, ahead of the end-of-year target mentioned in its Novelty Search materials.
24h change +4.76%
- What happened
- A miner (UID 136) recorded a score of 1.0 on the subnet's BEX challenge using an undisclosed bypass technique, prompting accusations from other miners that the result was obtained unfairly. The team reviewed the submission and concluded the technique did not constitute cheating, since it was available to all miners at the time it was used. The submission was granted full BEX emission, and the validation checklist was updated to block the same technique in future challenges. The team also launched a new website that tracks buybacks, conviction-locked alpha, and monthly miner submissions, with a linked buyback wallet for verification.
- Community
- Miners widely disputed the 1.0 score, with several asking for revalidation or for emissions to UID 136 to be withheld, arguing the outcome discourages genuine detection work. A second miner's near-passing score of 0.7956 was also questioned as possibly bypass-related, with one suggestion to treat it as equivalent to the 0.8 passing threshold. Other miners said they could no longer compete with the top submission using standard methods and asked when a new challenge set would open.
- Official
- The team stated the bypass technique was not cheating because it was available to all miners at the time, confirmed full BEX emission for the submission, and updated the validation checklist to prevent the same method from passing future challenges.