Daily digest of the Bittensor ecosystem

中文/EN

Daily edition
Nov 7, 2026

Bittensor Daily A 1T1B product
1T1B ↗
BITTENSOR DAILY

24H Market

01/10

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

THE DAILY BRIEFING

Bittensor Daily — November 7, 2026

The day's two biggest ecosystem threads ran on X as much as Discord: Opentensor's formal rollout of post-quantum signatures drew the most substantive technical discussion #Rao has produced on the feature so far, and SN92's REAX 1.3 decision model drew sustained attention from the network's most-followed accounts. #General and #Rao otherwise stayed light, with a community-reported benchmarking exploit on SN55 and a security-audit disclosure on SN54 the main subnet news of the day.

Today's highlights

  1. Opentensor formally unveils quantum-resistant wallets, but a #Rao member details why real transactions still can't use them

    Bittensor unveils quantum-resistant wallets. As AI renews debate over cryptographic security, the update gives users post-quantum signatures and the option to replace signing keys automatically. On #Rao, a member went further than the announcement: imo the hardware wallet lag is the real bottleneck, coldkeys wont move until ledger or vault actually ships it and also root still has to flip hashed accounts on, so even native isnt live for real txns yet. (1) The same question asked in #General the same day got only a vaguer answer limited to the chain level, underlining that community expertise in #Rao, not official channels, is currently carrying the technical detail on this rollout. (2) This builds on Oct 30's #Rao thread, which could only offer an informal ETA guess for the same Release 487 feature. (3) The feature is live on-chain for native tooling, but hardware-wallet support and root-level activation of hashed accounts remain outstanding, per the unconfirmed community account.

  2. SN92's REAX 1.3 decision model tops a 270-entry Hugging Face leaderboard, drawing coordinated praise from Bittensor's top accounts

    Bittensor’s open competition just produced a world-leading AI decision model. REAX 1.3 has the highest score among 270+ entries on the Decision Index hosted on @huggingface, ahead of leading models from Perplexity and Fastino. It's official. Bittensor subnet Reax has the best-performing Jev model at the frontier. Best in the world. $TAO (1) Both Opentensor and a prominent independent account credited the same subnet result the same day, echoing the concentration of attention Trishool's HaloGuard result drew on Nov 4. (2) The model's training process was framed on X as evidence that anonymous, permissionless mining networks can out-compete centralized AI labs on this task. (3) No skeptical or dissenting reply to the claim appears in today's material.

  3. On SN55 (NIOME), a community member publishes a reproducible analysis of two benchmarking-pipeline exploits used by top-10 submissions

    (1) The reporter showed that invalid guideRNA sequences were being accepted by the validator and that the consistency_factor metric could be inflated by submissions tuned to the three seeds drawn each round rather than seed-independent designs, backing the claim with per-round score comparisons against additional, non-drawn seeds. (2) Separately, unverified claims about the owner's account led moderators to ban several accounts and restrict discussion of the topic. (3) The team agreed to add a guideRNA validation guard but maintained the consistency_factor is computed as specified, leaving the broader scoring-integrity question unresolved as the token moved 0.38% over 24 hours.

  4. SN54 (Yanez) touts a new contract and buyback allocation the same day an independent audit reports one critical and three high-severity findings in its validator code

    (1) The team confirmed a 20% revenue buyback allocation tied to the new contract and is separately adding biometric approval to Hashgraph Online's HOL Guard security layer. (2) The audit findings were reported directly to the team, which asked for details by email rather than addressing them publicly. (3) The subnet's token fell 7.31% over 24 hours, and the audit's substance was not disclosed or resolved in today's material.

  5. Other: Taostats sets a Monday deadline to migrate off its old API, and Gamma sits live on-chain but still switched off

    Reminder: The new taostats API is live. Same keys, same auth. It's faster, has a cleaner schema, plus a number of data accuracy improvements. The old endpoints will be turned off on MONDAY, so make sure to switch over before then. Last night gamma was pushed to the Bittensor chain. It is still off, and requires the root wallet to turn it on. (1) Both notices are administrative follow-ons to changes shipped earlier this week -- the Gamma credit mechanism merged in Release 488 and the taostats API overhaul -- rather than new design decisions. (2) #General and #Rao carried little else of ecosystem substance beyond routine moderation and a London meetup promotion.

Discord conversations worth following

#General

2 REPORTS

Notable

A member asks when quantum-resistant wallets reach mainnet, and the answer the channel can offer only narrows the question rather than giving a date

Opening ·

The day Opentensor publicly unveiled the wallets, a member asked Hey, when will be released to mainnet the TAO quantum resistant wallets which has been unveiled today? and got only I don't have any information on that sorry.

Clarification ·

A second member asked a more specific scope question, Hi I have a question, the new Quantum Resistance Wallets/ Signatures is only Bittensor Native CLI & Python SDK right and not updated by third part providers like Polkadot.js, Ledger, Polkadot Vault, Talisman and Crucible wallet?, and received I believe it is on a chain level yes not the wallet providers, to which the asker replied okay thank you.

3 things to read from it

  1. This repeats the pattern from Oct 30, when a member asking about the same Release 487 wallet rollout got only an informal guess rather than an official timeline -- today the launch date question goes unanswered again, even as the feature is now officially announced.
  2. The chain-level clarification is useful but tentative ('I believe'), and it leaves the harder compatibility question -- when third-party wallets like Ledger or Polkadot.js will support the new keys -- open.
  3. The same question drew a much more detailed answer in #Rao today, where a member explained that hardware wallets need their own scheme support before they can create or sign the new keys and that root still has to enable hashed accounts before native signing works for real transactions -- detail that never reached #General.

In the week’s context

  • Oct 30's #Rao thread on Release 487's wallet rollout also closed with an informal guess standing in for an official answer; today's #General exchange shows the same gap persisting after the feature's public unveiling.

Where it stands

Partially answered: the mainnet-timing question remains open, while the scope question got a tentative chain-level clarification that was not confirmed by an authoritative voice.

Other

Other: a subnet-number lookup, a newcomer's welcome and scam warning, an off-topic power-level question, and a London meetup invite filled the rest of a busier day

Mixed ·

A member asking What was the Jev sn # got the reply 92 i believe. A newcomer wrote Hey guys just got into the tao ecosystem. Got myself 1 tao for now 🙂 and was met with the channel's standing reminder that anyone sending you a direct message or friend request is a scammer, even if they look like a mod or admin. Another member asked an unrelated question, Hey guys, does anyone know what the maximum power level a character can have is?, and a London social was promoted with Hey guys, Happy Friday! Anyone in London that is a bittensor fanatic please feel welcome to come to the social, the more the merrier..

2 things to read from it

  1. Volume rose to 22 messages, the channel's busiest since Nov 3's 27, but as on that day the increase was mostly greetings, routing and standard moderation rather than ecosystem substance.
  2. The subnet-number lookup lands the same day #Rao and X both carried extensive coverage of SN92 (REAX)'s REAX 1.3 model, though the channel itself made no connection to that news.

Where it stands

All items closed through quick replies, redirect or the standing scam reminder; nothing substantive remains open.

#Rao

2 REPORTS

Notable

A member's question about third-party support for quantum-resistant wallets gets the most substantive answer the channel has offered on the rollout, including a warning that real transactions still are not live

Opening ·

A member repeated the question already circulating in #General the same day: Hi I have a question, the new Quantum Resistance Wallets/ Signatures is only Bittensor Native CLI & Python SDK right and not updated by third part providers like Polkadot.js, Ledger, Polkadot Vault, Talisman and Crucible wallet?

Clarification ·

A member confirmed the premise directly: yeah youre basically right, native cli and the python sdk with matching core are what can create and sign pq keys today

Expansion ·

The same member explained why other wallet providers are not yet compatible: polkadot.js ledger vault talisman etc need their own scheme support first or they just reject the keyfile

Pushback ·

They went further than confirming the question, flagging two practical blockers to the feature actually being usable: imo the hardware wallet lag is the real bottleneck, coldkeys wont move until ledger or vault actually ships it and also root still has to flip hashed accounts on, so even native isnt live for real txns yet

3 things to read from it

  1. This is the most detailed answer #Rao has produced on the quantum-resistant wallet rollout since Oct 30's ETA question drew only an informal guess of 'early next week' -- fittingly, today is also the day @opentensor formally unveiled the feature on X, describing ML-DSA-65, Falcon-512 and Falcon-1024 signature options and automatic key rotation.
  2. The answer goes beyond confirming native-tool-only support to flag that hardware wallets lag behind and that root itself has not yet enabled hashed accounts, meaning the feature is live on-chain but not yet usable for real transactions -- a caveat the official announcement did not spell out.
  3. The identical question was asked in #General the same day and received a vaguer answer limited to 'on a chain level... not the wallet providers,' underlining that #Rao's community expertise, not official channels, is currently carrying the technical detail on this rollout.

In the week’s context

  • Oct 30's #Rao thread asked for an ETA on ML-DSA wallets and got only an assumption of 'early next week' with no confirmation from an authoritative voice; today's exchange is the first time anyone in the channel has given a substantive, specific answer on the mechanism's current limits.

Where it stands

Answered in detail by a community member with no official confirmation; the claim that root still needs to enable hashed accounts before real transactions can use the new keys was not addressed by anyone else in the channel.

Other

Other: a one-line question about zero-APY assets drew a single two-word reply

Opening ·

A member asked Nothing has an APY of 0?, which another member answered with just RootReburn

What to read from it

  1. The exchange was too brief to establish what was being discussed or whether the answer satisfied the asker, and no further detail appears in the material.

Where it stands

Closed without elaboration; nothing further followed in the channel.

Subnets

2 REPORTS

SN55 24h +0.38%

NIOME

What happened
A community member published a detailed, reproducible analysis showing that top-10 submissions across several rounds exploited two issues in the v3 benchmarking pipeline: guideRNA sequences that were not valid DNA were accepted by the validator, and the consistency_factor metric could be inflated by submissions effectively tuned to the three benchmark seeds drawn each round rather than producing seed-independent designs. The reporter supplied per-round data comparing published scores to scores recomputed on additional, non-drawn seeds. Separately, a user made unverified claims about the owner's account, after which moderators banned several accounts and restricted discussion of the topic in the channel.
Community
Several miners pressed the team for a concrete timeline on fixing the seed-related scoring issue and noted that concerns about the seed range had been raised multiple times before; one member suggested extending the seed range to reduce the chance of miners benefiting from favorable seed draws. Others argued that achieving high scores on specific seeds without prior knowledge still reflects genuine skill rather than exploitation.
Official
The team agreed to add a guideRNA validation guard but maintained that the consistency_factor is computed correctly as specified, and said it would consider extending the seed range as part of ongoing improvements to the benchmarking system.

SN54 24h −7.31%

Yanez

What happened
SN54 (Yanez) publicized a new large business contract and confirmed that 20% of revenue from it is allocated to token buybacks. Separately, an independent auditor reported one critical and three high-severity structural findings in the subnet's validator code to the team. Yanez AI also announced it is adding biometric approval to Hashgraph Online's HOL Guard, an open-source security layer for AI coding agents, with a second pull request already integrated and a third in progress.
Community
Community members asked how the contract revenue, beyond the 20% buyback allocation, would be used, and were told to direct investment and revenue questions to X. A community member who reported the security findings had trouble reaching the team via Discord direct message and was redirected to email instead.
Official
The team confirmed the 20% buyback allocation from the new contract and asked that investment and revenue questions be raised on X. It also asked the auditor reporting the security findings to send details by email.

More subnet community coverage every day in the Telegram channel →

Ecosystem debate

4 participants

Quantum-resistant wallet: support scope and mainnet readiness

A quantum-resistant wallet/signature feature was unveiled, prompting questions from community members about which tools support it and when it can be used for live transactions. Discussion centered on the gap between native tooling and third-party wallet providers.

Positions

  • A community member asked whether the feature currently works only through Bittensor's native CLI and Python SDK, not third-party wallet providers.

    “the new Quantum Resistance Wallets/ Signatures is only Bittensor Native CLI & Python SDK right and not updated by third part providers”
  • A community member confirmed the change operates at the chain level rather than being implemented by individual wallet providers.

    “I believe it is on a chain level yes not the wallet providers”
  • A community member said third-party wallets need their own scheme support and that hardware wallet support is the main bottleneck, with even native tooling not yet live for real transactions pending a root-level switch.

    “the hardware wallet lag is the real bottleneck, coldkeys wont move until ledger or vault actually ships it”
Official response
There has been no official response from the team in the messages shown; a community member stated they had no information on a mainnet release date.
What to watch
Whether root enables hashed accounts and whether third-party wallet providers such as Ledger or Polkadot Vault add support for the new signature scheme.

Voices on X

  • @opentensor

    Bittensor announced quantum-resistant wallets, adding post-quantum signatures and an option to automatically replace signing keys.

  • @reaxlabs

    Reax Labs said its REAX 1.3 model, built on SN92, ranked first on the Hugging Face Decision Index with a Full score of 74.0.

  • @opentensor

    Opentensor said REAX 1.3 scored highest among 270+ entries on the Hugging Face Decision Index, ahead of models from Perplexity and Fastino.

  • @byteleap_ai

    Byteleap AI reported runtime 488 is live on mainnet from block 9,442,681, introducing Gamma, a mechanism to burn subnet alpha for dollar-valued service credits pending activation steps.

  • @trishoolai

    Trishool said SN23 (Trishool) and SN92 (REAX) are partnering so REAX's decision models, run on EU data centers, power Trishool's EU Mode security product.

  • @chutes_ai

    SN64 (Chutes) said it is a launch partner for Tencent's Hy4 model, priced at $0.525 per million input tokens and $1.5625 per million output tokens.

  • @taostats

    Taostats said Gamma was pushed to the Bittensor chain but remains off until the root wallet activates it, and pointed subnet owners to Taostats Actions.

  • @oroagents

    Oro Agents said 8 of 9 tested models performed worse than its fixed-buying rule for wholesaler demand forecasting.

◆2026-11-07 · End of this edition

Protocol

1 PR

#3310

Build macOS core wheels on macos-15

What
The CI pipeline that builds and publishes macOS wheels for the Subtensor SDK was switched from the retired macOS 14 runner to macOS 15.
Why
GitHub removed the macOS 14 hosted runners, which was causing the macOS build jobs to fail and blocking publication of SDK packages to PyPI.
Who it affects
This is an infrastructure fix affecting only developers who install the SDK via PyPI; it restores the stalled PyPI release for spec 488 but has no direct effect on TAO holders, validators, or miners.

Recent editions

Past editions +