Can't access staking VEGA

[andreykv11]

The hard drive on which the VEGA wallet was installed failed. I installed a wallet from the Recovery phrase on a new hard drive, but the key of the restored wallet is different and there is no access to the VEGA validator. Tell me what to do?

[ValentinTrinque]

@andreykv11 We upgraded the way the wallet derives the keys a while back. When importing a wallet, it defaults to the latest version, which is version 2. You are probably on the version 1, so you might want to specify the version through the command line flags.

More info on vegawallet import -h

[andreykv11]

The key number has become the same as it was on the broken hard drive, but I can not connect through it. Connects only through originally installed on version 1

[andreykv11]

How to remove extra keys?

[andreykv11]

[ValentinTrinque]

Sorry for not being clear enough.

First you need to re-import your wallet, and generates the keys.

Here's what you need to do, on the CLI:

1. Save the recovery phrase in a file, such as recovery.txt.
2. Run the command vegawallet import --wallet "NAME_OF_YOUR_WALLET" --recovery-phrase-file "/path/to/your/recovery.txt" --version 1. This command will generate a wallet v1 using your recovery phrase. The name of the wallet doesn't affect anything. The keys generation is only done through the recovery phrase.
3. Verify the generated key. You can use the command vegawallet key list --wallet "NAME_OF_YOUR_WALLET".

If the keys match, then you are good to go.

If they do not, then try the import command with the flag --version set to 2. Then, re-run the command on point 3, and compare.

You do not need to connect to the wallet to verify your keys. Everything can be done through the CLI.

[ValentinTrinque]

You can also refer to this documented process here:
https://docs.vega.xyz/docs/mainnet/tools/vega-wallet/cli-wallet/latest/guides/restore-wallet#i-restored-my-wallet-but-the-generated-keys-are-different