This error was removed in v377
This error is no longer present in the current runtime. Existed from v195 to v377. Shown here for historical reference.
SwapAlreadyScheduled
Error Removed v195 → v202, v205 → v212, v216 → v216, v217 → v219, v233 → v315, v320 → v326, v334 → v377 (removed) 7.65A coldkey swap is already pending for this account.
Why This Error Exists
Coldkey swaps are security-critical operations that transfer all stake, balances, and hotkey ownership to a new coldkey. To prevent abuse, only one swap can be pending at a time. The swap has a delay period during which the owner can cancel or the community can dispute if the key was compromised.
Deep Dive
ColdkeySwapScheduled maps old_coldkey -> (new_coldkey, execution_block). When you call schedule_swap_coldkey, it sets this pending swap. The swap executes automatically after ColdkeySwapScheduledDuration blocks. During the wait period, you can cancel with cancel_coldkey_swap, but you cannot schedule a different swap.
Debugging Example
You call schedule_swap_coldkey(old=5Old..., new=5NewA...). Later, you call schedule_swap_coldkey(old=5Old..., new=5NewB...). Error: SwapAlreadyScheduled. Query ColdkeySwapScheduled(5Old...) - returns (5NewA..., block 1200000). Solution: Either wait for the first swap to execute, or cancel it first with cancel_coldkey_swap(5Old...).
Prevention Tips
- Query ColdkeySwapScheduled(your_coldkey) before scheduling a swap
- If one is pending, cancel it first if you need to change the destination
- Track your pending swaps and their execution blocks
From Chain Metadata
Swap already scheduled.
What This Means
A coldkey swap is already pending for this account.
Common Causes
- Previous schedule_swap_coldkey is still pending
- Swap hasn't executed yet
How to Fix
- Wait for the pending swap to complete
- Check SubtensorModule.ColdkeySwapScheduled for pending swaps
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 65
- Error Code
- 7.65
- Removed In
- v377