# LockHotkeyMismatch (/docs/errors/chain/LockHotkeyMismatch)

A conviction lock on this subnet is bound to a different hotkey than the one in the call. One coldkey may lock to only one hotkey per subnet: topping up `lock_stake` must reuse that hotkey (`btcli lock move` to retarget), and a stake transfer that moves locked alpha must land on the receiver's existing lock hotkey (`btcli stake transfer --destination-hotkey <lock-hotkey>`). Check the lock with `btcli lock show --netuid <n>` / `btcli stake list` (locked · free · lock → hotkey).

Declared by the `SubtensorModule` pallet; it classifies to the semantic code [`invalid_argument`](/docs/errors/invalid-argument).

Declared at [`pallets/subtensor/src/macros/errors.rs#L302`](/code/pallets/subtensor/src/macros/errors.rs#L302).

## Remediation [#remediation]

Reuse the existing lock hotkey, or for transfers of locked alpha land on the receiver's lock hotkey via `btcli stake transfer --destination-hotkey <lock-hotkey>`; inspect with `btcli lock show` / `btcli stake list`

The same explanation is available in the terminal: `btcli explain LockHotkeyMismatch`.