HotKeyNotRegisteredInSubNet
Error Re-added v151 → v315, v320 → current 7.4The hotkey you're trying to interact with is not registered on the specified subnet .
Why This Error Exists
Most operations require the hotkey to be registered on the target subnet. Registration gives you a UID on that subnet. Without it, you can't stake to that hotkey on that subnet, set weights, serve axon, or do anything subnet-specific.
Deep Dive
Hotkeys can be registered on multiple subnets independently. Each registration is per-subnet. Being registered on subnet 1 doesn't mean you're on subnet 3. Also, hotkeys can be deregistered if they perform poorly and get pruned.
Debugging Example
You try to stake to hotkey X on subnet 3, but get this error. Query Uids(netuid=3, hotkey=X) - returns None. The hotkey isn't on subnet 3. Either register it first, or stake to a different subnet where it IS registered.
Prevention Tips
- Verify registration before subnet operations
- Keep your miner/validator performing well to avoid deregistration
- Double-check the netuid in your calls
From Chain Metadata
The hotkey is not registered in subnet
What This Means
The hotkey you're trying to interact with is not registered on the specified subnet.
Common Causes
- Hotkey was never registered on this subnet
- Hotkey was deregistered due to low stake/performance
- Using wrong netuid for this hotkey
How to Fix
- Check SubtensorModule.Uids to verify registration
- Register the hotkey first using register or burned_register
- Verify you're using the correct netuid
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 4
- Error Code
- 7.4
- Runtime Version
- v393