Bittensor Daily Daily digest of the Bittensor ecosystem

SUBNET TRACKER · All subnets

SN61 · RedTeam

Every Bittensor Daily mention of SN61 RedTeam, newest first. Price changes are snapshots from each edition.

24h change −3.38%

What happened
A dashboard issue left BEX challenge scores calculated only for UIDs up to 190 for several hours; the team confirmed the cause and said scoring was later completed. Separately, the team announced a new BV-2 challenge, which will replace the ADA-3 challenge rather than BEX-1, with a target release within the week.
Community
Miners repeatedly asked the team to check the scoring issue, and one community member asked the team to clarify what had gone wrong and what the new challenge would involve. A moderator later intervened after repeated personal attacks and spam in the channel, warning of timeouts if the bickering continued.
Official
The team confirmed the dashboard scoring issue, said BV-2 will replace ADA-3 (not BEX-1), and targeted a release within the week.

Read the full edition: Opentensor formally launches Gamma Tokens, letting wallets pay directly for subnet services, as the protocol ships three more emission-related changes the same week. →

24h change −0.27%

What happened
SN61 (RedTeam) said its CEO represented the subnet at the UK House of Lords to discuss cybersecurity threat detection technology, framing it as recognition of the subject at a government level rather than only by enterprise teams. The subnet's dashboard went down for several hours during the period and was reported multiple times by users. A miner also reported that submissions committed about 10 hours earlier had not been processed, asking whether there was a server issue.
Community
Community members discussed the House of Lords appearance, with some noting the team had gone quiet for several days beforehand after saying updates on clients and buybacks were coming. Others pointed out that many Bittensor-linked companies have been similarly quiet recently. A moderator reminded a community member to keep investor-related communication to channels outside the server.
Official
The official X account confirmed the CEO's appearance at the House of Lords, stating the subnet was introduced to members there and invited due to the relevance of its technology to recent major threats.

Read the full edition: The root-basket deposit freeze first confirmed on Nov 7 runs into a third day in #General, with a new symptom reported: a validator's entire basket appearing to vanish after an unstake. →

24h change +0.17%

What happened
A miner in the SN61 (RedTeam) channel raised concerns about InnerWorks' alpha buyback practices, noting that only 115 TAO had been bought back over more than three months despite the team's pledge to allocate 10% of SaaS revenue to buybacks. The miner called for transparent, consistent, and preferably monthly buybacks that reflect that commitment, and suggested the allocation could eventually be increased beyond 10%. The same miner compared the pledge to another subnet team's commitment of 20% of revenue.
Community
One community member responded approvingly, calling the post 'well said.' Separately, other members in the channel expressed frustration over delayed team announcements and unanswered questions, describing the team's silence on related topics as giving off 'weak team feels.'

Read the full edition: Subtensor confirms Root dividends are accruing but blocked from reaching stakers' baskets, an issue independently reported in #General the same day as a basket-display glitch. →

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.

Read the full edition: In #Rao, a flare-up over subnet 82's manually toggled emissions revives calls for transparent criteria, while #General logs a bridge-support scam vector and the week's quantum-wallet rollout gets an informal ETA. →

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.

Read the full edition: Opentensor launches eTAO, letting subnets set their own miner-validator-owner emission splits →