Bittensor Developers Release Runtime 475 Update
The new update introduces an optional Null Consensus mode to increase subnet capacity for participants.
Updated on Oct. 19, 2026 in Remote Work
Live Poll
Do you trust protocols that concentrate scoring authority to increase network capacity?
Bittensor developers have released Runtime 475, which introduces an optional Null Consensus mode for the network. This update allows subnet capacity to expand significantly, supporting up to 2,500 identifiers compared to the previous limit.
Why it matters
The change is designed to provide room for more registered participants within subnets. By enabling this mode, subnet owners can accommodate larger participant populations that exceed standard network limits.
The Null Consensus mode supports 2,500 total identifiers, a major increase from the 256-identifier capacity limit of Yuma consensus. Pruning processes are now restricted to removing a maximum of 64 identifiers per transaction.
The players
Bittensor
Bittensor is a decentralized machine learning protocol that allows users to train and trade artificial intelligence models across a global network.
The details
Subnet owners can now manually select the Null mode to increase their capacity, while also utilizing proof-of-work registration to bypass traditional registration burn fees. Switching back to Yuma consensus requires reducing the registered population to the 256-identifier limit.
Timeline
Runtime 475 was officially released on October 7, 2026.
Market Landscape
The introduction of Null Consensus marks a shift in how Bittensor handles network growth by moving beyond the constraints of the legacy Yuma consensus mechanism. This update positions the protocol to scale its infrastructure to accommodate larger participant counts.
Subnet owners can now increase participant capacity to 2,500, potentially allowing for more contributors within their specific networks. Users should note that switching back to Yuma consensus requires a reduction in registered population to 256.
The takeaway
This update offers subnet owners greater flexibility in managing participation through higher capacity limits. Participants should monitor their subnet settings to ensure compatibility with the new consensus modes.
Further reading
Learn more about the evolving nature of decentralized protocols in the Remote Work section.
Source note: This article includes information reported by TokenPost.
Live Poll
Do you trust protocols that concentrate scoring authority to increase network capacity?
