THE DAILY BRIEFING

Bittensor Daily — October 15, 2026

Bittensor reduced the immunity period for newly registered subnets from 120 days to 60 and said registration lock costs will now fall twice as fast, a change aimed at speeding up subnet experimentation. The announcement came alongside a day of subnet-level incidents, including a self-transfer exploit identified on SN105 (Beam) and a prolonged validator outage on SN100 (Cortex) that left miners at zero incentive before being resolved.

01
Newly registered subnets now receive 60 days of immunity instead of 120, and registration lock costs will fall twice as fast as before.
The change affects how quickly new subnets can be tested and how capital flows into early-stage subnets across the network.
02
Miners on SN105 (Beam) identified an apparent self-transfer exploit allowing unusually fast transfer completions that bypass genuine upload verification, and the team temporarily raised transfer pricing to $15 per TB in response.
The exploit and a separately reported unstable benchmark destination caused penalties and rank drops for some honest miners, directly affecting miner payouts.
03
SN100 (Cortex)'s owner validator stopped setting weights on chain for over 100 hours, leaving newer bounty miners at zero incentive before the team reinstalled the validator and weight-setting resumed.
The outage shows how a single validator's failure can directly zero out miner rewards until the team intervenes.
04
SN28 (SayGM) was named TokenGauge's 2026 Provider of the Year, citing the lowest real-time inference prices on 17 of 21 AI models tested.
The recognition points to a Bittensor-based subnet being competitive on price against non-Bittensor inference providers.
05
A community member alleged that the Engy inference infrastructure used by SN11 and SN53 enables manipulation of evaluation scores, a claim the Engy team and a SN53 team member pushed back on.
The dispute touches on the integrity of scoring infrastructure shared across multiple subnets and remains unresolved.

SN92 24h +511.29%

REAX

What happened: SN92 (REAX)'s channel, previously unclaimed, was claimed by a new operator who launched the DecisionModels project built on a REAX inference engine and opened mining. Mining launched in two parts, 80% model hosting and 20% competitions, with the first competition focused on speeding up the REAX engine. Miners initially reported zero incentive with 100% burn because the operator's validator had not yet become the lead validator on-chain. The operator later introduced an EU-GDPR-compliant mining tier requiring EU company registration and a written contract for enterprise hosting.
Community: For an extended period before the claim, members speculated about who controlled the unclaimed channel, with some stating as fact that a known figure directed it; a moderator repeatedly intervened to limit unverified claims. After the channel was claimed, members congratulated the new operator and asked about the project's purpose, mining access, and the burn/incentive issue.
Official: The operator clarified that their validator's child hotkey would activate the next day around 09:30 UTC, after which their larger stake weight would determine consensus and resolve the zero-incentive issue. The operator also described the EU-GDPR tier as a way to serve enterprise customers subject to European regulation and stated it is, to their knowledge, the first subnet to offer this.

In debate · Who owns/runs SN92 (REAX) · 32 participants

Some members asserted as fact that a known figure was directing the subnet before any official claim.

“While it cannot be definitively stated whether the owner is Const, sn92 is precisely under Const's direction.”
Others pushed back, saying the figure in question was only an investor, not the owner.

“Ofc, he isn't the owner, just an investor”

SN105 24h −2.15%

Beam

What happened: Miners on SN105 (Beam) identified an apparent self-transfer exploit in which transfers show files already present at the destination, allowing unusually fast completions (one case cited at 2140 Mbps, ~400ms) that bypass genuine upload verification; one miner reported records suggesting roughly 100 UIDs involved across multiple groups. Separately, a validator-pointed benchmark destination (172.232.226.191:9000) was reported unstable, refusing connections and causing legitimate transfers from honest miners to fail, triggering 3x PRISM penalties and rank drops from Tier D to Tier E for some participants. The team temporarily raised Beam transfer pricing to $15 per TB as a short-term measure tied to the miner-owned transfer issue. Orchestrator operators also continued to report recurring NATS authentication-expired errors.
Community: Miners shared transfer IDs and timing data to document the exploit and debated whether it could be explained by legitimate caching, with one miner noting the etag used to verify uploads can be generated locally without an actual upload. A miner proposed an 'accredited account' system so only vetted customer traffic counts toward incentive, as a way to curb wash trading without banning accounts. Separately, miners affected by the unstable benchmark endpoint asked the team to filter or blacklist destinations that drop connections, and others troubleshot the NATS auth errors by rebuilding against the latest commit and matching API keys.
Official: The team stated the self-transfer exploit "is not tolerated and will be punished," with further information to come, and said a separate issue with stuck sell-allowance debt would be addressed separately. It also announced a temporary increase in transfer pricing to $15 per TB while the miner-owned transfer issue is addressed, calling the adjustment short-term.

In debate · Self-transfer wash trading exploit on Beam (SN105) · 10 participants

A miner presented transfer data suggesting a coordinated exploit across many UIDs.

“exactly. I have records that ~100UID involved. even different groups working together.”
A miner argued the exploit cannot be reliably distinguished from legitimate caching using current verification.

“the etag can be generated locally without upload. this one I have a code for already.”
A miner proposed an accredited-account system to separate genuine customer traffic from incentive-gaming transfers.

“Customer accounts can be "accredited" which is a distinction that is earned and makes your transfers part of the IM.”

SN100 24h −3.56%

Cortex

What happened: SN100 (Cortex)'s owner validator (UID 0) stopped setting weights on chain for over 100 hours, starting around block 9,246,399. Several other validators continued committing each epoch but revealed vectors identical to UID 0's old weight set rather than updated ones, leaving newer bounty miners at zero incentive. The team later reinstalled the validator, which resumed setting weights.
Community: Multiple community members, including affected bounty miners, flagged the frozen weights over several days and asked for an ETA and whether valid reports submitted during the outage would still be paid. One miner questioned whether unresolved comments meant the subnet was inactive; others defended the team, saying weight issues take time to diagnose. Separate discussion covered how long bug bounty rewards should remain valid, with one miner proposing a 72-hour decay period and another suggesting 48 hours.
Official: The team acknowledged the validator issue, said a fix was in progress, and confirmed the validator had been reinstalled to resume setting weights. Separately, the team announced Cortex received $10,000 in AWS credits following its earlier acceptance into NVIDIA Inception.

SN15 24h −4.89%

ORO

What happened: SN15 (ORO) validators repeatedly hit evaluation infrastructure failures, logged as "environment_error," with the leaderboard becoming stuck or stuck in a loop across several races. Miners reported agents completing evaluation on one validator but failing or being skipped on another, leaving results missing from the final leaderboard. The team later changed validator logic between races aimed at reducing these failures, though a miner reported the same "environment_error" message again in a subsequent race.
Community: Miners flagged the stuck leaderboard and evaluation errors directly to the team and asked for fixes, including a case where a specific agent's full evaluation did not appear in final results. Separate exchanges in the channel covered unrelated, informal discussion about team names and membership.
Official: The team said it made changes to validator logic between races intended to reduce environment-error failures and increase successful evaluation runs.

SN118 24h −7.41%

Ditto

What happened: SN118 (Ditto) adjusted its emission burn rate multiple times, setting burn to 70% with gamma at 0, after which the rate reportedly reached 100% before being reset back to 70%. Separately, a validator failed to submit scores, leaving several miners' agent submissions stuck and requiring team follow-up. The team also outlined plans, discussed at an Aug 26 AMA with Subnet Summer TAO, to cover costs from subnet revenue before putting a share of profit toward buyback-and-lock or buyback-and-burn.
Community: Miners objected when the burn rate reached 100%, arguing their work was effectively going unrewarded, and asked the team to lower it back to 70%. Others asked when the miner share would be increased and reported stuck submissions awaiting validator fixes.
Official: The team said the burn adjustments were meant to manage sell pressure, later reset the rate to 70%, and stated miner payouts are being informed by estimates of research value. Ditto's X account described the subnet as paying other Bittensor subnets for search, storage and compute while directing a share of revenue toward buyback-and-lock or buyback-and-burn.

More subnet community coverage every day in the Telegram channel →

Dispute over alleged score manipulation via Engy inference provider on SN11

A community member alleged that the Engy inference infrastructure used by SN11 and SN53 enables manipulation of evaluation scores and said the SN11 owner team has detected but ignored cheating patterns. The Engy team and a SN53 team member pushed back on the claims and asked that SN11-specific discussion be moved to the SN11 channel.

Positions

A community member argued that miners are exploiting the Engy provider to manipulate eval scores and that the SN11 owner team is aware but not acting on it.

“many cheaters tried to change eval scores. And the owner team detected cheating patterns, but they're still ignoring them”
The Engy team said such manipulation is technically possible but has not been observed and would be prevented by their safeguards.

“it's possible for now but we don't see people try to do it yet, and won't happen because:”
A SN53 team member maintained that complaints about SN11's incentive mechanism belong in the SN11 channel rather than SN53's.

“Please focus your issues with SN11 in the channel for SN11.”

Official response: The Engy team responded directly, stating that onboarded boxes are access-controlled via SSH, that logins or attempts to alter them would result in a ban, and that SN11 requests use zero-data-retention routing to avoid supply-chain manipulation; it also asked that SN11-specific debate be moved to the SN11 channel. No response from the SN11 owner team is recorded in these messages.
What to watch: Whether the SN11 owner team addresses the cheating allegations directly, and whether the discussion continues in the SN11 channel as requested.

@CryptoZPunisher

A community member argues that lowering Bittensor's subnet registration costs and immunity period will speed experimentation but raises questions about how capital identifies strong subnets, citing Yuma's ASMR research.

View the original post on X ↗
@YumaGroup

Yuma Group reports its Yuma Asset Management funds held 2.0% of Bittensor's total subnet market cap at the close of September, with AUM reaching an all-time high of $34.4M across three funds and an SMA.

View the original post on X ↗
@NiomeAI

NiomeAI reports SN55 (Niome) completed 10 million synthetic CRISPR experiments with 248 miners across 256 slots, 9 validators, and 723 tasks processed, and will now shift focus to pharmacogenomics.

View the original post on X ↗
@taodaily_io

Bittensor Daily reports SN28 (SayGM) was named TokenGauge's 2026 Provider of the Year, citing the lowest real-time inference prices on 17 of 21 AI models tested.

View the original post on X ↗
@chutes_ai

Chutes AI's week 22 update describes a new method called Epigenesis for adding knowledge to compressed Parallax models without altering base weights, plus an ongoing Lambda training run that has absorbed seven host failures.

View the original post on X ↗
@taodaily_io

Bittensor Daily reports newly registered subnets now get 60 days of immunity instead of 120, while registration lock costs will fall twice as fast as before.

View the original post on X ↗
@CryptoZPunisher

A community member highlights that SN28 (SayGM) now supports anonymous signup without email, positioning it as a private, TEE-routed gateway to frontier AI models.

View the original post on X ↗
@airesearch12

A developer announces the launch of DecisionModels, a platform for using benchmarked decision models, citing speeds up to 4x faster via its REAX engine and pricing from $0.019 per 1M input tokens.

View the original post on X ↗

◆2026-10-15 · End of this edition

No pull requests merged and no new release today.

24H Market

Gainers

Losers

Bittensor Daily — October 15, 2026

REAX

Beam

Cortex

ORO

Ditto

Dispute over alleged score manipulation via Engy inference provider on SN11

24H Market

↗Gainers

↘Losers

Bittensor Daily — October 15, 2026

Today's highlights

Subnet Community Pulse

REAX

Beam

Cortex

ORO

Ditto

Ecosystem debate

Dispute over alleged score manipulation via Engy inference provider on SN11

Voices on X

Protocol

Recent editions

Gainers

Losers