InvalidSpecName
Error v101 → current 0.0The runtime upgrade has a different spec name than the current runtime .
Encountered by: validatorsdevelopers
Why This Error Exists
Runtime upgrades check that the new code is for the same chain. Different spec names indicate different chains (like deploying Polkadot code on Subtensor). This prevents accidentally replacing the runtime with incompatible code.
From Chain Metadata
The name of specification does not match between the current runtime and the new runtime.
What This Means
The runtime upgrade has a different spec name than the current runtime.
Common Causes
- Trying to deploy a runtime built for a different chain
- Wrong runtime binary selected for upgrade
- Accidental chain mismatch during upgrade process
How to Fix
- Verify you have the correct runtime binary for Subtensor
- Check that spec_name in the new runtime matches 'node-subtensor'
- Use the runtime from the official release for this chain
Storage to Check
Runtime Info
- Pallet Index
- 0
- Error Index
- 0
- Error Code
- 0.0
- Runtime Version
- v393