Subnet News — September 20, 2026

SN76 Ormas jumps 73.6% in the rolling 24-hour snapshot

At 11:26 AM ET, SN76 Ormas alpha is up 73.6% against TAO over 24 hours. Its current metadata describes an outcomes API for coding work that is still in development, with miners paid for independently accepted delivery. The pool holds about 609 TAO in reserves, so the move should be read in the context of a small pool. No new official announcement was established as the cause. This is a timestamped market move, not proof of a product launch or a price forecast.

Why 3 stars: A large move deserves visible market coverage, while limited liquidity and no verified catalyst keep it below a five-star product story.

+73.6% α/TAO 24H price action as of Sep 20, 2026, 11:26 AM ET

StonkFun reports $1.25M revenue, $750K buybacks and $60M cumulative holder rewards

StonkFun’s September 19 operating report lists $1,247,924 in revenue, $749,636 in buybacks and 2.93 million STONK burned. A separate post reports cumulative holder rewards reaching $60 million. These are fresh, project-reported platform totals. They are not independently audited accounts, TAO-only revenue or TAO token burns, and today’s report is not a new announcement of the previously covered TAO pairing.

Why 3 stars: Fresh operating figures update the ongoing StonkFun watch without conflating platform-wide activity with TAO-specific economics.

Emission watch: tiny allocations return to SN71 Leadpoet and SN76 Ormas

At 11:26 AM ET, SN71 Leadpoet has 0.000239% observed network allocation and SN76 Ormas has 0.000001%, both above zero after zero in yesterday’s saved snapshot. SN92 and SN58 remain at zero. These are small snapshot changes, not confirmation of meaningful miner payouts. Network allocation, voluntary burns and actual distributions are different measurements; the data does not establish that Const, Arbos or another named person manually switched these subnets on.

Why 3 stars: The new zero/nonzero changes continue the emissions watch, with scale and unknown causes made explicit.

SN118 Ditto adds a reproducible V13 enterprise benchmark candidate

SN118 Ditto’s repository adds deterministic V13 enterprise datasets and checks that scorers support the intended benchmark version. Seeded generation makes evaluation inputs reproducible, and the release separates that path from deferred private dataset production. The code comments explicitly say V13 has not activated publicly. This is a benchmark implementation and readiness update, not proof of a completed public scoring migration or a new independently confirmed leading agent.

Why 3 stars: Reproducible evaluation and verified scorer compatibility improve the ability to inspect competition results.

SN15 ORO prepares new qualifying and race suites

SN15 ORO’s team is preparing new qualifying and race problems to reduce overlap between suites and the need for subjective review. The channel brief also describes consideration of a single task family, with current races continuing under sanity checks. The new suite and single-family design should not both be treated as already active.

Why 3 stars: Evaluation design changes can alter what miners build and how fairly submissions are compared.

SN21 AdTAO makes gate verdicts and model transitions easier to inspect

SN21 AdTAO adds public gate verdicts with per-horizon measurements and exposes the transition from a hotkey’s previous model to its new model, including remaining allocation and ramp factor. These changes help participants see why a model passes or fails and how its rewards transition. They are verified transparency changes, not evidence of a new advertising-performance record.

Why 3 stars: Visible eligibility and allocation transitions make reward decisions more understandable to miners.

SN23 Trishool acknowledges a mismatch between jailbreak detection and scoring

The SN23 Trishool channel brief records a case in which content was flagged as jailbroken but received a zero score. A team member acknowledges the mismatch and says the judge model will be tightened. This is an acknowledged scoring issue and a planned improvement, not a verified completed repair.

Why 3 stars: A mismatch between detection and scoring affects trust in the security evaluation.

SN34 BitMind reports a benchmark reset and fixes reward-result truncation

Today’s SN34 BitMind channel brief reports gasbench 0.9.8 with new holdouts, removal of the rendering category and a full benchmark reset. It describes a temporary upload closure during holdout preparation and a six-hour window for selecting new leaders; the exact reset schedule remains flexible. Separately, the public validator 5.0.8 change removes a 1,000-result cap and fetches the full two-hour reward lookback, preventing eligible older results from being displaced simply by newer activity. The reward fix is verified in code; reset timing is attributed to the channel brief.

Why 3 stars: Both the evaluation reset and result-window fix affect how miners qualify and receive rewards.

SN55 NIOME reports another scoring interruption after a validator crash

SN55 NIOME’s latest brief says a validator crash left only five miners scored on one task while others received zero. The team reports restarting the validator and investigating continuing anomalies. This is a new interruption after yesterday’s task-generator repair, so the earlier fix should not be read as resolution of every scoring issue.

Why 3 stars: Repeated scoring disruption is material to participants whose work may not be evaluated.

SN74 Gittensor separates access and health checks across leased compute

SN74 Gittensor merges one SSH port per machine with workload access over private addresses, alongside revised lease accounting. Related changes distinguish unexecuted checks from benchmark failures and allow a clean operating period to reduce accumulated strikes. These changes target access reliability and misleading penalties in its compute pool. They establish code changes, not measured fleet-wide uptime gains.

Why 3 stars: Access reliability and failure classification directly affect compute suppliers and customers.

SN78 UMI targets its first evaluation batch while bridge weights remain

SN78 UMI’s channel brief targets closing its first evaluation batch and starting scoring today, subject to code cleanup. It says temporary bridge weights remain until evaluated results replace them and submissions will stay open for later batches. Exact cutoff instructions are still to be published. This is a planned transition, not confirmation that the first results have already set on-chain rewards.

Why 3 stars: The handoff from temporary weights to evaluated results is material to miners awaiting scoring.

SN81 Reliquary avoids duplicate checkpoint staging for remote proofs

SN81 Reliquary’s new remote-proof path avoids staging model checkpoint weights unnecessarily when proof work is handled remotely. Companion environment changes add a per-turn token budget and make telecom task state serializable. The main operational benefit is avoiding redundant model-weight handling; a realized speed or cost reduction was not independently measured.

Why 3 stars: Reducing repeated checkpoint handling is a substantive training and proof-infrastructure improvement.

SN90 KubeTEE reports two image-generation backends live behind its gateway

SN90 KubeTEE’s deployment documentation now reports end-to-end checks for two Michigan image backends: FLUX.2 Klein 4B and Cosmos 3 Super. It documents protected infrastructure and mutual TLS between services. Klein is exposed through an OpenAI-style image-generation route, while Cosmos uses its native inference schema through a separate passthrough. This follows yesterday’s attestation news with specific model-serving infrastructure. The live tests are maintainer-reported; this scan did not submit image requests or independently audit the security design.

Why 3 stars: Named model backends and documented gateway paths are a concrete product step beyond a general infrastructure roadmap.

SN91 Cascade tightens GPU comparability for challenger evaluations

SN91 Cascade now keeps a manifest’s evaluations on the same GPU type and requeues challengers when that condition cannot be met. Related changes let available lanes continue work past a deadline without unnecessarily holding the incumbent. These are evaluation-scheduling changes intended to keep comparisons consistent while avoiding blocked capacity, not a new model-quality result.

Why 3 stars: Comparable hardware and clearer scheduling matter when competition results determine the winning model.

SN100 Cortex merges a new Bounty reward profile; activation is still a separate step

SN100 Cortex’s new algorithm assigns up to 30% of emissions to Bounty and 70% to Proof. Each valid Bounty report earns one point, authors share proportionally and ten valid reports unlock the full Bounty share; unused allocation burns. The code explicitly requires an owner-signed profile and coordinated activation before these rules apply. At this scan, the public network page still says automatic payouts are not wired and weights are not sealed, and its older scoring description differs from the new repository rules. Report intake and a merged reward design therefore should not be confused with confirmed live 30% payouts.

Why 3 stars: The reward design is material, and the activation requirements prevent a premature claim that miners are already receiving the new split.

SN105 Beam tightens transfer-integrity enforcement and warns of stale dashboard data

SN105 Beam’s channel brief attributes permanent UID and worker bans for false transfer chunks to the team. It also says dashboard worker-linkage data may be stale and advises operators to consult local data. This report does not identify or accuse individual miners; the operational news is the enforcement policy and the dashboard limitation.

Why 3 stars: Transfer integrity and unreliable operator visibility are practical issues for a file-routing network.