metanull-operator / eth2-ubuntu

Configuration of an Ubuntu 20.04 LTS server for use as an Eth2 staking system, including setup of monitoring dashboard.
106 stars 30 forks source link

Adding a second validator later on #6

Closed kyodhin closed 3 years ago

kyodhin commented 3 years ago

Would be nice if there was an addon description for how to add a validator to the existing setup

metanull-operator commented 3 years ago

Using the same mnemonic or a different mnemonic? I'm sure both would be helpful to someone, but which are you particularly interested in?

kyodhin commented 3 years ago

Thx for taking the time! Although, I believe too that ppl would appreciate both, for me personally, I'm more interested in using a different mnemonic.

metanull-operator commented 3 years ago

Using a new mnemonic is pretty much the same process as you would have done with the first mnemonic. Use the deposit-cli tool to generate deposit data and keys. Upload deposit data to launchpad and make deposits. Import keys into validator.

The main difference between your first time and second time is that you might already have some keys in your deposit-cli folder from your first run. What I would do is backup/rename the first deposit-cli folder, then start from the beginning, downloading a new deposit-cli folder and following the instructions I already have.

Make sure you keep a copy of all mnemonics and passwords used.

That's a rough outline, but I completely understand if you'd rather see it all written out.

kyodhin commented 3 years ago

Thx. Yeah, I'm fairly certain that I know what I have to do. I was just trying to make really sure that it doesn't happen that my first keys somehow end up twice in there & I get slashed for running the validator twice on the network. I read that it happened to ppl with certain backup configs.

Thx for your great write up, really appreciated it!

metanull-operator commented 3 years ago

I have not heard of that happening when using a single validator, particularly from an import of keys. We would have to ask the Prysm folks, but I imagine that re-importing keys that are already imported is harmless. Still, it is worth confirming. A lot of ETH is on the line, so it is best to double-check and be safe.

kyodhin commented 3 years ago

Okay, I have successfully added the validator:

Going through launchpad process via airgapped temp. ubuntu system. Saving keystore, deposit file & seed safely.

Then placed the keys in /home/validator/validator_keys (deleting old content before or one can rename the folder & creating a new validator_keys folder).

Import keys:

sudo -u validator /home/validator/bin/prysm.sh validator accounts import --keys-dir=/home/validator/validator_keys

Restart validator:

sudo systemctl restart validator

List all accts (optional):

sudo -u validator /home/validator/bin/prysm.sh validator accounts list