Bittensor Adds Optional Mode That Raises Subnet Capacity to 2,500

Photo: TokenPost
Bittensor’s Runtime 475 adds an optional way for subnet owners to expand registration capacity, while giving one identifier control of the scores used to calculate miner rewards. The change offers room for more registered participants but concentrates scoring authority in the highest-stake-weight validator. Released Oct. 7 at 4:40 p.m. ET (20:40 UTC), Runtime 475 introduced Null Consensus. Subnets stay on Yuma by default, including newly created subnets. An owner must select Null and separately increase the subnet’s configured capacity for the higher limit to apply. Under Yuma, multiple eligible validators contribute scores.
Source: TokenPost







