Bittensor Daily News

Latest edition
#01 · Ecosystemverified
★★★★★

Grayscale files amended TAO ETF application; NYSE Arca trading remains conditional

Grayscale Bittensor Trust filed Amendment No. 2 to its S-1 on October 23, reviewed here as a late-found filing. The preliminary prospectus describes an intended NYSE Arca listing under GTAO and a planned rename to Grayscale Bittensor ETF. It explicitly says trading cannot begin until applicable listing requirements are met, and the registration statement must become effective. The trust’s existing OTCQX quotation is different from that proposed exchange listing. This is progress in the application process, not confirmation of ETF approval, a launch date or new inflows.

Why 4 stars: A primary regulatory filing materially advances the documented route to exchange-traded TAO exposure, with approval and trading conditions still outstanding.

#02 · Ecosystemverified
★★★★★

Crucible announces desktop-feature parity on mobile and wider iOS access

In an October 23 announcement found during the overlap review, Crucible says its iOS and Android apps now include Smart Account, Rewards Allocator, Token Discovery, Token Details and Address Book, matching its Chrome feature set. It also names Argentina, Japan and Brazil in the iOS expansion. These are the developer’s release claims; we did not independently install each regional build or audit wallet permissions.

Why 3 stars: The announced mobile capabilities and regional availability are useful changes for TAO wallet users, while security and installation claims are not independently tested.

#03 · Ecosystemverified
★★★★★

Latest Shizzy members update is available; next interviews remain scheduled

The 14:54 members-only October 24 news and TAO price-action video is now the site’s latest members entry. The public default remains a completed episode. YouTube still lists SN54 Yanez for October 27 at 12:30 PM ET, SN71 Leadpoet for October 28 at 11:00 AM ET, and TAO Templar for October 29 at 1:00 PM ET. They remain upcoming livestreams, not completed videos.

Why 3 stars: Current access labels and verified stream times help viewers find the right episode without implying an upcoming show has already aired.

#04 · SN8 · Vantaverified
★★★★★

SN8 Vanta: 343.333333333 alpha burn verified on chain

A successful finalized AlphaBurned event on October 25 removed 343.333333333 alpha on SN8 Vanta. The exact amount, historical subnet identity and execution are preserved in the evidence. This is a transaction burn from its recorded wallet, separate from miner-emission withholding, fees and recycling; it does not establish that the current owner wallet was the actor.

Why 3 stars: An executed native-token burn is independently verifiable; the actor and economic meaning are not inferred beyond the evidence.

#05 · SN14 · Cacheonverified
★★★★★

SN14 Cacheon: 1,448.4478 alpha burn verified on chain

A successful finalized AlphaBurned event on October 25 removed 1,448.4478 alpha on SN14 Cacheon. The exact amount, historical subnet identity and execution are preserved in the evidence. This is a transaction burn from its recorded wallet, separate from miner-emission withholding, fees and recycling; it does not establish that the current owner wallet was the actor.

Why 3 stars: An executed native-token burn is independently verifiable; the actor and economic meaning are not inferred beyond the evidence.

#06 · SN15 · OROdeveloping
★★★★★

SN15 ORO reports evaluation-key abuse; affected race is rescored

The October 25 Discord digest attributes an audit result to the team: 51 agent versions across 32 hotkeys were removed after evaluation-key spending limits were increased beyond the allowed budget, and Race 2 was rescored. We have not independently audited those accounts or payouts. Separately, public code now records upstream inference costs for bring-your-own-key calls and corrects their classification. Fair comparison depends on measuring the real compute budget; those code changes alone do not prove the reported bans.

Why 3 stars: A consequential evaluation-integrity dispute affects miner eligibility and confidence in comparisons; enforcement counts remain attributed.

#07 · SN25 · URverified
★★★★★

SN25 UR moves its settlement-v2 target to epoch 4; activation remains pending

The project’s October 25 timeline says production configuration and maintenance are complete, but validator history recovery and finalized pool registration are still outstanding. Epoch 3 was missed. The revised target is epoch 4 at block 9,398,428, estimated around October 30 at 18:25 UTC, conditional on registration before that boundary. First claims are estimated no earlier than November 8 after root commitment, challenge expiry and finalization. These are the project’s block-based estimates, not confirmed activation or a promised payment date.

Why 3 stars: The revised primary timeline changes what providers can expect from settlement; deployment of services is distinct from contract activation.

#08 · SN46 · Instantdeveloping
★★★★★

SN46 Instant reports higher emission withholding ahead of engine work

The October 25 team-attributed digest says the subnet moved to a 50% emission burn setting ahead of planned upgrades, with a new engine and RTX Pro 6000 mining next. It gives a target of returning to zero withholding in the coming weeks, rather than a fixed activation date. This is emission handling, not a qualifying transaction burn in our Burns archive. At the recorded 14:31 UTC alpha/TAO snapshot, the token was down about 15.65% over 24 hours; the price move does not prove a cause or an owner sale.

Why 3 stars: The reported operating change matters to miners; plans, market context and explicit transaction burns are kept distinct.

#09 · SN51 · lium.ioverified
★★★★★

SN51 lium.io enables GPU profiling for kernel developers

In an October 24 post found during the overlap review, the team says NVIDIA ncu profiling is enabled on its rental nodes, linking a profiling-enabled GPU listing for developers entering the Open Kernel Challenge. Another post shows a claimed 12-second setup of an eight-H100 rental. Profiling access is a concrete developer feature; the setup time is a provider demonstration, not a benchmark we reproduced. Separate referral payouts are conditional offers, not guaranteed GPU income.

Why 3 stars: Profiling helps developers inspect real GPU workloads; rental speed and referral examples retain their stated limits.

#10 · SN53 · engyverified
★★★★★

SN53 engy: 4,633.974128881 alpha burn verified on chain

A successful finalized transaction on October 25 burned 4,633.974128881 alpha on SN53 engy. Its matched buyback marker records 146.69 TAO spent to acquire the alpha; that TAO was not itself burned. The burn is counted once, not once per event marker. This is all-wallet subnet activity, not proof that the current owner coldkey performed it or that the funding came from business revenue.

Why 3 stars: An executed native-token burn is independently verifiable; the actor and economic meaning are not inferred beyond the evidence.

#11 · SN81 · Reliquaryverified
★★★★★

SN81 Reliquary removes its default minimum incentive-share cutoff

A new primary commit removes the default rule that reduced a hotkey’s task share below 2% to zero. The protocol default is now zero, allowing smaller verified contributions to receive a share; an individual task can still declare its own floor. Related code fixes optimizer setup so sharded training parameters, rather than transient unsharded buffers, receive updates. These are verified repository changes; we have not independently confirmed rollout on every running worker or validator.

Why 3 stars: The default payout rule directly affects smaller GPU contributors, and the training fix addresses whether model weights are actually updated.

#12 · SN91 · cascadedeveloping
★★★★★

SN91 Cascade user describes research integration and one live deployment

On October 25, @Tensor_Flow_ said its engineering stack uses Cascade’s synthetic time-series generator alongside the Alphacast forecasting feed, describing research-stage work and one live deployment. This is a direct user statement about use, rather than another model-size announcement. The user did not disclose a customer, revenue or independently measured production performance, so none is inferred. Bitstarter separately highlighted the statement.

Why 3 stars: A named public user describes actual integration, while commercial scale and effectiveness remain unverified.

Smaller developments and early plans. Verification labels distinguish confirmed information from developing claims.

#13 · SN1 · Apexdeveloping
★★★★★

SN1 Apex submission timeouts are reported by a miner

A community member’s October 25 digest report says Competition 10 round 93 submissions time out while read endpoints remain available, raising a question about unused paid fees. The digest contains no team response. We could not independently reproduce the authenticated submission path, so this remains an unresolved incident lead rather than a confirmed network-wide outage or promised refund.

Why 2 stars: A specific submission failure can affect participation and paid access; its reach and resolution remain unconfirmed.

#14 · SN34 · BitMinddeveloping
★★★★★

SN34 BitMind reports submission reopening after database work

Following the evaluation problems covered yesterday, the October 25 team-attributed digest says the database migration finished and submissions reopened at 18:00 UTC. It also describes Yugos as one track balancing output quality, cost and latency. This is an attributed recovery report, not independent proof that every earlier failed evaluation or payment was repaired.

Why 2 stars: A concrete recovery update is useful to affected miners; universal recovery is not established.

#15 · SN61 · RedTeamdeveloping
★★★★★

SN61 RedTeam announces a replacement miner dashboard

The October 25 team-attributed digest points miners to theredteam.io and says the older dashboard will be retired soon. No retirement deadline was supplied. The site responds, but its application could not be fully inspected in the text fetch; we do not claim to have verified every screen or a measured speed improvement.

Why 2 stars: The destination change is useful to miners without turning a dashboard refresh into a major product breakthrough.

#16 · SN62 · Ridgesdeveloping
★★★★★

SN62 Ridges reports recovery after maintenance-related evaluation pause

The October 25 team-attributed digest says evaluations paused during a short outage for a security update and scheduled maintenance, and that service subsequently returned. It does not establish a security breach, loss of funds or repair of every affected job. The item closes the operational loop while keeping the scope of the recovery claim explicit.

Why 2 stars: Service availability matters to participants; the evidence supports an attributed maintenance/recovery report, not a breach claim.

#17 · SN71 · Leadpoetdeveloping
★★★★★

SN71 Leadpoet reward-rule dispute continues as arena fixes land

The October 25 digest reports a miner dispute over when stricter improvement thresholds were applied, and says the team declined retrospective changes. We have not independently verified the claimed lost reward. Separately, public code allows miner execution alongside baseline judging and adds recovery for stopped scoring jobs with bound provider failures. The commits establish implementation changes, not resolution of the disputed payout or proof that all live rounds have recovered.

Why 2 stars: Miner-facing reliability fixes and an unresolved rule dispute deserve a concise update without treating allegations as settled facts.

#18 · SN78 · Umideveloping
★★★★★

SN78 Umi keeps C5 rewards active while C6 evaluation continues

The October 25 team-attributed digest reports 32 of 103 C6 models fully evaluated and a provisional completion target around 15:00 UTC. C5 remains the active reward cohort until final scoring and weight activation. New public code also schedules resident models against physical GPU capacity and preserves progress on longer cases. A target finish time is not evidence that C6 weights are active.

Why 2 stars: The active reward cohort is the useful distinction for miners; progress figures remain team-reported.

#19 · SN118 · Dittoverified
★★★★★

SN118 Ditto tightens resubmission review; a new track remains in testing

The October 25 v0.387.0 release adds review of same-hotkey submissions against their earlier lineage; v0.387.1 preserves the managed Gamma guard across configuration converges. Separately, the team-attributed digest describes a new competition track running in shadow mode, awaiting scoring verification. Published code is distinct from reward activation: the additional track is not reported as live.

Why 2 stars: Concrete release changes affect submission checks, while the planned track still has an activation gate.

Stars indicate editorial priority, not investment quality. Routine competition updates receive at most three stars. Shizzy videos receive three; substantive non-video Shizzy coverage receives at least four. Scheduled events remain plans.

Sources & coverage notes
04

Audit trail

Coverage notes

Grayscale’s amended filing keeps a TAO ETF on the application path; SN15 ORO reports an evaluation audit; SN25 UR revises its settlement timetable; and an SN91 Cascade user describes a live integration. Also: GPU profiling, miner-facing fixes, three finalized burns and the refreshed Shizzy video library.

Coverage: Oct 24, 2026, 12:24 PM – Oct 25, 2026, 10:57 AM ET

Searched

  • Signed-in @ShizzyUnchained Grok discovery, qualitative top-five and omission reconciliation.
  • All 128 current subnet project pages and dated Discord-brief URLs, grouped SN-number X searches, selected official and partner originals/replies, owner bookmarks and visible History surface.
  • Known repository paths from current metadata and prior registry, selected commit diffs and releases; primary SEC filing and original customer/developer statements.
  • Finalized full-block eTAO/burn review and full prior-report lifecycle scan; owner/registration reconciliation and same-block daily owner holdings/emission estimates.
  • Both YouTube Videos and Live shelves plus watch-page access/duration/schedule metadata; full 128-row alpha/TAO market snapshot and sector identity check.

Public-data gaps

  • X review used all subnet-number groups, current roster/project pages and selected direct team/partner profiles; it is sampled public coverage, not an exhaustive account or private-channel census.
  • Discord summaries are attributed discovery sources. Original private messages, ORO account enforcement and disputed miner payouts were not independently audited; those items remain developing.
  • The owner’s visible X History surface exposed Bookmarks and Likes, not a complete browsing history. Saved leads were reviewed; unviewed full-length interview media and private communities remain gaps.
  • Some repositories were unavailable and first-page supplemental results can omit older commits. Code publication does not establish production rollout.
  • Burn history before October 20 depends on paginated index discovery with qualifying events independently finalized-chain verified, not a complete earlier block replay. Daily full-block event coverage ends at the stated finalized cutoff.
  • Provider credit usage, internal revenue accounts, paid inference and every regional wallet build were not independently tested. Grok attention is a qualitative lead list, not measured mention rankings.
Browse all 78 editions

Conference news · September 30, 2026

Exploit Conference Catch Up · Day 1

The teams, the ideas and the practical takeaways from Exploit Summit’s first day in Montreal. From Gamma and phone-based AI to robotics, science and the business of running a subnet.

Catch up on Day 1

Conference news · October 1, 2026

Exploit Conference Catch Up · Day 2

Catch up on Exploit Summit’s second day: Carbon’s Pitchtensor win, SN107 Minos’ research app, agent controls, robotics data, inference partnerships and the decisions behind building a subnet business.

Catch up on Day 2