RootNetworkDoesNotExist
Error Re-added v151 → v315, v320 → current 7.0The root network (netuid 0) doesn't exist or isn't accessible.
Why This Error Exists
The root network (netuid 0) is special - it's where subnet validators vote on emissions distribution across all subnets. If it doesn't exist, the network isn't properly initialized. On mainnet, this should never happen. On testnet or local devnets, it might indicate incomplete setup.
Deep Dive
Netuid 0 is reserved for the root network. Operations like setting root weights, registering as a root validator, or querying root-specific storage require netuid 0 to exist. NetworksAdded(0) should always return true on a properly bootstrapped network. If it doesn't, you're likely on a broken or uninitialized chain.
Debugging Example
You call set_root_weights(...). Error: RootNetworkDoesNotExist. Query NetworksAdded(0) - returns false (or error). This indicates a fundamental network issue. Are you connecting to the right endpoint? Check your websocket URL - mainnet is wss://entrypoint-finney.opentensor.ai:443.
Prevention Tips
- Verify your RPC/websocket endpoint is correct for your target network
- On local devnets, ensure the init sequence created netuid 0
- If this occurs on mainnet, report it immediately - it's a critical issue
From Chain Metadata
The root network does not exist.
What This Means
The root network (netuid 0) doesn't exist or isn't accessible.
Common Causes
- Root network not initialized
- Network configuration issue
How to Fix
- This is typically a network-level issue
- Verify you're on a properly configured network
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 0
- Error Code
- 7.0
- Runtime Version
- v393