Daily digest of the Bittensor ecosystem

中文/EN

Daily edition
Nov 19, 2026

Bittensor Daily A 1T1B product
1T1B ↗
BITTENSOR DAILY

24H Market

01/10

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

THE DAILY BRIEFING

Bittensor Daily — November 19, 2026

Today's ecosystem channels were the quietest of the week, with #General down to 11 messages and #Rao to 7, leaving the day's substance to run through a protocol release and the subnet cards. Release v492 reworks how liquidity and locked funds move during coldkey swaps, the kind of safeguard the Nov 14-15 #Rao custody debate pointed toward after SN3 (Teutonic)'s owner-key compromise, while SN51 (Lium) reported its largest weekly buyback figure yet and SN116 (Carbon) and SN99 (Axonry) each carried less settled news.

Today's highlights

  1. Release v492 reworks coldkey-swap liquidity handling and reserves top transaction priority for the sudo key.

    (1) The release bundles a runtime upgrade reworking how liquidity is handled during coldkey swaps and how locked funds are migrated -- a protocol-level response to the custody risk #Rao's airgap and spend-limit debate raised at length on Nov 14-15 following SN3 (Teutonic)'s owner-key compromise. (2) Companion fixes stop a coldkey swap from overwriting a destination address that already holds state, and close a phantom-lock-conviction bug tied to subnet dissolution. (3) Transaction priority is now reserved for the sudo key, so validators and miners whose transactions previously carried elevated priority move to normal priority; ordinary TAO holders are unaffected unless they perform a coldkey swap.

  2. SN51 (Lium) reports roughly $3.3 million in buybacks and burns over the past week, entirely from usage revenue, with about 500 B300 GPUs nearly fully rented.

    (1) This extends the growth Lium reported on Nov 12 -- new paying customers up 78%, deposits up 94% -- into a concrete capital-return figure, and follows SubnetRadar data again placing the subnet first by TAO emissions. (2) The subnet also logged a record single-day spend of roughly $129k and an 82,159-alpha burn, alongside $79K in SN8 alpha buybacks from Vanta Trading. (3) A member's proposal to collaborate with the Peryn project was directed to a formal written-proposal process rather than a public commitment. The token rose 4.7% over 24 hours.

  3. SN99 (Axonry) opens mining Nov 19 as its token falls 29.77% over 24 hours and its min_burn hyperparameter is raised nearly threefold.

    (1) The subnet set mining to open Nov 19 at 06:00 UTC, with 50% of miner emission awarded to a champion model selected through weight-space programming edits. (2) Ahead of launch the team raised min_burn from 180,000,000 to 500,000,000, a steep increase to the cost of entry landing the same day the token fell sharply. (3) The team said miners can prepare and commit files locally before the on-chain window opens, with the initial model serving as the first champion to test the pipeline.

  4. SN116 (Carbon) suffers renewed grading outages, including an unreachable submission endpoint, despite a reported 3x throughput improvement.

    (1) This continues the backlog first flagged Nov 14 and partly addressed Nov 16 with parallel grading; today's outages included the submission endpoint going unreachable and a code rollback that briefly closed intake before it reopened. (2) The team said it is now achieving roughly 50 grades per hour after separating the build and grading pipelines so they no longer compete for the same machines, and that failures caused by its own restarts or outages are never charged to miners. (3) Submissions affected by daily allowance limits or side-infrastructure issues were queued for a free re-run. The token fell 2.15% over 24 hours.

  5. Both #General and #Rao log their quietest day of the week, with no new tokenomics or governance debate.

    One member reflected on the channel's drift, writing i remember when this place was an actual forum, now its super corporate and feels like im in a HR slack channel, while in #Rao an unanswered claim that validators use metrics to check if subnets follow contract of 50% revenue-share! if a subnet break contract, validators freeze alpha + tao emission drew no reply, and a role celebration gave way to don't ping me in public. (1) #General fell to 11 messages, its lowest point of the week after Nov 17's spike to 34, and #Rao fell to 7 messages from 50 on Nov 16. (2) The revenue-share enforcement claim continues Nov 16's circular-demand debate but stands unverified, with no subnet named and no official confirmation. (3) Routine moderation, the standing scam warning, and a London meetup notice filled out the rest of both channels.

Discord conversations worth following

#General

1 REPORT

Other

Other: a quiet day of channel housekeeping, a scam-imposter reminder, a nostalgic complaint about the channel's tone, and a London meetup notice.

Opening ·

A member asked about an unclaimed channel and was told well <#1498317068238327928> is still unclaimed but you should be able to see it. Separately, a member whose account had been compromised asked Could someone please direct me to the right moderator to appeal my ban and get my account unbanned? and was pointed to another user for help.

Moderation ·

A moderator declined a DM request, saying I'm over-capacity and am not able to provide personal, one-on-one support via DM, then repeated the standing warning that If you get a DM or FR from an account claiming to be me, it's a scam before posting the full scam checklist, including that The "Subtensor Wallet" and "Dsperse Wallet" are both SCAMS.

Aside ·

One member reflected on the channel's shift in character, writing i remember when this place was an actual forum, now its super corporate and feels like im in a HR slack channel.

Closing ·

The day closed with a song-share compliment asking Please share the full version with us!, a greeting (Good day everyone! Happy Thursday 🫡), and a reminder for a London social event: Reminder, if your in London tomorrow, swing by for the TAO social!.

3 things to read from it

  1. Volume fell to 11 messages, the channel's lowest point in the trend after Nov 17's spike to 34, and nothing today touched tokenomics, governance, or protocol mechanics.
  2. The complaint that the channel now 'feels like im in a HR slack channel' is a rare bit of commentary on the channel's own culture rather than on the ecosystem, and it drew no reply.
  3. The moderator's repeated scam checklist continues the same standing warning seen through the week, with no new imposter pattern reported today.

Where it stands

Closed; all items resolved through routine redirect, the standing scam warning, or no further reply.

#Rao

2 REPORTS

Other

A member claims validators enforce a 50% revenue-share contract on subnets by freezing emissions, continuing from Nov 16's circular-demand debate without drawing a reply.

Claim ·

Replying to the tail end of Nov 16's argument over whether reported TAO demand is real or recycled, a member asserted validators use metrics to check if subnets follow contract of 50% revenue-share! if a subnet break contract, validators freeze alpha + tao emission.

3 things to read from it

  1. This picks up directly where Nov 16's #Rao thread left off, where one participant shifted toward prioritizing inflation control over cheap registration -- today's comment frames that same debate in terms of an enforcement mechanism rather than pricing policy.
  2. The claim describes validator behavior in general terms without naming a subnet, consistent with the publication's own limits on repeating unverified claims about specific projects.
  3. No one in the channel challenged or confirmed the claim, and no official voice weighed in, leaving it as an unverified assertion rather than a resolved mechanism detail.

In the week’s context

  • Nov 16's #Rao thread debated whether most reported TAO demand is real capital or emission recycling between subnets, ending with one participant shifting toward favoring inflation control.

Where it stands

Unanswered; the claim stands alone in the channel with no reply or confirmation.

Other

Other: a member's role approval drew a brief celebratory reaction, followed by an etiquette dispute over public pinging that closed out the channel's quietest day of the week.

Reaction ·

A member noted he got the role btw 🥹 in reference to an earlier message, before another asked a third party directly what they were doing, prompting the retort don't ping me in public, with a wordless reaction from a fourth member closing the exchange.

What to read from it

  1. Channel volume fell to 7 messages today from 12 on Nov 17 and 50 on Nov 16, the lowest point of the week, with this social exchange making up most of the day's remaining content.

Where it stands

Closed; the exchange ended on the etiquette complaint with no further reply.

Subnets

5 REPORTS

SN51 24h +4.70%

lium.io

What happened
SN51 (Lium) reported total buybacks and burns of approximately $3.3 million over the past week, entirely from usage revenue, alongside a record ~$129k single-day spend and roughly 500 B300 GPUs nearly fully rented. The subnet also recorded a burn of 82,159 Alpha tokens and $79K in SN8 alpha buybacks from Vanta Trading last week. SubnetRadar data showed SN51 (Lium) leading Bittensor subnets by TAO emissions at 16.6%, ahead of SN64 (Chutes) at 8.69% and SN4 (Targon) at 7.69%. A community member proposed a possible collaboration between Lium's GPU network and the Peryn project.
Community
Members repeatedly questioned why the subnet owner's wallet was selling and transferring tokens, with some arguing this could hurt smaller holders if done too quickly. Others pointed to the buyback-and-burn totals and limited unlocked balance on the owner coldkey as reassurance. Several members also asked for a public dashboard or tracker to monitor burns and revenue.
Official
The team invited a formal written proposal for the Peryn collaboration via support email, to be reviewed by its partnerships team. It also confirmed that no public dashboard exists yet and logged the burn/revenue tracker request as a feature request.

In debate · Reactions to the SN51 owner wallet's repeated selling · 21 participants

  • Some members argued the owner should sell more slowly so other holders are not disadvantaged by a single large sale.

    “It's better if he sell slowly to let other exit as well, cause others will loose if he dumps in one go”
  • Others defended the sales as a normal part of funding the buyback-and-burn strategy rather than a problem.

    “because it's better for the subnet to do buybacks + burns”
  • A member noted that retail holders can react nervously to visible owner-wallet selling, especially given the subnet's prior hack, even though the owner's unlocked balance appears limited.

    “To be honest, it’s easy for ordinary retail investors to panic when they see the owner’s wallet continuously selling, especially given that the subnet has been hacked before.”

SN99 24h −29.77%

Axonry

What happened
Axonry announced that mining opens on SN99 (Axonry) on November 19 at 06:00 UTC, with 50% of miner emission awarded to a champion model via weight-space programming edits. The subnet also changed its min_burn hyperparameter from 180,000,000 to 500,000,000. The team opened a live view of its experiment process on its website and said on-chain submissions open at Finney block 9,538,688.
Community
A miner asked why the mining repos were already public 17 hours before mining opened and whether further changes would follow before launch. A community member suggested rewarding the top 3 to 5 miners instead of a winner-take-all model, and another raised concerns about potential spam issues, comparing it to another subnet.
Official
The team said miners can prepare and commit files locally ahead of the on-chain opening, and that the initial model (uid 0) will serve as the first champion to test the full pipeline before results are published.

SN61 24h −6.64%

RedTeam

What happened
On SN61 (RedTeam), a registration-fee war led to UID 201 being deregistered after a competing registration under UID 30 replaced it, prompting hours of discussion in the subnet channel. The team separately clarified that a submission under UID 228 would not be scored because the UID no longer matched its hotkey following a hotkey change. The team also said a new challenge is expected to be released this week or early next week after recent changes.
Community
Community members debated at length whether the deregistration of UID 201 was fair, with some arguing the subnet's design disadvantages miners whose solutions had already been accepted, while others treated it as a known outcome of the reg-fee mechanism.
Official
The team said the deregistration followed immunity and cooldown rules applied equally to all miners, placing responsibility on the UID 201 owner for submitting during that window. It also confirmed the UID 228 submission would not be scored due to a hotkey mismatch and said a new challenge is coming soon.

In debate · Fairness of the UID 201 deregistration · 22 participants

  • Some community members argued the outcome was unfair to miners whose accepted solutions lost emission.

    “this subnet is too unfair. even the solution is accepted and miners contributed enough, they cannot get weight, get emission.”
  • The team maintained the rules applied equally and that the UID 201 owner knowingly took the risk by submitting during that window.

    “The recent case is the fault of 201 itself; he/she knew this may happen but still submitted”
  • Another community member suggested reissuing UID 201 as a fairer resolution for all miners.

    “What about to give new uid 201. That is more fair to all miners”

SN105 24h −3.85%

Beam

What happened
Miners on SN105 (Beam) accused the team of favoring a single operator through open direct-transfer rooms while storage-room transfers were closed, raising concerns about fairness in point allocation. The team responded that direct rooms are open to all miners and that participants are selected by score rather than by the room's publisher, and said closing storage rooms ended a situation where one operator had been taking the large majority of room slots. The team later announced that room transfers are now split into chunk ranges distributed across multiple orchestrators based on score, live since November 18. Separately, the team announced Beam Studio is now one-click deployable on AWS, letting teams self-host in their own VPC with encrypted storage.
Community
Miners debated at length whether direct-transfer rooms amounted to unfair treatment of a single operator, with one miner repeatedly pressing the point and others mocking the exchange. One miner announced they were stepping away from mining on the subnet, citing drama and negativity; others reacted positively to the later transfer-distribution update.
Official
The team said direct-transfer room participants are chosen by score rather than by the room's publisher, and that the same rules now apply to all miners. It announced that room transfers are split into chunk ranges across orchestrators as of November 18, and that Beam Studio can now be deployed in one click on AWS with encrypted, self-hosted storage.

SN116 24h −2.15%

Carbon

What happened
SN116 (Carbon) experienced repeated outages and stalls in its Motor 1.8 grading and submission intake system throughout the period, prompting several rollbacks and emergency fixes from the team. The submission endpoint ('the door') went unreachable at multiple points, including one incident starting around 13:00 UTC on Nov 18, and a code rollback temporarily closed intake before it was reopened. The team said submissions that failed due to daily allowance limits or side-infrastructure issues were not charged, with some queued for a free re-run.
Community
Several miners asked repeatedly whether the dashboard and leaderboard were updating and sought clarification on wait times for queued submissions. Others asked the team to confirm moderator and validator roles within the Discord channel.
Official
The team reported grading throughput of about 50 grades per hour, roughly a 3x speedup, after separating the build and grading pipelines so they no longer compete for the same machines. It also said failures caused by its own restarts or outages are never charged to miners.

More subnet community coverage every day in the Telegram channel →

Voices on X

  • @taodaily_io

    @taodaily_io reports SN91 (Cascade) surpassed Salesforce's Moirai 2.0, trained on 295 billion data points, just 19 days into its training competition, and reached 86.2% parity with Mistral's Timestral.

  • @cascade_sn91

    SN91 (Cascade) says its MoE model scored 0.511 on the GIFT-EVAL CRPS benchmark, a 0.005 improvement over Moirai2, and reached 86.2% parity with Mistral's Timestral on MASE after 19 days.

  • @oroagents

    @oroagents says that in a 90-day test, only 3 of 16 AI models used for produce wholesaler purchasing outperformed a simple reorder formula.

  • @gordonfrayne

    @gordonfrayne announced the launch of Optia, SN47 (Optia), described as an AI visibility platform helping businesses get ranked and recommended by AI engines.

  • @conjectures_io

    @conjectures_io says its miners proved, and verified in Lean, a bound for Problem 18(b) stronger than Erdős considered reachable 52 years ago.

  • @JesusMartinez

    @JesusMartinez argues that when emissions are paused, as happened with SN110 (Green Compute), there should be a publicly displayed on-chain reason, saying the lack of one leaves holders uninformed.

  • @taodaily_io

    @taodaily_io, citing SubnetRadar, listed the top 10 subnets by TAO emissions, led by SN51 (Lium) at 16.6% and SN64 (Chutes) at 8.69%.

  • @b1m_ai

    @b1m_ai announced Beam Studio is now one-click deployable on AWS, which the post says holds about 28% of a $558B cloud market, letting enterprises self-host within their own AWS account.

◆2026-11-19 · End of this edition

Protocol

7 PRs

#3333 Breaking change

Release v492

What
This release bundles a runtime upgrade to version 492, reworking how liquidity is handled during coldkey swaps and how locked funds are migrated, and restricts top transaction priority to the sudo key.
Why
The changes consolidate several swap-related fixes into one coordinated upgrade and tighten control over which transactions can claim the network's highest priority.
Who it affects
Ordinary TAO holders using coldkey swaps may see different behavior around liquidity and locked balances; validators and miners are affected only indirectly through the transaction priority restriction described in PR 3341.

#3334 Breaking change

fix: protect used coldkey swap destinations

What
The update prevents a coldkey swap from overwriting a destination address that already has existing on-chain state.
Why
Without this check, a swap could unintentionally erase or corrupt data tied to an address that was already in use on the chain.
Who it affects
TAO holders performing coldkey swaps are protected from accidentally destroying existing account state; validators and miners are not directly affected.

#3336

Fix phantom lock conviction from coldkey swaps during dissolution

What
The fix stops a coldkey swap carried out during subnet dissolution from recreating a lock conviction that should no longer exist.
Why
The dissolution process could leave behind an inconsistent lock record if a coldkey swap happened at the same time, misrepresenting a holder's locked balance.
Who it affects
TAO holders with locked balances in a dissolving subnet get an accurate lock status; validators and miners are not directly affected.

#3341

Reserve Operational transaction priority for the sudo key

What
The network now reserves the highest transaction priority level for transactions signed by the sudo key; all other transactions, including ones that were previously classified as high priority, receive normal priority instead.
Why
This prevents any account other than sudo from being able to claim top-of-queue priority for its transactions.
Who it affects
Validators and miners whose transactions previously relied on elevated priority will now be processed at normal priority; ordinary TAO holders are not directly affected.

#3335

Fix phantom hotkey membership after full swap

What
The fix removes a false subnet membership record that could appear after a full hotkey swap, and corrects cases where a historical 'not registered' entry was wrongly read as an active registration during subnet-scoped swaps.
Why
These false records misrepresented a hotkey's actual registration status on a subnet.
Who it affects
Miners and validators who perform hotkey swaps get accurate subnet membership status; ordinary TAO holders are not directly affected.

#3338

Require the current coldkey to extend its lineage

What
Only the currently active coldkey in a lineage chain can now extend that lineage; calls from earlier, superseded coldkeys are silently ignored.
Why
This prevents a past coldkey from altering the lineage record after it has been replaced, which could otherwise break the chain's continuity.
Who it affects
TAO holders who have swapped coldkeys multiple times are protected from lineage tampering; validators and miners are not directly affected.

#3339

Preserve lock admission for already-paid V2 coldkey swaps

What
The update preserves the lock admission behavior for V2 coldkey swaps that have already been paid for, adding a tracking flag and a new preference option to manage this case.
Why
Without this change, an already-paid swap could lose its intended lock admission treatment when executed.
Who it affects
TAO holders who initiated a paid V2 coldkey swap retain the lock terms they paid for; validators and miners are not directly affected.

Recent editions

Past editions +