Daily digest of the Bittensor ecosystem

中文/EN

Daily edition
Nov 12, 2026

Bittensor Daily A 1T1B product
1T1B ↗
BITTENSOR DAILY

24H Market

01/10

Gainers
--Loading…--
Losers
--Loading…--

THE DAILY BRIEFING

Bittensor Daily — November 12, 2026

The day's busiest #Rao session of the week produced no resolution on whether stakers are owed anything beyond price appreciation, running alongside taostats' detailed explanation of how Gamma's anti-pump pricing actually works and a quieter #General carrying a stale-weights emissions question. Subnet news added real weight too: SN3's owner coldkey was compromised for roughly 2,068 TAO, and SN44 (Score) found a blacklisted coldkey re-registering under the same banned container within hours. The week's recurring root-basket freeze did not resurface in either channel today.

Today's highlights

  1. A #Rao member's proposal for a staker-elected board of directors to oversee subnet owners splits the channel between corporate-style oversight and a code-enforced alternative, with no agreement reached.

    there are board of directors, that oversee the company's affairs and ensures it acts in the best interest of the stakers. drew a counter-proposal: when bittensor would incentivize subnets to combine zktls (bank proofs) + telemetry (work logs) + gross revenue smart vaults (top-line buybacks), you don't need to trust the owner's word, and you don't need a slow corporate board to steer/replace them. A third member pushed back that the owners of subnets are generally the biggest holders of alpha, so they would appoint a board of directory of people close to them, or themselves, prompting the retort The investor class is the proletariat in this ecosystem. (1) This is the most developed #Rao exchange of the week, running over fifteen hours across a dozen participants, far beyond any prior mechanism question the channel has carried. (2) The information-asymmetry complaint at its center echoes the unresolved trust gaps raised around SN51 (Lium)'s unpublished buyback plan and SN82 (Noah)'s ownership-concentration dispute earlier this week, though no one in the thread named either subnet. (3) The thread ends without consensus: one member proposes simply moving capital toward subnets that prioritize token value as the only real lever, with no team or moderator voice weighing in at any point.

  2. SN3 (Teutonic)'s owner coldkey is compromised, with 101,141 alpha moved and sold for roughly 2,068 TAO.

    (1) The subnet owner confirmed the breach, saying the key had been exposed during a recent conviction-lock takeover and had originally held zero funds, framing the loss as about 20% of personal holdings. (2) An independent on-chain investigation corroborated the transaction details, tracing the stolen alpha to an untraceable wallet that was sold within minutes. (3) The owner reaffirmed commitment to the project and acknowledged that proper multisig, proxy or vault setup could have prevented the loss; the subnet's token fell 4.16% over 24 hours.

  3. Taostats publishes a detailed explanation of how Gamma's dual-price design is built to resist pump-and-mint manipulation, the same day a #Rao member asks about the feed's sourcing.

    can you pump a subnet's alpha price and mint more gamma? No, and the reason is a neat bit of design. When you burn alpha, it's valued at the LOWER of two prices and Prices that fall fast and rise slowly mean only lasting demand turns into gamma. In #Rao, a member asked What's the source of tao/usd price feed for gamma? and was told From an oracle by OTF, with 4 different CEX/API sources that average out to the TAO/USD feed on-chain. (1) This follows Gamma Tokens' formal launch on Nov 10, giving the mechanism its first detailed public breakdown rather than just an announcement. (2) The #Rao answer and the X thread describe the same oracle independently, with no cross-reference between them. (3) The asker in #Rao received a direct answer and did not follow up.

  4. A #General member reports miners keep earning emissions despite validators no longer sending tasks, and a community member traces it to stale on-chain weights.

    But no miners are getting tasks anymore. All miners were getting tasks every 2.5 hours before. But now, even though there is no changes in mechanism and no miners are getting tasks, top miners are fixed and continue to get emissions. Another member explained: Validators update their weights periodically by submitting them to the blockchain. Between updates, the most recently submitted weights remain active and continue to count toward emissions. (1) This is a plain mechanism explanation rather than a dispute, but it surfaces a real consequence of the weight-setting design: an idle validator doesn't stop payouts, it freezes them. (2) No moderator or official voice weighed in; the explanation came entirely from a community member, continuing the channel's pattern this week of peer answers carrying the technical detail official replies don't. (3) The asker did not confirm whether this matched what they were observing.

  5. Other: SN44 (Score) blacklists 45 hotkeys on its private cricket track, and the same coldkey re-registers under the banned container within hours, while #General logged its busiest week-day on routine moderation.

    (1) The team said the blacklist "had nothing to do with actual cheating inside the solution," but the rapid re-registration under the same banned image was not resolved in the material. (2) SN44 separately removed several challenge blocks across multiple tracks for incorrect ground-truth annotations and introduced a new zero-score exclusion rule to offset Chutes warmup failures; the token fell 1.12% over 24 hours. (3) #General rose to 35 messages, its busiest day of the week, but the volume was driven by redirects, a moderator-issued warning over a personal-attack spat, and recurring cryptic posts rather than new ecosystem substance.

Discord conversations worth following

#General

2 REPORTS

Notable

A member asks why miners keep earning emissions when validators appear to have stopped sending tasks, and the explanation points to stale on-chain weights.

Opening ·

A member asked Can it be possible to get emissions when there's no validator running? Miners are not getting tasks from validator but I can still see specific miners are getting emissions, and when told it was possible, pushed back: But no miners are getting tasks anymore. All miners were getting tasks every 2.5 hours before. But now, even though there is no changes in mechanism and no miners are getting tasks, top miners are fixed and continue to get emissions.

Clarification ·

Another member explained the mechanism: Validators update their weights periodically by submitting them to the blockchain. Between updates, the most recently submitted weights remain active and continue to count toward emissions. This means that if validators stopped querying miners but their previously submitted weights remain valid on-chain, the same top miners can keep receiving emissions at each epoch until those weights are updated.

2 things to read from it

  1. This is a plain mechanism explanation rather than a dispute, but it surfaces a real consequence of the weight-setting design: a validator going idle doesn't immediately stop payouts, it freezes them at whatever was last submitted.
  2. No moderator or official voice weighed in; the explanation came entirely from a community member, continuing the channel's pattern this week of peer answers carrying technical detail that official replies don't.

Where it stands

Answered by a community member with no official confirmation; the asker did not follow up to say whether this matched what they were observing.

Other

Other: a subnet concern was redirected to a pinned thread, routine support questions got FAQ pointers, a string of cryptic philosophical messages drew moderator redirects, a late-night 'alt account' spat prompted a warning, and greetings and a song share rounded out the busiest #General day of the week.

Mixed ·

A member raised a concern about a subnet owner's responsiveness and was told Please read https://discord.com/channels/799672011265015819/1411010027333877884/1423705944331784253, replying Thank you, the owner is not responding for weeks so I wrote here. Separately, a member asking for test TAO was pointed to the FAQ, and another with a blockmachine API issue was redirected with Here https://discord.com/channels/799672011265015819/1414687189752746167. One member repeatedly posted cryptic, abstract messages -- it's not a question, it's an invitation for you to test something you want so much. draw your own conclusions and I connected some separate areas of biology to physics, logic, form... can I send it here? -- each time redirected by a moderator, who at one point said I don't think it's relevant here. You can probably share it in the community-led Discord. Late in the day, an accusation that a member was an alt account (Bro, you joined this channel just 10 days ago. How do you already know all the history? 👀 Kinda sus, looks like an alt lol) drew a denial (New account ≠ new to TAO, bro) and a moderator reminder: Hi folks. Just a gentle reminder that if you start in with personal attacks and squabbling, I'll be handing out some mandatory breaktime. The day closed with a member sharing a Bittensor-themed song (I made a little song inspired by Bittensor and this amazing community.) and a mining-hardware question answered with a pointer to the Mining & Validating channel.

What to read from it

  1. Volume rose to 35 messages, the channel's busiest day this week after Nov 9's 30 and Nov 10's 24, but the increase was almost entirely routine redirects, a moderation flare-up, and recurring cryptic posts rather than new ecosystem substance.

Where it stands

Closed; all items resolved through redirect, moderator reminder, or no further reply.

#Rao

4 REPORTS

Key

A long #Rao thread debates whether subnet owners owe stakers any formal accountability, proposing a corporate-style board before splitting over whether holders are owed anything at all

Opening ·

A member argued that subnet owners increasingly treat they are only in a relationship with the miners and proposed importing a corporate mechanism: there are board of directors, that oversee the company's affairs and ensures it acts in the best interest of the stakers., adding that such a body would monitor financial performance, hold SN owners accountable, and in extreme cases, have the authority to replace the SN owner.

Alternative ·

Another member rejected a human oversight body in favor of code, asking wouldn't verifiable on-chain institutional frameworks be better aligned with bittensor's goal of a permanent, open network that produces intelligence anyone can use and no one can control? and sketching a design where subnets combine zktls (bank proofs) + telemetry (work logs) + gross revenue smart vaults (top-line buybacks), you don't need to trust the owner's word, and you don't need a slow corporate board to steer/replace them., concluding The code forces transparency and dtao handles the rest. The original proposer conceded: those solutions that you mention sound much better, although they sound like sci-fi to me and I had no idea they were possible.

Pushback ·

A third member disputed that any board would be independent, since the owners of subnets are generally the biggest holders of alpha, so they would appoint a board of directory of people close to them, or themselves., framing subnets instead as built to help business find workers (miners) and pay them in a permissionless and decentralized way. A reply countered: If that is the case I'm not sure what we are doing here and why we would remain in subnets., insisting The least a subnet can do is write out a plan how current investments will eventually lead to returning value to investors. A further voice summarized the dispute bluntly: The investor class is the proletariat in this ecosystem

Expansion ·

The argument spilled into a chicken-and-egg dispute over value itself -- one side holding The key is TAO, not the alpha token., the other asking And who or what gives that said TAO that is paid to miners /validators/owners value in real USD terms? before settling that it's a chicken or the egg issue depending on perspective. A separate member proposed a market answer rather than a governance one: I will put my tao in the subnet or subnets that make bringing value back to the alpha token a priority....and i suggest everyone else does the same, arguing If the subnets doing this end up with the lions share of emissions because everyone stakes with them then we force subnets to value us while warning the rest will see their alpha price degrades and their emissions dwindle.

4 things to read from it

  1. This is the most developed #Rao debate of the week on owner-staker accountability, running for over fifteen hours across a dozen participants, far beyond any prior mechanism question the channel has carried.
  2. No consensus emerged: the thread moves from a formal governance proposal to a cryptographic-transparency alternative to a flat disagreement over whether stakers are owed anything beyond price appreciation, and ends with one member proposing market exit as the only real lever.
  3. The information-asymmetry complaint at the center of the thread -- 'too much trust-me-bro atm' -- echoes the same gap that surfaced concretely on Nov 8-9 around SN51 (Lium)'s unpublished buyback plan and Nov 9's SN82 (Noah) ownership-concentration dispute, though no one in the thread named either subnet.
  4. The exchange ran entirely among community members with no team or moderator voice weighing in, consistent with #Rao's role this week as the channel for unresolved structural questions rather than official clarification.

In the week’s context

  • Nov 9's SN82 (Noah) card described on-chain evidence that most UIDs were controlled by multisigs tied to the owner, prompting a Root emissions cut -- the kind of owner-control concern this abstract #Rao debate is reaching for a general fix to.
  • Nov 8's SN51 (Lium) card recorded members pressing the team on a missing buyback plan and treasury transparency, the same trust gap today's thread frames as a design flaw rather than a one-subnet dispute.

Where it stands

Open and unresolved; the thread ends in disagreement over whether holders are owed formal accountability at all, with no proposal adopted and no official response.

Notable

A member asks what feeds Gamma's TAO/USD price, and gets a one-line answer on the oracle's sourcing

Question ·

A member asked What's the source of tao/usd price feed for gamma?

Answer ·

The reply: From an oracle by OTF, with 4 different CEX/API sources that average out to the TAO/USD feed on-chain

2 things to read from it

  1. The question lands the same day @taostats published a detailed breakdown of Gamma's anti-pump pricing design, including the same TAO/USD oracle, giving the #Rao answer a near-simultaneous official counterpart on X.
  2. This is a narrow technical follow-up to Gamma's formal Nov 10 launch rather than a new debate, and the asker received a direct answer with no further questions.

In the week’s context

  • Follows Gamma Tokens' formal launch on Nov 10, after the credit mechanism had sat live on-chain since Nov 6 pending activation steps.

Where it stands

Answered and closed; no follow-up in the channel.

Other

A side exchange clarifies that subnet ownership can in principle be taken over via conviction, though not easily or quickly

Clarification ·

Responding to an earlier question about conviction locking, one member said no. conviction lock is only the on-chain promise to not rug owner emission, which another corrected: No, he is right, you can get subnet ownership via conviction and boot the current owner out. Not easy to do, but possible.

Follow-up ·

Asked Not easy how?, the reply explained Maybe not the best word as the mechanic is permissionless, so easy enough in the sense that anyone could in principle do it. Was mainly referring to that you'd practically need substantial capital and that there's a time based element there (can't flash takeover for instance)

2 things to read from it

  1. This confirms, for the first time this week in #Rao, that subnet ownership itself is contestable through conviction rather than permanently fixed to the founding owner -- a mechanism detail relevant to the same day's larger debate over whether owners can be held accountable at all.
  2. The exchange stays at the mechanism level and does not connect explicitly to that parallel governance thread, though both concern who ultimately controls a subnet.

Where it stands

Resolved as a mechanism clarification; no one proposed actually attempting a conviction takeover in the material.

Other

Other: a proposed US AI-training bill draws a dismissive joke, with no further ecosystem discussion

Other ·

A member shared a claim that Democrats propose requiring AI companies to obtain federal government permission before training AI models, with up to 20 years in prison for violations, suggesting training subnets should avoid the US; another replied Yeah that will get Veto'ed least for the next 2 years

What to read from it

  1. A one-off political aside with no further ecosystem relevance in the channel today.

Where it stands

Closed; no reply beyond the single exchange.

Subnets

5 REPORTS

SN3 24h −4.16%

Teutonic

What happened
SN3 (Teutonic)'s owner coldkey was compromised, with 101,141 alpha moved and roughly 2,000 TAO transferred out through the compromised wallet. The subnet owner confirmed the breach and said the key had been exposed during a recent conviction-lock takeover, originally holding zero funds. TensiaFDN's on-chain investigation corroborated the transaction details.
Community
Members in the channel asked repeatedly who had sold and whether the owner's account had been hacked again, with some drawing comparisons to past owners' handling of their holdings. A community member proposed a verification test to confirm the owner's account was not compromised.
Official
The subnet owner confirmed the coldkey was compromised, apologized, said the loss amounted to about 2k TAO and roughly 20% of personal holdings, and reaffirmed commitment to the project, adding that proper use of multisig, proxy and vault setups could have prevented it.

In debate · SN3 owner coldkey hack fallout · 34 participants

  • Community members demanded proof that the owner's account itself was not compromised before trusting further updates.

    “Just so that we are all certain your account isnt compromised are you willing to do the Kim test?”
  • The owner acknowledged the incident as a personal security mishap and apologized while reaffirming commitment to the subnet.

    “Im sorry guys, this was a mishap on my side.”
  • Some community members framed the event as part of a pattern of SN3 owners benefiting from their holdings.

    “It seems that, historically, owners of the SN3 have known how to fill their bags.”

SN44 24h −1.12%

Score

What happened
The team blacklisted 45 hotkeys at once on the private cricket track, and within hours the same coldkey re-registered three new hotkeys using the same banned container image. The team also removed several challenge blocks on the Petrol Station, Room Dirtiness, Beverage, Person, and PPE tracks after miners flagged incorrect ground-truth annotations, and blacklisted three hotkeys on the Football element for forwarding challenges for external inference. Separately, the team introduced a rule excluding up to 2 zero scores per miner from average score calculations on Public Track to offset Chutes warmup failures. Miners also reported multi-hour outages on the Vehicle and Petrol detection elements.
Community
Several miners accused a specific coldkey of repeatedly re-registering banned solutions after the bulk blacklist, leading to heated exchanges and personal attacks in the channel. Miners pressed the team to implement a regular spot-check loop, saying honest miners had been requesting it for months.
Official
The team stated the latest blacklist "had nothing to do with actual cheating inside the solution" and referenced a rule limiting the number of hotkeys running similar solutions; it also announced the zero-score exclusion rule and listed the challenge blocks removed for incorrect annotations.

In debate · SN44 cheating and spot-check enforcement · 10 participants

  • A miner reported that a coldkey banned for cheating quickly returned with new hotkeys using the identical flagged image.

    “luckyscore is back after yesterday's blacklist. About 2 hours after commit 2b961bc, the same coldkey registered 3 new hotkeys with the same image”
  • The accused miner denied cheating and told critics to focus on their own model's performance.

    “calm down. i don't cheat. before insulting others, reflect on your own behaviors and focus on improving your model's performance.”
  • A team member said the recent blacklist action was unrelated to actual cheating within the solution itself.

    “Yesterday blacklist had nothing to do with actual cheating inside the solution”

SN102 24h −10.66%

ConnitoAI

What happened
SN102 (ConnitoAI) rolled out prompt validator v0.3, live from cycle 1392, which adds a mandatory JSON format check requiring exactly 3 lessons with required fields before an answer is sent to the judge. This follows v0.2, which graded lesson answers against lesson-specific rubric levels. 235 miners switched to the new Connito task and were scored, with about 46% of submissions failing JSON validity and most scores falling between 1 and 3 out of 5.
Community
A miner reported Cloudflare 403 errors on the cycle-api and dataless-api and asked for whitelisting, while another asked why results for a prior cycle were not yet visible. Other channel members discussed hardware requirements for mining and floated ideas for future task designs.
Official
A team member said they would follow up directly on the Cloudflare access issue, asking for the server IP and cf-ray IDs while warning that the team would never request keys or seed phrases. The team also published the v0.3 validator change log, noted the top three scores after the task switch were 2.08, 2.06 and 2.06 out of 5, and advised miners to test outputs for JSON validity before submitting.

SN64 24h −7.61%

Chutes

What happened
The official Bittensor account highlighted that SN64 (Chutes) trained an 8B parameter model, Parallax, across hundreds of consumer GPUs worldwide. Chutes' own account said the model runs at nearly 18,000 tokens per second on a single RTX 5090 GPU, handling 256 simultaneous requests. Separately, multiple miners reported chute warmup processes failing over several days, with team members asking for chute IDs to investigate.
Community
Miners repeatedly flagged the warmup failures in the subnet channel, with one miner confirming the issue was resolved after team follow-up. Other community members asked about a reported price drop; some speculated about wallet activity, though others pushed back on unverified claims and noted it was likely a large holder selling.
Official
Chutes' official account explained the speed is achieved through a small model, 4-bit math for expert layers, and a fixed-size cache for most attention, linking to the Parallax paper.

SN120 24h −1.56%

Affine

What happened
SN120 (Affine) experienced a two-hour stall in epoch 1081, which a miner flagged for review. Effective 03:38 UTC, the team enabled larger training files, raising the cap to 250 prompts x 8 rollouts and a 160 MiB file size limit, and introduced harder HEAD scoring at 24 rollouts per task. An independent evaluation using the Reliquary API compared Affine's latest king model against Qwen3.5-9B and MiMo base, reporting higher scores for the king model on AIME, MATH-500, and Apex Shortlist benchmarks.
Community
Miners repeatedly reported slow, non-concurrent evaluation and multi-day queue waits, with some describing waits of nearly 10 hours without queue progress. Discussion centered on registration-order queue disputes, which some miners referred to as a 'reg war,' alongside proposals to move to a first-submit-first-out queue and suggestions for pooled or elastic evaluation capacity.
Official
The team said it was working on the evaluation speed issue and published the updated training file size and scoring parameters along with the rollout's effective time.

More subnet community coverage every day in the Telegram channel →

Ecosystem debate

3 participants

Unclaimed SN36/SN42 ownership speculation

SN36 and SN42 remain unclaimed in their community Discord channels, meaning no confirmed owner has stepped forward there. Users repeatedly tried to identify the operators using on-chain identity data pulled from block explorers such as Taostats, prompting moderators to intervene and point to channel rules against making such claims.

Positions

  • A community member argued that on-chain identity data and repository information were enough to identify the subnet's operator and website even though the Discord channel was unclaimed.

    “I can check out the taostats and find out website and repo. The subnet is already running, just discord isn't claimed”
  • A moderator countered that on-chain identity information can persist from a subnet's previous registration and is not necessarily reliable evidence of current ownership.

    “this information is not reset when a subnet is deregistered, so it's possible you might be looking at old information”
  • A community member raised a technical concern that certain miner UIDs may not be eligible for rewards this early according to the subnet's published code.

    “According to the github repo code and the rules, those UIDs from 74-81 can't receive reward this early”
Official response
There has been no response from the subnet team or Opentensor. Channel moderators repeatedly stated that posting identity or ownership claims about unclaimed subnets is against channel rules and warned users against continuing to do so.
What to watch
Whether the subnet owner for SN36 or SN42 claims the channel and publicly addresses the on-chain identity and reward-eligibility questions raised by the community.

Voices on X

  • @taostats

    Taostats explains why pumping a subnet's alpha cannot mint more gamma, since gamma values burned alpha at the lower of the spot price or a slow-moving reference price.

  • @CryptoZPunisher

    CryptoZPunisher references a SN3 (unspecified name) compromised key incident involving 2,068 TAO sold, noting unanswered questions and crediting TensiaFDN's investigation.

  • @TensiaFDN

    TensiaFDN reports that on November 11 the owner key of a Bittensor subnet sent 101,141 alpha to an untraceable wallet, which was sold eight minutes later for 2,068 TAO; the owner says the key was compromised.

  • @opentensor

    Opentensor says SN64 (Chutes) trained the Parallax 8B model across consumer GPUs, and a new preview shows it handling 256 AI requests simultaneously on a single gaming GPU.

  • @JesusMartinez

    JesusMartinez says Google's new decision model uses Jev Bench, built and maintained by the SN92 developer team, which has also been referenced by Microsoft.

  • @CryptoZPunisher

    CryptoZPunisher reports a single wallet sold 22,536 TAO (about $4.95 million) across SN51 (Lium), SN64 (Chutes), SN4 (Targon), and SN120 (Affine), coinciding with the TAO share allocated to subnets falling from approximately 17.55% to 17.38%.

  • @taodaily_io

    TAO Daily says Gamma's launch lets users and AI agents access subnet services through a unified wallet-based payment system, aimed at interoperability across Bittensor.

  • @OfficialLoganK

    OfficialLoganK announces Gemini Decision 1, a new frontier decision model priced at $0.10 per 1M input tokens with a 256K context window and native image, audio, video, and PDF support.

◆2026-11-12 · End of this edition

Protocol

2 PRs

#3305

feat(btcli): protected-account UX on Substrate proxy pallet

What
Subtensor adds support for protected accounts in btcli, built on the existing proxy pallet, and makes a narrow runtime change so that during a coldkey swap dispute period a controller can remove its own proxy announcement while other actions on the account remain blocked.
Why
The change is meant to give coldkey holders a way to limit unauthorized actions on their account under duress, while still letting a legitimate controller clean up its own pending proxy announcement during a dispute.
Who it affects
This mainly affects TAO holders who use coldkey swap and proxy setups for account security; it does not change how validators or miners earn or allocate emissions.

#3328

Add gamma emission to the SDK and btcli

What
Subtensor adds gamma emission support to the SDK and btcli, wrapping on-chain extrinsics that set subnet emission weights (v2) and manage a whitelist for subnet gamma emission.
Why
The wrapping exposes existing sudo-controlled emission-weight and gamma-emission-whitelist extrinsics through SDK and CLI commands, with added pre-checks, so these settings can be managed without raw chain calls.
Who it affects
This is relevant to subnet owners and the team members who hold sudo access and manage subnet emission parameters; it does not directly change emission mechanics for ordinary TAO holders, validators, or miners.

Recent editions

Past editions +