Installing consensus client (beacon chain and validator)

Pick a consensus client
To strengthen Ethereum's resilience against potential attacks or consensus bugs, it's best practice to run a minority client in order to increase client diversity. Find the latest distribution of consensus clients here: https://clientdiversity.org/​
Your choice of Lighthouse, Nimbus, Teku, Prysm or Lodestar.
Lighthouse
Nimbus
Teku
Prysm
Lodestar
​Lighthouse is an Eth client with a heavy focus on speed and security. The team behind it, Sigma Prime, is an information security and software engineering firm who have funded Lighthouse along with the Ethereum Foundation, Consensys, and private individuals. Lighthouse is built in Rust and offered under an Apache 2.0 License.
​
​⚙
 4.1. Install rust dependency
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
​
Enter '1' to proceed with the default install.
​
Update your environment variables.
echo export PATH="$HOME/.cargo/bin:$PATH" >> ~/.bashrc
source ~/.bashrc
​
Install rust dependencies.
sudo apt-get update
sudo apt install -y git gcc g++ make cmake pkg-config libssl-dev libclang-dev clang protobuf-compiler
​
​💡
 4.2. Build Lighthouse from source
mkdir ~/git
cd ~/git
git clone https://github.com/sigp/lighthouse.git
cd lighthouse
git fetch --all && git checkout stable && git pull
make
​
Improve some Lighthouse benchmarks by around 20% at the expense of increased compile time? Use maxperf profile.

To compile with maxperf, replace the above make command with
  PROFILE=maxperf make
​
In case of compilation errors, run the following sequence.
rustup update
cargo clean
make
​
This build process may take a few minutes.
​
Verify lighthouse was installed properly by checking the version number.
lighthouse --version
​
​🎩
 4.3. Import validator key
When you import your keys into Lighthouse, your validator signing key(s) are stored in the $HOME/.lighthouse/mainnet/validators folder.
​
Run the following command to import your validator keys from the eth2deposit-cli tool directory.
​
Enter your keystore password to import accounts.
lighthouse account validator import --network mainnet --directory=$HOME/staking-deposit-cli/validator_keys
​
Verify the accounts were imported successfully.
lighthouse account_manager validator list --network mainnet
​
WARNING: Do not import your validator keys into multiple validator clients and run them at the same time, or you might get slashed. If moving validators to a new setup or different validator client, ensure deletion of the previous validator keys before continuing.
​
​🔥
 4.4. Configure port forwarding and/or firewall
​
Specific to your networking setup or cloud provider settings, ensure your validator's firewall ports are open and reachable.
​
Lighthouse consensus client requires port 9000 for tcp and udp
Execution client requires port 30303 for tcp and udp
​
​⛓
 4.5. Start the beacon chain
​
Create a systemd unit file to define yourbeacon-chain.service configuration.
sudo nano /etc/systemd/system/beacon-chain.service
​
Paste the following configuration into the file.
# The eth beacon chain service (part of systemd)
# file: /etc/systemd/system/beacon-chain.service
​
[Unit]
Description=eth beacon chain service
Wants=network-online.target
After=network-online.target
​
[Service]
Type=simple
User=<USER>
Restart=on-failure
ExecStart=<HOME>/.cargo/bin/lighthouse bn \
  --network mainnet \
  --staking \
  --validator-monitor-auto \
  --metrics \
  --checkpoint-sync-url=https://beaconstate.info \
  --execution-endpoint http://127.0.0.1:8551 \
  --execution-jwt /secrets/jwtsecret
​
[Install]
WantedBy=multi-user.target
​
Checkpoint Sync: allows consensus layer to start within minutes instead of days.
Refer to https://eth-clients.github.io/checkpoint-sync-endpoints/ and feel free to pick one of the random state providers from the list, instead of the above endpointhttps://beaconstate.info
Do not trust any single checkpoint provider. Verify the state root and block root against multiple checkpoints to ensure you're on the correct chain.
​
To exit and save, press Ctrl + X, then Y, thenEnter.
​
Update the configuration file with your current user's home path and user name.
sudo sed -i /etc/systemd/system/beacon-chain.service -e "s:<HOME>:${HOME}:g"
sudo sed -i /etc/systemd/system/beacon-chain.service -e "s:<USER>:${USER}:g"
​
Update file permissions.
sudo chmod 644 /etc/systemd/system/beacon-chain.service
​
Run the following to enable auto-start at boot time and then start your beacon node service.
sudo systemctl daemon-reload
sudo systemctl enable beacon-chain
sudo systemctl start beacon-chain
​
Nice work. Your beacon chain is now managed by the reliability and robustness of systemd.
​
​🧬
 4.6. Start the validator
​
Create a systemd unit file to define your validator.service configuration.
sudo nano /etc/systemd/system/validator.service
​
Paste the following configuration into the file.
# The eth validator service (part of systemd)
# file: /etc/systemd/system/validator.service
​
[Unit]
Description=eth validator service
Wants=network-online.target beacon-chain.service
After=network-online.target
​
[Service]
Type=simple
User=<USER>
Restart=on-failure
ExecStart=<HOME>/.cargo/bin/lighthouse vc \
 --network mainnet \
 --metrics \
 --suggested-fee-recipient 0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS
​
[Install]
WantedBy=multi-user.target
​
Replace0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS with your own Ethereum address that you control. Tips are sent to this address and are immediately spendable, unlike the validator's attestation and block proposal rewards.
​
To exit and save, press Ctrl + X, then Y, thenEnter.
​
Update the configuration file with your current user's home path and user name.
sudo sed -i /etc/systemd/system/validator.service -e "s:<HOME>:${HOME}:g"
sudo sed -i /etc/systemd/system/validator.service -e "s:<USER>:${USER}:g"
​
Update file permissions.
sudo chmod 644 /etc/systemd/system/validator.service
​
Run the following to enable auto-start at boot time and then start your validator.
sudo systemctl daemon-reload
sudo systemctl enable validator
sudo systemctl start validator
​
Nice work. Your validator is now managed by the reliability and robustness of systemd.
​Nimbus is a research project and a client implementation for Ethereum 2.0 designed to perform well on embedded systems and personal mobile devices, including older smartphones with resource-restricted hardware. The Nimbus team are from Status the company best known for their messaging app/wallet/Web3 browser by the same name. Nimbus (Apache 2) is written in Nim, a language with Python-like syntax that compiles to C.
​
​⚙
 4.1. Build Nimbus from source
​
Install dependencies.
sudo apt-get update
sudo apt-get install curl build-essential git -y
​
Install and build Nimbus.
mkdir ~/git
cd ~/git
git clone https://github.com/status-im/nimbus-eth2
cd nimbus-eth2
make update
make -j$(nproc) nimbus_beacon_node
​
The build process may take a few minutes.
​
Verify Nimbus was installed properly by displaying the version.
cd $HOME/git/nimbus-eth2/build
./nimbus_beacon_node --version
​
Copy the binary file to /usr/bin
sudo cp $HOME/git/nimbus-eth2/build/nimbus_beacon_node /usr/bin
​
​🎩
 4.2. Import validator key
​
Create a directory structure to store nimbus data.
sudo mkdir -p /var/lib/nimbus
​
Take ownership of this directory and set the correct permission level.
sudo chown $USER:$USER /var/lib/nimbus
sudo chmod 700 /var/lib/nimbus
​
The following command will import your validator keys.
​
Enter your keystore password to import accounts.
cd $HOME/git/nimbus-eth2
build/nimbus_beacon_node deposits import --data-dir=/var/lib/nimbus $HOME/staking-deposit-cli/validator_keys
​
Now you can verify the accounts were imported successfully by doing a directory listing.
ll /var/lib/nimbus/validators
​
You should see a folder named for each of your validator's pubkey.
​
WARNING: Do not import your validator keys into multiple validator clients and run them at the same time, or you might get slashed. If moving validators to a new setup or different validator client, ensure deletion of the previous validator keys before continuing.
​
​🔥
 4.3. Configure port forwarding and/or firewall
​
Specific to your networking setup or cloud provider settings, ensure your validator's firewall ports are open and reachable.
​
Nimbus consensus client will use port 9000 for tcp and udp
Execution client requires port 30303 for tcp and udp
​
​🏂
 4.4. Start the beacon chain and validator
​
Reminder: Nimbus combines both the beacon chain and validator into one process.
​
Running Checkpoint Sync
​
Checkpoint Sync: allows consensus layer to start within minutes instead of days.
Refer to https://eth-clients.github.io/checkpoint-sync-endpoints/ and feel free to pick one of the random state providers from the list, instead of the endpointhttps://beaconstate.info
Do not trust any single checkpoint provider. Verify the state root and block root against multiple checkpoints to ensure you're on the correct chain.
​
Run the following command.
/usr/bin/nimbus_beacon_node trustedNodeSync \
--network=mainnet  \
--trusted-node-url=https://beaconstate.info \
--data-dir=/var/lib/nimbus \
--network=mainnet \
--backfill=false
​
When the checkpoint sync is complete, you'll see the following message:
Done, your beacon node is ready to serve you! Don't forget to check that you're on the canonical chain by comparing the checkpoint root with other online sources. See https://nimbus.guide/trusted-node-sync.html for more information.
​
🛠 Setup systemd service
​
Create a systemd unit file to define yourbeacon-chain.service configuration.
sudo nano /etc/systemd/system/beacon-chain.service
​
Paste the following configuration into the file.
# The eth beacon chain service (part of systemd)
# file: /etc/systemd/system/beacon-chain.service
​
[Unit]
Description=eth consensus layer beacon chain service
Wants=network-online.target
After=network-online.target
​
[Service]
Type=simple
User=<USER>
Restart=on-failure
ExecStart=/bin/bash -c '/usr/bin/nimbus_beacon_node \
  --network=mainnet \
  --data-dir=/var/lib/nimbus \
  --web3-url=ws://127.0.0.1:8551 \
  --metrics \
  --metrics-port=8008 \
  --suggested-fee-recipient=0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS \
  --jwt-secret="/secrets/jwtsecret"'
​
[Install]
WantedBy=multi-user.target
​
Replace0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS with your own Ethereum address that you control. Tips are sent to this address and are immediately spendable, unlike the validator's attestation and block proposal rewards.
​
To exit and save, press Ctrl + X, then Y, thenEnter.
​
Update the configuration file with your current user's name.
sudo sed -i /etc/systemd/system/beacon-chain.service -e "s:<USER>:${USER}:g"
​
Update file permissions.
sudo chmod 644 /etc/systemd/system/beacon-chain.service
​
Run the following to enable auto-start at boot time and then start your beacon node service.
sudo systemctl daemon-reload
sudo systemctl enable beacon-chain
sudo systemctl start beacon-chain
​
Nice work. Your beacon chain is now managed by the reliability and robustness of systemd.
​PegaSys Teku (formerly known as Artemis) is a Java-based Ethereum 2.0 client designed & built to meet institutional needs and security requirements. PegaSys is an arm of ConsenSys dedicated to building enterprise-ready clients and tools for interacting with the core Ethereum platform. Teku is Apache 2 licensed and written in Java, a language notable for its maturity & ubiquity.
​
​⚙
 4.1 Build Teku from source
​
Install git.
sudo apt-get install git -y
​
Install Java 17 LTS.
sudo apt update
sudo apt install openjdk-17-jdk -y
​
Verify Java 17+ is installed.
java --version
​
Install and build Teku.
mkdir ~/git
cd ~/git
git clone https://github.com/ConsenSys/teku.git
cd teku
RELEASETAG=$(curl -s https://api.github.com/repos/ConsenSys/teku/releases/latest | jq -r .tag_name)
git checkout tags/$RELEASETAG
./gradlew distTar installDist
​
This build process may take a few minutes.
​
Verify Teku was installed properly by displaying the version.
cd $HOME/git/teku/build/install/teku/bin
./teku --version
​
Copy the teku binary file to /usr/bin/teku
sudo cp -r $HOME/git/teku/build/install/teku /usr/bin/teku
​
​🔥
 4.2. Configure port forwarding and/or firewall
​
Specific to your networking setup or cloud provider settings, ensure your validator's firewall ports are open and reachable.
​
Teku consensus client will use port 9000 for tcp and udp
Execution client requires port 30303 for tcp and udp
​
​🏂
 4.3. Configure the beacon chain and validator
​
Teku combines both the beacon chain and validator into one process.
​
Setup a directory structure for Teku.
sudo mkdir -p /var/lib/teku
sudo mkdir -p /etc/teku
sudo chown $USER:$USER /var/lib/teku
​
Copy your validator_files directory to the data directory we created above.
cp -r $HOME/staking-deposit-cli/validator_keys /var/lib/teku
​
Remove the extra deposit_data file. Answer 'y' to remove write-protected regular file.
rm /var/lib/teku/validator_keys/deposit_data*
​
WARNING: Do not import your validator keys into multiple validator clients and run them at the same time, or you might get slashed. If moving validators to a new setup or different validator client, ensure deletion of the previous validator keys before continuing.
​
Storing your keystore password in a text file is required so that Teku can decrypt and load your validators automatically.
​
Replace <my_keystore_password_goes_here> with your keystore password between the single quotation marks and then run the command to save it to validators-password.txt
echo '<my_keystore_password_goes_here>' > $HOME/validators-password.txt
​
Confirm that your keystore password is correct.
cat $HOME/validators-password.txt
​
Move the password file and make it read-only.
sudo mv $HOME/validators-password.txt /etc/teku/validators-password.txt
sudo chmod 600 /etc/teku/validators-password.txt
​
Clear the bash history in order to remove traces of keystore password.
shred -u ~/.bash_history && touch ~/.bash_history
​
Create your teku.yaml configuration file.
sudo nano /etc/teku/teku.yaml
​
Paste the following configuration into the file.
# network
network: "mainnet"
initial-state: "https://beaconstate.info/eth/v2/debug/beacon/states/finalized"
​
# validators
validator-keys: "/var/lib/teku/validator_keys:/var/lib/teku/validator_keys"
​
# execution engine
ee-endpoint: http://localhost:8551
ee-jwt-secret-file: "/secrets/jwtsecret"
​
# fee recipient
validators-proposer-default-fee-recipient: "<0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS>"
​
# metrics
metrics-enabled: true
metrics-port: 8008
​
# database
data-path: "/var/lib/teku"
data-storage-mode: "prune"
​
Checkpoint Sync: allows consensus layer to start within minutes instead of days.
Refer to https://eth-clients.github.io/checkpoint-sync-endpoints/ and feel free to pick one of the random state providers from the list, instead of the above endpointhttps://beaconstate.info
Do not trust any single checkpoint provider. Verify the state root and block root against multiple checkpoints to ensure you're on the correct chain.
​
Replace<0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS> with your own Ethereum address that you control. Tips are sent to this address and are immediately spendable, unlike the validator's attestation and block proposal rewards.
​
​🎩
 4.4 Import validator key
​
When specifying directories for your validator-keys, Teku expects to find identically named keystore and password files.
For example keystore-m_12221_3600_1_0_0-11222333.json and keystore-m_12221_3600_1_0_0-11222333.txt
​
Create a corresponding password file for every one of your validators.
for f in /var/lib/teku/validator_keys/keystore*.json; do cp /etc/teku/validators-password.txt /var/lib/teku/validator_keys/$(basename $f .json).txt; done
​
Verify that your validator's keystore and validator's passwords are present by checking the following directory.
ll /var/lib/teku/validator_keys
​
​🏁
 4.5. Start the beacon chain and validator
​
Use systemd to manage starting and stopping teku.
​
​🛠
 Setup systemd service
​
Run the following to create a unit file to define yourbeacon-chain.service configuration. Simply copy and paste.
cat > $HOME/beacon-chain.service << EOF
# The eth beacon chain service (part of systemd)
# file: /etc/systemd/system/beacon-chain.service
​
[Unit]
Description=eth consensus layer beacon chain service
Wants=network-online.target
After=network-online.target
​
[Service]
User=$USER
ExecStart=/usr/bin/teku/bin/teku -c /etc/teku/teku.yaml
Restart=on-failure
Environment=JAVA_OPTS=-Xmx5g
​
[Install]
WantedBy=multi-user.target
EOF
​
Move the unit file to /etc/systemd/system
sudo mv $HOME/beacon-chain.service /etc/systemd/system/beacon-chain.service
​
Update file permissions.
sudo chmod 644 /etc/systemd/system/beacon-chain.service
​
Run the following to enable auto-start at boot time and then start your beacon node service.
sudo systemctl daemon-reload
sudo systemctl enable beacon-chain
sudo systemctl start beacon-chain
​
Nice work. Your beacon chain is now managed by the reliability and robustness of systemd.
​Prysm is a Go implementation of Ethereum 2.0 protocol with a focus on usability, security, and reliability. Prysm is developed by Prysmatic Labs, a company with the sole focus on the development of their client. Prysm is written in Go and released under a GPL-3.0 license.
​
​⚙
 4.1. Install Prysm
mkdir ~/prysm && cd ~/prysm
curl https://raw.githubusercontent.com/prysmaticlabs/prysm/master/prysm.sh --output prysm.sh && chmod +x prysm.sh
​
​🔥
 4.2. Configure port forwarding and/or firewall
​
Specific to your networking setup or cloud provider settings, ensure your validator's firewall ports are open and reachable.
​
Prysm consensus client will use port 12000 for udp and port 13000 for tcp
Execution client requires port 30303 for tcp and udp
​
​🎩
 4.3. Import validator key
​
$HOME/prysm/prysm.sh validator accounts import --mainnet --keys-dir=$HOME/staking-deposit-cli/validator_keys
Type "accept" to accept terms of use
Press enter to accept default wallet location
Enter a new prysm-only password to encrypt your local prysm wallet files
and enter the keystore password for your imported accounts.
​
For simplicity, use the same password for the keystore and prysm-only password.
​
Verify your validators imported successfully.
$HOME/prysm/prysm.sh validator accounts list --mainnet
​
Confirm your validator's pubkeys are listed.
#Example output:
Showing 1 validator account View the eth1 deposit transaction data for your accounts by running `validator accounts list --show-deposit-data
Account 0 | pens-brother-heat
[validating public key] 0x2374.....7121
​
WARNING: Do not import your validator keys into multiple validator clients and run them at the same time, or you might get slashed. If moving validators to a new setup or different validator client, ensure deletion of the previous validator keys before continuing.
​
​🏂
 4.4. Start the beacon chain
​
​🛠
 Setup systemd service
​
Create a systemd unit file to define yourbeacon-chain.service configuration.
sudo nano /etc/systemd/system/beacon-chain.service
​
Paste the following configuration into the file.
# The eth beacon chain service (part of systemd)
# file: /etc/systemd/system/beacon-chain.service
​
[Unit]
Description=eth consensus layer beacon chain service
Wants=network-online.target
After=network-online.target
​
[Service]
Type=simple
User=<USER>
Restart=on-failure
ExecStart=<HOME>/prysm/prysm.sh beacon-chain \
  --mainnet \
  --checkpoint-sync-url=https://beaconstate.info \
  --genesis-beacon-api-url=https://beaconstate.info \
  --execution-endpoint=http://localhost:8551 \
  --jwt-secret=/secrets/jwtsecret \
  --suggested-fee-recipient=0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS \
  --accept-terms-of-use
​
[Install]
WantedBy=multi-user.target
​
Checkpoint Sync: allows consensus layer to start within minutes instead of days.
Refer to https://eth-clients.github.io/checkpoint-sync-endpoints/ and feel free to pick one of the random state providers from the list, instead of the above endpointhttps://beaconstate.info
Do not trust any single checkpoint provider. Verify the state root and block root against multiple checkpoints to ensure you're on the correct chain.
​
Replace0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS with your own Ethereum address that you control. Tips are sent to this address and are immediately spendable, unlike the validator's attestation and block proposal rewards.
​
To exit and save, press Ctrl + X, then Y, thenEnter.
​
Update the configuration file with your current user's home path and user name.
sudo sed -i /etc/systemd/system/beacon-chain.service -e "s:<HOME>:${HOME}:g"
sudo sed -i /etc/systemd/system/beacon-chain.service -e "s:<USER>:${USER}:g"
​
Update file permissions.
sudo chmod 644 /etc/systemd/system/beacon-chain.service
​
Run the following to enable auto-start at boot time and then start your beacon node service.
sudo systemctl daemon-reload
sudo systemctl enable beacon-chain
sudo systemctl start beacon-chain
​
Nice work. Your beacon chain is now managed by the reliability and robustness of systemd.
​
​🧬
 4.5. Start the validator
​
Store your prysm-only password in a file and make it read-only.
This is required so that Prysm can decrypt and load your validators.
​
Replace <my_password_goes_here> with your prysm-only password.
echo '<my_password_goes_here>' > $HOME/.eth2validators/validators-password.txt
sudo chmod 600 $HOME/.eth2validators/validators-password.txt
​
Verify your password is correct.
cat $HOME/.eth2validators/validators-password.txt
​
Clear the bash history in order to remove traces of your prysm-only password.
shred -u ~/.bash_history && touch ~/.bash_history
​
​🛠
 Setup systemd service
​
Create a systemd unit file to define your validator.service configuration.
sudo nano /etc/systemd/system/validator.service
​
Paste the following configuration into the file.
# The eth validator service (part of systemd)
# file: /etc/systemd/system/validator.service
​
[Unit]
Description=eth validator service
Wants=network-online.target beacon-chain.service
After=network-online.target
​
[Service]
Type=simple
User=<USER>
Restart=on-failure
ExecStart=<HOME>/prysm/prysm.sh validator \
  --mainnet \
  --accept-terms-of-use \
  --wallet-password-file <HOME>/.eth2validators/validators-password.txt \
  --suggested-fee-recipient 0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS
​
[Install]
WantedBy=multi-user.target
​
Replace0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS with your own Ethereum address that you control. Tips are sent to this address and are immediately spendable, unlike the validator's attestation and block proposal rewards.
​
To exit and save, press Ctrl + X, then Y, thenEnter.
​
Update the configuration file with your current user's home path and user name.
sudo sed -i /etc/systemd/system/validator.service -e "s:<HOME>:${HOME}:g"
sudo sed -i /etc/systemd/system/validator.service -e "s:<USER>:${USER}:g"
​
Update file permissions.
sudo chmod 644 /etc/systemd/system/validator.service
​
Run the following to enable auto-start at boot time and then start your validator.
sudo systemctl daemon-reload
sudo systemctl enable validator
sudo systemctl start validator
​Lodestar is a Typescript implementation of the official Ethereum 2.0 specification by the ChainSafe.io team. In addition to the beacon chain client, the team is also working on 22 packages and libraries. A complete list can be found here. Finally, the Lodestar team is leading the Eth2 space in light client research and development and has received funding from the EF and Moloch DAO for this purpose.
​
​⚙
 4.1 Build Lodestar from source
​
Install curl and git.
sudo apt-get install gcc g++ make git curl -y
​
Install yarn.
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt update
sudo apt install yarn -y
​
Confirm yarn is installed properly.
yarn --version
# Should output version >= 1.22.4
​
Install nodejs.
curl -sL https://deb.nodesource.com/setup_18.x | sudo -E bash -
sudo apt-get install -y nodejs
​
Install and build Lodestar.
mkdir ~/git
cd ~/git
git clone -b stable https://github.com/chainsafe/lodestar.git
cd lodestar
yarn install --ignore-optional
yarn run build
​
This build process may take a few minutes.
​
Verify Lodestar was installed properly by displaying the version.
./lodestar --version
​
Setup a directory structure for Lodestar.
sudo mkdir -p /var/lib/lodestar
sudo chown $USER:$USER /var/lib/lodestar
​
​🔥
 4.2. Configure port forwarding and/or firewall
​
Specific to your networking setup or cloud provider settings, ensure your validator's firewall ports are open and reachable.
​
Lodestar consensus client will use port 9000
Execution client requires port 30303
​
​🎩
 4.3. Import validator key
./lodestar validator import \
  --network mainnet \
  --dataDir /var/lib/lodestar \
  --keystore $HOME/staking-deposit-cli/validator_keys
​
Enter your keystore password to import accounts.
​
Confirm your keys were imported properly.
./lodestar validator list \
  --network mainnet \
  --dataDir /var/lib/lodestar
​
WARNING: Do not import your validator keys into multiple validator clients and run them at the same time, or you might get slashed. If moving validators to a new setup or different validator client, ensure deletion of the previous validator keys before continuing.
​
​🏂
 4.4. Start the beacon chain and validator
​
Run the beacon chain automatically with systemd.
​
🛠 Setup systemd service
​
Create a systemd unit file to define yourbeacon-chain.service configuration.
sudo nano /etc/systemd/system/beacon-chain.service
​
Paste the following configuration into the file.
# The eth2 beacon chain service (part of systemd)
# file: /etc/systemd/system/beacon-chain.service
​
[Unit]
Description=eth2 beacon chain service
Wants=network-online.target
After=network-online.target
​
[Service]
Type=simple
User=<USER>
Restart=on-failure
WorkingDirectory=<HOME>/git/lodestar
ExecStart=<HOME>/git/lodestar/lodestar beacon \
  --network mainnet 