Guide: How to stake on ETH2 Mainnet with Lighthouse on Ubuntu

Nov 24 2020 Update: The new mainnet guide is located here.
Instructions below are now deprecated and for reference only.
​Lighthouse is an Eth2.0 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.
​🏁
 0. Prerequisites
​👩💻
 Skills for operating a eth2 validator and beacon node
As a validator for eth2, you will typically have the following abilities:
operational knowledge of how to set up, run and maintain a eth2 beacon node and validator continuously
a long term commitment to maintain your validator 24/7/365
basic operating system skills
have learned the essentials by watching 'Intro to Eth2 & Staking for Beginners' by Superphiz​
have passed or is actively enrolled in the Eth2 Study Master course​
and have read the 8 Things Every Eth2 validator should know.​
****🎗
 Minimum Setup Requirements
Operating system: 64-bit Linux (i.e. Ubuntu 20.04 LTS)
Processor: Dual core CPU, Intel Core i5–760 or AMD FX-8100 or better
Memory: 8GB RAM
Storage: 20GB SSD
Internet: Broadband internet connection with speeds at least 1 Mbps.
Power: Reliable electrical power.
ETH balance: at least 32 ETH and some ETH for deposit transaction fees
Wallet: Metamask installed
​🏋♀
 Recommended Hardware Setup
Operating system: 64-bit Linux (i.e. Ubuntu 20.04 LTS)
Processor: Quad core CPU, Intel Core i7–4770 or AMD FX-8310 or better
Memory: 16GB RAM or more
Storage: 1TB SSD or more
Internet: Broadband internet connections with speeds at least 10 Mbps
Power: Reliable electrical power with uninterruptible power supply (UPS)
ETH balance: at least 32 ETH and some ETH for deposit transaction fees
Wallet: Metamask installed
​✨
 Pro Validator Tip: Highly recommend you begin with a brand new instance of an OS, VM, and/or machine. Avoid headaches by NOT reusing testnet keys, wallets, or databases for your mainnet validator.
​🔓
 Recommended eth2 validator Security Best Practices
If you need ideas or a reminder on how to secure your validator, refer to
https://github.com/coincashew/coincashew/blob/master/coins/overview-eth/broken-reference/README.md
​🛠
 Setup Ubuntu
If you need to install Ubuntu, refer to
2. Install Ubuntu
​🎭
 Setup Metamask
If you need to install Metamask, refer to
MetaMask: Ethereum
​🌱
 1. Buy/exchange or consolidate ETH
Every 32 ETH you own allows you to make 1 validator. You can run thousands of validators with your beacon node.
Your ETH (or multiples of 32 ETH) should be consolidated into a single address accessible with Metamask.
If you need to buy/exchange or top up your ETH to a multiple of 32, check out:
Guide: How to buy ETH
​👩💻
2. Signup to be a validator at the Launchpad
1.Install dependencies, the ethereum foundation deposit tool and generate your two sets of key pairs.
Each validator will have two sets of key pairs. A signing key and a withdrawal key. These keys are derived from a single mnemonic phrase. Learn more about keys.​
You have the choice of downloading the pre-built ethereum foundation deposit tool or building it from source.
Pre-built eth2deposit-cli
Build from source code
Advanced - Most Secure
Download eth2deposit-cli.
cd $HOME
wget https://github.com/ethereum/eth2.0-deposit-cli/releases/download/v1.0.0/eth2deposit-cli-9310de0-linux-amd64.tar.gz
Verify the SHA256 Checksum matches the checksum on the releases page.
sha256sum eth2deposit-cli-9310de0-linux-amd64.tar.gz 
# SHA256 should be
# b09da136895a7f77a4b430924ea2ae5827fa47b2bf444c4ea6fcfac5b04b8c8a
Extract the archive.
tar -xvf eth2deposit-cli-9310de0-linux-amd64.tar.gz
cd eth2deposit-cli-9310de0-linux-amd64
Make a new mnemonic.
./deposit new-mnemonic --chain mainnet
Install dependencies.
sudo apt update
sudo apt install python3-pip git -y
Download source code and install.
mkdir ~/git
cd ~/git
git clone https://github.com/ethereum/eth2.0-deposit-cli.git
cd eth2.0-deposit-cli
sudo ./deposit.sh install
Make a new mnemonic.
./deposit.sh new-mnemonic --chain mainnet
​🔥
[ Optional ] Pro Security Tip: Run the eth2deposit-cli tool and generate your mnemonic seed for your validator keys on an air-gapped offline machine.
You can copy via USB key the pre-built eth2deposit-cli binaries from an online machine to an air-gapped offline machine.
Protects against key-logging attacks, malware/virus based attacks and other firewall or security exploits.
Physically isolated from the rest of your network.
Must not have a network connection, wired or wireless.
Is not a VM on a machine with a network connection.
Learn more about air-gapping at wikipedia.
2. Follow the prompts and pick a password. Write down your mnemonic and keep this safe and offline.
3. Follow the steps at https://launchpad.ethereum.org/ while skipping over the steps you already just completed. Study the eth2 phase 0 overview material. Understanding eth2 is the key to success!
4. Back on the launchpad website, upload yourdeposit_data-#########.json found in the validator_keys directory.
5. Connect to the launchpad with your Metamask wallet, review and accept terms.
6. Confirm the transaction(s). There's one deposit transaction of 32 ETH for each validator.
Your transaction is sending and depositing your ETH to the official ETH2 deposit contract address.​
Check, double-check, triple-check that the official Eth2 deposit contract address is correct.0x00000000219ab540356cBB839Cbe05303d7705Fa​
Be sure to write down or record your mnemonic seed offline. Not email. Not cloud.
Make offline backups, such as to a USB key, of your validator_keys` ``` directory.
​🛸
3. Install a ETH1 node
Ethereum 2.0 requires a connection to Ethereum 1.0 in order to monitor for 32 ETH validator deposits. Hosting your own Ethereum 1.0 node is the best way to maximize decentralization and minimize dependency on third parties such as Infura.
The subsequent steps assume you have completed the best practices security guide.
Your choice of either OpenEthereum, Geth, Besu or Nethermind.
OpenEthereum (Parity)
Geth
Besu
Nethermind
Minimum Hardware Setup
​🤖
 Install and run OpenEthereum.
mkdir ~/openethereum && cd ~/openethereum
wget https://github.com/openethereum/openethereum/releases/download/v3.0.1/openethereum-linux-v3.0.1.zip
unzip openethereum*.zip
chmod +x openethereum
rm openethereum*.zip
​ ⚙
 Setup and configure systemd
Run the following to create a unit file to define your eth1.service configuration.
cat > $HOME/eth1.service << EOF 
[Unit]
Description     = openethereum eth1 service
Wants           = network-online.target
After           = network-online.target 
​
[Service]
User            = $(whoami)
WorkingDirectory= /home/$(whoami)/openethereum
ExecStart       = /home/$(whoami)/openethereum/openethereum --chain foundation
Restart         = on-failure
​
[Install]
WantedBy	= multi-user.target
EOF
Move the unit file to /etc/systemd/system and give it permissions.
sudo mv $HOME/eth1.service /etc/systemd/system/eth1.service
sudo chmod 644 /etc/systemd/system/eth1.service
Run the following to enable auto-start at boot time.
sudo systemctl daemon-reload
sudo systemctl enable eth1
​⛓
 Start OpenEthereum on mainnet.
sudo systemctl start eth1
​🧬
 Install from the repository.
sudo add-apt-repository -y ppa:ethereum/ethereum
sudo apt-get update -y
sudo apt-get install ethereum -y
​⚙
 Setup and configure systemd
Run the following to create a unit file to define your eth1.service configuration.
cat > $HOME/eth1.service << EOF 
[Unit]
Description     = geth eth1 service
Wants           = network-online.target
After           = network-online.target 
​
[Service]
User            = $(whoami)
ExecStart       = /usr/bin/geth --http
Restart         = on-failure
​
[Install]
WantedBy	= multi-user.target
EOF
Move the unit file to /etc/systemd/system and give it permissions.
sudo mv $HOME/eth1.service /etc/systemd/system/eth1.service
sudo chmod 644 /etc/systemd/system/eth1.service
Run the following to enable auto-start at boot time.
sudo systemctl daemon-reload
sudo systemctl enable eth1
​⛓
 Start geth on mainnet.
sudo systemctl start eth1
​🧬
 Install java dependency.
sudo apt install openjdk-11-jdk
​🌜
 Download and unzip Besu.
cd
wget -O besu.tar.gz https://bintray.com/hyperledger-org/besu-repo/download_file?file_path=besu-1.5.0.tar.gz
tar -xvf besu.tar.gz
rm besu.tar.gz
mv besu-1.5.0 besu
​⚙
 Setup and configure systemd
Run the following to create a unit file to define your eth1.service configuration.
cat > $HOME/eth1.service << EOF 
[Unit]
Description     = openethereum eth1 service
Wants           = network-online.target
After           = network-online.target 
​
[Service]
User            = $(whoami)
WorkingDirectory= /home/$(whoami)/besu/bin
ExecStart       = /home/$(whoami)/besu/bin/besu --data-path="$HOME/.ethereum_besu"
Restart         = on-failure
​
[Install]
WantedBy	= multi-user.target
EOF
Move the unit file to /etc/systemd/system and give it permissions.
sudo mv $HOME/eth1.service /etc/systemd/system/eth1.service
sudo chmod 644 /etc/systemd/system/eth1.service
Run the following to enable auto-start at boot time.
sudo systemctl daemon-reload
sudo systemctl enable eth1
​⛓
 Start besu on mainnet.
sudo systemctl start eth1
​⚙
 Install dependencies.
sudo apt-get update && sudo apt-get install libsnappy-dev libc6-dev libc6 unzip -y
​🌜
 Download and unzip Nethermind.
mkdir ~/nethermind && cd ~/nethermind
wget -O nethermind.zip https://nethdev.blob.core.windows.net/builds/nethermind-linux-amd64-1.8.77-9d3a58a.zip
unzip nethermind.zip
rm nethermind.zip
​🛸
 Launch Nethermind.
./Nethermind.Launcher
Select Ethereum Node
Select Ethereum (mainnet) then select Fast sync
Yes to enable web3 / JSON RPC
Accept default IP
Skip ethstats registration
​🚧
 Untested - TBD - Work in progress 🚧
​
Use a third party by signing up for an API access key at https://infura.io/​
Syncing the eth1 node could take up to 24 hour.
Your eth1 node is fully sync'd when these events occur.
OpenEthereum: ``Imported #<block number>
Geth: ``Imported new chain segment
Besu: ``Imported #<block number>
Nethermind: ``No longer syncing Old Headers
​🛠
 Helpful eth1.service commands
​​ 🗒
 To view and follow eth1 logs
journalctl -u eth1 -f
​🗒
 To stop eth1 service
sudo systemctl stop eth1
​🛑
 Before continuing the rest of this guide, we recommend you wait until closer to Dec 1st as the lighthouse code is rapidly preparing for mainnet. 🚧
​
​👩🌾
 4. Install rust
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
In case of compilation errors, runrustup update
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 install -y git gcc g++ make cmake pkg-config libssl-dev llvm-dev libclang-dev clang
​💡
 5. Install Lighthouse
cd ~/git
git clone https://github.com/sigp/lighthouse.git
cd lighthouse
make
This build process may take up to an hour.
Verify lighthouse was installed properly by checking the version number.
lighthouse --version
​🎩
 6. Import validator key
Select the tab corresponding to how you installed eth2deposit-cli.
Pre-built eth2deposit-cli
Built from source code
lighthouse account validator import --directory=$HOME/eth2deposit-cli-9310de0-linux-amd64/validator_keys
lighthouse account validator import --directory=$HOME/git/eth2.0-deposit-cli/validator_keys
Enter your keystore's password to import accounts.
WARNING: DO NOT USE THE ORIGINAL KEYSTORES TO VALIDATE WITH ANOTHER CLIENT, OR YOU WILL GET SLASHED.
​🔥
 7. 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 beacon chain requires port 9000 for tcp and udp
eth1 node requires port 30303 for tcp and udp
****✨
 Port Forwarding Tip: You'll need to forward and open ports to your validator. Verify it's working with https://www.yougetsignal.com/tools/open-ports/ or https://canyouseeme.org/ .
​🏂
 8. Start the beacon chain
If you participated in any of the prior test nets, you need to clear the database.
rm -rf $HOME/.lighthouse
Your choice of running a beacon chain manually from command line or automatically with systemd.
Systemd - Automated
CLI - Manual
🍰 Benefits of using systemd for your beacon chain
1.Auto-start your beacon chain when the computer reboots due to maintenance, power outage, etc.
2.Automatically restart crashed beacon chain processes.
3.Maximize your beacon chain up-time and performance.
​🛠
 Setup Instructions
Run the following to create a unit file to define yourbeacon-chain.service configuration.
cat > $HOME/beacon-chain.service << EOF 
# 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]
User            = $(whoami)
WorkingDirectory= /home/$(whoami)/git/lighthouse
ExecStart       = $(which lighthouse) bn --staking --metrics
Restart         = on-failure
​
[Install]
WantedBy	= multi-user.target
EOF
Move the unit file to /etc/systemd/system and give it permissions.
sudo mv $HOME/beacon-chain.service /etc/systemd/system/beacon-chain.service
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. Below are some commands for using systemd.
​🛠
 Some helpful systemd commands
​✅
 Check whether the beacon chain is active
sudo systemctl is-active beacon-chain
​🔎
 View the status of the beacon chain
sudo systemctl status beacon-chain
​🔄
 Restarting the beacon chain
sudo systemctl reload-or-restart beacon-chain
​🛑
 Stopping the beacon chain
sudo systemctl stop beacon-chain
🗄 Viewing and filtering logs
journalctl --unit=beacon-chain --since=yesterday
journalctl --unit=beacon-chain --since=today
journalctl --unit=beacon-chain --since='2020-12-01 00:00:00' --until='2020-12-02 12:00:00'
In a new terminal, start the beacon chain.
lighthouse bn --staking --metrics
The --metrics flag enables reporting on port 5054 and will be monitored with Prometheus.
Allow the beacon chain to fully sync with eth1 chain before continuing.
Continue when you see the "Beacon chain initialized" message.
​🧬
 9. Start the validator
Your choice of running a validator manually from command line or automatically with systemd.
Systemd - Automated
CLI - Manual
🍰 Benefits of using systemd for your validator
1.Auto-start your validator when the computer reboots due to maintenance, power outage, etc.
2.Automatically restart crashed validator processes.
3.Maximize your validator up-time and performance.
​🛠
 Setup Instructions
Run the following to create a unit file to define yourvalidator.service configuration.
cat > $HOME/validator.service << EOF 
# The eth2 validator service (part of systemd)
# file: /etc/systemd/system/validator.service 
​
[Unit]
Description     = eth2 validator service
Wants           = network-online.target beacon-chain.service
After           = network-online.target 
​
[Service]
User            = $(whoami)
WorkingDirectory= /home/$(whoami)/git/lighthouse
ExecStart       = $(which lighthouse) vc
Restart         = on-failure
​
[Install]
WantedBy	= multi-user.target
EOF
Move the unit file to /etc/systemd/system and give it permissions.
sudo mv $HOME/validator.service /etc/systemd/system/validator.service
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. Below are some commands for using systemd.
​🛠
 Some helpful systemd commands
​✅
 Check whether the validator is active
sudo systemctl is-active validator
​🔎
 View the status of the validator
sudo systemctl status validator
​🔄
 Restarting the validator
sudo systemctl reload-or-restart validator
​🛑
 Stopping the validator
sudo systemctl stop validator
🗄 Viewing and filtering logs
journalctl --unit=validator --since=yesterday
journalctl --unit=validator --since=today
journalctl --unit=validator --since='2020-12-01 00:00:00' --until='2020-12-02 12:00:00'
In a new terminal, start the validator.
lighthouse vc
Verify that your validator public key appears in the logs. Example below:
INFO Enabled validator       voting_pubkey: 0x2374.....7121
Validator client - Responsible for producing new blocks and attestations in the beacon chain and shard chains.
Beacon chain client - Responsible for managing the state of the beacon chain, validator shuffling, and more.
Congratulations. Once your beacon chain is sync'd, validator up and running, you just wait for activation. This process can take 24+ hours. When you're assigned, your validator will begin creating and voting on blocks while earning staking rewards.
Use beaconcha.in and register an account to create alerts and track your validator's performance.
​🕒
 10. Time Synchronization
Because beacon chain relies on accurate times to perform attestations and produce blocks, your computer's time must be accurate to real NTP or NTS time within 0.5 seconds.
Setup Chrony with the following guide.
https://github.com/coincashew/coincashew/blob/master/coins/overview-eth/broken-reference/README.md
chrony is an implementation of the Network Time Protocol and helps to keep your computer's time synchronized with NTP.
​🔎
 11. Monitoring your validator with Grafana and Prometheus
Prometheus is a monitoring platform that collects metrics from monitored targets by scraping metrics HTTP endpoints on these targets. Official documentation is available here. Grafana is a dashboard used to visualize the collected data.
​🐣
 11.1 Installation
Install prometheus and prometheus node exporter.
sudo apt-get install -y prometheus prometheus-node-exporter 
Install grafana.
wget -q -O - https://packages.grafana.com/gpg.key | sudo apt-key add -
echo "deb https://packages.grafana.com/oss/deb stable main" > grafana.list
sudo mv grafana.list /etc/apt/sources.list.d/grafana.list
sudo apt-get update && sudo apt-get install -y grafana
Enable services so they start automatically.
sudo systemctl enable grafana-server.service
sudo systemctl enable prometheus.service
sudo systemctl enable prometheus-node-exporter.service
Update prometheus.yml located in /etc/prometheus/prometheus.yml
cat > $HOME/prometheus.yml << EOF
global:
  scrape_interval:     15s # By default, scrape targets every 15 seconds.
​
  # Attach these labels to any time series or alerts when communicating with
  # external systems (federation, remote storage, Alertmanager).
  external_labels:
    monitor: 'codelab-monitor'
​
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
   - job_name: 'node_exporter'
     static_configs:
       - targets: ['localhost:9100']
   - job_name: 'nodes'
     metrics_path: /metrics    
     static_configs:
       - targets: ['localhost:5054']
EOF
sudo mv $HOME/prometheus.yml /etc/prometheus/prometheus.yml
Finally, restart the services.
sudo systemctl restart grafana-server.service
sudo systemctl restart prometheus.service
sudo systemctl restart prometheus-node-exporter.service
Verify that the services are running properly:
sudo systemctl status grafana-server.service prometheus.service prometheus-node-exporter.service
****💡
 Reminder: Ensure port 3000 is open on the firewall and/or port forwarded if you intend to view monitoring info from a different machine.
​📶
11.2 Setting up Grafana Dashboards
1.Open http://localhost:3000 or http://<your validator's ip address>:3000 in your local browser.
2.Login with admin / admin
3.Change password
4.Click the configuration gear icon, then Add data Source
5.Select Prometheus
6.Set Name to "Prometheus"
7.Set URL to http://localhost:9090
8.Click Save & Test
9.Download and save this json file.****
10.Click Create + icon > Import
11.Add dashboard by Upload JSON file
12.Click the Import button.
​⚠
11.3 Setup Alert Notifications
Setup alerts to get notified if your validators go offline.
Get notified of problems with your validators. Choose between email, telegram, discord or slack.
Email Notifications
Telegram Notifications
Discord Notifications
Slack Notifications
1.Visit https://beaconcha.in/​
2.Sign Up **** for an account
3.Verify your email
4.Search for your validator's public address
5.Add validators to your watchlist by clicking the bookmark symbol.
1.On the menu of Grafana, select Notification channels under the bell icon. 
​
2.Click on Add channel.
3.Give the notification channel a name.
4.Select Telegram from the Type list.
5.To complete the Telegram API settings, a Telegram channel and bot are required. For instructions on setting up a bot with @Botfather, see this section of the Telegram documentation.
6.Once completed, invite the bot to the newly created channel.
1.On the menu of Grafana, select Notification channels under the bell icon. 
​
2.Click on Add channel.
3.Add a name to the notification channel.
4.Select Discord from the Type list.
5.To complete the set up, a Discord server (and a text channel available) as well as a Webhook URL are required. For instructions on setting up a Discord's Webhooks, see this section of their documentation.
6.Enter the Webhook URL in the Discord notification settings panel.
7.Click Send Test, which will push a confirmation message to the Discord channel.
1.On the menu of Grafana, select Notification channels under the bell icon. 
​
2.Click on Add channel.
3.Add a name to the notification channel.
4.Select Slack from the Type list.
5.For instructions on setting up a Slack's Incoming Webhooks, see this section of their documentation.
6.Enter the Slack Incoming Webhook URL in the URL field.
7.Click Send Test, which will push a confirmation message to the Slack channel.
​🎉
 Congrats on setting up your validator! You're good to go on eth2.0.
Did you find our guide useful? Let us know with a tip and we'll keep updating it.
Use cointr.ee to find our donation addresses. 🙏
​
Any feedback and all pull requests much appreciated. 😊
​
Hang out and chat with fellow stakers on telegram @ https://t.me/coincashew 🌛
​
​🧙♂
 12. Updating Lighthouse
cd ~/git/lighthouse
git pull
make
Restart beacon chain and validator as per normal operating procedures.
Systemd - Automated
CLI - Manual
sudo systemctl reload-or-restart beacon-chain
sudo systemctl reload-or-restart validator
killall lighthouse
lighthouse vc
lighthouse bn --staking --metrics
​🧩
 13. Reference Material
Appreciate the hard work done by the fine folks at the following links which served as a foundation for creating this guide.
Join the Lighthouse (Ethereum 2.0) Discord Server!
Discord
https://launchpad.ethereum.org/
ethereum
Introduction - Lighthouse Book
​🎉
 14. Bonus links
​🌰
 CoinCashew Guides for other ETH2 Clients
Guide: How to stake on ETH2 Mainnet with Teku on Ubuntu
Guide: How to stake on ETH2 Mainnet with Prysm on Ubuntu
Guide: How to stake on ETH2 Mainnet with Nimbus on Ubuntu
Guide: How to stake on ETH2 Medalla Testnet with Lodestar on Ubuntu
​🧱
 ETH2 Block Explorers
Ethereum 2.0 Beacon Chain (Phase 0) Block Chain Explorer - Index - beaconcha.in - 2022
beaconcha.in
Mainnet | Beacon Chain Explorer (Phase 0) for Ethereum 2.0
Etherscan Beacon Chain (Phase 0) Ethereum 2.0 Explorer
​🗒
 Latest Eth2 Info
What’s New in Eth2 - HackMD
HackMD
r/ethstaker
reddit
Home
Custom Discord Invite Links
INVITE.GG
​🔥
 15. Additional Useful Tips
​🛑
 15.1 Voluntary exit a validator
Use this command to signal your intentions to stop validating with your validator. This means you no longer want to stake with your validator and want to turn off your node.
Voluntary exiting takes a minimum of 2048 epochs (or ~9days). There is a queue to exit and a delay before your validator is finally exited.
Once a validator is exited in phase 0, this is non-reversible and you can no longer restart validating again.
Your funds will not be available for withdrawal until phase 1.5 or later.
After your validator leaves the exit queue and is truely exited, it is safe to turn off your beacon node and validator.
lighthouse account validator exit \
--keystore $HOME/.lighthouse/mainnet/validators \
--beacon-node http://localhost:5052
​🔐
 15.2 Verify your mnemonic phrase
Using the eth2deposit-cli tool, ensure you can regenerate the same eth2 key pairs by restoring your validator_keys
./deposit existing-mnemonic --chain mainnet
When the pubkey is identical, this means your keystore file you correctly verified your mnemonic phrase. Other fields will be different because of salting.
​🤖
 15.3 Add additional validators
Using the eth2deposit-cli tool, you can add more validators by creating a new deposit data file and validator_keys
For example, in case we originally created 3 validators but now wish to add 5 more validators, we could use the following command.
./deposit existing-mnemonic --validator_start_index 3 --num_validators 5 --chain mainnet
Complete the steps of uploading the deposit_data-#########.json to the launch pad site.