forked from opentensor/developer-docs
-
Notifications
You must be signed in to change notification settings - Fork 19
Announcements #88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Announcements #88
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
7c067fa
wip
MichaelTrestman 54f517a
wip
MichaelTrestman 6b46bf4
wip
MichaelTrestman 94c3e6f
wip
MichaelTrestman e24f66c
wip
MichaelTrestman 600004d
Update announcements.md
chideraao 58331ee
wip
MichaelTrestman 00865e6
wip
MichaelTrestman 416aa01
Apply suggestions from code review
MichaelTrestman 5f11ec7
wip
MichaelTrestman f28e6ae
wip
MichaelTrestman 8df5419
wip
MichaelTrestman 32aefbb
wip
MichaelTrestman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,65 @@ | ||
| --- | ||
| title: "Announcements and Developments" | ||
| --- | ||
| # Announcements and Developments | ||
|
|
||
| This page tracks recent and upcoming changes to the Bittensor protocol and other major events in the Bittensor ecosystem. | ||
|
|
||
|
|
||
| ## Sub-Subnets (Major Feature Launch) | ||
|
|
||
| **Status**: Ready for deployment on September 12, 2025 | ||
| - **What**: Sub-subnets allow subnet owners to apportion emissions across multiple sub-subnets, each running Yuma Consensus independently | ||
| - **Key Features**: | ||
| - Enables up to 8 sub-subnets (IDs 0-7) within each main subnet for multi-task validation | ||
| - Fully backward-compatible with existing miners and validators via sub-subnet ID 0 | ||
| - Each sub-subnet has its own weight matrix and independent emissions | ||
| - All validators participate in all sub-subnets with identical stake weights | ||
| - Miners automatically participate in ALL sub-subnets when registering for a subnet | ||
| - Emissions are divided evenly, but subnet owners can configure proportions. | ||
| - First version focuses on core functionality with additional features planned based on community feedback | ||
|
|
||
| ## Hyperparameter Rate Limiting | ||
| **Status**: WIP | ||
| - **What**: Prevents subnet owners from changing hyperparameters too frequently | ||
| - **Rules**: Cannot change hyperparameters in last 10 blocks of a tempo | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Worth to mention it's 3 blocks on fast-blocks? |
||
| - **Purpose**: Prevent exploitation where subnet owners kick off root validators to take full incentives | ||
| - **Implementation**: Applies 7,200-block rate limit to prevent subnet owner exploitation | ||
|
|
||
| ## Child Key Fee | ||
|
|
||
| A percentage fee will be deducted from emissions bound to validator hotkeys through a *child hotkey* relationship. This is designed to more highly incentivize validators who perform validation work, over child-key-only validators. It is being gradually rolled out to reduce surprise for the community and allow validators to adjust. | ||
|
|
||
| **Status**: Implemented (Merged) | ||
| - **Plan**: | ||
| - Start at 1% (September 10) | ||
| - 30-day delay | ||
| - Increase by 1% per day for 17 days | ||
| - Final rate: 18% | ||
|
|
||
| ## Changes to the Subnet Registration/Deregistration Process | ||
|
|
||
| **Status**: Ready for deployment on September 16, 2025 | ||
| - **Key Changes**: | ||
| - Subnet limit remains at 128 initially with no new registrations available immediately | ||
| - Immunity period reduced from 6 months to 4 months from registration block | ||
| - Network rate limit increased to 3 days (from 2 days) between registrations | ||
| - Initial lock cost set at 1,000 TAO with standard linear decay mechanism | ||
| - First deregistrations available approximately September 23 (one week after deployment) | ||
|
|
||
| ## Auto-Staking for Miners | ||
| **Status**: Implemented (Merged) | ||
| - **What**: Miners can automatically stake their mining income to a validator of their choice | ||
| - **Implementation**: | ||
| - New extrinsics `set_coldkey_auto_stake_hotkey` and `get_coldkey_auto_stake_hotkey` | ||
| - Set per coldkey, affects all miner hotkeys | ||
| - No transaction fees required | ||
| - Reduces sell pressure by allowing automatic delegation of mining rewards | ||
| - Event emission system being added to distinguish mining vs staking rewards for proper accounting | ||
| - Requires CLI support for configuration and management | ||
|
|
||
| ## Registration Fee Controls | ||
| **Status**: Deployed | ||
| - **What**: Subnet owners can configure neuron registration fees | ||
| - **Implementation**: | ||
| - Subnet owners can configure neuron registration fees between 0.1 and 1 TAO | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.