NotSubnetOwner
Error v133 → v141, v142 → v145, v146 → v148, v149 → v150, v151 → v212, v216 → v216, v217 → v219, v233 → v315, v320 → v326, v334 → v393, v401 → current 7.41You're not the owner of this subnet .
Why This Error Exists
Subnet owner operations (like changing hyperparameters, transfer ownership, or dissolving the subnet) are restricted to the owner coldkey. This protects subnets from unauthorized modifications. The owner is set at subnet creation and can only be changed by the current owner.
Deep Dive
SubnetOwner(netuid) returns the coldkey address that owns that subnet. Only this coldkey can sign owner-restricted calls: sudo_set_* hyperparameters, transfer_subnet_ownership, dissolve_network, etc. If you're building a tool, check ownership before attempting these operations to give users clear feedback.
Debugging Example
You call sudo_set_tempo(netuid=5, tempo=100). Error: NotSubnetOwner. Query SubnetOwner(5) - returns 5OwnerKey.... Compare to your signing coldkey - they don't match. Solution: You need to use the wallet containing 5OwnerKey... to make this call.
Prevention Tips
- Query SubnetOwner(netuid) before attempting owner operations
- Document which coldkey owns each of your subnets
- After ownership transfers, update your records immediately
From Chain Metadata
Not a subnet owner.
What This Means
You're not the owner of this subnet.
Common Causes
- Trying to modify subnet you don't own
- Using wrong coldkey
- Ownership was transferred
How to Fix
- Check SubtensorModule.SubnetOwner for the actual owner
- Use the owner's coldkey for this operation
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 41
- Error Code
- 7.41
- Runtime Version
- v411