Bittensor subnet news

Bittensor Community, Contributors, and TAO Holders, The Opentensor Foundation (OTF) will hold a Community Call on Discord Tuesday, July 9, 5:00 PM US Eastern. The call will take place on Discord. To join the call please use this link: https://discord.gg/bittensor?event=1260319001611862107 During the call we will cover the topics listed below. Opening the mainnet Today, Tuesday, July 9, 5:00 PM US Eastern, the schedule_coldkey_swap extrinsic will become available. As of now, we expect to fully open the mainnet on July 12, 5:00 PM US Eastern. The schedule_coldkey_swap extrinsic will remain available on the mainnet after the mainnet is fully open. Available mainnet functionality, starting today When the mainnet opens today, the following mainnet extrinsics will be available: Chain state of the mainnet will be available today. From today when the mainnet opens, until Friday July 12, 5:00 PM US Eastern, only the following extrinsics will be available on the mainnet: set_weights , serve_axon , set_commitments, set_root_weights and schedule_coldkey_swap No other extrinsics will be available on the mainnet until Friday July 12, 5:00 PM US Eastern. All other extrinsics will become available on the mainnet after Friday July 12, 5:00 PM US Eastern. When will my coldkey swap execute? Your scheduled coldkey swap will execute on the mainnet exactly 7200 * 3 blocks (72 hours) after the original call is made (after you successfully ran the btcli wallet schedule_coldkey_swap command). After this 72-hour period is elapsed the original coldkey will be unlocked entirely Arbitration If multiple coldkey swaps involving the same coldkey are scheduled, the swap will not be performed when the mainnet opens. Instead, the swap will enter an arbitration stage where the Senate votes to determine which coldkey swap should occur. If a coldkey goes into arbitration, it will only be able to be unlocked by a senate vote. Testnet The schedule_coldkey_swap extrinsic is already available on the testnet

Opentensor Blogsource ↗

92SN92Blog · Jun 11, 2024

Consensus-based Weights

Summary This post describes the new Bittensor feature consensus-based weights. This feature is also known as “liquid alpha” in Bittensor Discord threads. This consensus-based weights feature will be available on the Bittensor testnet (see the Chain release notes for the exact date of the release). With this feature, the dividends to a subnet validator are better correlated to the performance of the subnet miner they are setting the weights on. This feature is made possible by changing the way the exponential moving average for the subnet validator bonds are calculated. See also the release note on the consensus-based weights feature here. Additionally, this feature is designed to amplify the effects of the commit reveal feature that was released recently. Introduction In a Bittensor subnet, the subnet validators assess the work of subnet miners, and set the weights on the subnet miners. These weights determine how to distribute the 41% of subnet emissions, i.e., incentives, earned by the subnet miners. As stated in this Bittensor doc, 18% of subnet’s emission it goes to the subnet owner. 41% goes to subnet validators (this is called dividend). 41% goes to the subnet miners (this is called incentive). This new feature consensus-based weights pertains to the dividends to the subnet validators. To understand the how and why of the changes brought on by the new feature consensus-based weights, below we present how the dividends for a subnet validator are calculated. For a full, mathematically rigorous, explanation of the calculation of dividends, see the section on consensus policy in the Subtensor document for technical details. We compare the weights that each subnet validator sets on each subnet miner, to the average of all subnet validators’ weight settings for that subnet miner. Weights set by an individual subnet validator that are above this average are set to the consensus (average) — a process called clipping. Clipping is used to discourage selfish behavior by

Opentensor Blogsource ↗