← All Subnet News

October 14, 2026 · Published daily

Subnet News — October 14, 2026

Bittensor halves subnet immunity and accelerates registration-cost decay. SN65 TPN publishes its model evidence, SN46 Instant joins Liquid Inference, SN55 NIOME reports its completed synthetic CRISPR run, and SN10 Pareton opens a Kimi K3 optimization campaign. Also: cross-subnet integrations, miner reward and reliability changes, Const’s SN92 correction and today’s SN48 Quantum Compute interview. Coverage through October 14 at 11:02 AM Eastern.

Coverage window
Oct 13, 2026, 12:49 PM – Oct 14, 2026, 11:02 AM ET
Subnets in coverage roster
128
Subnets with updates
25
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 · Ecosystemverified
★★★★★

Bittensor halves subnet immunity and speeds up registration-cost decay

Direct finalized node reads show NetworkImmunityPeriod falling from 864,000 to 432,000 blocks and NetworkLockReductionInterval from 115,200 to 57,600 blocks between blocks 9,275,607 and 9,282,237. At an assumed 12 seconds per block, those correspond to roughly 120→60 days of immunity and 16→8 days for the lock-reduction interval; calendar timing depends on block production. NetworkMinLockCost remains 1 TAO. This gives new teams less protected time to establish their subnet and makes registration costs decline faster. It is an observed active parameter change, not merely a proposal; it does not identify a newly deregistered slot or prove any particular sale.

Why 4 stars: Active protocol parameters change the protection period and entry-cost dynamics for subnet operators.

#02 · Ecosystemverified
★★★★★

Finney runtime 478 is now active

Yesterday’s report described Release 478 as merged without assuming activation. The node now returns specVersion 478 at finalized block 9,282,237, compared with 477 at the previous cutoff. Its release includes bounded restoration of missing staking-hotkey associations and stake-exit charging sized to the caller’s hotkey list on EVM/contract paths. That advances the story from available code to an active network version. It does not by itself certify that every historical association has already finished migrating.

Why 4 stars: Direct node evidence confirms deployment of protocol staking and execution-cost repairs.

#03 · SN46 · Instantverified
★★★★★

SN46 Instant joins Architect’s Liquid Inference marketplace

SN46 Instant announced on October 13 after the previous cutoff that it is actively serving GLM-5.3-Flash-Uncensored-FP8 through Liquid Inference, where providers bid on requests. Architect’s official profile welcomes the integration. This is a concrete external distribution channel for subnet inference, rather than yesterday’s unconfirmed listing plan. Request volume, revenue and independently measured latency were not disclosed. The team also directs followers from its recovered @instantsubnet account to @thinkinstant; both accounts now identify that migration.

Why 4 stars: Team and counterpart acknowledge a live inference distribution integration.

#04 · SN55 · NIOMEverified
★★★★★

SN55 NIOME reports completion of ten million synthetic CRISPR experiments

SN55 NIOME’s October 14 post reports completion of its synthetic CRISPR run and a transition toward pharmacogenomics, predicting drug response. Its post and inspected artwork explicitly describe synthetic experiments, not procedures performed on patients; the team says no real patient records were involved. It reports 248 miners across 256 slots, nine validators and723 tasks processed alongside the ten-million total. Those are distinct counts, not ten million independently audited clinical successes. This matters as a completed network workload and a clearly stated next research focus, while model utility and biological validity still require separate evidence.

Why 4 stars: A completed, named synthetic workload is a substantive milestone with clear boundaries around clinical interpretation.

#05 · SN65 · True Performance Networkverified
★★★★★

SN65 TPN publishes the evidence behind TPN-005

SN65 TPN’s October 14 case study adds concrete evidence to its October 12 model announcement. The K11 run record lists a 7.24 GB artifact, 10.98 GiB of measured RAM under an 11 GiB ceiling, and 73.93% on 1,400 fluid_knowledge items versus the F16 reference’s 66.57%. The file is 57.4% smaller than the 16.99 GB reference and the score is 7.36 percentage points higher. The study attributes the gain to capability-directed tuning as well as compression. Both linked records use the same sealed epoch and manifest; their recorded evaluation context is 8,192 tokens, so the model’s wider context capability is not a benchmark of that full window. These are published team results, not an independent rerun or a universal reasoning advantage. The new value is traceable evidence of meeting a specific memory-and-knowledge target.

Why 4 stars: A dated detailed case study and matching public run records substantiate a useful constrained-model result.

#06 · SN7 · Allwaysverified
★★★★★

SN7 allways changes capacity rewards and repairs validator startup

SN7 allways’ merge makes the capacity ramp linear and raises the qualified-volume portion of each lane pool from 25% to 35%. The same release addresses a repeated bond-relay vault walk that its incident notes say could stall validator boot for roughly300 seconds. A separate merge excludes unusable-address quotes from scoring for12 rounds. These changes alter how miners earn and reduce a documented startup failure path. Public code is verified; actual adoption by every validator and future returns are not.

Why 3 stars: Specific reward changes and an operational repair affect miner competition and validator availability.

#07 · SN10 · Paretondeveloping
★★★★★

SN10 Pareton announces a live Kimi K3 optimization campaign

SN10 Pareton’s October 14 announcement asks miners to accelerate Kimi K3 on SGLang using eight B300 GPUs and16 concurrent requests while preserving model quality. Its merged campaign fixture provides a primary implementation trail. The opportunity is workload-specific inference optimization, not a newly measured speedup or a claim that every customer already receives cheaper inference. The general landing page still includes a Coming Soon label, so this report attributes the live-campaign status to the official announcement rather than claiming a completed end-to-end miner submission test. A separate RTX5090 purchase post describes planned capacity expansion, not GPUs already serving customers.

Why 3 stars: A specific announced campaign and implementation give miners an actionable new optimization target.

#08 · SN15 · OROverified
★★★★★

SN15 ORO updates task-pack compatibility and the runtime contract

SN15 ORO’s merged release moves to oro-env-runtime3.7.0 and contract5, using a shared reader for both v7 andv8 task packs. It corrects a preflight startup failure when a v8 pack begins with an encoding record, and refreshes practice delivery and checks. The bundled practice set keeps the same30 tasks and grading. This matters to miners preparing submissions because a packaging mismatch should not masquerade as model failure; it is not a new benchmark win.

Why 3 stars: A verified task-loading and runtime compatibility update prevents a concrete startup failure.

#09 · SN21 · AdTAOverified
★★★★★

SN21 AdTAO adds an optional champion what-if forecasting relay

SN21 AdTAO’s code adds read-only forecasts from the current champion for what-if episodes, running under the daily sandbox and limits with a 75 second wall clock. It is off unless SN21_FORECAST_RELAY=1 and does not write those episodes into the scoring ledger. Another model-privacy state machine is expressly not wired into publication. This is a specific implementation step toward interactive campaign scenarios, not a confirmed public feature rollout or a promise of additional ad conversions.

Why 3 stars: An optional implementation connects champion models to scenario forecasts while protecting scoring state.

#10 · SN44 · Scoredeveloping
★★★★★

SN44 Score digest reports another evaluation check

SN44 Score’s October 14 digest says the team will investigate a requested UID 192 spot check and a possible person-detection ground-truth issue at block 9,277,200. A harder fallen-person challenge is planned for this week. Original scoring artifacts and the final investigation outcome were not independently obtained. This is a developing evaluation follow-up, separate from yesterday’s cricket restrictions; neither an accusation of cheating nor a promise of a harder test establishes what caused the disputed scores.

Why 3 stars: A current attributed incentive or evaluation issue is material to miners and remains unresolved.

#11 · SN51 · lium.ioverified
★★★★★

SN51 Lium protects rental hosts from memory exhaustion

SN51 Lium’s merged rental fix reserves host memory, caps each rental’s share, disables container swap and gives renter processes a higher out-of-memory priority. The incident notes describe an8×H200 rental consuming99.7% of guest RAM and starving the agent/executor for25 hours. Another fix isolates DNS lookups with a 15 second deadline and miner-scoped quotas so one stalled miner cannot monopolize resolution. These are concrete safeguards for availability, not evidence that every prior rental issue is resolved or a new monthly revenue result.

Why 3 stars: Primary incident notes and repairs address long-running rental and validator failure modes.

#12 · SN66 · conjecturesverified
★★★★★

SN66 Conjectures extends chat-log requirements to every open proof target

SN66 Conjectures’ merged October 13 policy requires the AI chat logs used to produce a proof for every open target, including submissions through the coldkey-signed CLI. The code checks linked-account logs after signature verification and refuses a missing-log submission before spending its payment. New-target terms also describe a 2.5% starting treasury share ramping to 12.5% over15 days and earlier-proof bonus provisions. This changes both evidence obligations and reward expectations; accepted submissions retain their recorded policy. Production publication settings are separately gated, so merged terms are not proof that every deployment has adopted them.

Why 3 stars: Verified submission and bounty-policy changes materially affect proof contributors.

#13 · SN67 · Harnyxverified
★★★★★

SN67 Harnyx adds SN28 SayGM as an agent inference option

SN67 Harnyx says its research miners can now run agents through SN28 SayGM’s model gateway. This links research competition on one subnet to inference competition on another: miners gain another way to supply the models their agents call. The official post describes auction-based serving and below-list pricing, but does not provide a matched invoice or guarantee savings on every model. It establishes an announced access option, not exclusive routing or a disclosed commercial contract.

Why 3 stars: A concrete cross-subnet integration offers research miners an additional inference route.

#14 · SN78 · Umideveloping
★★★★★

SN78 UMI prepares to preserve native reward history during cutover

SN78 UMI merged retained-history writer preparation and cutover support. This provides an implementation trail for carrying native reward history through the transition, but it does not independently establish that the successor reward system is paying in production. The dated digest still describes remaining work and a near-term target. The earlier activation question remains open rather than being quietly converted into a successful launch.

Why 3 stars: Reward-history continuity is material to a transition, with activation status kept separate.

#15 · SN81 · Reliquaryverified
★★★★★

SN81 Reliquary fixes a duplicate-answer cursor deadlock

SN81 Reliquary’s merged correction lets a corpus walk advance without payment when a submission repeats its own completion. Previously a prompt that naturally elicited only one answer could trap a miner indefinitely because admission rejected the duplicate before moving its cursor. Copying earlier work still does not earn advancement under this exception. This is a focused availability repair, separate from the earlier holdout scoring changes; deployment across the fleet was not independently checked.

Why 3 stars: A reproduced class of permanently blocked miner jobs receives a targeted implementation fix.

#16 · SN85 · Vidaioverified
★★★★★

SN85 VIDAIO and SN75 Hippius describe the Exploit archive integration

SN85 VIDAIO’s October 13 post describes its Exploit Summit test: English livestreams with French, Spanish and Chinese dubbing and subtitles, plus compression and searchable archives. SN75 Hippius explicitly confirms it supplies the archive’s storage. The conference itself happened earlier; today’s distinct evidence is the counterpart-confirmed storage connection and explanation of the workflow. The companies, universities and public services listed as possible users are use cases, not newly signed customers. Translation quality, cost savings and revenue were not independently measured.

Why 3 stars: Counterpart confirmation shows how two subnet services combine in a real event archive.

#17 · SN89 · InfiniteQuantdeveloping
★★★★★

SN89 InfiniteQuant raises its Markets entity dust floor after a pruning incident

SN89 InfiniteQuant’s October 14 commit says a collateral-holding Markets entity was pruned from UID199 around04:36UTC because its dust allocation sat below immune low/high-frequency miners. The change schedules a vault-UID floor inside the Markets vector from 13:00UTC, while retaining earlier-cycle behavior for historical replay. This is a concrete protective correction to the new Markets mechanism, not proof that pruning is reversed or every claimant is paid. The reported pruning details come from the primary incident note; the particular event was not separately reconstructed on-chain.

Why 3 stars: A documented pruning failure leads to an explicit reward-floor repair for collateral-holding entities.

#18 · SN96 · Verathosdeveloping
★★★★★

SN96 Verathos schedules its Decide validator handover

SN96 Verathos’ code now schedules the Decide validator handover at the approved block. The October 15 transition remains upcoming at this report’s cutoff. Yesterday’s legacy scoring outage and corrections remain an open incident; a scheduled handover does not prove missed emissions were repaired or the new production system is live. Miners should distinguish the tested code and transition plan from completed execution.

Why 3 stars: A primary handover implementation advances an imminent transition without implying incident resolution.

#19 · SN105 · Beamdeveloping
★★★★★

SN105 Beam digest reports continuing 503 and scoring complaints

SN105 Beam’s October 14 digest describes miners reporting destination 503 errors counted as hard failures and zero incentives despite workload completion. Deployment of the earlier NormalizePoints correction is questioned in the discussion. These are attributed reports awaiting original task traces and an independently verified resolution; they should not be read as established losses for every miner. Yesterday’s merged scoring code is not treated as an all-clear while these operational complaints remain open.

Why 3 stars: A current attributed incentive or evaluation issue is material to miners and remains unresolved.

#20 · SN108 · ChipForgeverified
★★★★★

SN108 ChipForge passes fair timing budgets to its EDA server

SN108 ChipForge’s validator code now supplies both remaining batch time and a fair per-evaluation window to the EDA server, preserving the location and timing of timeout failures. Named validator timeout outcomes distinguish no time to start, no server response and a batch timeout. This helps separate a poor chip-design submission from scheduling or infrastructure failure. The snapshot shows alpha/TAO down18.88% over24 hours; that is a market observation, not proof this patch caused the move or that all earlier disputes are settled.

Why 3 stars: Evaluation timing and diagnosable failures directly affect miner fairness and reliability.

#21 · SN117 · everyframe.studioverified
★★★★★

SN117 Everyframe releases miner profile recovery and batch offers

SN117 Everyframe’s everycli v0.5.3 release adds automatic profile recovery and batch model offers, followed by a fix for deleted workload bindings and refreshing approved operating-system deployments. The practical benefit is less manual recovery when a miner’s local profile no longer matches its registered workload. This advances the miner tooling beyond the previously covered v0.4 media work; it does not establish new inference demand or universal successful deployment.

Why 3 stars: A named miner release and recovery fix reduce specific onboarding and continuity problems.

#22 · SN118 · Dittodeveloping
★★★★★

SN118 Ditto digest acknowledges gamma-allocation concerns

The October 14 SN118 Ditto digest attributes an apology for insufficient advance notice of gamma allocations to the team and says the split is dynamic. It describes plans to increase miners’ share and introduce some burn this week alongside multi-track competitions. This is a developing response to the incentive dispute, not a newly verified fixed split, completed burn or independently checked Const endorsement. A primary treasury merge separately supports cold-approved manual transfers up to 2,500 alpha; that capability is not evidence any particular transfer occurred.

Why 3 stars: A current attributed incentive or evaluation issue is material to miners and remains unresolved.

#23 · SN120 · Affineverified
★★★★★

SN120 Affine documents unfunded proof-of-work onboarding and reward penalties

SN120 Affine’s public code and guide add an unfunded proof-of-work onboarding path and support1,000 registered UIDs after its Null consensus switch. A separate guide explains current audit penalties and decaying reward assessment, while history exports freeze the finalized evidence inventory. These are meaningful changes to access and reward transparency. “Unfunded” describes the supported onboarding path, not a guarantee of free compute, free network operations or profitable mining. No fresh Const claim is inferred from a secondary digest.

Why 3 stars: Verified onboarding and reward-accounting documentation affect who can participate and how rewards are assessed.

#24 · Ecosystemdeveloping
★★★★★

Registration and sale watch: no changed endpoints; history coverage remains incomplete

All128slot comparisons between finalized blocks9,275,607 and9,282,237 found no changes to SubnetOwner, NetworkRegisteredAt or NetworksAdded. The archive rejected the requested historical range method as unsafe externally, so this is a bounded state comparison rather than a complete no-event finding. SN109 Finsight’s previously reported operational handover still lacks independently verified buyer identity and price; an unchanged key neither proves nor disproves an off-chain agreement. SN24 Quasar’s reported multisig rotation likewise remains distinct from a completed sale. No new completed transaction is asserted from price alerts or scheduled swaps.

Why 2 stars: A sourced daily chain check separates observable state from unverified transfer and sale narratives.

#25 · Ecosystemverified
★★★★★

Today with Shizzy: SN48 Quantum Compute at 11:30 AM Eastern

Both the channel Live tab and player metadata confirm the SN48 Quantum Compute interview for October 14 at 15:30UTC, or11:30 AM Eastern/8:30 AM Pacific. At verification it is upcoming, not live. The Videos tab also shows the October 13 members update,12:22 long, which is now the latest members selection; playback stays behind YouTube membership access. The latest verified public episode remains the October 12 upload and stays the default player.

Why 2 stars: Verified schedule and upload metadata keep the channel library and access labels current.

#26 · SN28 · SayGMverified
★★★★★

SN28 SayGM offers an invoice-matching welcome credit

SN28 SayGM’s October 14 post offers to match an OpenRouter invoice with welcome credit up to$5,000 through its claim form. This is a promotional credit offer, not cash paid out, token yield or a guarantee every applicant qualifies. A separate model-pricing post claims Nano Banana2.1 costs31%less through the gateway, but a matched rate comparison was not independently exercised. The offer is relevant to inference buyers; private invoices were not submitted during this review.

Why 2 stars: A specific acquisition offer changes trial economics, with eligibility and savings left to the published process.

#27 · SN37 · Aureliusdeveloping
★★★★★

SN37 Aurelius publishes a disabled stake-retention design

SN37 Aurelius’ new incentives document describes a planned holding-time mechanism: retained stake builds credit, transferred-in stake earns no credit, and exits can incur penalties and debt. The document explicitly says the mechanism is currently disabled and details will be published before activation. Separate miner tooling adds an incentive-terms acknowledgement. This is useful advance notice for operators deciding how to participate; it must not be presented as an already enforced lock or a guaranteed reward boost.

Why 2 stars: An explicit planned incentive change and terms requirement warrant notice without assuming activation.

#28 · SN80 · OpenRobotodeveloping
★★★★★

SN80 OpenRoboto and peaq schedule an October 19 robotics discussion

Both teams’ posts schedule a joint discussion for October 19 at 11:00CEST, equivalent to 09:00UTC/5:00 AM Eastern. SN80 OpenRoboto names robotics data, machine identity and the economy around collecting real-world experience. This provides specific context for the earlier eye-emoji teasers, but no disclosed contract, deployed integration or commercial value. The four upcoming Solana Accelerate appearances remain separate, already-covered plans.

Why 2 stars: Counterpart-confirmed timing clarifies the teaser while preserving the difference between discussion and deployment.

#29 · SN92 · Subnet 92verified
★★★★★

Const denies owning SN92 after launch speculation

In a directly reviewed October 14 reply, Const answers “No not me” to a bot asking whether he owns SN92. The bot’s launch label and the slot’s roughly293.90%24 hour alpha/TAO rise do not establish current team identity or a new registration. Direct node endpoint comparisons show no registration-height or owner change between yesterday’s cutoff and block9,282,237; that comparison cannot exclude every intervening event or an off-chain deal. The verified news here is the denial, not an endorsement, ownership claim or negotiated sale.

Why 2 stars: A direct correction prevents a prominent identity rumor from being repeated as fact.

04

Audit trail

Coverage notes

Searched

  • All 128 subnet profiles, 98 dated briefs, 192 associated repository paths and 205 public X account samples; original announcements and selected full commit patches.
  • Signed-in @ShizzyUnchained: Grok daily discovery, qualitative top-five attention, omission checks and direct Const Posts/Replies.
  • AlphaGap public sources, SubnetRadar profiles/Moments, TAO Daily, TAO media, partners, market outliers, emission leaders and seven preceding editions.
  • Finalized archive-node owner, registration-height and network-status comparisons for all slots; runtime and registration-parameter state checked directly.
  • Both YouTube Videos and Live tabs, player metadata, public default, members access and next scheduled broadcast.

Public-data gaps

  • Public samples and Grok are not an exhaustive X census. Ten account samples returned no post links; private Discord originals were not read. Digest-only developments are labelled developing.
  • Historical state_queryStorage was rejected by the public archive RPC with error4003 (unsafe externally). Endpoint comparisons cannot exclude intervening temporary changes; full-window registration/removal replay remains incomplete. No exhaustive no-events claim is made.
  • Some media and older sparse-caption posts remain unreviewed or inaccessible. Viewed media and individual gaps are retained in the dated audit; text or a scheduled time is not proof of a completed launch.
  • AlphaGap’s full paid/live leaderboard was not inspected. Public commits establish code state, not fleet-wide deployment. Team benchmarks and synthetic experiment totals were not independently rerun.