existing-mnemonic

Including sensitive arguments when executing CLI commands poses a security risk, as these values can be accessible through disk and shell history. This exposure can allow other users, including admins and malicious actors, to gain access to sensitive information, putting your funds at risk.

Description

Uses an existing BIP-39 mnemonic phrase for key generation.

Optional Arguments

--chain: The chain to use for generating the deposit data. Options are: 'mainnet', 'holesky', etc...
--mnemonic: The mnemonic you used to create withdrawal credentials.
--mnemonic_password: The mnemonic password you used in your key generation. Note: It's not the keystore password.
--validator_start_index: The index of the first validator's keys you wish to generate. If this is your first time generating keys with this mnemonic, use 0. If you have generated keys using this mnemonic before, use the next index from which you want to start generating keys from. As an example if you've generated 4 keys before (keys #0, #1, #2, #3), then enter 4 here.
--num_validators: Number of validators to create.
--keystore_password: The password that is used to encrypt the provided keystore. Note: It's not your mnemonic password.
--withdrawal_address: The Ethereum execution address for validator withdrawals.
--pbkdf2: Will use pbkdf2 key derivation instead of scrypt for generated keystore files as defined in EIP-2335. This can be a good alternative if you intend to work with a large number of keys, as it can improve performance however it is less secure. You should only use this option if you understand the associated risks and have familiarity with encryption.
--folder: The folder where keystore and deposit data files will be saved.

Example Usage

./deposit existing-mnemonic