Daily digest of the Bittensor ecosystem

中文/EN

Daily edition
Oct 25, 2026

Bittensor Daily A 1T1B product
1T1B ↗
BITTENSOR DAILY

24H Market

01/10

Gainers
--Loading…--
Losers
--Loading…--

THE DAILY BRIEFING

Bittensor Daily — October 25, 2026

SN15 (ORO) concluded an audit of its race system by banning accounts found to have manipulated inference spend limits, forcing a re-score of an affected race. Elsewhere, Grayscale filed an amended S-1 for a proposed TAO-holding ETF, and SN92 (REAX) released a new open-weights model alongside fresh engine champions. SN71 (Leadpoet) and SN51 (lium.io) also saw governance and transparency changes.

Today's highlights

  1. 01

    SN15 (ORO) banned 32 accounts covering 51 agent versions after an audit of races 1 and 2 found manipulated OpenRouter spend limits, discarding the affected agents and re-scoring Race 2 with a new top agent.

    The action sets a precedent for how the subnet enforces its inference cost cap and could affect miner incentives going forward.

  2. 02

    Grayscale filed Amendment No. 2 to its S-1 for the Grayscale Bittensor Trust on October 23, 2026, proposing a TAO-holding ETF for NYSE Arca listing.

    A listed TAO product would expand institutional access to TAO exposure through traditional markets.

  3. 03

    SN92 (REAX) crowned two new Generalist-track champions and released REAX 1.2, an open-weights fine-tune of REAX 1 under Apache-2.0.

    The release and new champions mark continued technical progress within the subnet's engine competition.

  4. 04

    A SN71 (Leadpoet) miner disputed new reward thresholds introduced 17 hours after a round's submission cutoff, saying the change cost a winning submission its reward; the team declined to adjust past rounds.

    The dispute highlights tension between mid-round rule changes and miner expectations for reward predictability.

  5. 05

    SN51 (lium.io) removed customer and miner IDs from its public rental dashboard for privacy and clarified that providers receive 95% of rental fees, with Lium keeping 5%.

    The changes alter transparency around participant identity while clarifying how rental revenue is split.

Subnet Community Pulse

5

SN15 24h −0.77%

ORO

What happened
Miners flagged the top-ranked agent, identified as Leen, for exceeding the $5 per-run OpenRouter inference cost cap during races 1 and 2, with other agents including Konoha and Saffron Lantern v1 also named. The SN15 (ORO) team opened an investigation, later confirmed an audit of races 1 and 2 (Oct 22-23) found accounts that had raised the spend limit on their evaluation keys after creation. The team discarded the affected agents, banned 32 accounts covering 51 agent versions, and re-scored Race 2 with 'enjoy' as the new top agent. Separately, several miners reported repeated anti-cheating rejections with 18-hour cooldowns and said the CLI gave no specific reason for the rejections.
Community
Miners posted detailed cost and eval-run data to support the cost-cap allegations and asked the team for clarity on anti-cheat policy. Some community members praised the miners who had flagged the exploit, while others continued to report unresolved anti-cheating rejections and asked for help identifying the cause.
Official
The team acknowledged the investigation, later confirmed via a detailed post that the audit found manipulated OpenRouter spend limits, and announced that affected agents would be discarded and accounts banned, reminding miners via a pinned message that manipulated keys lead to discard and ban.

In debate · SN15 inference cost cap exploit · 14 participants

  • Miners alleged the top-ranked agent exceeded the $5 per-run cost cap without consequence.

    “Why does the $5 limit not apply to this agent? Not fair!!!”
  • The team confirmed an audit found manipulated OpenRouter keys and detailed how the inference cap was supposed to work.

    “Every evaluation runs on a per-run OpenRouter key that ORO creates in your account with a fixed spend limit”
  • Some community members defended miners who had helped detect the exploit as strengthening the subnet.

    “He even detected LEEN's cheating on openrouter api key. They are making this sn much stronger and stronger.”

SN71 24h −3.36%

Leadpoet

What happened
A miner disputed new reward thresholds (+8/+15/+20) that were committed 17 hours after the arena-2026-10-23 round's submission cutoff, while scoring was already underway, and requested that the prior reward structure be applied to that round. The miner's submission had won arena-2026-10-23 with a score of 13.3 against a baseline of 5.725 but received no reward under the new thresholds. The miner requested compensation of about 1,030 alpha, citing the mid-round timing of the change. The team declined, stating the new reward system would not be adjusted for past rounds.
Community
Several other members echoed the miner's complaint, calling the change unfair and repeatedly asking the team to resolve it. One miner separately asked why they had not received incentive despite being a prior round's winner.
Official
The team said the new reward system is intentional, meant to ensure rewards go only to genuine agent improvements, and confirmed it will not adjust scores or emissions for the disputed rounds, noting no noticeable agent quality improvements occurred in those rounds.

In debate · SN71 retroactive reward threshold change · 9 participants

  • The miner argues the new thresholds were committed mid-round, after submissions closed and scoring began, making retroactive application unfair.

    “That was 17 hours after the cutoff, while the round was already being scored.”
  • The miner says the historical data shows the new thresholds are nearly impossible to clear given how margins are structured.

    “Only one round in six cleared +8, and that was 10-18, where the baseline scored 0.0.”
  • The team maintains the new system is final and that no reward should apply to rounds without genuine score improvement.

    “There wasn’t noticeable agent quality improvements in those rounds so no reward should be assigned”

SN105 24h −0.81%

Beam

What happened
On SN105 (Beam), a miner reported that sell-debt had appeared on a hotkey with zero recorded sales. Separately, a miner described a dispute over room-transfer eligibility, saying another operator's agent added delay to competing transfers and that requests from that operator's room consisted largely of hotkeys it controlled itself. The team confirmed that adaptive transfer limits and managed room lanes, which adjust parallel transfer capacity per destination based on delivery history, have been live since October 24.
Community
The miner who raised the sell-debt question asked for an explanation of how the debt was calculated. The miner raising the room-transfer concern asked the team how the current eligibility gate could detect the described pattern and whether delayed responses from a customized agent could be identified.
Official
The team said connection limits will become Beam-managed and that the eligibility gate needs more reference transfers to work at full capacity, adding that excluding such transfers is the anti-cheat system's responsibility. It also announced the adaptive transfer limits and managed room lanes update, live since October 24.

SN92 24h −3.69%

REAX

What happened
SN92 (REAX) saw two new REAX Engine champions crowned on the Generalist track: uid 57 at 12:42 UTC and uid 223 at 16:41 UTC. A separate submission (uid 196) was denied an award after the team found that undoing a per-channel rescaling of its MLP weights made it mathematically identical to an earlier submission. Separately, REAX released REAX 1.2, an open-weights fine-tune of REAX 1 under Apache-2.0, alongside REAX 1.1.
Community
Miners asked about inference weighting and the status of award approvals, with one miner asking directly why uid 223's award was taking longer than uid 57's. A validator also warned the channel about fake support-ticket links circulating in replies, telling members not to follow them or share keys and seed phrases.
Official
The team explained that uid 57's award was approved quickly because its runtime and kernel sources were already public, while uid 223's approval was held pending publication of source for 14 new compiled kernels; the award was approved once the source check passed. The team also detailed why uid 196 was denied an award, citing an identical computation after undoing a weight rescaling.

SN51 24h +1.95%

lium.io

What happened
The Lium team removed customer and miner IDs from the public rental dashboard, citing a privacy change, and is building anonymised concentration metrics showing the share of rented GPU-hours and rental revenue held by the top 1, 5 and 10 renters and providers. The team also clarified that providers receive 95% of rental fees, with Lium keeping 5%, paid daily as SN51 (lium.io) alpha or USDT, while emissions are a separate stream funding idle pay and a burn.
Community
A community member asked about the removal of IDs from the dashboard and requested anonymised concentration stats, later also asking for revenue-split, retention, and payment-method breakdowns. Another community member guessed the top 10 provider share was around 60%, without confirmation from the team.
Official
The team confirmed the privacy-driven removal of IDs and said an anonymised concentration view is built and in review, with additional holder metrics such as card-vs-crypto deposit share and renter retention also built but not yet live. It also clarified that the 95% provider share comes from rental fees, separate from the emissions stream.

More subnet community coverage every day in the Telegram channel →

Voices on X

  • @CryptoZPunisher

    Grayscale filed Amendment No. 2 to its S-1 for the Grayscale Bittensor Trust on October 23, 2026, proposing a TAO-holding ETF for NYSE Arca listing.

  • @VenturaLabs

    SN15 (ORO) removed 51 agent versions from 32 accounts that had raised evaluation spending limits above the $5 cap, then re-scored Race 2 without them.

  • @CryptoZPunisher

    The poster cites 90-day net trading flows of −306,600 TAO across subnets, SN51 (Lium) at +19,650 TAO, and estimated annualized subnet revenue rising from $32–35M to over $50M.

  • @reaxlabs

    Reax Labs released REAX 1.2, an open-weights fine-tune of REAX 1 under Apache-2.0, alongside the previously released REAX 1.1.

  • @TaoOutsider

    Astroware AI is offering HaloGuard EU at $30 per billion input tokens, using SN23 (Trishool) to screen AI outputs, described as a technical control without guaranteed EU compliance.

  • @TaoOutsider

    A proposed Bittensor lending draft would let traders go long or short subnet alpha with a default borrowing rate of 100% APR while positions stay in protocol custody.

  • @0xarrash

    Vanta plans to release permissionless entity miners that let anyone run a competing miner, onboarding traders via USDC-to-alpha conversion and earning emissions tied to volume driven.

  • @yanez__ai

    Yanez AI notes that US bank regulators are asking banks five questions about AI agents, per Reuters on October 13, covering oversight, auditability, authority limits, human control and shutdown.

◆2026-10-25 · End of this edition

Protocol

No pull requests merged and no new release today.

Recent editions

Past editions +