SUBTENSOR RUNTIME · v476
Subtensor v476 lets Subnet Owners configure PoW registration difficulty
This release lets Subnet Owners set the minimum and current PoW registration difficulty on their own subnets. Previously only governance could change these values, so a subnet stuck at maximum difficulty needed governance intervention. The release does not change any live subnet's settings.
Its changes shipped as part of v477.
- Changes since
- v475
- Commit
d6dd557a7e- GitHub release
- v476 ↗
Medium impact Validators / Miners
Subnet Owners can set minimum and current PoW difficulty
Subnet Owners can now change the minimum and current PoW registration difficulty of their subnet, in addition to enabling PoW registration. Each setting has its own owner cooldown and respects the existing admin freeze window. Root can bypass the owner cooldowns, and the root subnet remains governance-only. The Owner proxy type also covers these settings.
Source #3217
Also includes benchmark, fee-baseline, test, SDK description and documentation updates for the new owner permissions.
-
#3217 ↗ Merged
Allow subnet owners to configure PoW difficulty
Subnet owners (not just root) can now set the minimum and current PoW difficulty for their own Subnet within existing cooldown and freeze rules, and this requires a runtime spec_version bump from 475 to 476 for the upgrade to take effect.
AI-generated summary of the release code. Check the linked pull requests for authoritative details. Report generated Oct 13, 2026.
v476