Bittensor Toolkit →Find the right tool for your question.

BITTENSOR · THE NEWS ARCHIVE

Find the story.

Search 86 dated editions without scrolling through them one by one.

Reset filters

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.

2,335 matching stories

2026-10-21 edition →SN76 · Ormasverified3 / 5 stars

SN76 Ormas improves public-work recovery while its SayGM case study details team costs

SN76 Ormas’ repository retains the work packet needed when recovering a public job and prepares release 0.0.3. Separately, SN28 SayGM’s dated case study describes SN76 Ormas as a beta service that charges clients only for work passing their agreed tests; its $19,553 usage figure concerns the team’s engineering agents. The article distinguishes standard plaintext work from a Protected tier still broadening access. Recovery behavior and model-cost reporting help assess the operating workflow, without turning the team’s own model spend into client revenue.

A specific documented code/reliability change with a clear use for participants; impact and independent adoption are not yet established.

2026-10-21 edition →SN78 · Umideveloping2 / 5 stars

SN78 UMI clarifies when C5 endpoints can be retired

SN78 UMI’s October 21 channel digest says C5 endpoints can go offline only after every issued request has a retirement receipt, while signed requests, responses, grants and receipts must be retained. C6 and later endpoints still need to remain available. Current repository work also handles authenticated winning-baseline consumption. This is new operational guidance around reward verification, not another announcement of the already-covered C5 rewards.

Relevant operational or planned change, but primary execution or full incident details remain unverified.

2026-10-21 edition →SN85 · Vidaioverified3 / 5 stars

SN85 Vidaio names Tobruk as a sales partner

SN85 Vidaio announced Tobruk Protective Security Solutions as a new sales partner on October 20, describing it as the first of four prospects in its current pipeline. That pipeline is not four completed agreements, and no contract value or resulting revenue was disclosed. A sales partner can provide access to markets the video-processing team would find harder to reach directly. This remains Vidaio’s announcement; independent confirmation from Tobruk was not obtained.

A specific documented product or operating update with a clear use for participants; impact and independent adoption are not yet established.

2026-10-21 edition →SN91 · cascadeverified3 / 5 stars

SN91 Cascade fixes numerical missing-data sentinels in its pool filter

SN91 Cascade merged a change counting numeric no-data sentinel values as missing. This addresses a channel report that codes such as -999999 could pass a missingness filter for time-series datasets. The public patch establishes the filtering change; it does not independently quantify earlier evaluation contamination or prove every deployed evaluator is updated. Cleaner input handling matters because time-series training and benchmark conclusions depend on distinguishing observations from placeholder values.

A specific documented code/reliability change with a clear use for participants; impact and independent adoption are not yet established.

2026-10-21 edition →SN92 · REAXverified3 / 5 stars

SN92 REAX opens its generalist decision-model competition

SN92 REAX announced REAX 1, based on Perplexity Decider v1.2, and its competition page says the generalist track opened October 21 at 13:00 UTC, replacing the demand-forecasting and risk-assessment use-case tracks. Their final leaderboards remain available. The team reports a 2.4-point improvement over the base model across six test draws and ten areas; this is its own measurement, not an independently rerun benchmark. Published release code also addresses engine champion payouts. The important change is that miners can now compete on a broader decision model, alongside engine optimization, rather than only the two earlier specialist tasks.

A new competition track and team-reported model scores; competition launches and routine benchmark updates are capped at three stars.

2026-10-21 edition →SN102 · ConnitoAIdeveloping2 / 5 stars

SN102 ConnitoAI outlines dataless expert-finetuning plans

SN102 ConnitoAI’s October 21 channel digest describes a planned competitive loop in which model and prompt miners are scored by a judge, allowing customers to begin with a task description instead of a supplied dataset. The digest’s role count and exact launch state require primary clarification, so no completed launch or performance claim is made here. The proposed change targets the data-preparation barrier for specialized models; it remains a design update to watch.

Relevant operational or planned change, but primary execution or full incident details remain unverified.

2026-10-21 edition →SN105 · Beamdeveloping3 / 5 stars

SN105 Beam reports a fix separating publisher and viewer room access

SN105 Beam’s October 21 channel digest says a shared room-media token vulnerability was fixed October 20 and asks miners to update. The reported problem allowed viewer access to interfere with a publisher’s stream; the fix is described as separate access privileges. A secondary technical account independently describes the same issue, but complete primary release and deployment evidence was not obtained, so the remediation remains attributed. The team also outlines geographic worker-distribution metrics for next week, which are future work rather than a current decentralization result.

Relevant operational or planned change, but primary execution or full incident details remain unverified.

2026-10-21 edition →SN107 · Minosverified3 / 5 stars

SN107 Minos publishes ASHG poster-session times for October 22–23

SN107 Minos has now supplied the details missing from earlier coverage. In an October 20 evening Eastern post, the team names ASHG in Montreal, Exhibition Hall Room 220: synthetic whole-genome cohorts on October 22, 4:15–6:15 p.m. ET, and continuous variant-calling benchmarking on October 23, 2:30–4:30 p.m. ET. These are scheduled presentations, not completed talks or announced customer contracts. The attached material shows branded scientific outreach merchandise; the event planner could not be independently accessed, so times and room remain explicitly team-reported. This gives researchers a concrete opportunity to inspect the work behind the subnet.

Useful scheduling information for researchers; the sessions are still upcoming and the team-reported details were not independently confirmed in the event planner.

2026-10-21 edition →SN114 · SOMAdeveloping2 / 5 stars

SN114 SOMA reports miner-rule enforcement and plans clearer evaluation logs

SN114 SOMA’s October 20–21 channel digests report disallowed prompt-injection and loop-string techniques in competition submissions, followed by a promise of more detailed evaluation logs. The report that eight miners were flagged remains attributed to the digest; original review records and appeals were not independently audited. This is a competition-integrity follow-up, not proof of wrongdoing beyond the specific team findings or a newly verified model release. Better logs would help miners understand rejection decisions and distinguish invalid tactics from ordinary failed submissions.

A relevant competition or development update, with plans and channel-only details distinguished from verified execution.

2026-10-21 edition →SN116 · Carbondeveloping2 / 5 stars

SN116 Carbon highlights ScoreLab and separates simulations from physical evidence

SN116 Carbon’s October 21 ScoreLab post describes work on testing which scoring methods reward useful physics models across accuracy, speed and behavior near design limits. It points back to the October 19 development update; this is continuing development, not a new live customer product. A separate team article explains using solver-generated practice data, rebuilding submissions under fixed limits and evaluating unseen cases. It explicitly notes that matching a simulation can inherit that simulation’s errors, making physical validation a separate requirement.

A relevant competition or development update, with plans and channel-only details distinguished from verified execution.

2026-10-21 edition →SN117 · everyframe.studioverified3 / 5 stars

SN117 everyframe publishes miner 0.6.0 and validator reward-scheduling work

SN117 everyframe’s public repositories release miner 0.6.0 with routing and worker-reliability work, while validator 0.4.0 addresses miner reward scheduling. The release notes describe multi-platform validation; this report did not independently rerun those checks. The operating change matters for miners receiving and completing work and for predictable reward processing. It does not establish customer uptake or revenue by itself.

A specific documented code/reliability change with a clear use for participants; impact and independent adoption are not yet established.

2026-10-21 edition →SN118 · Dittoverified4 / 5 stars

SN118 Ditto demonstrates WhatsApp context alongside Slack and Notion

SN118 Ditto’s October 21 product demonstration connects WhatsApp chats and photos to persistent memory alongside Slack and Notion. The sampled screen answers a bathroom-job status question using information from those sources, and the team says connected Claude can use that context too. This is a demonstrated workflow for reducing manual copying between business apps, not independently tested reliability or new customer revenue. The team’s agent-source releases and sandbox-memory adjustments are separate operating work, not a reason to claim every integration is production-proven.

A visible multi-app business workflow extends the product’s usable context; adoption and reliability remain unproven.

2026-10-21 edition →SN120 · Affineverified2 / 5 stars

SN120 Affine launch draws a server-capacity warning from Const

SN120 Affine’s video launch was covered yesterday. In a follow-up just after that report’s main cutoff, Const said the servers were immediately overwhelmed and thanked users for the demand. This is operator commentary about launch capacity, not a verified attack, measured usage total or proof of paid adoption. Community claims about emissions being burned were not promoted into an eTAO event: current chain allocation vectors and validator reward-routing behavior are different things.

A specific documented product or operating update with a clear use for participants; impact and independent adoption are not yet established.

2026-10-21 edition →SN125 · Refinerydeveloping2 / 5 stars

SN125 Refinery describes a three-week incentive narrowing plan

SN125 Refinery’s October 20 channel digest says emissions will be reduced to its first challenge over the next three weeks if improvements do not continue. The precise execution schedule and on-chain allocation were not independently established. This is a planned change to challenge incentives, not a newly verified five-slot eTAO transaction. It matters to miners deciding which work remains rewarded.

Relevant operational or planned change, but primary execution or full incident details remain unverified.

2026-10-20 edition →SN1 · Apexdeveloping3 / 5 stars

SN1 Apex moves to a tougher competition iteration

The October 20 channel digest reports v0.1.5 activation at round 4 and a one-day reveal period for new competitions. A public account reports the NIST-Lite board nearly maxed out at 639/640, giving context to harder evaluation discussions. These are attributed operational reports rather than independently replayed results. Expectations for v0.1.6 are not a completed release.

A concrete operating or product change with useful implications for participants.

2026-10-20 edition →SN7 · Allwaysdeveloping3 / 5 stars

SN7 Allways reports reopening after its halt

The October 20 team-channel digest says SN7 Allways resumed with 3.7.0, reopened swaps, reservations and deposits, and planned a return to zero burn. The repository contains new payout-delivery and gas-floor safeguards. Full recovery and the burn transition were not independently verified on-chain in this pass; miners and validators should follow version-specific team instructions.

A concrete operating or product change with useful implications for participants.

2026-10-20 edition →SN8 · Vantaverified4 / 5 stars

SN8 Vanta removes its owner allocation and reports trader payouts

At October 20 00:14 UTC, a successful transaction changed SN8 Vanta from approximately 18/41/41 to 0/50/50 for owner/validators/miners. Its founder describes removing owner emissions as a maturation step, not a prohibition on team participation in incentives. Separately, SN8 Vanta reports $930,128 across 339 rewards to 122 traders, and over 5,000 registered traders since February. Those totals were not independently reconciled against every ledger entry; the split change itself is verified on-chain.

Executed removal of the owner allocation changes reward economics; operating totals remain attributed.

2026-10-20 edition →SN9 · iotaverified3 / 5 stars

SN9 IOTA reports faster decentralized-training merges; Const endorses it

SN9 IOTA’s October 19 team post, quoted by Const, says a tree-based merge graph makes merges about five times faster and training almost 20% cheaper, reducing swarm waiting time. These are reported measurements, not independently reproduced benchmarks. Const’s description of the team as the grand masters of decentralized training is commentary, not separate technical verification.

A concrete operating or product change with useful implications for participants.

2026-10-20 edition →SN16 · Zero Hourverified4 / 5 stars

SN16 Zero Hour raises miner allocation to 61.5% through eTAO

SN16 Zero Hour executed an eTAO allocation change on October 20 at 16:37:12 UTC, in finalized transaction 9325968-13. The owner allocation remains approximately 18%; validators fall from approximately 41% to 20.5%, while miners rise from approximately 41% to 61.5%. Successful execution and the exact five-slot storage were checked immediately before and after the transaction; burn and recycle remain zero. This redirects a larger share of alpha rewards toward miners. Root receives its live baseline first, capped by the validator bucket, and alpha validators share the remainder. Historical yield can still include the previous split, so this change does not establish a specific new APR or APY.

A finalized allocation change materially redistributes miner and validator rewards; transaction and before/after storage are verified.

2026-10-20 edition →SN22 · Desearchverified3 / 5 stars

SN22 Desearch publishes an MCP agent example and updates embed checks

SN22 Desearch’s October 20 post demonstrates an agent using hosted MCP to discover tools, read pages and produce sourced answers with a cost log; the team says the default scripted loop needs no LLM. Code publishes 0.0.238 and longer reference-vector waits during server failover. A channel statement forecasting embed mining in one hour is a schedule claim rather than independently confirmed activation.

A concrete operating or product change with useful implications for participants.

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.