-
Notifications
You must be signed in to change notification settings - Fork 243
mainnet deploy 9/25/2025 #2066
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
mainnet deploy 9/25/2025 #2066
Conversation
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
Rate limit hyperparams setting
…mage-set-toolchain-version Install and set toolchain 1.88 as default in `Dockerfile-localnet`
…workflow Improve docker-localnet workflow
…etagraph Fix/Use `netuid_index` in selective metagraph
…-logging Fix/remove unnecessary error logging
…solution LP Dissolution validator selection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Deregistration/Registration
Starting one week from this deploy (50,400 blocks after the mainnet deploy), subnet registrations will resume! The initial lock cost will be 2,000 TAO on day 7. The
SubnetLimit
is being introduced starting at 128. Registrations beyond this limit will trigger deregistration of the lowest scoring subnet. Some other parameters that have changed:ImmunityPeriod
is now 4 months (down from 6 months)NetworkRateLimit
has been raised from 2 days to 4 daysNetworkLockReductionInterval
has been set to 8 daysFor more information please see #1651 and/or BIT-0016.
Subnet Mechanisms (previously "Subsubnets")
Previously each subnet was capable of supporting a single "mechanism" (or problem that can be solved by miners and checked by validators via yuma consensus) out of the box unless the subnet implemented complex logic to simulate multiple mechanisms manually. Now subnets will natively support the concept of multiple mechanisms within the same subnet. This feature can be enabled at the discretion of the subnet owner, with an initial limit of 2 mechanism IDs per subnet (we plan to increase this later). This should be a huge boon for subnets that want to have miners work on multiple problems without needing to register multiple subnets, and subnets that want to try new miner code deployment strategies such as zero downtime deployment. Another positive effect of this change should be that multi-subnet ecosystems should feel less pressure to register multiple subnets since they will be able to do more with a single subnet, allowing them to unite multiple projects under a single market cap when desirable. This should foster new innovations by making it easier for existing subnets to experiment in a low-cost, low-risk way.
For more information please see:
btcli:
btcli subnet mech count btcli subnet mech set btcli subnet mech emissions btcli subnet mech emissions-split
Trim UIDs
Some subnets have grown their set of miner UIDs to be larger than they originally intended. The Trim UIDs feature allows subnet owners in this situation to trim their set of UIDs down to 64 if and only if at least 20% of the resulting untrimmed UIDs are non-immune.
For more information please see #1998.
Hyperparameter Rate Limiting
We have introduced rate-limiting for hyperparameter changes within subnets. This should help prevent abuse by subnet owners and reduce volatility for stakers and subnet participants. The rate limit will be 2 tempos by default and applies to each hyperparameter individually (if you change hyperparameter A, you have to wait 2 tempos before changing it again, however this does not affect changing hyperparameter B, etc.). The triumvirate will update this rate-limit accordingly in the future via sudo call, as needed.
For more information please see #2048.
What's Changed
netuid_index
in selective metagraph #2073 by @JohnReedV.dockerignore
#2044 by @basfromanDockerfile-localnet
#2043 by @basfroman