staking-deposit-cli VS lodestar

I am looking for a way to automatically create deposit data. So far I tried https://github.com/ethereum/staking-deposit-cli but although it offers a --non_interactive flag it still asks for an encryption password for the keystore files. Are there any other open source tools? I really don't want to fork and maintain my own version of the deposit cli.

First, you need to generate new keys using the staking deposit CLI software. It is recommended to do this on an offline computer. You can generate a new mnemonic phrase, but it seems simpler to reuse the same one as your other validators.

I am trying to setup a local devnet in my computer by using geth and prysm using https://docs.prylabs.network/docs/advanced/proof-of-stake-devnet. I can able to setup network with three execution nodes and three consensus nodes. Now I want to add new validators to the network. I tried with https://github.com/protolambda/eth2-val-tools and https://github.com/ethereum/staking-deposit-cli. I do get keystore-###.json and deposit_data-###.json files.

I’ve been trying to fix the initial language selection screen, and it displays right for me but not for a staking-deposit-cli dev. See https://github.com/ethereum/staking-deposit-cli/pull/325

Deposit cli will support it. See https://github.com/ethereum/staking-deposit-cli/issues/312

For those that are interested about the staking-deposit-cli PR: https://github.com/ethereum/staking-deposit-cli/pull/313

You can check this instructions: https://github.com/ethereum/staking-deposit-cli --eth1_withdrawal_address String. Eth1 address in hexadecimal encoded form

I think I found it. This pull request helped me: https://github.com/ChainSafe/lodestar/pull/3782

Somer's guides are awesome and extremely thorough, but they help you learn to build a validator from scratch. In practice, I always download client binaries rather than building from scratch. You can find the lodestar releases page here.

https://github.com/ChainSafe/lodestar 63 contributors

My mainnet lodestar node crashed today. Thankfully, the validator process switched over to my backup lighthouse node without missing a single attestation.

Daily Goerli: I've been periodically running into some issues when updating nethermind which require force killing the Nethermind.Runner process. Recently had an issue where geth in lodestar-geth thought it was waiting for updates from lodestar, but lodestar was reporting connection refused. A restart of geth fixed it. I'm currently running into No state found for id 'head' in all lodestar instances, which was supposed to be fixed by this PR. I also recently encountered a long stack error from erigon in prysm-erigon when closing to update, but restarting both clients allowed sync to resume.

The following sections outline how to configure an execution-layer client and a consensus-layer client so that they have everything in place to execute the entire merge already in the genesis block. Here, we'll use Geth and Lodestar.

Consensus Layer client ✅ Teku v22.11.0: https://github.com/ConsenSys/teku/releases/tag/22.11.0 ✅ Lodestar v1.2.2: https://github.com/ChainSafe/lodestar/releases/tag/v1.2.2 🟡 Lighthouse: coming soon 🟡 Nimbus: coming soon ❌ Prysm: advised to switch to other clients