SubnetLimitReached
Error Re-added v320 → v326, v334 → v377, v385 → current 7.115The maximum number of subnets has been reached.
Why This Error Exists
Bittensor limits the total number of active subnets to manage network resources and ensure quality. When the limit is reached, new subnet creation requires an existing low-performing subnet to be dissolved. Subnets in their immunity period cannot be pruned, which can temporarily block new creations.
Deep Dive
SubnetLimit is a governance parameter (currently around 52). TotalNetworks is the active count. When TotalNetworks >= SubnetLimit, the chain attempts to prune the lowest-emission subnet that's outside its immunity period (NetworkImmunityPeriod). If ALL subnets are in immunity, this error occurs. The lock cost also increases with demand, creating economic pressure.
Debugging Example
You call register_network(...). Error: SubnetLimitReached. Query TotalNetworks - returns 52. Query SubnetLimit - returns 52. Network is at capacity. Query NetworkRegisteredAt for each subnet to find ones outside immunity. If all are immune, you must wait for immunity periods to expire (typically days to weeks).
Prevention Tips
- Monitor TotalNetworks vs SubnetLimit before planning subnet launch
- Check AllNetworksInImmunity to see if pruning is possible
- Consider acquiring an existing subnet rather than creating new
From Chain Metadata
Subnet limit reached & there is no eligible subnet to prune
What This Means
The maximum number of subnets has been reached.
Common Causes
- Network at maximum subnet capacity
- No eligible subnet to prune for new creation
How to Fix
- Wait for a subnet to be dissolved
- Check SubtensorModule.SubnetLimit for the maximum
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 115
- Error Code
- 7.115
- Runtime Version
- v393