Bittensor Toolkit →Find the right tool for your question.

Bittensor Daily News

From the archive
#01 · SN116 · Carbonverified
★★★★★

SN116 Carbon announces mainnet with a motor-design challenge

Carbon announced its mainnet launch on November 14 and identified a motor challenge as the first live task. The project focuses on physics AI: models that help engineers predict how physical systems behave, alongside evidence about when those predictions can be trusted. The motor problem targets smoother torque while retaining the turning force a design needs. Carbon describes miners researching model-building methods and validators rebuilding and evaluating candidates against challenge requirements. That offers a concrete starting point for its broader engineering roadmap. Its website lists eight proposed challenges spanning cooling, batteries, optical links, motors, robotics, acoustics and fluid mixing. The wider portfolio remains a roadmap, and its dollar-value examples are hypothetical customer scenarios, not Carbon revenue or measured results. The launch is a direct team announcement; this review did not independently run the motor evaluation or establish commercial customers.

Why 4 stars: Four stars: a substantive subnet mainnet launch with a concrete first engineering task is more consequential than a routine competition update. Five is not established because the announced scope does not yet demonstrate an exceptional network-wide deployment milestone.

#02 · SN24 · ms.computerverified
★★★★★

SN24 ms.computer records an owner-address change after a coldkey swap

Finalized November 14 records show a coldkey swap followed about 26 minutes later by a separate SubnetOwnerChanged event on SN24. The latter changed the owner address from 5Csm…evdw to 5DkB…XZXe. The subnet remained named ms.computer and retained its existing registration block. These are two distinct chain events, not proof of two negotiated sales. They establish a change to the address controlling the subnet, but do not by themselves identify a new beneficial owner or operating team. The cause and any implications for the planned product launch remain under review; no compromise or completed product launch is inferred.

Why 4 stars: Four stars: a finalized change to subnet control following a key migration has material consequences for tracking SN24 ownership. Three understates that control change; five is not supported by established broader impact or an independently confirmed incident.

#03 · SN47 · Unknownverified
★★★★★

SN47 is re-registered after the former GF registration is removed

SN47 was removed and then re-registered on November 13. Before removal, its on-chain name changed from GF to FG. The new registration was activated at block 9,499,920, with a different owner address and no registered project identity at the reviewed boundary. The registration queue recorded a lock amount of 85.943566688 TAO. That is the recorded registration amount, not evidence of a negotiated purchase price for the former business. The new team, project name and operating plans have not been established. Old and new registrations must not share a continuous price-return calculation. The site is applying the verified registration boundary so the prior project’s history is not presented as a gain made by the new registration.

Why 4 stars: Four stars: replacing an active subnet registration is a major lifecycle change affecting identity and market-history interpretation. Three understates this reset; five lacks evidence of exceptional ecosystem impact.

#04 · SN51 · lium.ioverified
★★★★★

SN51 Lium records more than 43,244 Gamma credits spent

Two finalized November 13 events consumed 21.543754649 and 43,223.230117033 Gamma on Lium, a combined 43,244.773871682 credits. Both used the same deposit-owning address and the spender listed in Lium’s registered service. These are additional events after the previous report’s cutoff. Lium describes Gamma as a way to add account balance for GPU pods billed by the second. The chain proves that credits were consumed; it does not establish that this amount is recognized revenue, that all corresponding GPU work was delivered, or that the two events represent two customers. Those distinctions matter when comparing a large payment-credit movement with commercial adoption.

Why 4 stars: Four stars: a substantial step up in recorded service-credit consumption through the registered integration warrants major tracking coverage. Three understates the scale of the verified change; five is not supported by verified customer reach or delivered-work impact.

#05 · SN28 · SayGMdeveloping
★★★★★

SN28 SayGM introduces optional guardrails before requests reach providers

SayGM announced request guardrails on November 13 for detecting secrets, personal information and blocked words before a request leaves its gateway. The team says the checks run inside its enclave and can be configured per API key. They are optional and off by default. This gives API users a new control over what they submit upstream. It is an announced product feature, not a guarantee that every sensitive value will be detected; this review has not independently tested detection coverage or bypass resistance.

Why 3 stars: Three stars: a useful, bounded gateway feature for existing users. Four would require evidence of a more consequential service change beyond optional request filtering.

#06 · SN103 · Terza Inferenceverified
★★★★★

SN103 Terza records a 97-Gamma spend through its registered spender

A finalized November 14 event consumed 97.048535340 Gamma on Terza. The authorized spender matches the entry in the service registry at the review cutoff. Terza describes its service as inference. This verifies payment-credit activity associated with the listed spender, not a count of completed inference requests or independently verified customer revenue.

Why 3 stars: Three stars: meaningful verified activity through a registered service spender. Four is not supported by the event alone without greater demonstrated operational consequences.

#07 · SN80 · OpenRobotoverified
★★★★★

SN80 OpenRoboto records another 125 Gamma spent without a registered service

Five finalized events across November 13 and 14 consumed 25 Gamma each on OpenRoboto, adding 125 Gamma after the previous report’s cutoff. No service was registered at the reviewed snapshot. In each event, the deposit-owning address was also the authorized spender. The activity is real on-chain credit consumption. It does not establish independent customer purchases, delivered robotics work or a newly launched commercial service.

Why 3 stars: Three stars: additional measurable Gamma activity is useful to track, but the absent service listing and unknown purpose do not establish four-star commercial adoption.

Stars indicate editorial priority, not investment quality. Routine competition updates receive at most three stars. Shizzy videos receive three; substantive non-video Shizzy coverage receives at least four. Scheduled events remain plans.

Sources & coverage notes
04

Audit trail

Coverage notes

Carbon announces mainnet on SN116 with its first motor challenge. SN24 records an owner-address change, SN47 is re-registered, and Lium records more than 43,244 Gamma spent. SayGM introduces optional request guardrails.

Coverage: Nov 13, 2026, 11:31 AM – Nov 14, 2026, 10:58 AM ET

Searched

  • Primary websites for all 128 subnet roster entries, bounded direct reviews of the required ecosystem accounts, owner discovery sources and submitted Grok queries.
  • Contiguous finalized lifecycle, eTAO, transaction-burn and Gamma event review through November 14 at 10:58 AM Eastern; owner balances refreshed at one finalized block.

Public-data gaps

  • Full seven-day social, media and Discord coverage remains incomplete. Selected verified developments are published without claiming exhaustive coverage.
  • Several large market moves lack a verified cause. Team-channel and registration follow-ups remain open.
  • The broader site audit is incomplete; news publication does not certify every site function.
Browse all 100 editions

Conference news · September 30, 2026

Exploit Conference Catch Up · Day 1

The teams, the ideas and the practical takeaways from Exploit Summit’s first day in Montreal. From Gamma and phone-based AI to robotics, science and the business of running a subnet.

Catch up on Day 1

Conference news · October 1, 2026

Exploit Conference Catch Up · Day 2

Catch up on Exploit Summit’s second day: Carbon’s Pitchtensor win, SN107 Minos’ research app, agent controls, robotics data, inference partnerships and the decisions behind building a subnet business.

Catch up on Day 2