Dates and verification labels belong to the original edition. A past verified announcement can now be outdated. Historical project names are retained; an SN filter searches the slot across registrations. All keywords must match the story text or subnet label. Ratings describe editorial priority, not investment quality.
SN105 Beam briefs report security fixes and a fresh task-volume concern
Late-found SN105 Beam coverage distinguishes two dates. The October 11 digest attributes to the team caller-ownership checks on orchestrator routes, hidden miner identities during integrity checks, corrected sale counting and lower telemetry prices. An October 12 digest then reports community concerns about a NATS protocol change, falling verified task volume and persistent debt calculations. Those later messages are not automatically team statements, and the private originals and underlying measurements were not independently inspected. These remain developing reports: earlier fixes do not establish that the later operational concerns are resolved. Operators should confirm current SDK and migration instructions with the team.
Reported security and accounting fixes plus fresh operational concerns warrant a carefully attributed incident follow-up.
SN107 Minos bounds genomic scoring to stop late jobs holding up rounds
Late-found code update: SN107 Minos merged its scoring-deadline fix on October 9 at 03:53 UTC. New secondary work stops seven minutes before the scoring deadline by default; once results can no longer be stored, the validator stops waiting and removes remaining scoring containers. That frees CPU for the next round instead of letting a slow genomic job delay finalization. The merge and implementation are verified; adoption by every validator and a measured production speed gain are not. This is a scoring-reliability change, separate from the planned second incentive mechanism.
A concrete merged reliability fix prevents one slow scoring job from delaying an entire round.
SN108 ChipForge brief reports revalidation, reopened submissions and 13 bans
SN108 ChipForge’s October 12 digest attributes to the team a completed re-evaluation of 85 quest_001_npu entries using hardened validation, a new winner, reopened submissions and a return to a 10% minimum-improvement requirement. It also reports 13 coldkeys banned for exploiting evaluation. The private original messages and per-account evidence were not independently read, so these remain attributed reports rather than independently proven misconduct. This updates the unresolved validation story; it does not certify every payment or submission issue as resolved.
A material reported validation recovery and eligibility change updates an ongoing incident.
SN112 THOR replaces its owner key and updates its public identity
A direct Finney archive-node check confirms SN112’s owner coldkey changed at 13:19 UTC on October 12, block 9,267,377. The decoded ColdkeySwapped event is attached to extrinsic 4, and owner storage differs immediately before and after that block. The registration height remained unchanged between the daily snapshots. This establishes an executed owner-key replacement, not a new registration or proof of a negotiated sale. By the 15:54 UTC market snapshot, the slot’s identity had changed from for sale to THOR, with the description Home of Open Source Robotics and a thormachines.ai website. SubnetRadar separately reports the rename. The new identity and key swap do not establish a buyer, purchase price, completed negotiated sale or launched robotics product.
An independently traced ownership-key execution is useful slot-watch information, with sale and registration claims kept separate.
SN118 Ditto ends its memory track and announces an interim emission allocation
SN118 Ditto’s October 12 post says its memory track is finished and a router competition is next. A reranker, learned retrieval weights and a small language model under seven billion parameters are also planned. Until the new incentive mechanism is live, the team says miner emissions go to its UID 21 to fund development. That allocation is a team statement here, not a separately reconstructed chain-payment total. This is a consequential change for miners: the replacement competition is not yet live, and the team’s claim that memory is solved should not be read as a universal scientific result.
A directly announced mining transition and interim reward destination materially affect participants.
SN120 Affine separates fresh training diagnostics from held-out claims
SN120 Affine’s October 12 code and documentation add a separate dashboard series for fresh generations on a fixed 128-task training cohort. Results require authenticated aggregates and complete provenance; missing or invalid observations stay unavailable rather than becoming zero accuracy. The docs distinguish the original 7B comparison reference from the actual training-run starting checkpoint, and explicitly say this is not independent held-out confirmation. Publishing the display does not establish that the producer is deployed or that the first new numerical measurement is available.
Clearer evaluation provenance helps readers interpret learning results without mistaking training diagnostics for independent validation.
taostats API migration: October 8 launch, November 9 retirement deadline
Late-found infrastructure update: taostats’ primary launch article is dated October 8 and says the new API is live, with the old /api/ endpoints switching off on November 9. An October 12 X reminder says 30 days, but the published migration timeline gives the precise date. Existing keys, host and Authorization header stay the same; paths move to /v1/, with revised endpoint names and sorting parameters. Developers should follow the guide and test field mappings. The provider’s speed and accuracy claims were not independently benchmarked here.
A live API migration and retirement deadline can affect many Bittensor dashboards and integrations.
Const comments “Gamma” in an inference-for-equity discussion
On October 11 at 19:35 UTC, Const replied “Gamma” to Algod’s public question about giving startups inference instead of only cash investment. This is relevant ecosystem commentary and is included with the original thread context. The one-word reply does not announce a new protocol feature, launch date, funding program or finalized Gamma economics. Other commenters’ descriptions are not substituted for an official specification.
The owner-requested Const review found a fresh relevant reply; its limited wording supports commentary, not a launch claim.
Yoko opens selection for its first subnet bouts; ForeverMoney points to TAO bridging
Yoko’s October 12 post asks users to select three subnets for its first prediction-market bouts and says the podium locks Sunday at 20:00 UTC. ForeverMoney quote-posts that invitation, explicitly saying the market has not yet gone live and pointing to existing TAO bridging to Robinhood Chain through its site or Talisman. This connects a planned Bittensor-focused application to available cross-chain infrastructure. The invitation is verified; completed trading launch, final selected subnets and volumes are not. This is reported as product planning, without a recommendation to trade or bridge funds.
A direct Bittensor product-selection announcement and partner context are material, while trading activation remains unconfirmed.
SN4 Targon brief outlines requirements for eight-B300 onboarding
SN4 Targon’s October 11 digest attributes to its team an onboarding path for eight-B300 systems using AMD or Intel hosts. It describes bare-metal operation, host confidential-computing support through TDX or SEV-SNP, and NVIDIA confidential computing enabled. These are reported provider requirements, not an announcement that every such machine is accepted or that a new customer contract is complete. Operators should confirm the current requirements with the team before provisioning hardware.
Specific provider requirements are useful operational news, though the original private-channel guidance was not independently read.
SN15 ORO adds fallbacks for its configured Reader’s Gemini calls
SN15 ORO’s October 11 proxy change adds fallback models for validator-originated calls from the configured Reader when the requested Gemini model cannot be reached through a miner’s OpenRouter account. The configured chain can fall back to another Gemini model and then GPT-6 Sol, and logs the model that actually served the call. Agents’ own Gemini calls are unchanged. This is a narrowly scoped reliability fix rather than a new general model launch or evidence that all previous evaluation concerns are resolved.
A specific dependency failure can affect miner evaluation; the fix has a clearly defined scope.
SN22 Desearch restores rendered rechecks and protects miners from provider refusal
SN22 Desearch’s October 11 validator code restores a 5% sampling rate and rechecks doubtful pages with JavaScript rendering. Rendering can clear a questionable sample rather than introduce an additional failure. A related change stops checks or weight updates when the scraping provider refuses the validator key or has no credits, and avoids assigning a verdict to a refused task. This addresses false penalties caused by the validator’s data provider; the repository changes do not prove every validator has upgraded.
Specific validation safeguards improve fairness and reliability without claiming universal deployment.
SN44 Score brief reports continuing challenge-pipeline disruption
SN44 Score’s October 11 digest reports an unavailable beverage-element evaluation and a separate PPE evaluation delay described as resolved. It also reports an annotation-rule fix. This is a follow-up to yesterday’s pipeline outage, not a blanket recovery announcement: the individual task states differ, and the private original messages were not independently read. Today’s public sub-subnet flywheel comment is a future ambition, not a new confirmed commercial deployment.
Task-specific incident follow-up matters to miners; partial recovery is kept separate from a network-wide all-clear.
SN50 Synth brief reports a public-API sunset and next-week Ultra onboarding
SN50 Synth’s October 11 digest attributes to the team a sunset of the public API and planned Ultra UID onboarding the following week. It also reiterates one hotkey per operator. This could change how users access forecasts and how miners join the next phase, but the private original discussion was not independently read and a replacement service was not verified live. The onboarding date is a plan, not a completed launch.
A reported service-access change and miner transition warrant attention, with primary access and timing limitations explicit.
SN66 Conjectures brief reports withdrawal of a completeness bounty
SN66 Conjectures’ October 11 digest reports that its Idoneal-numbers completeness bounty was removed after the team identified prior literature and an existing solution. This is a reported change to the available research work, not a new proof announced by the subnet. The underlying mathematical claim and private original messages were not independently verified in this check.
A removed bounty affects contributors, but secondary evidence does not justify promoting a mathematical result.
SN71 Leadpoet exposes miner-credit diagnostics and partial evaluation scores
SN71 Leadpoet’s October 11 changes expose proved miner credit and scoring-window diagnostics. Its dashboard can show already-published per-ICP scores even when the overall evaluation is incomplete, while another fix bounds synchronous billing reads for completed OpenRouter errors. These changes make partial results and payment evidence easier to inspect; they do not constitute a new revenue announcement or prove every delayed evaluation is resolved.
More visible payment evidence and partial results address concrete operator uncertainty.
SN81 Reliquary caps corpus pay by verified tokens and improves exported answers
SN81 Reliquary’s October 11 code changes let a corpus period pay the lower of its budget cap or its price ceiling multiplied by verified tokens. Payments are divided by tokens; unused budget is not automatically paid out. A new read-only /corpus/pay endpoint exposes job projections, saturation and settlement lag for miners choosing work. Separately, exports now reject unfinished completions and grade the final answer after the reasoning block; optional deduplication removes repeated completions within or across jobs. These are published payout and data-quality changes, not evidence of a new benchmark-winning model or guaranteed miner income.
Material reward accounting and delivered-data quality changes affect both miners and training-data customers.
SN89 InfiniteQuant checks collateral throughout open bets
SN89 InfiniteQuant’s October 11 code adds collateral checks every 15 minutes while bets remain open. If an entity’s stake minus debt falls below its open-bet amount at any checkpoint, the cycle’s payable amount becomes zero. Previously collateral was checked when a bet was taken, allowing later unstaking to leave the bet valid. The change names the cycle beginning October 11 at 13:00 UTC; actual adoption by every live validator is not independently confirmed.
Closes a concrete reward-accounting gap for an active prediction/trading mechanism.
SN92 slot watch: October 9 re-registration replaced the previous owner
Late-found chain-event coverage: SubnetRadar records the former SN92 Available slot being re-registered on October 9 at 20:07:18 UTC, block 9,247,819, for 884.377 TAO. Its event lists a different previous and new owner. This is a slot re-registration after the previous registration was displaced, rather than evidence of a negotiated subnet sale. The new project’s current identity and operating launch were not independently established. Historical returns attached to SN92 may cross occupants and should not be read as seven-day performance of a newly launched project.
A dated registration replacement helps users track slot turnover while keeping identity, launch and sale claims separate.
SN108 ChipForge validation overhaul remains unresolved
SN108 ChipForge’s October 11 digest describes a revised validator, revalidation of submissions and a proposed 12–24-hour update window. It distinguishes exact final-output matching from permitted intermediate fusion. This follows yesterday’s verified winner-reset and payment fixes; those fixes do not establish an all-clear. The latest timetable is secondary reporting, not a confirmed restoration. At the 18:17 UTC alpha/TAO snapshot, SN108 ChipForge was up 35.41% over 24 hours and 188.15% over seven days; price does not demonstrate incident recovery.
An unresolved rewards and validation issue remains material despite large market moves.
Searches published headlines and summaries, not private bookmarks, unpublished leads or source-page contents. Duplicate headlines within an edition appear once; separate editions remain separate so follow-ups are preserved. Share the page URL to retain your filters.
