THE DAILY BRIEFING
Bittensor Daily — November 16, 2026
#Rao carried almost all of today's substance: the custody conversation that began Nov 14 around SN3 (Teutonic)'s coldkey compromise extended into concrete personal practices and a sharp disagreement over sharing them in public, while a parallel thread weighed whether a proposed shorting/lending feature is worth the added attack surface. #General stayed at its thinnest point of the week, and the subnet cards carried the day's other concrete news -- Carbon clearing a grading backlog and ms.computer shipping its first release. No new tokenomics or governance resolution emerged beyond echoes of last week's unresolved owner-accountability debate.
01HIGHLIGHTS
Today's highlights
A #Rao member details their own wallet-security setup in public and is told it contradicts the paranoia they claim to practice.
Spend limits + manual hardware confirmation is what saves ya, I’ve never had any crypto stolen
and chutes even our like team payment wallet is a 3/5 multisig that’s not even owner wallet. Pita but better than getting robbed
drew the challenge Why are you sharing this in public? Doesn’t match “insanely security paranoid”. Better delete all this.
, answered with Because my main wallet has $11 in it
and They can come for me 🤣
. (1) This continues Nov 14's airgap debate into a second day, moving from abstract device design to concrete operational practice -- spend limits, multisig payment wallets, periodic machine wipes. (2) It produced the week's first visible friction over disclosure itself, rather than over the underlying security question. (3) The exchange closed without consensus or any official guidance, and the SN3 (Teutonic) compromise from Nov 11 was referenced only obliquely.
A #Rao member warns a proposed shorting/lending feature risks a Kava-style drain, prompting a converging counter-proposal of capped rollout plus a staged bug bounty.
let Kava drained pools be (another) warning on how dangerous is to expose a lending protocol at the blockchain level. Just one bug may be needed for total catastrophe
and do not implement this. at least not until AI tools have enough training to understand all corner cases
drew the reply id rather see it off by default and enabled per subnet with small caps first
, met with offer a 100 000 usd bounty for example if someone can drain the pool in test net and slowly raise it up to 1 000 000
. (1) This is a substantive risk debate over a protocol feature still in development, with design detail -- capped rollout, staged bounties -- not seen in prior #Rao security exchanges. (2) It frames protocol-level attack surface as the same underlying worry as the day's parallel personal-custody thread. (3) The two participants ended closer together on id still keep the caps tho, testnet bounty plus capped rollout beats either one alone
, with no team voice weighing in.
A #Rao member argues decentralized governance structurally misaligns investors and subnet owners, echoing Nov 11's unresolved staker-accountability debate.
There’s a problem with alignment between investors and sn owners. A stock is much better aligned
and If we add a layer of disagreement on top of everything rn in development it would be really bad
. (1) This raises the same investor-owner alignment gap Nov 11's fifteen-hour #Rao thread debated between a staker board of directors and a code-enforced alternative, but from a governance-structure angle rather than a proposed oversight mechanism. (2) Unlike that thread, today's comment drew no reply or counter-proposal in the channel. (3) The concern was left standing unanswered at day's end.
SN116 (Carbon) removes the crown-recheck step that had slowed its Motor mainnet lane to roughly one verdict per 45 minutes.
(1) The team attributed the slowdown to crown rechecks rebuilding models on the grading machine for about two hours each and removed the step so the lane now only grades, following Nov 14's backlog that cancelled roughly 75 queued submissions. (2) It also introduced a one-waiting-submission-per-coldkey limit rolling out in stages and a king-promotion rule requiring a grade margin above 0.0129. (3) A re-registered miner hotkey was refused submission with a direct_provider_registration_unavailable error, and a roughly 9 KiB graph-size limit was flagged as a gap the team acknowledged; the subnet's token rose 1.89% over 24 hours.
Other: #General held its thinnest day of the week, ms.computer shipped its first release as its token fell 17.91%, and taodaily_io's Gamma weekly tally showed Lium minting nearly all of the week's $43,902 in service credits.
You can ask your questions or use the <#1230665820859007039> channel.
(1) #General logged 13 messages, its lowest point on the week's trend, with an unanswered sell-limit-order complaint and routine moderator and EVM-channel redirects filling the day. (2) SN24 (ms.computer) released HOST and RUN features and opened mining to anyone, with CONNECT planned next, even as its token fell 17.91%. (3) @taodaily_io reported SN51 (Lium) accounted for $43,267.36 of the week's $43,902 in Gamma service credits minted Nov 8-14.
Securing subnet owner and operator wallets
Following past wallet compromises in the ecosystem, community members discussed how subnet owners and operators should protect their keys, covering device separation, multisig setups, hardware wallets and spend limits. A team member from SN64 (Chutes) noted that the team's own payment wallet uses a multisig arrangement, though this is separate from subnet owner keys. No subnet-wide standard for key security was referenced in the discussion.
Positions
-
Some participants argue that layered setups with separate signing devices are necessary because a single compromised device can eventually lead to full key exposure regardless of scheme complexity.
“if devices are already compromised it just a matter of time before escalation, so its really important to have separate devices to sign”
-
Others favor an assume-breach mindset, treating any device as potentially compromised through malware, bad downloads or shared files from contacts.
“I’d just assume for security posture that your stuff is going to get compromised, maybe you download malware”
-
A practical safeguard favored by some is combining spend limits with manual hardware confirmation, which one operator said has prevented any crypto theft for them.
“Spend limits + manual hardware confirmation is what saves ya, I’ve never had any crypto stolen”
- Official response
- There has been no official response from Opentensor or any subnet team on standardizing wallet security practices for subnet owners or operators.
- What to watch
- Whether subnet owners adopt formal practices such as multisig or spend limits voluntarily, or whether further wallet compromises prompt a broader push for standardized security requirements.
04VOICES ON X
Voices on X
-
@opentensor
Opentensor's weekly ecosystem recap highlights Lium's nearly $35M annualized GPU rental run rate alongside updates from Hippius, Almanac, Beam, Score and OpenRoboto.
View the original post on X ↗
-
@taodaily_io
TAO Daily reports that SN105 (Beam) went live with a Chainlink CRE integration, letting b1m_ai record data transfer reports as attested receipts on Base mainnet.
View the original post on X ↗
-
@2xnmore
A community member describes SN44 (Score) as an open computer-vision competition whose winning models power Manako, a camera-based system monitoring 124 fuel stations in France.
View the original post on X ↗
-
@TatsuEcosystem
TatsuEcosystem's weekly brief announces TatsuOS is live, letting users buy plans and AI credits with a listed token, USDC or USDT, credited automatically on-chain.
View the original post on X ↗
-
@CryptoZPunisher
A community member discusses SN24 (Ms. Computer), noting its November 15, 2026 launch announcement aligns with prior speculation about the project's direction.
View the original post on X ↗
-
@chainlink
Chainlink's adoption update lists 10 recent integrations across 5 services and 7 chains, including users such as b1m_ai among others.
View the original post on X ↗
-
@taodaily_io
TAO Daily's Gamma weekly report shows $43,902 in service credits minted by burning subnet alpha from Nov 8-14, led by SN51 (Lium) at $43,267.36.
View the original post on X ↗
-
@KakashiTao
A community member welcomes SN24 (Ms. Computer) as the third new subnet launched this year, alongside SN28 and SN53, expressing bullishness.
View the original post on X ↗
◆2026-11-16 · End of this edition
05RECENT EDITIONS
Recent editions
Past editions +