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.
SN15 ORO updates its runtime and reportedly begins duplicate-agent enforcement
SN15 ORO validator v2.2.0 adopts oro-env-runtime 3.3.0 and runtime contract 2. The release aligns stock tasks with the current contract and rejects incompatible older practice packs before loading them. Separately, today’s team-attributed brief says enforcement is rolling out against the same or trivially varied agent submitted across multiple hotkeys. Miners who think a flag is wrong can submit their hotkey for review, and additional checks may remove entries before the current race ends. The runtime change is verified in code; the enforcement rollout remains a secondary team report. Yesterday’s Race 2 recovery does not independently close the separately reported Race 11 pause.
SN15 ORO has a substantive runtime release and reported participation-rule enforcement, with code, rollout and separate incidents distinguished.
SN21 AdTAO reports its second weekly conviction lock
SN21 AdTAO says its second weekly conviction lock is complete and reiterates a plan to commit roughly 25% of its owner emissions to Conviction. The announcement links a public lock portfolio. This is a reported recurring owner-emission commitment, not new advertising revenue, a guaranteed return or proof of an additional market purchase. The exact new lock amount and transaction were not independently matched during this review.
SN21 AdTAO’s reported second weekly commitment is relevant incentive information, with amount and chain-verification limits preserved.
SN26 Perturb reportedly shifts scoring toward adversarial robustness
Today’s team-attributed brief says SN26 Perturb now weights evaluation 70% adversarial accuracy and 30% clean accuracy, replacing the previous 50/50 mix. That would reward models more heavily for handling deliberately difficult inputs, rather than only normal examples. The brief also reports consensus-rank changes for scanning emissions and asks validators to update and restart together. The original announcement and full validator rollout were not independently located, and current repository attribution remains uncertain. Treat this as a reported scoring change rather than a verified chain-wide activation.
SN26 Perturb’s reported scoring split changes what miners optimize for, but the source and deployment gaps require a developing label.
SN28 SayGM demonstrates its combined AI dashboard
SN28 SayGM has published a two-minute walkthrough of its shipped dashboard: chat across models, image generation, guardrails on API keys, custom model fusions and cascades, and spending tracked to the cent. The useful angle is control over how AI services are combined and paid for, rather than another standalone chatbot. This is a new product demonstration of existing shipped features, not evidence that every feature launched today or that an external revenue target has been reached. The authenticated product’s full workflow was not independently exercised.
A direct SN28 SayGM walkthrough helps readers understand the product, while its recap nature keeps the rating modest.
SN38 ChronoLLM proposes faster Round 14 evaluation and persistent model caching
SN38 ChronoLLM’s open Round 14 pull request, created on October 4 and updated today, proposes batching duel generation and retaining downloaded models through evaluation. That would avoid downloading weights twice and prevent a model going private after qualification from blocking its next evaluation stage. The author reports roughly 20-fold faster batched generation, but this review did not reproduce that measurement. The pull request was still open at the check: these are proposed evaluation improvements, not a merged release, a confirmed new round or a verified live speedup.
SN38 ChronoLLM has a specific fresh proposal worth tracking, but an open pull request and author-reported speedup do not justify a launch-level rating.
SN41 Almanac reports better forecasting accuracy and more repeatable evidence
SN41 Almanac’s weekly development report puts its Jev-integrated forecasting harness at a 0.165 Brier score versus 0.169 for standalone Claude Sonnet; lower is better. It also reports source-URL agreement between repeated runs improving from roughly 80% to 93%, with probability outputs stable to the third decimal place. Those are useful measures of forecasting quality and reproducibility, rather than a vague claim that a model is smarter. Alma has entered a September 28–January 6 tournament with a $30 daily budget and approximately $1 median forecast cost. The team’s results have not been independently reproduced, and execution still takes about 40 minutes. Faster inference and a self-improving harness remain work in progress.
SN41 Almanac supplies scoped accuracy, repeatability and cost measurements, while latency and unfinished development remain visible.
SN44 Score reportedly removes a challenge with incorrect ground truth
Today’s team-attributed brief says SN44 Score removed petrol-station challenge block 9209400 after an incorrect ground-truth annotation was reported. It separately says rewards for the top Detect Worksite miner are functioning and that tiebreak rules apply. This is a targeted evaluation correction, not confirmation that every PPE annotation concern or yesterday’s warmup-related zero scores has been resolved. Vision Lab remains marked coming soon.
A specific SN44 Score challenge correction is useful incident follow-up without closing unrelated scoring complaints.
SN49 Nepher Robotics records a 46,437-alpha conviction lock
SubnetRadar records a 46,436.627-alpha lock on SN49 Nepher Robotics at block 9215815, timestamped 09:33 UTC on October 5. It targets the subnet owner’s hotkey. This is a lock and commitment signal; it does not prove a same-sized new purchase, revenue or any particular locker’s motive. Separately, today’s “Nepher Verified” certification post looks back to last month and is not a new regulatory approval or evidence of equivalence to CE, UL or ISO certification.
The sourced SN49 Nepher Robotics lock is a fresh chain event, with commitment separated from spending and product certification.
SN50 Synth tightens forecasting backtests and avoids blocking on every asset
SN50 Synth’s synthlib code now requires an offline market-data bundle for backtesting and moves the evaluation cutoff before the forecast horizon, reducing the risk of accidentally using future information. It also reads the published champion tree rather than relying on a stale local model. Asset warmup runs in the background: an asset can be served once ready instead of waiting for every asset to finish loading. These are useful reliability and evaluation changes for synthetic forecasting. They do not establish a new predictive-accuracy record, commercial revenue or an independently measured faster production service.
SN50 Synth improves the credibility of offline evaluation and readiness of its serving path, with performance and business claims kept separate.
SN61 RedTeam plans an ADA-3 replacement as scoring issues continue
SN61 RedTeam’s team-attributed brief acknowledges anti-detect-browser and device-timeout issues affecting ADA-3 scoring. Failed sessions cannot simply be excluded under the current process. A replacement challenge is being prepared, but the brief says it will be introduced after miners solve the current BEX challenge. Separately, today’s public v4.10.9 code raises the number of unique commits allowed for ADA detection. That is a specific submission change, not proof that the grading problem has been fixed or a replacement is already live.
SN61 RedTeam moves from member complaints to a reported team response and a concrete code change, while the replacement remains gated.
SN71 Leadpoet adds bounded recovery after provider-credit failures
SN71 Leadpoet’s Arena code allows an owner-signed second attempt after a provider-credit failure only when the gateway proves the original call settled with zero charge. The miner must first restore credit on the same provider account; the scoring stage and frozen deadline must still be open. Uncertain charges, closed rounds and old failures without the new proof are excluded, and the original spend limit and two-attempt cap remain. This prevents a narrowly recoverable billing failure from automatically ending a submission. Separately, the team-attributed channel brief still reports duplicate-agent slot pressure and a planned capacity increase; the retry feature does not settle that access problem.
SN71 Leadpoet supplies a concrete, limited recovery path that preserves spending and deadline rules, without claiming the separate spam incident is resolved.
SN74 Gittensor’s SparkInfer v0.6.28 closes a scoped serving gap
SN74 Gittensor has published SparkInfer v0.6.28. Its RTX 5090 test on Qwen3.6-35B-A3B reports 2,366 output tokens per second at 32 simultaneous chat requests, matching vLLM in that test and improving about 5% over v0.6.27. Median first-token latency is 318 ms versus vLLM’s 580 ms; vLLM still has lower inter-token latency. Packing incoming prompts together is the main improvement. The tests use 1,024-token prompts, 256 output tokens and two runs per cell on the same machine. The systems use different quantization formats, so this is a defined serving comparison, not a universal performance lead. Qwen3.8 is unchanged.
SN74 Gittensor publishes a concrete release with workload-specific throughput and latency gains, including remaining tradeoffs.
SN78 UMI’s intake is open again; rewards are still inactive
SN78 UMI’s public competition status at 15:04 UTC on October 5 showed admission open, capacity available and 203 accepted submissions. Yesterday’s observation showed admission unverified and not accepting new entries, so this is a meaningful status change. Assignment delivery, model intake and evaluation were marked ready, but rewards_active and chain_submission_authorized both remained false: accepting work is not the same as paying for it. New code also adjusts cohort processing budgets and carries chain state forward through runtime changes. Those repairs do not by themselves prove C5 has settled or miners have received rewards.
SN78 UMI has a directly checked change in participation availability, with the separate reward and chain-authorization gates made explicit.
SN80 OpenRoboto’s published rules allocate 35% to egocentric data
SN80 OpenRoboto has updated its published allocation to 15% simulation, 25% real-robot π0.5, 25% real-robot LingBot-VLA 2.0 and 35% egocentric data collection. That makes accepted first-person data a substantial part of the incentive model alongside training robots. The data score combines accepted minutes, task rate, quality and novelty; weekly weights use the previous week’s accepted contributions. Invalid data earns nothing. The same documentation specifies a 0.2 TAO simulation submission fee, checked against the selected season before payment. These are current published rules, not a notice opening a new physical-robot competition; this review did not independently reconstruct the chain’s applied allocation. The Open Axis partnership post is a September recap, not another new launch.
SN80 OpenRoboto’s explicit 35% data allocation materially changes how participation is rewarded, with settlement rules, fee scope and activation limits kept clear.
SN81 Reliquary improves usable dataset exports and terminal-task reliability
SN81 Reliquary’s new code exports bounded instruction datasets alongside its existing corpus deliveries, helping turn generated work into prompt-and-response training data. This applies to supported single-turn jobs; episode or unsupported prompt formats retain their original delivery rather than being forced into the wrong schema. A separate terminal-environment merge adds a default 180-second command timeout, per-test grading detail and cleanup of containers left by interrupted runs. Grading fixes also avoid drawing impossible cross-provider rechecks when only one provider is available. These are inspected implementation changes; the reported new software-engineering mining job and production deployment were not independently confirmed.
SN81 Reliquary improves both the usability of its training output and the reliability of agent-task execution without treating merged code as confirmed mining activation.
SN106 Nodexo team reportedly focuses on SN96 Verathos and explores a sale
Today’s team-attributed brief says the SN106 Nodexo team is now focused on SN96 Verathos, with hardware verification for a mesh of grouped compute resources and plans to operate its own inference service. It also says SN106 is in sale discussions with several candidate teams. The distinction matters: a discussion is not a completed sale, a new owner or an announced purchase price. This review did not locate a matched completed chain transfer or an independently tested SN96 service launch.
A reported team and product focus shift is material for both SN106 Nodexo and SN96 Verathos; sale completion and service activation remain unconfirmed.
SN108 ChipForge ships clearer evaluation visibility; its challenge is not open yet
SN108 ChipForge’s October 4 update describes a redesigned live leaderboard with per-submission scores, quality gates, validator progress, downloadable logs and a view of which design the chain rewards. The team also says NPU tests now use trained benchmark models with hidden expected answers checked against Google’s reference software. At 15:05 UTC on October 5, the public leaderboard showed no active challenge, no submissions and all three validators’ stake burning emissions. Its API reported healthy. That is useful infrastructure progress ahead of mining, not confirmation that today’s planned competition has opened. The accompanying TatsuOS update reports end-to-end testing completed, with infrastructure deployment and BLE/OTA work still ahead of a preview.
SN108 ChipForge improves the transparency of hardware-design evaluation, and the actual leaderboard prevents a scheduled launch from being mistaken for an active challenge.
SN114 SOMA reportedly restarts 330 sandbox-affected miner runs
Today’s team-attributed brief says SN114 SOMA restarted 330 miner runs affected by sandbox errors, with a competition review planned for October 6. Restarting the affected work is a recovery step, not confirmation that every run has finished, rewards have settled or the broader competition is clear. Member allegations about cheating were not confirmed by the team and are not treated as established misconduct.
SN114 SOMA provides a specific reported recovery action and review date, with completion still unconfirmed.
SN120 Affine adds recovery for missed hourly reward records
SN120 Affine’s latest code reconciles missed hourly records using the learner’s original completion time, rather than counting old work as if it finished in the current hour. Previously published records are checked against their saved journal and retained unchanged. The practical purpose is to recover gaps without rewriting reward history or double-counting work. This is an implementation update, not independent confirmation that affected miners have been paid. Today’s operator status still describes a recovery job in progress and additional H200 nodes awaiting qualification and enrollment; preparation and tests are not a completed rollout.
SN120 Affine addresses a concrete reward-accounting failure while preserving immutable history and separating implementation from actual receipts.
Stillcore publishes its TAO 2030 investment thesis
Stillcore Capital published its TAO 2030 paper on October 4 after yesterday’s cutoff, explaining its scenario for a trillion-dollar-plus Bittensor ecosystem by 2030. Its argument centers on intelligence becoming cheaper, outside customers paying for subnet services, and value flowing through the network’s currency and markets. This is an investor’s valuation thesis with assumptions and milestones to track, not an achieved valuation or a guaranteed price target. Its revenue estimates are not added to yesterday’s already-covered revenue index as a second, independent pool of sales.
A newly published primary research paper is useful ecosystem context, with its forecasts distinguished from verified commercial results.
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.
