← All Subnet News

October 3, 2026 · Published daily

Subnet News — October 3, 2026

SN64 Chutes stops Kappa training and reports preliminary results. SN120 Affine documents revealed weights for its new math-mining mechanism. SN15 ORO reports a race pause, SN118 Ditto targets reward recovery, and SN111 Claims reportedly plans a 90% miner-emission burn. Plus SN78 UMI intake, SN105 Beam’s live bug portal, shipped tooling, launch delays and the latest members video.

Coverage window
Oct 2, 2026, 11:34 AM – Oct 3, 2026, 2:07 PM ET
Subnets in coverage roster
128
Subnets with updates
29
01

Biggest stories first

Today's ranked news

★★★★★ marks the day's most consequential news. Scores weigh the size of the announcement, evidence quality, ecosystem reach and relevant market reaction.

#01 · SN64 · Chutesverified
★★★★★

SN64 Chutes stops Kappa training and reports preliminary benchmark results

The Kappa run has stopped. On October 3, Jon Durbin says its 576-billion-token checkpoint beat Llama 3.2 1B on ARC-C, OBQA and TQA, and nearly matched it on ARC-E and SciQ. He reports roughly 90% lower cost per training token, but also discloses gradient spikes, discarded late-node evidence and weak reasoning. An attention change is being tested for a future run. Preliminary serving code is public. These are scoped team results, not an independently reproduced benchmark or a production-ready chatbot; the older model card still describes an ongoing research run.

Why 4 stars: A stopped distributed-training run, specific comparisons, disclosed failure modes and inspectable serving code provide substantial research progress. Cost and quality claims retain their preliminary scope.

#02 · SN120 · Affinedeveloping
★★★★★

SN120 Affine reports revealed reward weights for its new math-mining mechanism

SN120 Affine has moved beyond yesterday’s preparation-only pilot. Its October 3 public release documents 42 audited task batches from 19 miners and says the revealed reward vector matched those recipients at Finney block 9203767. It reports its validator now assigns all its weights to the new mechanism; earlier nonpayable pilot epochs remain ineligible. The public dashboard shows a finalized epoch and 20/32 solved held-out tasks. The latest matched score fell from 22/32 to 20/32, so this is a mining and reward-routing milestone, not evidence of improved learning. Wallet-level receipts and other validators’ vectors were not independently checked here.

Why 4 stars: A documented cutover from a nonpayable pilot to revealed reward weights is material execution, supported by current public release and dashboard evidence. Learning gains and individual payments remain separate.

#03 · SN8 · Vantaverified
★★★★★

SN8 Vanta adds selectable daily loss limits in public code

SN8 Vanta’s new public code allows standard and Hyperliquid-linked subaccounts to choose a 3% or 5% intraday drawdown limit when created. The chosen value is immutable afterward; omitted values keep each bucket’s default. This adds a specific risk-control choice to the existing account system. The merge was checked, but a live customer creating an account under the new setting was not tested, and no change to every existing account is implied.

Why 3 stars: A defined account risk-control option is useful product progress, with code publication distinguished from customer activation.

#04 · SN10 · Paretondeveloping
★★★★★

SN10 Pareton prepares to sunset its current Qwen optimization campaign

The October 3 team-attributed brief says SN10 Pareton’s Qwen3.8-27B NVFP4-BF16-LMHead campaign is nearing its performance ceiling and will be sunset. Alternative GPU targets are being considered, but no replacement campaign is finalized. This is separate from yesterday’s production integration with SN53 engy: closing one miner optimization challenge does not mean that serving partnership has ended. A completed replacement launch or exact reward-stop time was not located.

Why 3 stars: A campaign transition affects what miners should prepare for, with the replacement and timing still unresolved.

#05 · SN14 · Cacheonverified
★★★★★

SN14 Cacheon adds reward-publication continuity through outages

SN14 Cacheon merges code that retains validated reward inputs when intake or a gateway is unavailable. Followers can reuse the latest authenticated allocation for up to 12 hours; missing or older evidence selects the subnet-owner burn vector. Repeated refreshes do not extend that evidence’s lifetime. This aims to stop an infrastructure outage from immediately interrupting publication while preserving an expiry boundary. The commit explicitly records no live service or chain writes, so it is a verified code change rather than a confirmed production recovery.

Why 3 stars: A bounded fallback directly addresses reward-publication reliability without silently making stale allocations permanent.

#06 · SN15 · OROdeveloping
★★★★★

SN15 ORO reports a race pause and tightens copied-agent rules

Yesterday’s Race 11 reminder needs an operational follow-up. The October 3 team-attributed channel brief reports a validator problem paused the race, with a fix underway, and says copied or padded agents will be removed from rankings. Public validator v2.1.0 also binds work claims and deliveries to the same runtime contract. The brief reports 100% incentive burn while no race ran; a proposed reset after the next race is not a confirmed payout. Low-cost agent reports are under review, not proof that particular miners exploited the network.

Why 3 stars: A paused race, payout implications and a concrete runtime fix are actionable changes for miners; unresolved accusations are kept out of the findings.

#07 · SN46 · Instantdeveloping
★★★★★

SN46 Instant reports its verifier back online and a higher epoch reward

The October 3 team-attributed brief says SN46 Instant’s verifier is back online, proofs are populating again and the epoch reward increased from $50 to $80. It also reports performance gains, but this scan did not reproduce the workload or confirm every miner’s payment. Yesterday’s validator v0.1.3 release remains available; publishing that release alone does not prove all operators updated. The recovery and reward amount are developing operational reports, not an independently verified network-wide all-clear.

Why 3 stars: Reported proof recovery and a specific epoch-reward change matter to miners, with measurement and payment gaps retained.

#08 · SN49 · Nepher Roboticsdeveloping
★★★★★

SN49 Nepher plans stricter rules for its next tournament

An October 2 team-attributed channel brief says SN49 Nepher will keep the current tournament rankings while strengthening checks that distinguish users and enforce policy-compliance rules in the next tournament. This is a new operational follow-up to the previously announced simulation environment. The revised checks are prospective, and this scan did not independently audit the disputed submissions or confirm payout settlement. Allegations about individual participants are not presented as findings.

Why 3 stars: Reported changes to tournament eligibility and enforcement affect miner preparation and advance the earlier environment announcement.

#09 · SN54 · Yanezdeveloping
★★★★★

SN54 Yanez reportedly returns online; UAV rewards remain gated

An October 2 team-attributed brief, reviewed as a late operational follow-up, says SN54 Yanez is back online and miners compete for KAV rewards. It says additional UAV rewards open after the sandbox cycle ends. That preserves the distinction from the September 30 pause: a general service recovery does not establish UAV rewards are already active. A separate primary update explains how Pulse and Gate transactions are intended to buy alpha and hold a share publicly; this is a described mechanism, not a reconciled purchase ledger.

Why 3 stars: A reported service recovery updates the prior outage and keeps the separate reward gate visible.

#10 · SN60 · Bitsec.aideveloping
★★★★★

SN60 Bitsec reportedly starts a round with an upgraded screener

SN60 Bitsec’s October 3 team-attributed brief says a new round began Friday using Opus 5.5 in the screener. Previously passing agents may fail under the updated evaluation, and the team may extend the submission window if none pass. That is a changed screening standard, not proof earlier agents acted improperly. The preliminary hard-steering measurements reported October 2 were team tests; this scan did not reproduce them or independently check the new round’s payouts.

Why 3 stars: A changed active screening standard can materially affect submissions and eligibility.

#11 · SN74 · Gittensorverified
★★★★★

SN74 Gittensor ships SparkInfer v0.6.9 with broader model support

SN74 Gittensor’s SparkInfer v0.6.9 has downloadable Linux and Windows builds and adds support for llama.cpp UD dynamic-quantized models. Its scoped RTX 5090 benchmark on Qwen3.8-27B-UD-Q4_K_M reports 94.7 versus 83.1 decode tokens per second at 128-token context. The notes retain a 1.2% perplexity cost from one quantization conversion and mixed results at different concurrency levels. New runtime code also falls back to eager execution when CUDA graph capture fails, preventing stale-token output. These are release measurements, not universal speed or accuracy guarantees.

Why 3 stars: An actual release expands supported models and addresses correctness, with hardware, workload and accuracy tradeoffs stated.

#12 · SN78 · Umiverified
★★★★★

SN78 UMI grows C5 intake to 203 submissions; rewards remain inactive

SN78 UMI’s public API at 17:58 UTC on October 3 recorded 203 accepted submissions with admission open. It still returned intake_no_weight mode, rewards_active false and chain_submission_authorized false. New model-intake code streams artifacts directly into storage and recovers expired uploads, a useful step for larger model submissions. The channel’s October 3–4 roster and evaluation targets remain targets, rather than a completed payout round. New press distribution describes camera-based sign translation, but it does not establish shipped SignVision glasses, paid orders or independently verified deployment.

Why 3 stars: Growing intake and a concrete artifact-upload improvement are meaningful competition progress; the live API prevents an unsupported reward-restart claim.

#13 · SN79 · MVTRXdeveloping
★★★★★

SN79 MVTRX reports v0.6.2 on mainnet; multi-asset simulation is next

The October 3 team-attributed brief reports v0.6.2 on mainnet, with account skill based on its own trading and both scoring halves paying proportionally. The proportional-pay direction was already covered September 29; the new claim is versioned mainnet rollout. Reported liquidity growth and lower aggressive volume remain team figures. Multi-asset simulation in v0.6.3 targets next week, while TradingView and anonymous access remain pending. The public site refresh is visible, but this scan could not independently inspect the claimed mainnet release or payout vector.

Why 3 stars: The reported versioned rollout and next-step timing advance the previous scoring story without treating plans as shipped features.

#14 · SN81 · Reliquaryverified
★★★★★

SN81 Reliquary adds numeric science tasks; the profile is still dormant

SN81 Reliquary registers a science environment with 13,547 numeric-answer problems from physics, chemistry, computer science and economics. Current grading accepts answers within 2% of the reference without an AI judge; biology was removed after a teacher-model probe. This extends the available training catalog, but the release explicitly places it in a dormant profile that no live registry entry pins. A new public paying science job is not established. The revised count and tolerance supersede the first draft’s 14,145 problems and 1% tolerance.

Why 3 stars: A concrete new environment broadens verifiable training tasks, while its dormant activation status is explicit.

#15 · SN105 · Beamverified
★★★★★

SN105 Beam opens a signed bug-report portal for orchestrators

SN105 Beam’s bug-report page is accessible and describes reports signed with an orchestrator hotkey. The loaded page says reporting is open to registered orchestrators, who connect a wallet and sign a message. Confirmed bugs may qualify for a reward; that is eligibility, not a promised payment for every report. This is a completed reporting interface beyond yesterday’s announcement that one was coming. No wallet was connected and no report submitted during this check.

Why 3 stars: A directly inspected reporting interface gives operators a concrete support and reward-eligibility path.

#16 · SN111 · Claimsdeveloping
★★★★★

SN111 Claims reportedly plans 90% miner-emission burn next week

SN111 Claims’ October 3 channel brief and TAOli’s recap describe a plan to raise the burned share of miner emissions from zero to 90% next week, then reduce it as processing capacity grows. If applied, only the remaining 10% of that miner allocation would be distributed before other eligibility rules. This is a prospective allocation change, not an observed token sale or a confirmed burn already in force. The channel brief does not identify a confirmed team speaker, and the profitability and price-stability claims are not independently established.

Why 3 stars: A reported change this large warrants miner visibility, with source identity, future timing and activation uncertainty explicit.

#17 · SN118 · Dittodeveloping
★★★★★

SN118 Ditto reports reward propagation and targets unburning today

The October 3 team-attributed brief says screening fixes are being verified before unburning today and reports rewards propagating through weights. Public code now retries a transient provider failure without discarding a completed review and safely retries an image-upload completion whose response was lost. It also adds line-based copying checks for code split across modules. These fixes are inspectable, but this scan did not reconcile a revealed reward vector or wallet receipts. The reward restart remains developing; the planned 2027 Gamma beta is not a launched payment service.

Why 3 stars: The reported restart and concrete recovery fixes advance a long-running reward incident, while payment confirmation remains outstanding.

#18 · SN122 · CookingTAOverified
★★★★★

SN122 CookingTAO publishes participation docs; revenue dashboard is planned

SN122 CookingTAO’s October 2 announcement links a working documentation site covering developer code submissions and no-code miner deployment. Its separate update says a dashboard for revenue, buybacks and user growth is planned for next week, with buybacks intended after beta V2 completion in October. Those are future steps, not an already published dashboard or independently checked purchases. The practical change today is that developers and users have a public participation guide.

Why 3 stars: Working documentation lowers the barrier to participating, while the dashboard and buyback plans remain accurately prospective.

#19 · SN11 · TrajectoryRLdeveloping
★★★★★

SN11 TrajectoryRL reportedly investigates missing miner rewards

The October 3 team-attributed brief says SN11 TrajectoryRL is checking an incident in which a miner reported receiving no rewards. Suggested UI and scoring explanations remain speculation; no confirmed root cause or completed repair was located. This is a reported investigation, not evidence that all miners stopped earning.

Why 2 stars: A newly reported reward investigation deserves visibility without generalizing one report to the whole subnet.

#20 · SN44 · Scoredeveloping
★★★★★

SN44 Score demonstrates beverage detection and works on evaluation images

SN44 Score’s October 3 primary post shows its Beverage Container Detector handling crowded Oktoberfest scenes and describes Score Studio as a way to refine detection beyond a base model. Separately, the team-attributed brief says a better image pipeline for fallen or crouching person detection is in development. These are a product demonstration and work in progress, not a newly proven customer contract or a confirmed fix for yesterday’s zero-score emission issue. The break-even and burn milestone was already covered October 2.

Why 2 stars: A fresh demonstration and specific pipeline work add product context without repeating yesterday’s business milestone.

#21 · SN61 · RedTeamdeveloping
★★★★★

SN61 RedTeam reports a browser restart after degradation

The October 3 team-attributed brief says degraded browsers were restarted after a day off and the team expects the issue to be resolved. Browser availability was not independently exercised here, and member reports about ADA grading remain separate. This does not resolve the previously tracked Kraken onboarding and buyback dependency, or turn disputed registration-fee allegations into findings.

Why 2 stars: A specific operational recovery is relevant, with other incidents kept separate.

#22 · SN71 · Leadpoetverified
★★★★★

SN71 Leadpoet tightens article evidence extraction

SN71 Leadpoet’s October 3 code removes related-news widgets from article evidence used in its lead-review pipeline, preventing an unrelated recommendation from being read as part of the article itself. This is a specific evidence-quality fix amid broader recovery work. The previously reported upstream scoring API incident is not declared resolved merely because new code merged or an interview was reposted.

Why 2 stars: A concrete evidence-extraction correction improves review fidelity while preserving the unresolved incident watch.

#23 · SN80 · OpenRobotodeveloping
★★★★★

SN80 OpenRoboto considers higher fees and private submissions

The October 3 team-attributed brief says SN80 OpenRoboto is considering a 0.5 TAO submission fee and private entries in response to concerns about near-copy models. These are proposals under assessment, not fees confirmed in force. Member accusations against individual miners were not independently established and are not repeated as findings. Yesterday’s simulation result remains a separate, already-covered story.

Why 2 stars: Possible participation-rule changes warrant a clearly labelled watch, without overstating adoption.

#24 · SN97 · Albedoverified
★★★★★

SN97 Albedo stops its simulator inventing Git history

SN97 Albedo’s October 2 code fix requires its simulator to use real repository history for git show and git log instead of inventing commits. That improves the fidelity of a coding agent’s evaluation environment. A separate member-only brief reports wrongful strikes removed and submissions requeued; those account-level recovery claims were not independently verified and are not treated as a completed reward correction.

Why 2 stars: A specific environment-fidelity fix is inspectable and relevant to evaluation quality.

#25 · SN108 · ChipForgedeveloping
★★★★★

SN108 ChipForge moves its launch target to Monday, October 5

SN108 ChipForge is still inactive according to the October 3 team-attributed brief, which now targets Monday, October 5 for launch. This replaces the October 2–3 expectation tracked in the previous edition. No active challenge or completed launch was verified at cutoff. Questions about self-mining in an inactive subnet are not evidence of misconduct.

Why 2 stars: A changed launch date resolves an outdated expectation without claiming activation.

#26 · SN109 · Finsightdeveloping
★★★★★

SN109 Finsight holds mining launch for additional social APIs

The October 3 team-attributed brief says SN109 Finsight has MVP code ready but is delaying mining while integrating additional social-media API endpoints following discussions with SN13 Data Universe. A weekend update is planned. Ready code and conference discussions do not establish active mining, a completed partnership or production access to the additional data.

Why 2 stars: A concrete launch dependency explains why mining has not begun.

#27 · SN114 · SOMAdeveloping
★★★★★

SN114 SOMA plans access to its JEV decision model in miner runs

The October 3 team-attributed brief describes a next-round feature letting miners call the JEV decision model with their existing OpenRouter key. It points to a feature branch and says the current Copilot and DeepSeek V4.1 Flash harness remains for this round. This is a planned integration, not a verified deployed feature. Completion of the earlier sandbox rerun remains unconfirmed, and the previously described savings fees and buyback model are not treated as active revenue.

Why 2 stars: A specific next-round capability is useful roadmap information with deployment and recovery gates retained.

#28 · SN117 · everyframe.studioverified
★★★★★

SN117 everyframe.studio ships clearer readiness checks in v0.2.3

SN117 everyframe.studio’s everycli v0.2.3 has downloadable macOS and Linux binaries and replaces a generic approval error with specific readiness diagnostics. It distinguishes pending or stale attestation, missing heartbeats, disabled miners and mismatched workloads. The docs clarify that workload attestation is automatic. This is a real maintenance release beyond yesterday’s v0.2.2, not a guarantee of admission or earnings.

Why 2 stars: Shipped diagnostics help operators resolve real setup failures without confusing automatic checks with manual approval.

#29 · SN121 · sundae_bardeveloping
★★★★★

SN121 sundae_bar delays SBC30 while revising scoring

The October 3 team-attributed brief says SBC29 has concluded and SBC30 is delayed until Monday or Tuesday, October 5–6. Planned changes aim to distinguish general skills from test-tailored submissions, allow reference files and improve grading of long legitimate outputs. These are next-round changes, not a completed new challenge or proof every prior reward has been settled.

Why 2 stars: The revised schedule and scoring direction give participants a useful preparation update.

04

Audit trail

Coverage notes

Searched

  • All 128 active subnet slots and 97 October 2–3 channel briefs screened, with selected briefs read in full.
  • Signed-in @ShizzyUnchained X research included general Bittensor/TAO discovery, reward/launch watch searches and the full SN64 result thread. 192 associated public account candidates sampled and 181 unique current post records screened; these include commentators and quoted accounts, not only official teams.
  • 178 repository paths scanned. 22 selected commit records inspected, together with current release assets, SN78 public status, SN120 release documents and dashboard, SN105 portal and SN122 docs.
  • Signed-in AlphaGap 119-subnet leaderboard, SubnetRadar news and Moments, TAO Daily, TAO Media and partner sources reviewed. Market snapshot and current emission leaders checked separately.
  • September 26–October 2 editions reviewed for duplicate stories, unresolved incidents and missed material announcements. Code, forecasts, launches, weights and individual payments were distinguished.
  • YouTube Videos and Live tabs checked. New October 2 members upload ChgsHOGC1hM has verified member restriction and 526-second player duration; latest public upload and SN49 replay remain unchanged.

Public-data gaps

  • Research cutoff 2026-10-03T18:07:32.413Z; overlap includes October 2 announcements after the previous cutoff. Associated-account samples and focused signed-in X searches are not exhaustive SN-number/name searches, and no Grok scan is claimed.
  • 12 repository paths returned errors and 9 public account candidates yielded no usable posts. SN79 release and guessed SN46 miner repository paths returned 404; those releases are not independently verified.
  • Channel briefs are AI-generated discovery summaries. Team-attributed statements remain developing when the original speaker or live activation was not independently checked. Member-only allegations do not become findings.
  • SN120 reward-vector readback is reported in public operator documentation; this scan checked the documents and current dashboard, not a full independent on-chain recipient reconstruction or wallet payments. SN64 cost and benchmark comparisons are team-reported and not reproduced.
  • SN78 API still says rewards inactive. AP-hosted press release returned 403; the official press link and secondary recap were read, but syndicated press exposure is not independent customer verification or proof of shipped glasses.
  • SN118 reward restart, SN46 proof recovery, SN54 recovery and SN111 proposed 90% burn retain activation or payment gaps. SN22 scoring bottleneck and SN44 reward issue are not independently closed.
  • No completed SN104 security-track mainnet launch, SN124 Sentinel release, unrestricted SN94 mining or SN114 sandbox rerun was verified. SN108 now targets October 5; SN65 TPN-005 remains in final diligence. SN55 display repair does not close its prior scoring investigation.
  • SN82 current identity remains unverified after re-registration; its flagged seven-day return is not attributed to a former project. SN26 identity discrepancies remain unresolved. SN113 ownership-transfer reports lack verified team identity and a matched chain transfer.