Regenerating Keystore file using the 24 words

Regenerating Keystore file using the 24 words

Original guide by: “tropicar”

Download the ETH CLI tool, you can obtain it from Releases · ethereum/eth2.0-deposit-cli · GitHub 5

In this case we are going to use the eth2deposit-cli-ed5a6d3-XXXXXXXX.tar.gz, where ed5a6d3 should be changed for the latest version.

To execute the tool to regenerate our keystore from the mnemonic or 24 words:

  • (If we are restoring a testnet keystore we must indicate on the flag –chain)
    deposit existing-mnemonic –chain pyrmont
  • (If we are restoring a mainnet keystore we must indicate on the flag –chain with the work mainnet)
    deposit existing-mnemonic –chain mainnet

Now, the console will ask you for the words:

Type your 24 words, for example:

chaos jewel security draw embody project route funny impact brief decorate palace sky figure blue eleven crop ocean fly bear wasp bird arrest arrow

The next question will be:

Enter the index (key number) you wish to start generating more keys from (starting from 0 for the first validator). For example, if you’ve generated 4 keys in the past, and you want to generate the keystore for the latest validator you created, you’d enter 3 here:

Enter the index (key number) you wish to start generating more keys from. For example, if you’ve generated 4 keys in the past, you’d enter 4 here, [0]:

Depends on how many keys you have generated in the past. In my case I generated 1, so I would write:


Repeat the confirmation.


You will be asked for Please choose how many validators you wish to run:

Depends on your preferences, I am running only 1, then I type:


Now the tool will generate new keystores for the derived keys. It will ask us for a password to secure these new keystores. It doesn’t need to be the same as the original keystore, but it’s very important that you secure it properly: you will need it.

Prompt asks to Type the password that secures your validator keystore(s):

> whatever_password

After writing it down, confirm.

After this process, we should have a directory called validator_keys, where the keystores will be.

To check if you have restored correctly your validator, you can check it comparing the pubkey from:

If you know your validator in Beaconchain or Beaconscan, compare the string above with the string in the field called ‘pubkey’ on the file keystore-m…

If it is the same, you have regenerated the keystore of that validator correctly.

Now you can proceed to the 2nd half of this guide:

Step 1

Reach out to one of the [] Admins on Discord.

You’ll have to share the email address you used to register, so that we can identify the relevant account.

Step 2

Access and send us your logs so we can make sure that you’re not jeopardizing anything by deleting your validators.

Step 3

Access and delete your Config Files. You should also remove the entire ‘blox-live-desktop-app’ folder as instructed.

Step 4

‘Clean’ your AWS account to make sure that your ‘old’ EC2 instance and activity is properly removed.

Step 5

At this point we will also delete your old information from our database. Before opening Blox Live to set up your mainnet validator(s), please reach out to us again on Discord to make sure everything is in order. Once everything is good to go, you can download the latest version of the Blox app, reinstall it and Follow the instructions on this guide to import those validators back to Blox, without the seed this time by using the keystore files we just created.

More Support