THE DAILY BRIEFING

Bittensor Daily — November 4, 2026

Discord carried little ecosystem substance today: #General logged its busiest volume of the week but almost entirely in routine moderation, and #Rao's traffic was mostly banter apart from one unresolved security claim. The week's governance and tokenomics threads -- the SN82 emissions dispute, the emission-decay proposal -- did not resurface, leaving the subnet cards and protocol changes to carry the day's actual news: SN118 (Ditto) reworked its emission split again, SN55 (NIOME) faced questions over rounded top-miner scores, and SN70 (Fugal) launched into the Yuma Accelerator.

Subtensor merges a breaking security fix for proxy announcements and basket-dividend minting.
(1) The change tightens security controls around how proxy announcements are processed and how basket dividends are minted, a protocol-level fix rather than a feature addition. (2) It is marked breaking, meaning node operators and developers integrating with proxy or basket-dividend functionality must update, while ordinary TAO holders are not directly affected beyond the added protection. (3) It lands in the same week as Release 487's quantum-resistant wallet rollout, continuing a run of security-hardening changes to the proxy and wallet system first shipped Oct 27.
In #Rao, a member's claim of a "critical security problem" in the substrate chain draws no triage beyond a moderator's redirect to GitHub.
Who's currently responsible for substrate chain security? was met only with Please see the "Official Links" article in the FAQ for a link to the GitHub, if you want to report an issue via GitHub. When the asker escalated -- so, should I open an issue about the critical security problem in public repo? -- the reply left the decision to them: If you want to. But there's another option in the article I linked. (1) No one in the channel, moderator or otherwise, asked what the claimed problem actually was, so a security report passed through #Rao without acknowledgment of its severity. (2) This differs from the week's tokenomics and governance threads, which went unanswered but were policy debates rather than a potential vulnerability report. (3) The asker thanked the moderator and did not return with further detail in the material.
SN118 (Ditto) reworks its eTAO emission split again and ships Benchmark v15 with an expanded tool menu.
(1) The subnet changed its emission split from 18/41/41 to 18/33/49 and removed the 50% miner burn, raising payouts to miners and to validators and stakers, a further adjustment on top of the split change reported Nov 1. (2) Benchmark v15 expands the tool menu to roughly 235 tools per test run and gives every agent a decision model, though v14 continues to control emissions until the top cohort reaches a full v15 quorum. (3) Separately, an agent submission was rejected on manual review for rewriting its model reply and answer line after generation, which the team said violated policy; its token fell 2.37% over 24 hours.
On SN55 (NIOME), miners say top-ranked scores turned suspiciously rounded from the same point WandB logging stopped.
(1) A miner compared score outputs before and after WandB logging was paused and said several top miners' scores began appearing unusually rounded from that round onward. (2) The subnet team paused both the task generator and the owner validator for a leaderboard update, attributing the WandB outage to a service issue rather than addressing the scoring pattern directly. (3) Separately, other miners asked the team to share more detail on the winning compression algorithm to verify results; the team said it is investigating how top miners submit, with no resolution in the material and the token roughly flat at -0.18% over 24 hours.
SN70 (Fugal) launches as an LLM-routing subnet and joins the Yuma Accelerator, with its token up 339.24%.
Fugal is joining the Yuma Accelerator. (1) The subnet's scoring design benchmarks a miner-trained router inside a TDX virtual machine each epoch, requiring it to beat a fixed baseline mix of models at the same cost, with no central evaluator including the team itself. (2) The team confirmed emissions are live and published a miner guide on GitHub as part of the launch. (3) The move follows a pattern of new subnets entering the Yuma Accelerator framework seen with other subnets this month; the token's 339.24% move stands out even among the week's subnet price swings.
Other: SN127 (Zils)'s identity change prompts channel questions, SN91 (Cascade) partners with SN6 (Numinous) on election forecasts, and #General spends a busy day on routine moderation.
A member asked is it normal that there is no channel 16 ? 16 has been registered and its already live(tradable), which a moderator traced to a setup interrupted by the subnet's deregistration, while a separate question about btcli drew the unconfirmed note Latent doesn't maintain btcli since v10. I'll check out the page though. (1) SN127 (Zils)'s on-chain identity change drew member questions referencing a similar earlier incident on SN27, with the channel later archived ahead of an incentive-mechanism change. (2) SN91 (Cascade) announced a partnership with SN6 (Numinous) combining knowledge graphs with time-series forecasting, publishing zero-shot Senate-seat election forecasts through its new Ephemeris platform. (3) #General's volume rose to 27 messages, its busiest this week, but the increase was almost entirely moderation and repeated scam warnings rather than ecosystem discussion.

#General

4 REPORTS

Notable

A member's question about btcli's safety surfaces that the tool is no longer maintained by its original team

Opening · 09:20–13:00 UTC

A member asked Is this safe?, which another member turned into a pointed question about the CLI itself: btcli is safu?

Clarification · 13:59 UTC

A community regular answered with a maintenance detail rather than a security verdict: Latent doesn't maintain btcli since v10. I'll check out the page though

2 things to read from it

The exchange starts as a generic safety check but lands on a specific, unresolved fact: the CLI tool the whole ecosystem depends on for staking and validation has reportedly changed hands in maintenance terms without any wider announcement in the channel.
No moderator or official voice confirmed who, if anyone, now maintains btcli, leaving the claim about the handoff since v10 unverified in the material.

Where it stands

Left open; the maintenance claim was offered by a community member but not confirmed or elaborated on by a moderator or developer.

Notable

A gap in the subnet-channel list turns out to be a moderator oversight from subnet 16's deregistration, not a deliberate policy

Question · 19:45 UTC

A member flagged a missing channel for a subnet that was already trading: is it normal that there is no channel 16 ? 16 has been registered and its already live(tradable)

Reply · 19:47 UTC

A moderator checked and found an unfinished setup: Hm. Let me go look at that one. I see the unclaimed channel, but it's not public yet.

Outcome · 19:48 UTC

The moderator traced the cause to the subnet's deregistration: I think I got interrupted while setting up the channel after subnet 16 was deregistered the other day. Thanks very much for pointing that out. : )

2 things to read from it

The channel's subnet-list maintenance runs on manual moderator work rather than any automated process, and a live, tradable subnet can sit without a public channel until a member happens to notice and ask.
Unlike most of today's traffic, this is a case where a member's question produced a concrete, acknowledged fix rather than a redirect or a standing reminder.

Where it stands

Resolved: the moderator confirmed the cause and thanked the member for flagging it, with the new channel still described as not yet public.

Other

A question about whether a new owner took over subnet 127 is redirected to archived channels rather than answered directly

Redirect · 16:52–16:54 UTC

A member asked Did Zils take over sn 127? and was told first to use the proper reporting path -- Please don't ping me personally for moderation issues. I'm not on 24/7. -- and then pointed elsewhere: Please read the pinned posts in the channel. I'd also recommend you read the most recent messages in the archived Astrid channel.

What to read from it

The ownership question itself was never answered in the channel, consistent with the channel's standing pattern of routing subnet-specific queries to other resources rather than resolving them directly.

Where it stands

Unresolved in the channel; the member was pointed to pinned posts and an archived channel rather than given a direct answer.

Other

Other: profile-privacy reminders, a testnet-TAO scam attempt, an off-topic job pitch, and a newcomer's mining question filled out a routine day

Moderation · 00:49–17:17 UTC

The channel repeated its standing profile rule twice -- Please make your profile public and keep it that way. Private profiles are not allowed in this server -- while a request to send testnet funds to an address drew a scam warning: we can't do that, sorry, and any DMs or FRs you get about it are a scam.

Off-topic · 17:51 UTC

An unrelated job pitch ran with no reply: Hi I'm looking for a caller. all the country is available. can speak native language fluently. payment:$50/hr if you wanna work with me send me DM..

Newcomer · 18:24 UTC

A newcomer asking how to start mining TAO was redirected to the FAQ -- please see the "Mining & Validating" section of the <#1215386737661055056> channel. -- alongside the channel's broader scam reminder: If you get any DMs or FRs from people claiming to be support for Bittensor, any subnet (or any kind of support at all, **including people pretending to be me or other mods**), **it's a scam**. Block all such requests.

2 things to read from it

Volume rose to 27 messages, the channel's busiest since Oct 30's 18, but as on Oct 30's bridge-scam case and Nov 2's double scam warning, the increase was almost entirely moderation and repeated reminders rather than ecosystem discussion.
The unanswered job pitch and the newcomer's mining question show the channel continuing to route anything outside routine support elsewhere rather than engaging with it directly.

In the week’s context

Oct 30: #General logged a member's funds stuck in a third-party bridge and the same standing imposter-scam warning used again today.
Nov 2: #General ran its standing scam warning twice in one day with no ecosystem discussion, the same pattern repeated today.

Where it stands

All items closed through standard moderator response, redirect or silence; nothing substantive remains open.

#Rao

2 REPORTS

Notable

A member claims a critical security problem in the substrate chain, and the channel's only response is to route them to standard reporting channels

Opening · 15:27 UTC

Asking who holds responsibility for the chain's underlying security, the asker got no direct answer from anyone in the channel beyond a moderator: Who's currently responsible for substrate chain security?

Reply · 15:28 UTC

A moderator pointed only to standard process rather than naming anyone responsible: Please see the "Official Links" article in the FAQ for a link to the GitHub, if you want to report an issue via GitHub.

Escalation · 15:34 UTC

The asker then stated the issue was serious: so, should I open an issue about the critical security problem in public repo?

Outcome · 15:36–15:38 UTC

The moderator left the choice to the asker without engaging on the substance: If you want to. But there's another option in the article I linked., drawing only a brief Okay, thanks

3 things to read from it

The word "critical" was used by the asker to describe the problem but no one in the channel -- moderator or otherwise -- asked what it was, meaning a claimed security issue passed through #Rao without any triage or acknowledgment of its severity.
The exchange shows the channel has no mechanism to escalate a security report beyond pointing to a public GitHub or an unnamed alternative in a linked article, leaving the asker to decide unassisted whether to disclose a vulnerability publicly.
Unlike the emission-decay and SN82 tokenomics threads that ran through much of last week without official input, this is a potential security matter rather than a policy debate, which makes the absence of a substantive response more notable even in a lower-volume channel day.

Where it stands

Unresolved in the channel: the moderator declined to evaluate the claim and left the reporting route up to the asker, who thanked them and did not return with further detail in the material.

Other

Other: a banned account seeks reinstatement, a subnet promotion gets redirected, and a running joke answers a question about an unofficial server badge

Items · 01:20–15:27 UTC

A member asked how to resolve a friend's ban from the server: My fr discord account banned from this community, he would like to join again, how can we resolve this?, and was told to open a support thread. Separately, a member promoting an SN30 (Endure) mainnet countdown was checked by a moderator -- Hi. Is this the product of a subnet? If not, please don't promote it here. -- before confirming it was sn30. A question about earning the channel's Rao badge drew only a joke: Need to say rao 3x in a row into a mirror at 3 am, followed by why 3am, not possible to do it at 7am? I generally wake up at 7am 😉 and the deadpan close Sacrifice.

What to read from it

None of today's remaining traffic touched tokenomics or governance, a sharp drop in substance from the week's earlier SN82 and emission-decay threads, consistent with the lighter volume the channel has shown since Oct 31's 102-message peak.

Where it stands

All items closed through moderator routing or banter; nothing substantive remains open.

Subnets

5 REPORTS

SN70 24h +339.24%

Fugal

What happened: SN70 (Fugal) launched as a new subnet under new ownership, positioned as an LLM-routing subnet that selects the cheapest model capable of answering a query correctly. The subnet joined the Yuma Accelerator, and emissions were enabled. The team described a scoring design in which miners train a router that is benchmarked inside a TDX virtual machine each epoch and must beat a fixed baseline mix of models at the same cost to earn rewards.
Community: Community members welcomed the new team and asked questions about verification, how the subnet differs from SN34, and the timing of emissions. One community member raised concerns based on the subnet's history under previous ownership, while others called the mechanism promising but cautioned against full token distribution to miners early on.
Official: The team introduced itself, published a miner guide on GitHub, and stated that benchmark results run in miners' own TDX VMs with attestation verified by validators, with no central evaluator including the team itself. The team confirmed emissions were live as of the latest update.

SN127 24h +33.93%

Zils

What happened: SN127 (Zils)'s on-chain identity changed to "Zils," prompting questions in the subnet channel about whether the change was legitimate, with several members referencing a similar earlier incident involving SN27. A person identifying as the project lead, posting as "Ken // Zils," said the team had been working on the project and that more updates would follow. A moderator later confirmed the subnet owner had requested the channel be archived ahead of a new one, citing a change to the incentive mechanism.
Community: Several members urged caution and asked for official confirmation before accepting the name change, citing the earlier SN27 case as a reason for doubt. Others pointed out that a message sent to the apparent project lead on X had gone unanswered for a time, which added to the uncertainty.
Official: A person identifying as the project lead posted confirming months of work on the project with more details to come, and a moderator later confirmed the identity change was tied to the subnet owner and announced the channel would be archived for a new one due to an incentive mechanism change.

In debate · Whether SN127's rename to Zils was legitimate · 17 participants

Some members cited a similar incident on SN27 as reason to treat the rename with suspicion.

“Same happened to sn27”
Others noted the apparent project lead had not responded to direct questions on X, which deepened doubts.

“I asked him on X. He saw my message but didn’t answer. Think why?”
A community member and a person identifying as the project lead confirmed the rename was part of a legitimate launch.

“I can confirm, Zils is on the subnet.”

SN91 24h −4.13%

cascade

What happened: Cascade (SN91) announced a partnership with Numinous (SN6) that combines knowledge graphs with time-series forecasting. The subnet also launched Ephemeris, a customer-facing time-series inference platform that can ensemble multiple forecasting models, offering a choice of seven models. Using Ephemeris, Cascade published zero-shot midterm election forecasts, including projected Senate seat leans by state.
Community: In the subnet channel, a validator noted a scoring issue involving the dethroning "crown" mechanism, saying a fix had been pushed to GitHub after a challenger's metrics appeared to clear the margin without the crown changing hands. One participant raised concerns about mining practices on the subnet, which another community member disputed, attributing the discrepancy to a bug rather than any deliberate conduct; the matter remained unresolved in the discussion.
Official: The team announced the Numinous partnership and the Ephemeris launch on X, and published zero-shot Senate seat forecasts for the midterms via Ephemeris, projecting Democrats leaning to 53 seats with specific state-level leans listed.

SN118 24h −2.37%

Ditto

What happened: SN118 (Ditto) rolled out Benchmark v15, which expands the tool menu to about 235 tools per test run and gives every agent a decision model; Benchmark v14 continues to control emissions until the top cohort reaches a full v15 quorum. The subnet also changed its emission split from 18/41/41 to 18/33/49 and removed the 50% miner burn, raising payouts to miners and to validators/stakers. Separately, an agent submission, Crown v8, was rejected on manual review for rewriting model replies and the answer line after generation, which violated policy v13.
Community: Miners repeatedly asked about submissions stuck in "under review" status and about when their scores would appear on the new v15 leaderboard. Some also asked whether only the top 5 agents could run retests under v15 and pressed for updates on delayed scoring caused by validator capacity issues.
Official: The team announced the emission split change and the Benchmark v15 launch, and explained that the Crown v8 rejection stemmed from code that altered the model's reply and ANSWER line after generation. The team also acknowledged a gap in applying v15 scores to some agents scored right after rollout and said it was working on a fix.

SN55 24h −0.18%

NIOME

What happened: Miners reported that SN55 (NIOME)'s top-ranked miners have been receiving scores with unusually rounded values since a round identified as 5f7cc0c7, the same point at which WandB logging for the subnet stopped. The subnet team subsequently paused the task generator and owner validator for a leaderboard update, saying both would return online soon.
Community: Multiple community members, including a miner and a validator, repeatedly asked the team to explain the rounded scores and to restore WandB logging, noting they could not audit miner performance without it. Several messages expressed frustration at what they described as a lack of response from the subnet owner.
Official: A team representative said WandB is currently unavailable due to a service issue, that the leaderboard is being updated, and that the team is investigating how top miners submit their results.

More subnet community coverage every day in the Telegram channel →

SN55 (Soma) scoring transparency dispute

A miner compared score outputs before and after WandB logging was paused on SN55 (Soma) and said several top miners' scores began appearing unusually rounded from that point on. The subnet team said WandB and the task generator were temporarily paused for a leaderboard update, while separately other miners asked the team to share more detail on the winning compression algorithm to verify results.

Positions

A miner argued that scores for several top miners have looked suspiciously rounded since WandB logging stopped, which would not normally happen with values derived from averages over many rows.

“It's totally weird that top miners' scores are all rounded.”
Other miners said they do not trust the outcome of the competition and pressed the team to explain or share more about how the top result was produced.

“miners cannot believe winner's result.”
A team member said the winning code cannot be fully open-sourced because it underpins SOMA's commercial product, while maintaining that its output can be tested through the public API.

“it's accessible - anyone can use it and check that it's really doing its job.”

Official response: The team said WandB and the task generator were temporarily paused because of a leaderboard update and that both would return online soon. It also said it was investigating how top miners share their submissions, and separately pushed a fix for a reported validator bug; it has not given a specific explanation for the rounded score values raised by the miner.
What to watch: Whether WandB logging is restored and whether the team issues a direct explanation for the rounded scores that prompted the original complaint.

@TensiaFDN

TensiaFDN says on-chain data shows a subnet owner bought and sold alpha within minutes, collected 539 τ in 19 days via a single miner, then repeated it on another subnet.

View the original post on X ↗
@reaxlabs

@reaxlabs introduced REAX 1.3, an open decision model built from models developed in its Bittensor miner competition plus existing open models, now available via API.

View the original post on X ↗
@CryptoZPunisher

@CryptoZPunisher welcomed SN70 (Fugal), noting it competed against @carbonphysicsai at the PitchTensor event in Montreal, but cautioned that liquidity is thin and Root proportion is still building.

View the original post on X ↗
@404gen_

@404gen_ said 404 is building Found Games, a platform letting creators generate games, build audiences, and monetize work on Bittensor, following its Game Jam.

View the original post on X ↗
@ReadyAI_

@ReadyAI_ said Skill Store 33 is live, claiming an open model with one skill beats Claude Opus 5.5, with 95 skills so far outperforming it at 26x cheaper and 6x faster.

View the original post on X ↗
@harnyx_ai

@harnyx_ai said SN67 now awards two titles: one for best deep research report with sourced claims, and a new one rewarding accuracy alone.

View the original post on X ↗
@cascade_sn91

@cascade_sn91 said SN91 (Cascade) partnered with @numinous_ai to combine knowledge graphs with time-series forecasting for better predictions of company and event relationships.

View the original post on X ↗
@xeveryframe

@xeveryframe said SN117 (EveryFrame) will route emission unused by miners to a new EveryFrame Treasury Wallet funding the EveryFrame AI Film Contest, while miners remain paid first.

View the original post on X ↗

◆2026-11-04 · End of this edition

#3299 Breaking change

fix: secure proxy announcements and basket minting

What: This PR tightens security controls around proxy announcements and the process used to mint basket dividends.
Why: The change addresses a vulnerability in how proxy announcements and basket dividend minting were validated, which could have affected the pricing used in that process.
Who it affects: This is a breaking change at the protocol level; node operators and developers integrating with proxy or basket dividend functionality need to update accordingly, while ordinary TAO holders are not directly affected beyond the added security.

#3301

fix(lending): clone-500 UX — amount path, deferrals, results, help

What: This PR improves the user experience of the lending tool, including error messages for amount inputs, logging of deferral reasons, result labeling, and help documentation.
Why: These are usability and clarity fixes to make the lending tool's behavior and output easier to understand.
Who it affects: This affects developers and users of the lending tool's command-line interface; it has no direct effect on miners, validators, or TAO holders outside of that tool.

Past editions +

24H Market

Gainers

Losers

Bittensor Daily — November 4, 2026

#General

A member's question about btcli's safety surfaces that the tool is no longer maintained by its original team

A gap in the subnet-channel list turns out to be a moderator oversight from subnet 16's deregistration, not a deliberate policy

A question about whether a new owner took over subnet 127 is redirected to archived channels rather than answered directly

Other: profile-privacy reminders, a testnet-TAO scam attempt, an off-topic job pitch, and a newcomer's mining question filled out a routine day

#Rao

A member claims a critical security problem in the substrate chain, and the channel's only response is to route them to standard reporting channels

Other: a banned account seeks reinstatement, a subnet promotion gets redirected, and a running joke answers a question about an unofficial server badge

Subnets

Fugal

Zils

cascade

Ditto

NIOME

SN55 (Soma) scoring transparency dispute

fix: secure proxy announcements and basket minting

fix(lending): clone-500 UX — amount path, deferrals, results, help

24H Market

↗Gainers

↘Losers

Bittensor Daily — November 4, 2026

Today's highlights

Discord conversations worth following

A member's question about btcli's safety surfaces that the tool is no longer maintained by its original team

A gap in the subnet-channel list turns out to be a moderator oversight from subnet 16's deregistration, not a deliberate policy

A question about whether a new owner took over subnet 127 is redirected to archived channels rather than answered directly

Other: profile-privacy reminders, a testnet-TAO scam attempt, an off-topic job pitch, and a newcomer's mining question filled out a routine day

A member claims a critical security problem in the substrate chain, and the channel's only response is to route them to standard reporting channels

Other: a banned account seeks reinstatement, a subnet promotion gets redirected, and a running joke answers a question about an unofficial server badge

Fugal

Zils

cascade

Ditto

NIOME

Ecosystem debate

SN55 (Soma) scoring transparency dispute

Voices on X

Protocol

fix: secure proxy announcements and basket minting

fix(lending): clone-500 UX — amount path, deferrals, results, help

Recent editions

Gainers

Losers