Setting up Validator Keys
Last updated
Last updated
To make the deposit transaction(s), you will want your 32 ETH, or multiples, in a single hardware wallet address.
If this is not possible, at least physically disconnect from the network by unplugging ethernet cable or disconnecting from Wifi.
Ways to create your validator keys:
Keystore file(s)
[i.e.. keystore-16945983.json]
Controls the validator's ability to sign transactions
Imported and loaded into your validator
Keep private. Do not share with anyone
Can be recreated from your mnemonic seed/secret recovery phrase
Deposit data file(s)
[i.e. deposit_data-16945983.json]
Public information about your validator
Required to execute your deposit through the Ethereum Launchpad
Can be recreated from your mnemonic seed/secret recovery phrase
After creating the validator keys offline, you'll want to copy these validator keys to your node.
To align with this guide's steps, make the default validator_keys path on your node.
To transfer validator key files to your node from your local computer, consider using:
After transferring the files, verify that the keystore-m files are in the proper location on your node.
Expected sample output:
Only deposit the 32 ETH per validator if you are confident your node will be fully synced, which takes on average a day - check your logs, and ready to perform validator duties. You can return later to launchpad with your deposit-data to finish the next steps.
Upload yourdeposit_data-#########.json found in the validator_keys directory.
Connect the launchpad with your wallet, review and accept terms. Ensure you're connected to Mainnet network.
Confirm the transaction(s). There's one deposit transaction of 32 ETH for each validator.
Deposit Example: If you want to run 3 validators you will need to have (32 x 3) = 96 ETH plus some extra to cover the gas fees.
Ledger Nano Hardware wallet users: If you encounter difficulty making the deposit transaction, enable blind signing and contract data.
Stay Offline: Write down your mnemonic seed offline. Not email. Not cloud.
Verify your hardware wallet's backup: Most important of all data, this is where your withdrawal address belongs and ultimately controls the 32 ETH
In case of recovery: Stored on a USB key, keep copies of
validator_keys directory - contains all the keystore .json files
keystore password - used to encrypt keystore files
DO NOT USE AN EXCHANGE ADDRESS AS WITHDRAWAL ADDRESS.
Offline Key Generation Best Practices: The mnemonic seed (24 words) to your validator should be protected by keeping them offline. Use Tails OS (see option 3) or a (Option 1) or Wagyu to generate keys.
1. Download from Github.
Download Wagyu:
You will learn how to boot up a windows PC into an airgapped .
Download the official image from the . Might take a while, go grab a coffee.
For Mac, download
Make sure you have saved your validator keys directory in your other USB stick (non Tails OS) before you shutdown Tails. Tails will delete everything saved on it after you shutdown.
Congrats on learning how to use Tails OS to make an air gapped system.
Windows OS - use or
Mac or Linux - use or or
Follow the walk-through at the Launchpad:
Batch Depositing Tip: If you have many deposits to make for many validators, consider using This greatly improves the deposit experience as multiple deposits can be batched into one transaction, thereby saving gas fees and saving your fingers by minimizing Metamask clicking.
Source:
Verify Deposit Contract: Your transaction is depositing ETH to the Check, double-check, triple-check that the official Ethereum Deposit Contract address is correct.
Critical Crypto Reminder: Keep your mnemonics, keep your ETH.
More than 1 backup of mnemonic: Multiple copies with multiple locations is better. Best stored in a
