NewHotKeyIsSameWithOld

Error Re-added v151 → v212, v216 → v219, v233 → v315, v320 → current 7.22

The new hotkey address is the same as the old hotkey .

Encountered by: validatorsminersdevelopers

Why This Error Exists

Hotkey swapping allows changing the operational key while maintaining stake and position. Swapping to the same key would be a no-op, so the chain rejects it to prevent wasted fees.

From Chain Metadata

The new hotkey is the same as old one

What This Means

The new hotkey address is the same as the old hotkey.

Common Causes

  • Passing the same hotkey for both old and new parameters
  • Typo in hotkey addresses

How to Fix

  • Verify the new hotkey is different from the existing one
  • Generate a new hotkey if swapping is intended

Storage to Check

SubtensorModule.OwnerSubtensorModule.OwnedHotkeys

Thrown By

swap_hotkey

Version History

v151 block 3,157,274 Added
v216 block 4,510,996 Re-added
v233 block 4,920,350 Re-added
v320 block 6,523,566 Re-added Current

Runtime Info

Pallet Index
7
Error Index
22
Error Code
7.22
Runtime Version
v393
Back to SubtensorModule Errors