← All Subnet News

October 6, 2026 · Published daily

Subnet News — October 6, 2026

SN108 ChipForge’s NPU challenge is active, SN65 True Performance Network opens TPN-005, and SN91 Cascade’s ensemble leads its live forecasting benchmark. SN107 Minos details its second mechanism and SN55 NIOME announces pharmacogenomic inference. Plus Talisman’s TAO bridge integration, Grayscale’s Coinbase custody filing, SN38 ChronoLLM’s merged Round 14, reward repairs, business updates and today’s stream.

Coverage window
Oct 5, 2026, 11:10 AM – Oct 6, 2026, 10:44 AM 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 · Ecosystemverified
★★★★★

Talisman adds ForeverMoney’s TAO bridge inside wallet swaps

Talisman and ForeverMoney both announced on October 5 that TAO bridging is now available inside Talisman Swaps. The route connects Bittensor Finney and EVM with Base and Robinhood Chain using ForeverMoney’s Chainlink CCIP infrastructure. The practical advance is distribution and access: holders can begin the cross-chain route in a wallet they already use for Bittensor staking, while people acquiring bridged TAO can move back toward native subnet participation. This is a new wallet integration, not the first launch of TAO on those networks. TAO on Base and Robinhood is a bridged representation. Both announcements and the integration article were checked; this review did not submit a bridge transaction or independently audit reserves and security.

Why 4 stars: A confirmed wallet and bridge integration expands practical TAO access, supported by both parties and direct documentation rather than unrelated platform activity.

#02 · Ecosystemverified
★★★★★

Grayscale adds Coinbase custody for its Bittensor Trust

Grayscale’s October 5 Form 8-K confirms Coinbase was added to the Bittensor Trust’s custody arrangements through a September 29 agreement amendment. Coinbase is intended to safeguard a portion of the trust’s TAO; BitGo remains primary, and the filing says Grayscale had not yet decided how much TAO to move. It also updates the BitGo agreement through a September 30 amendment. Adding a second custodian is a concrete institutional infrastructure development and is described as risk management as the trust grows. The document does not announce an ETF approval, exchange listing, new Coinbase retail TAO listing or completed transfer amount. Those are separate claims from the custody change verified here.

Why 4 stars: The primary SEC filing establishes a material TAO trust custody change, with exact agreement dates, retained primary custodian and no invented ETF approval.

#03 · SN55 · NIOMEdeveloping
★★★★★

SN55 NIOME announces its pharmacogenomic inference network

SN55 NIOME announced a live pharmacogenomic inference network at 13:03 UTC today. Miners analyze synthetic patient cases, infer genetic variants, derive metabolizer phenotypes and match prescribing actions to CPIC reference tables; validators compare them with known answers and score accuracy, consistency and confidence. This makes the target a reproducible research benchmark rather than collecting private patient genomes. The announcement names seven genes, but the linked repository’s current scope lists five: CYP2C19, TPMT, CYP2C9, SLCO1B1 and CYP3A5. DPYD, CYP2D6 and more difficult read-based cases remain on its documented development path. The launch is a direct team announcement backed by public implementation; this scan did not independently demonstrate production rewards, clinical validation or use in patient treatment.

Why 4 stars: SN55 NIOME publishes a substantive new inference task and inspectable scoring design. The actual implemented scope and unverified clinical and production outcomes are explicit.

#04 · SN65 · True Performance Networkverified
★★★★★

SN65 True Performance Network opens TPN-005 with an 11 GiB model ceiling

SN65 True Performance Network has opened TPN-005, its first competition since the Fluid Bench upgrade. The target is Ministral-3-8B-Uncensored: fit within an 11 GiB measured memory ceiling while retaining a 32,768-token context and capability on Fluid Knowledge. The live validator configuration lists three winners with a 60/25/15 split of this competition’s pool. Miners now pay for and run their own benchmarks before committing; runs must finish before scoring starts and must match the submitted model’s exact revision and file. The team says the private question set is intended to resist benchmark memorization. Published competition rules are not a winning result: weights begin during the later distribution phase, and no TPN-005 winner or payment was established in this scan.

Why 4 stars: SN65 True Performance Network has an active, directly checked competition with a new evaluation process and concrete memory, context and reward rules.

#05 · SN91 · cascadeverified
★★★★★

SN91 Cascade’s Ephemeris ensemble leads its current live forecasting benchmark

SN91 Cascade has published an Ephemeris update combining six forecasting models instead of betting on one. Its Weir page showed the ensemble first in the current round, with CRPS 0.581 and MASE 0.767; lower is better. That round covers 1,280 forecast windows across 289 live series and 19 entries, including statistical baselines and other ensembles. The October 6 update weights models by measured accuracy and replaces PatchTST-FM r1 with r2. This is a useful product and evaluation advance: forecasts can combine strengths across changing real-world series. Weir is separate from the static TIME comparison mentioned in the announcement, and these displayed results were not independently rerun. SN91 Cascade’s own Bittensor-trained model is still described as coming soon, not already included.

Why 4 stars: SN91 Cascade supplies a fresh ensemble release with a visible, scoped benchmark lead and a clear distinction between current inference and its future subnet-trained model.

#06 · SN107 · Minosdeveloping
★★★★★

SN107 Minos details its second mechanism for genomic AI research

Following its September 29 conference preview, SN107 Minos detailed Incentive Mechanism 2 in an article published at 22:33 Eastern on October 5. Its existing synthetic genomic data engine supplies examples with known answers; the new mechanism is designed to have miner-run AI agents find research questions in the scientific literature and turn them into verifiable evaluation briefs. The team describes a native Mac app, an iPhone companion and inference through SN28 SayGM, SN53 engy or SN64 Chutes, with evidence stored on SN75 Hippius. The angle is broader participation and demand between subnets: agentic research can use an AI subscription or API instead of rented GPUs. The article describes internal testing and the intended workflow, but this review did not verify an open public app download, mechanism-wide activation or rewards to outside participants.

Why 4 stars: SN107 Minos details a substantial second incentive design linking research questions, synthetic data and other subnet services. Public availability and paid participation remain developing.

#07 · SN108 · ChipForgeverified
★★★★★

SN108 ChipForge’s NPU challenge is open, with real submissions under evaluation

SN108 ChipForge has crossed the launch line. Its public leaderboard at 14:34 UTC showed an active challenge to build an NPU and optimized kernels for four AI models, six submissions from five miners, and no winner yet. Designs run MLPerf Tiny workloads for voice, vision and sensors; outputs must match reference answers, with chip area and performance evaluated separately. The challenge ends October 20. This advances yesterday’s no-active-challenge observation, rather than repeating a promised start date. All three validators still showed their stake burning emissions until a qualifying design wins, so an open contest is not a completed payout. At 14:28 UTC, alpha/TAO was up 293.01% over 24 hours; that is market attention, not a dollar return or evidence of chip sales.

Why 4 stars: SN108 ChipForge now has a directly observed active hardware-design competition and submitted work. Its rating reflects activation and evaluation, not the price spike.

#08 · SN8 · Vantaverified
★★★★★

SN8 Vanta adds limit orders outside regular equity hours

SN8 Vanta’s latest code supports equity limit orders during pre-market, 04:00–09:30 Eastern, and after-hours, 16:00–20:00 Eastern. Regular equity trading remains 09:30–16:00; the wider windows are not unrestricted overnight market-order trading. The update adds trade and quote handling for those sessions, and separate code permits corrections to an entity’s account size without resetting its history. These are substantive trading-infrastructure changes, not a performance or revenue claim. The merged implementation and published market-hour rules were checked; full production adoption was not independently demonstrated.

Why 3 stars: SN8 Vanta extends its documented equity trading sessions with bounded order rules and improved account handling.

#09 · SN10 · Paretonverified
★★★★★

SN10 Pareton adds evaluation under simultaneous demand

SN10 Pareton’s new benchmark code evaluates completion time across input tiers under simultaneous requests, with failed requests reducing eligible scores. The published breakdown includes tier weights, absolute times, failures and deductions so miners can reconstruct the arithmetic. This tests how a tuned inference system handles competing work rather than judging only isolated requests. It is a verified implementation change, not a newly demonstrated customer speedup. Separately, the Opentensor conversation with SN10 Pareton is scheduled for Thursday, October 8; it has not happened yet.

Why 3 stars: SN10 Pareton broadens evaluation toward realistic concurrency and auditable failure penalties, with customer outcomes and the upcoming talk distinguished.

#10 · SN17 · 404—GENverified
★★★★★

SN17 404 records its Round 51 winner and opens Round 52

SN17 404’s public competition records now identify computer-vision-ai-lab/jade-harrier-6 as the Round 51 winner and mark Round 52 open. The new schedule closes reveals at block 9229786, sets the generation deadline at block 9230986 and gives an October 7, 08:00 UTC next-stage estimate. The winner’s entry is scheduled to become effective at block 9229786; that future block should not be confused with a payment already made. This resolves the earlier pending Round 51 result at the repository level and opens the next cycle. Separately, its game-jam community prize remains a different competition, with voting through October 12.

Why 3 stars: SN17 404 has newly published competition results and a next-round state, with future effective blocks and the separate game jam distinguished.

#11 · SN22 · Desearchdeveloping
★★★★★

SN22 Desearch changes task timing as the team reports a lower burn

SN22 Desearch’s new task API code starts a miner’s clock when tasks are actually handed over and judges completion when the upload reaches the API, rather than penalizing the miner for later server processing. Repeated completion requests return the original answer, and verified page updates are published in numbered files for downstream indexing. Today’s team-attributed brief also reports faster queues and a burn reduction to 70%, with validators updating automatically. The timing and publishing changes are verified implementation; the new burn and production rollout remain a secondary team report. Reported queue backlogs were not independently shown to have cleared, so the repair is not presented as an all-clear.

Why 3 stars: SN22 Desearch addresses a concrete fairness and throughput problem, while the reported emission change and complete backlog recovery remain developing.

#12 · SN23 · Trishoolverified
★★★★★

SN23 Trishool reports its output guard climbing to 81.87% F1

SN23 Trishool’s October 5 update reports output-guard F1 improving from 73.9% in its initial version to 78.53%, then 81.87%. The team says successful miner attacks become training examples for the next version, making the subnet’s adversarial work feed directly into the guard’s development. It describes the latest score as less than one point from the leading result in its comparison. That is a measured progress report, not proof that the system blocks every attack or leads every security benchmark. The result and comparison were not independently reproduced. The post landed at 15:14 UTC, four minutes after yesterday’s cutoff, so it belongs in today’s window.

Why 3 stars: SN23 Trishool reports a concrete progression tied to miner-generated attacks, with evaluation scope and independent-reproduction limits retained.

#13 · SN33 · ReadyAIverified
★★★★★

SN33 ReadyAI verifies a 19.24 TAO buy-and-burn and reports $95,000 ARR pace

SN33 ReadyAI reports that its jobs API’s latest weekly pace annualizes to about $95,000 in recurring revenue, with a six-figure target for October. That is an annualized pace, not $95,000 received last week or audited booked revenue. The team also says September’s buyback was 45% larger than August’s. Its linked explorer record confirms a successful add_stake_burn into SN33 for 19.24 TAO at block 9221415, timestamped 04:05:36 UTC on October 6, with AlphaBurned and AddStakeBurn events. The transaction is inspectable evidence of the burn; it does not independently verify the revenue figure, its funding source or the month-to-month percentage.

Why 3 stars: SN33 ReadyAI links a business progress report to a directly checked burn transaction, separating on-chain facts from reported revenue and comparisons.

#14 · SN38 · ChronoLLMverified
★★★★★

SN38 ChronoLLM merges Round 14’s model caching and batched evaluation

SN38 ChronoLLM’s Round 14 pull request, still open in yesterday’s report, merged at 16:55 UTC on October 5. The change keeps downloaded model weights in a persistent cache and batches model-versus-model generation according to available memory. Qualified models are prefetched, with availability checked before evaluation, reducing repeated downloads and avoidable stalls. The validator container pin also changes. This is a concrete step toward more efficient and repeatable evaluation, but a merge does not confirm every validator has upgraded or establish a measured production speedup. Today’s channel discussion still mentions logs being lost on redeployment and a plan to preserve them; that separate observability issue is not declared resolved.

Why 3 stars: SN38 ChronoLLM advances from a proposal to merged evaluation code, with rollout, measured performance and log persistence kept separate.

#15 · SN44 · Scoredeveloping
★★★★★

SN44 Score reports September break-even and demonstrates general object detection

SN44 Score shared an October 5 interview reporting that September was its first break-even month and that buybacks had begun from its owner address. Those are reported business milestones; this scan did not verify financial accounts or match the buyback transactions. Its own new demo shows the General Object Detector counting overlapping apples inside Score Studio without custom training for that example. Separately, the founder describes SN44 Score models being used by Manako’s Rig for client vision workflows. The product demonstrations add concrete context to the commercial claim, but are not proof of an unnamed packhouse deployment. New world-model training remains a next step, and the petrol-station track issue is not independently closed.

Why 3 stars: SN44 Score combines a fresh reported break-even milestone with concrete product demonstrations, while financial verification, customer scope and ongoing incidents remain clear.

#16 · SN51 · lium.ioverified
★★★★★

SN51 lium.io removes collateral scoring while preserving existing reclaim paths

SN51 lium.io’s new code removes the collateral requirement from validator scoring and the miner deposit commands. Existing locked collateral can still be reclaimed through a local contract client, with checks intended to avoid losing track of transactions whose outcome is uncertain. Another change starts host probes at SSH connection and runs GPU power restoration alongside volume creation, reducing sequential setup work. This changes provider onboarding and maintenance rather than proving a faster completed rental. The implementation is verified; current wallet reclaims and chain-wide validator adoption were not independently reconstructed. A member-reported rented node outage remains a separate, unresolved report.

Why 3 stars: SN51 lium.io makes a significant provider requirement change and preserves recovery for previously locked funds, without assuming automatic refunds or measured rental gains.

#17 · SN74 · Gittensorverified
★★★★★

SN74 Gittensor assigns 30% of its miner pool to compute

SN74 Gittensor’s new code allocates 70% of miner emissions to open-source work and 30% to compute, replacing the previous 100% open-source allocation. Compute weights come from the controller’s signed scoring record; an invalid or stale record recycles that share rather than paying unsupported work. Related changes add GPU rates and restore multi-GPU handling. This gives supplied compute an explicit place beside software contributions in the reward model. The split is verified in the merged constants and validator path, but this review did not reconstruct the first applied on-chain distribution or miner receipts. Published rate targets are not guaranteed dollar earnings.

Why 3 stars: SN74 Gittensor makes a material incentive-allocation change with clear accounting rules, while actual distributions and returns are not inferred from code.

#18 · SN74 · Gittensorverified
★★★★★

SN74 Gittensor’s SparkInfer v0.6.32 improves Muse Glimmer serving

SN74 Gittensor released SparkInfer v0.6.32 with a targeted memory change for Muse Glimmer 30B. On an RTX 5090 with sixteen simultaneous 8,000-token prompts, its published test reports 351 output tokens per second and a 2.5-second first token, versus 281 and 9.7 seconds before the change. The same-GGUF llama.cpp comparison reports 76 tokens per second and 7.9 seconds. The gain comes from reserving less spare GPU memory and making more available for active request context; other models keep their existing headroom. These are workload-specific release measurements, not a universal model or hardware ranking, and the tests were not independently repeated.

Why 3 stars: SN74 Gittensor publishes a fresh serving release with explicit hardware, prompt, concurrency and competitor conditions.

#19 · SN78 · Umiverified
★★★★★

SN78 UMI merges C5 delivery repairs; rewards remain inactive

SN78 UMI has merged a substantial C5 repair covering request delivery, retained-work recovery and bounded retries through runtime changes. The aim is to preserve acknowledged work and distinguish missing evidence from a miner’s missed opportunity. The code still requires qualification of the actual evaluator service environment before broader release. Its checked public API at 14:29 UTC continued to show open admission and 203 accepted submissions, but rewards_active and chain_submission_authorized were both false. That prevents the repair from being mistaken for settled rewards. An October sign-language app beta remains a reported target, not a confirmed public launch.

Why 3 stars: SN78 UMI ships meaningful recovery code while a directly checked status endpoint keeps intake, reward activation and the future app launch separate.

#20 · SN81 · Reliquaryverified
★★★★★

SN81 Reliquary adds faster reward-backlog recovery and fixed task contracts

SN81 Reliquary’s new accounting code allows up to four archived periods of rewards to enter together, rather than making a settled backlog wait one period at a time behind ongoing work. Reward totals stay unchanged, and replacement records prevent the same archive being counted twice. Operators must update weight setters before moving the backlog, or older software can clamp the catch-up and burn it. A separate merge fixes task identities and result delivery to their signed contracts, while sandbox infrastructure failures are kept distinct from an agent failing its task. These changes target delayed settlement and reliable training data; merged repairs are not independent proof that affected miners have received their outstanding rewards.

Why 3 stars: SN81 Reliquary fixes a specific persistent reward delay and strengthens task consistency, with upgrade order and payment verification limits visible.

#21 · SN87 · Provenonceverified
★★★★★

SN87 Provenonce opens its code and testnet attestation history

SN87 Provenonce now publishes MIT-licensed code and a checker for its repeated weight-setting on Bittensor testnet subnet 582. The public page lists 21 attested runs beginning October 4, with the first block at 8152574; this builds on the September 28 first graded cycle already covered. The proposal evaluates whether autonomous work followed its declared requirements, rather than merely finishing. Its own limits are explicit: miners are run by the team, tasks are synthetic fixtures, outside miners are not enrolled, and public readers cannot reproduce scoring because the reference executor is private. The verifier’s overall result therefore stays UNVERIFIED even when chain checks pass. This is new public evidence and access, not a mainnet commercial launch.

Why 3 stars: SN87 Provenonce makes its implementation and repeatable testnet evidence inspectable, including what outsiders still cannot verify.

#22 · SN97 · Albedoverified
★★★★★

SN97 Albedo moves evaluation toward SN53 engy and quicker fallback

SN97 Albedo’s new code routes GLM-5.3-Flash judging and question generation through SN53 engy, with an OpenRouter fallback using GLM-5.2. It also uses Jev for question and milestone deduplication, and changes generation so timeouts can fall back promptly rather than holding up the whole queue. The practical aim is faster, cheaper evaluation using another Bittensor service, while retaining a route when the preferred provider fails. The implementation is verified, but the stated activation after pending evaluations finish is only a channel report. This scan did not confirm all validators had changed providers or measure production savings.

Why 3 stars: SN97 Albedo has concrete evaluation and cross-subnet inference changes, with fallback model differences and rollout limits stated.

#23 · SN116 · Carbonverified
★★★★★

SN116 Carbon’s new validator code retains payout activation gates

SN116 Carbon’s latest validator change permits its service key to sign a registered winner-weight intent while retaining integrity checks and refusing other weight shapes. The commit also says broader mainnet authorization and switching the testnet path on remain held. This is progress in the reward infrastructure for its industrial physics AI work, not proof of completed rewarded mining or customer delivery. At 14:28 UTC the market snapshot showed +110.94% over 24 hours in alpha/TAO; its +2,552.02% seven-day figure spans the slot’s pre-registration history and is not a Carbon investment-performance record. Yesterday’s eight proposed challenges are not eight completed customers, and a newly claimed Discord channel is not evidence of a subnet ownership transfer.

Why 3 stars: SN116 Carbon’s market outlier warrants a fresh primary-source check; its actual authorization change is covered with retained gates and slot-history limits.

#24 · SN120 · Affineverified
★★★★★

SN120 Affine records a completed optimizer step and remaining training limits

SN120 Affine’s operator log now records E15 finishing with durable optimizer step six, then E16 continuing under a bounded training selection after a 256-document cap caused a retry loop. It reports 309 eligible contributions, with 256 selected for that training job and 53 unselected; all remain eligible for continuous audit and reward estimation. The distinction is progress in the training pipeline, not demonstrated learning improvement. Its separate 128-task comparison scored 83 before and 82 after, which the log explicitly says is not evidence of convergence. Step seven and a faster completed epoch remain unclaimed. These are public operator records, not independent validation of every run or affected miners’ wallet receipts.

Why 3 stars: SN120 Affine has a concrete completed training checkpoint and documented recovery, with negative evaluation evidence and unfinished steps preserved.

#25 · SN124 · Swarmdeveloping
★★★★★

SN124 Swarm reportedly re-evaluates champions after five environment fixes

Today’s team-attributed brief says SN124 Swarm is rolling out V5.1.6.5 to correct five miner-reported environment problems: landing-score penalties, disappearing village pads, rescue victims placed below slopes, coupled forest difficulty and search area, and terrain loading order. Champions in affected modes are being re-evaluated; Office Interceptor is unchanged. These repairs matter because an environment defect can distort which drone controller earns rewards. The original release and full validator rollout were not independently confirmed, so this remains a reported fix rather than proof that every affected ranking has settled. Its October 7–8 World Summit AI appearance is still upcoming.

Why 3 stars: SN124 Swarm reports a substantive scoring-environment repair and targeted re-evaluation, with source and rollout limits visible.

#26 · Ecosystemverified
★★★★★

Today on Shizzy: validator choice at 11 AM Eastern

Today’s scheduled public stream is “Your Stake. Your Decision. Inside Bittensor’s First Democratised Validator,” with guests from Subnet Summer and Medulla Labs. YouTube lists the start as October 6 at 11 AM Eastern / 8 AM Pacific. The discussion is about validator choice and stake participation; the title’s “first” wording is the episode’s framing, not an independently established global-first claim. The site also now lists yesterday’s public “Bittensor TAO at $300: Is This the Launchpad for Liftoff?” video, 22:09. The October 4 members video remains correctly gated, and the SN49 Nepher Robotics replay stays in the library.

Why 2 stars: A verified public schedule and refreshed video library give readers a concrete way to follow today’s Bittensor discussion.

#27 · SN25 · URdeveloping
★★★★★

SN25 UR’s feed records a large lock changing to perpetual

SubnetRadar’s October 5 feed records an existing 545.1-thousand-alpha SN25 UR lock switching from decaying to perpetual at 19:49:35 UTC. It attributes the change to hotkey 5CyQFy…1wxG using set_perpetual_lock. This is a change in lock commitment, not 545,100 alpha newly purchased or added. The linked event page failed to load its details in both the public fetch and browser check, so the exact block and full event parameters remain unverified. The feed report is included as developing because of its scale, with no locker motive or ownership-transfer claim.

Why 2 stars: SN25 UR has a potentially material commitment change, but unavailable event details require a developing label and no purchase inference.

#28 · SN26 · Perturbdeveloping
★★★★★

SN26 Perturb reportedly targets a November product launch

Today’s team-attributed brief says SN26 Perturb is moving into a product phase after five months of subnet development, with launch targeted for next month. The team reportedly plans to continue buybacks before revenue begins and use a substantial share of future revenue for alpha buybacks. This is a stated roadmap and proposed funding model, not an already launched product, a disclosed customer contract or existing product revenue. The original announcement and buyback transactions were not independently matched during this scan.

Why 2 stars: SN26 Perturb supplies a new product timetable and reported business plan, with future launch and revenue distinguished from completed outcomes.

#29 · SN30 · Endure Networkdeveloping
★★★★★

SN30 Endure targets today’s mainnet launch; activation is not confirmed

SN30 Endure’s October 5 announcement targets October 6 for its mainnet launch, describing competitive, outcome-scored risk intelligence. A signed-in latest-post check still found that announcement, rather than a completed launch notice. Today’s team-attributed channel brief says validators are not currently setting weights and that the miner burn is being reduced later this week. The launch remains developing at this edition’s cutoff. A scheduled date and an operating subnet slot do not establish active scoring or reward distribution.

Why 2 stars: SN30 Endure has a material launch target, but the separate weight-setting and burn status prevents premature launch confirmation.

#30 · SN39 · deprecateddeveloping
★★★★★

SN39 is marked deprecated despite a large reported inflow

SN39’s current identity in our chain-derived market feed is “deprecated,” while some directories still call it Cathedral or Basilica. SubnetRadar records a 1,315.7 TAO inflow from wallet 5GuRL…iuaC at block 9219245, timestamped 20:51:41 UTC on October 5. At 14:28 UTC today, alpha/TAO was up 16.98% over 24 hours. Those observations warrant attention, but neither establishes a relaunch, new owner, customer milestone or the wallet’s motive. The associated public repository has no new commit in this window. Use the current slot identity and the specific recorded movement rather than treating price or stale branding as proof that a new project is live.

Why 2 stars: SN39’s outlier move and large recorded inflow make its conflicting identity material, without inventing a catalyst or ownership event.

#31 · SN49 · Nepher Roboticsdeveloping
★★★★★

SN49 Nepher Robotics reportedly requires simulator upgrades

Today’s team-attributed brief instructs SN49 Nepher Robotics miners to upgrade to Isaac Sim 6.1 and Isaac Lab 3.0.0. Keeping simulation environments aligned matters when robot policies are compared under common conditions. The original upgrade notice and deployed validator requirements were not independently matched, so this is an operational instruction reported by the channel brief, not a newly opened competition or a new physical-robot deployment. Yesterday’s conviction lock remains a prior event.

Why 2 stars: SN49 Nepher Robotics has a miner-relevant compatibility instruction, with the source and deployment gaps clearly marked.

#32 · SN53 · engydeveloping
★★★★★

SN53 engy is reported to process 4–5 billion Kimi K3 tokens daily

An October 6 post by Algod reports SN53 engy revenue growing 100% month over month and processing 4–5 billion Kimi K3 tokens daily through direct distribution. If sustained, direct usage would matter for an inference subnet’s business beyond its emissions. The post does not provide an independently audited revenue amount or public usage ledger, and those figures were not reproduced in this scan. Separately, SN107 Minos names SN53 engy as an intended provider for its second mechanism, while SN97 Albedo has merged code that uses it for evaluation. Those integrations are evidence of a broader role, but do not verify Algod’s numerical claims or mean every announced workload is already live.

Why 2 stars: SN53 engy has a material public usage and growth claim plus specific subnet integration context, with unverifiable business figures labelled as reported.

#33 · SN105 · Beamdeveloping
★★★★★

SN105 Beam announces a separate professional-services partnership

SN105 Beam says Beam Professional Services has partnered with a consulting firm to support current client engagements and integrate Beam into existing workflows. The announcement explicitly describes that organization as a separate services entity supporting the ecosystem. Its scope includes data movement, streaming, Rooms and programmable actions, but the consulting firm is unnamed and no contract value or independently confirmed customer deployment is supplied. This is a reported integration effort, not proof of subnet revenue. The separate QoS-whitelist issue remains under repair; the October 1 chunk-size fix is not a new fix today.

Why 2 stars: SN105 Beam has a fresh business-development announcement, with the separate entity, unnamed counterparty and unverified commercial outcomes retained.

04

Audit trail

Coverage notes

Searched

  • All 128 current identities and 98 October 5–6 dated channel briefs screened. Current roster, source attribution and earlier editions checked before selection.
  • Signed-in @ShizzyUnchained X discovery covered Bittensor/TAO, launches, SN91 Cascade and focused official-account launch follow-ups. 195 associated public-account candidates yielded 183 usable samples and 183 current unique post records; these include commentators and quoted accounts, not just subnet teams.
  • 181 repository paths scanned; 23 selected commit records inspected. SN38 PR29 merge, SN74 release, SN78 status API, SN65 live competition configuration, SN55 current implementation, SN108 active challenge and SN91 Weir benchmark checked separately.
  • Signed-in AlphaGap feed and leaderboard, SubnetRadar news and dated Moments, TAO Daily, TAO Media, partner accounts and both sides of the Talisman integration checked. The Grayscale custody claim was verified in the original SEC filing through the browser.
  • September 29–October 5 editions reviewed for duplicates, late findings, unresolved incidents and scheduled events. Market outliers and the top 12 emission recipients compared separately with selected stories.
  • Signed-in YouTube Videos and Live tabs checked. EY-s2-882uA public video verified at 22:09, mTJBFowN4Yo scheduled October 6 15:00 UTC, M2nWtKAkw6I latest members video retained, and NAbCyYwZ_5w public SN49 replay retained.
  • An overlapping pass of 30 priority public profiles ended at 2026-10-06T14:37:41.230Z; no newly exposed post after the initial scan cutoff was returned. Subsequent primary and signed-in checks extend this edition’s research cutoff to 2026-10-06T14:44:22.533Z.

Public-data gaps

  • Research cutoff 2026-10-06T14:44:22.533Z. Associated public-account samples and selected signed-in searches are not an exhaustive search of every SN-number/name. No Grok scan or complete private-community coverage is claimed.
  • 13 repository paths returned errors and 12 public-account candidates yielded no usable sample. Directory metadata can be stale. SN55’s newly linked subnet-niome-v4 repository and SN65’s actual taofu-labs repository were checked separately; the guessed TPN-Labs path returned 404. The sundae_bar overlap alias returned 404, not a successful official-account check.
  • Generated briefs and AlphaGap summaries are discovery. Team-attributed burn, upgrade and environment changes remain developing without independent rollout confirmation; member allegations were not promoted as verified facts.
  • SN107 Minos IM2 public app availability, outside paid participation and mechanism activation were not independently verified. SN55 NIOME current code has a five-gene scope, narrower than the announcement; rewards, clinical validation and patient use were not demonstrated.
  • SN108 ChipForge is active with submissions but no winner; all three validators were still burning their stake at observation. SN65 TPN-005 configuration is live, but its later winner distribution was not reconstructed.
  • SN91 Cascade, SN23 Trishool and SN74 SparkInfer measurements were not independently rerun. Cascade’s future subnet-trained model is not part of the current ensemble. SN53 engy numerical usage and growth claims, SN44 Score break-even and buybacks, and SN33 ReadyAI annualized pace and 45% comparison are not audited financial statements.
  • SN78 UMI rewards remain inactive and chain submission unauthorized. SN120 Affine’s operator records and SN81 Reliquary recovery code do not independently establish wallet receipts. SN118 Ditto, SN11 TrajectoryRL, SN54 Yanez UAV and SN44 Score incidents are not independently closed. SN15 ORO’s no-false-positive statement is not an external audit; its separate Race 11 issue remains unclosed.
  • SN30 Endure launch remains prospective at cutoff. SN121 sundae_bar SBC30, SN114 SOMA review completion, SN61 RedTeam replacement, SN111 Claims burn proposal, SN94 permissionless access, SN104 launch, SN122 dashboard and SN25 production qualification were not confirmed activated. SN124 World Summit AI and SN10 October 8 discussion remain upcoming.
  • SN39 chain-derived identity says deprecated while directories use Cathedral/Basilica; its recorded inflow is not a verified relaunch or ownership transfer. SN116 Carbon’s seven-day return crosses the slot’s pre-registration history, its payout generalization retains gates, and a Discord channel claim does not establish new ownership.
  • SN25 UR’s 545.1k-alpha perpetual-lock change is visible in the feed, but its event detail failed to load and the block was not matched. SN106 Nodexo detail amounts differ from one feed headline; exact detail records were retained without asserting a completed sale.
  • Talisman’s Medium article returned a public-fetch 403; both primary X announcements and ForeverMoney’s full article were available. No bridge transfer, independent reserve audit or clinical experiment was performed. Members-only YouTube access was not bypassed.