| description |
|---|
Become a validator and help secure eth2, a proof-of-stake blockchain. Anyone with 32 ETH can join. |
{% hint style="success" %} As of Jan 5 2021, this guide is updated for mainnet. π {% endhint %}
β¨ For the testnet guide, please click here.
****π 2020-12 Update: Thanks to all Gitcoin contributors, where you can contribute via quadratic funding and make a big impact. Funding complete! Thank you!π
{% embed url="https://gitcoin.co/grants/1653/eth2-staking-guides-by-coincashew" %}
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.
- Operating system: 64-bit Linux (i.e. Ubuntu 20.04 LTS Server or Desktop)
- Processor: Dual core CPU, Intel Core i5β760 or AMD FX-8100 or better
- Memory: 8GB RAM
- Storage: 128GB 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
- Operating system: 64-bit Linux (i.e. Ubuntu 20.04 LTS Server or Desktop)
- 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 without data limit.
- 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
{% hint style="success" %} β¨ 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 validator. {% endhint %}
If you need ideas or a reminder on how to secure your validator, refer to
{% page-ref page="../guide-or-security-best-practices-for-a-eth2-validator-beaconchain-node.md" %}
If you need to install Ubuntu Server, refer to
{% embed url="https://ubuntu.com/tutorials/install-ubuntu-server\#1-overview" %}
Or Ubuntu Desktop,
{% page-ref page="../../overview-xtz/guide-how-to-setup-a-baker/install-ubuntu.md" %}
If you need to install Metamask, refer to
{% page-ref page="../../../wallets/browser-wallets/metamask-ethereum.md" %}
{% hint style="info" %} At the end of this guide, you will build a node that hosts three main components: a validator client, a beacon chain client and an eth1 node.
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.
Eth1 node - Supplies incoming validator deposits from the eth1 mainnet chain to the beacon chain client.
Note: Teku and Nimbus combines both clients into one process. {% endhint %}
{% hint style="info" %} Every 32 ETH you own allows you to make 1 validator. You can run thousands of validators with your beacon node. {% endhint %}
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:
{% page-ref page="../guide-how-to-buy-eth.md" %}
- Install dependencies, the ethereum foundation deposit tool and generate your two sets of key pairs.
{% hint style="info" %} 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. {% endhint %}
You have the choice of downloading the pre-built ethereum foundation deposit tool or building it from source.
{% tabs %} {% tab title="Build from source code" %} Install dependencies.
sudo apt update
sudo apt install python3-pip git -y
Download source code and install.
cd $HOME
git clone https://github.com/ethereum/eth2.0-deposit-cli.git eth2deposit-cli
cd eth2deposit-cli
sudo ./deposit.sh install
Make a new mnemonic.
./deposit.sh new-mnemonic --chain mainnet
{% endtab %}
{% tab title="Pre-built eth2deposit-cli" %} Download eth2deposit-cli.
cd $HOME
wget https://github.com/ethereum/eth2.0-deposit-cli/releases/download/v1.1.0/eth2deposit-cli-ed5a6d3-linux-amd64.tar.gzVerify the SHA256 Checksum matches the checksum on the releases page.
echo "2107f26f954545f423530e3501ae616c222b6bf77774a4f2743effb8fe4bcbe7 *eth2deposit-cli-ed5a6d3-linux-amd64.tar.gz" | shasum -a 256 --checkExample valid output:
eth2deposit-cli-ed5a6d3-linux-amd64.tar.gz: OK
{% hint style="danger" %} Only proceed if the sha256 check passes with OK! {% endhint %}
Extract the archive.
tar -xvf eth2deposit-cli-ed5a6d3-linux-amd64.tar.gz
mv eth2deposit-cli-ed5a6d3-linux-amd64 eth2deposit-cli
rm eth2deposit-cli-ed5a6d3-linux-amd64.tar.gz
cd eth2deposit-cli
Make a new mnemonic.
./deposit new-mnemonic --chain mainnet
{% endtab %}
{% tab title="Advanced - Most Secure" %} {% hint style="warning" %} π₯**[ Optional ] Pro Security Tip**: Run the eth2deposit-cli tool and generate your mnemonic seed for your validator keys on an air-gapped offline machine booted from usb. {% endhint %}
Follow this ethstaker.cc exclusive for the low down on making a bootable usb.
{% embed url="https://www.youtube.com/watch?v=DTR3PzRRtYU" %}
{% embed url="https://www.youtube.com/watch?v=C97\_6MrufCE" %}
You can copy via USB key the pre-built eth2deposit-cli binaries from an online machine to an air-gapped offline machine booted from usb. Make sure to disconnect the ethernet cable and/or WIFI. {% endtab %} {% endtabs %}
- Follow the prompts and pick a KEYSTORE password. This password encrypts your keystore files. Write down your mnemonic and keep this safe and offline.
{% hint style="warning" %} ****π§ Caution: Only deposit the 32 ETH per validator if you are confident your ETH1 node and ETH2 validator will be fully synched and ready to perform validator duties. You can return later to launchpad with your deposit-data to finish the next steps. {% endhint %}
-
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!
-
Back on the launchpad website, upload your
deposit_data-#########.jsonfound in thevalidator_keysdirectory. -
Connect to the launchpad with your Metamask wallet, review and accept terms.
-
Confirm the transaction(s). There's one deposit transaction of 32 ETH for each validator.
{% hint style="info" %} 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
{% endhint %}
{% hint style="danger" %} ****π₯ Critical Crypto Reminder: Keep your mnemonic, keep your ETH. π
- Write down your mnemonic seed offline. Not email. Not cloud.
- Multiple copies are better. Best stored in a metal seed.
- The withdrawal keys will be generated from this mnemonic in the future.
- Make offline backups, such as to a USB key, of your
validator_keysdirectory. {% endhint %}
{% hint style="info" %} 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. {% endhint %}
{% hint style="warning" %} The subsequent steps assume you have completed the best practices security guide.
π Do not run your processes as ROOT user. π± {% endhint %}
Your choice of either OpenEthereum, Geth, Besu, Nethermind or Infura.
{% tabs %} {% tab title="OpenEthereum (Parity)" %} {% hint style="info" %} OpenEthereum - It's ****goal is to be the fastest, lightest, and most secure Ethereum client using the Rust programming language. OpenEthereum is licensed under the GPLv3 and can be used for all your Ethereum needs. {% endhint %}
sudo apt-get update
sudo apt-get install curl jq unzip -y
Review the latest release at https://github.com/openethereum/openethereum/releases
Automatically download the latest linux release, un-zip, add execute permissions and cleanup.
mkdir $HOME/openethereum
cd $HOME/openethereum
curl -s https://api.github.com/repos/openethereum/openethereum/releases/latest | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux | xargs wget -q --show-progress
unzip -o 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.
Simply copy/paste the following.
cat > $HOME/eth1.service << EOF
[Unit]
Description = openethereum eth1 service
Wants = network-online.target
After = network-online.target
[Service]
User = $(whoami)
ExecStart = $(echo $HOME)/openethereum/openethereum --metrics --metrics-port=6060
Restart = on-failure
RestartSec = 3
[Install]
WantedBy = multi-user.target
EOF{% hint style="info" %} Nimbus Specific Configuration: Add the following flag to the ExecStart line.
--ws-origins=all{% endhint %}
Move the unit file to /etc/systemd/system and give it permissions.
sudo mv $HOME/eth1.service /etc/systemd/system/eth1.servicesudo chmod 644 /etc/systemd/system/eth1.serviceRun the following to enable auto-start at boot time.
sudo systemctl daemon-reload
sudo systemctl enable eth1
sudo systemctl start eth1
{% endtab %}
{% tab title="Geth" %} {% hint style="info" %} Geth - Go Ethereum is one of the three original implementations (along with C++ and Python) of the Ethereum protocol. It is written in Go, fully open source and licensed under the GNU LGPL v3. {% endhint %}
Review the latest release notes at https://github.com/ethereum/go-ethereum/releases
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.
Simply copy/paste the following.
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 --metrics --pprof
Restart = on-failure
RestartSec = 3
[Install]
WantedBy = multi-user.target
EOF{% hint style="info" %} Nimbus Specific Configuration: Add the following flag to the ExecStart line.
--ws{% endhint %}
Move the unit file to /etc/systemd/system and give it permissions.
sudo mv $HOME/eth1.service /etc/systemd/system/eth1.servicesudo chmod 644 /etc/systemd/system/eth1.serviceRun the following to enable auto-start at boot time.
sudo systemctl daemon-reload
sudo systemctl enable eth1
sudo systemctl start eth1
{% endtab %}
{% tab title="Besu" %} {% hint style="info" %} Hyperledger Besu is an open-source Ethereum client designed for demanding enterprise applications requiring secure, high-performance transaction processing in a private network. It's developed under the Apache 2.0 license and written in Java. {% endhint %}
sudo apt update
sudo apt install openjdk-11-jdk -y
Review the latest release at https://github.com/hyperledger/besu/releases
File can be downloaded from https://dl.bintray.com/hyperledger-org/besu-repo
cd
wget -O besu.tar.gz https://dl.bintray.com/hyperledger-org/besu-repo/besu-20.10.1.tar.gz
tar -xvf besu.tar.gz
rm besu.tar.gz
mv besu* besu
β Setup and configure systemd
Run the following to create a unit file to define your eth1.service configuration.
Simply copy/paste the following.
cat > $HOME/eth1.service << EOF
[Unit]
Description = besu eth1 service
Wants = network-online.target
After = network-online.target
[Service]
User = $(whoami)
ExecStart = $(echo $HOME)/besu/bin/besu --metrics-enabled --rpc-http-enabled --data-path="$HOME/.besu"
Restart = on-failure
RestartSec = 3
[Install]
WantedBy = multi-user.target
EOFMove the unit file to /etc/systemd/system and give it permissions.
sudo mv $HOME/eth1.service /etc/systemd/system/eth1.servicesudo chmod 644 /etc/systemd/system/eth1.serviceRun the following to enable auto-start at boot time.
sudo systemctl daemon-reload
sudo systemctl enable eth1
sudo systemctl start eth1
{% endtab %}
{% tab title="Nethermind" %} {% hint style="info" %} Nethermind is a flagship Ethereum client all about performance and flexibility. Built on .NET core, a widespread, enterprise-friendly platform, Nethermind makes integration with existing infrastructures simple, without losing sight of stability, reliability, data integrity, and security. {% endhint %}
sudo apt-get update
sudo apt-get install curl libsnappy-dev libc6-dev jq libc6 unzip -y
Review the latest release at https://github.com/NethermindEth/nethermind/releases
Automatically download the latest linux release, un-zip and cleanup.
mkdir $HOME/nethermind
chmod 775 $HOME/nethermind
cd $HOME/nethermind
curl -s https://api.github.com/repos/NethermindEth/nethermind/releases/latest | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux | xargs wget -q --show-progress
unzip -o nethermind*.zip
rm nethermind*linux*.zipβ Setup and configure systemd
Run the following to create a unit file to define your eth1.service configuration.
Simply copy/paste the following.
cat > $HOME/eth1.service << EOF
[Unit]
Description = nethermind eth1 service
Wants = network-online.target
After = network-online.target
[Service]
User = $(whoami)
ExecStart = $(echo $HOME)/nethermind/Nethermind.Runner --baseDbPath $HOME/.nethermind --Metrics.Enabled true --JsonRpc.Enabled true --Sync.DownloadBodiesInFastSync true --Sync.DownloadReceiptsInFastSync true --Sync.AncientBodiesBarrier 11052984 --Sync.AncientReceiptsBarrier 11052984
Restart = on-failure
RestartSec = 3
[Install]
WantedBy = multi-user.target
EOFMove the unit file to /etc/systemd/system and give it permissions.
sudo mv $HOME/eth1.service /etc/systemd/system/eth1.servicesudo chmod 644 /etc/systemd/system/eth1.serviceRun the following to enable auto-start at boot time.
sudo systemctl daemon-reload
sudo systemctl enable eth1
sudo systemctl start eth1
{% hint style="info" %}
Note about Metric Error messages: You will see these until prometheus pushergateway is setup in section 6. Error in MetricPusher: System.Net.Http.HttpRequestException: Connection refused
{% endhint %}
{% endtab %}
{% tab title="Minimum Hardware Setup (Infura)" %} {% hint style="info" %} Infura is suitable for limited disk space setups. Always run your own full eth1 node when possible. {% endhint %}
Sign up for an API access key at https://infura.io/
- Sign up for a free account.
- Confirm your email address.
- Visit your dashboard https://infura.io/dashboard
- Create a project, give it a name.
- Select Mainnet as the ENDPOINT
- Follow the specific configuration for your eth2 client found below.
{% hint style="success" %} Alternatively use a free Ethereum node such as Chainstack at https://ethereumnodes.com/ {% endhint %}
- When creating your systemd's unit file, update the
--web-urlparameter with this endpoint. - Copy the websocket endpoint. Starts with
wss:// - Save this for step 4, configuring your eth2 node.
#example
--web3-url=<your wss:// infura endpoint>- After creating the
teku.yamllocated in/etc/teku/teku.yaml, update the--eth1-endpointparameter with this endpoint. - Copy the http endpoint. Starts with
http:// - Save this for step 4, configuring your eth2 node.
#example
eth1-endpoint: <your https:// infura endpoint>- When creating your beacon chain systemd unit file, add the
--eth1-endpointparameter with this endpoint. - Copy the https endpoint. Starts with
https:// - Save this for step 4, configuring your eth2 node.
#example
--eth1-endpoint=<your https:// infura endpoint>- When creating your beacon chain systemd unit file, update the
--http-web3providerparameter with this endpoint. - Copy the https endpoint. Starts with
https:// - Save this for step 4, configuring your eth2 node.
#example
--http-web3provider=<your https:// infura endpoint>{% endtab %} {% endtabs %}
{% hint style="info" %} Syncing an eth1 node can take up to 1 week. On high-end machines with gigabit internet, expect syncing to take less than a day. {% endhint %}
{% hint style="success" %} Your eth1 node is fully sync'd when these events occur.
OpenEthereum:Imported #<block number>Geth:Imported new chain segmentBesu:Imported #<block number>Nethermind:No longer syncing Old Headers{% endhint %}
ββ π To view and follow eth1 logs
journalctl -u eth1 -f
π To stop eth1 service
sudo systemctl stop eth1
Your choice of Lighthouse, Nimbus, Teku, Prysm or Lodestar.
{% tabs %} {% tab title="Lighthouse" %} {% hint style="info" %} 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. {% endhint %}
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | shEnter '1' to proceed with the default install.
Update your environment variables.
echo export PATH="$HOME/.cargo/bin:$PATH" >> ~/.bashrc
source ~/.bashrcInstall rust dependencies.
sudo apt-get update
sudo apt install -y git gcc g++ make cmake pkg-config libssl-dev
mkdir ~/git
cd ~/git
git clone https://github.com/sigp/lighthouse.git
cd lighthouse
git fetch --all && git checkout stable && git pull
make{% hint style="info" %} In case of compilation errors, run the following sequence.
rustup update
cargo clean
make
{% endhint %}
{% hint style="info" %} This build process may take a few minutes. {% endhint %}
Verify lighthouse was installed properly by checking the version number.
lighthouse --version
{% hint style="info" %}
When you import your keys into Lighthouse, your validator signing key(s) are stored in the $HOME/.lighthouse/mainnet/validators folder.
{% endhint %}
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/eth2deposit-cli/validator_keysVerify the accounts were imported successfully.
lighthouse account_manager validator list --network mainnet{% hint style="danger" %} WARNING: DO NOT USE THE ORIGINAL KEYSTORES TO VALIDATE WITH ANOTHER CLIENT, OR YOU WILL GET SLASHED. {% endhint %}
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
{% hint style="info" %} β¨ 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/ . {% endhint %}
- Auto-start your beacon chain when the computer reboots due to maintenance, power outage, etc.
- Automatically restart crashed beacon chain processes.
- Maximize your beacon chain up-time and performance.
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 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)
ExecStart = $(which lighthouse) bn --staking --metrics --network mainnet
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOF{% hint style="info" %}
****π₯ Lighthouse Pro Tip: On the ExecStart line, adding the --eth1-endpoints flag allows for redundant eth1 nodes. Separate with comma. Make sure the endpoint does not end with a trailing slash or/ Remove it.
# Example:
--eth1-endpoints http://localhost:8545,https://nodes.mewapi.io/rpc/eth,https://mainnet.eth.cloud.ava.do,https://mainnet.infura.io/v3/xxxπΈ Find free ethereum fallback nodes at https://ethereumnodes.com/ {% endhint %}
Move the unit file to /etc/systemd/system
sudo mv $HOME/beacon-chain.service /etc/systemd/system/beacon-chain.serviceUpdate file permissions.
sudo chmod 644 /etc/systemd/system/beacon-chain.serviceRun 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
{% hint style="info" %} Troubleshooting common issues:
The beacon chain couldn't connect to the :8545 service?
- In the beacon chain unit file under [Service], add, "
ExecStartPre = /bin/sleep 30" so that it waits 30 seconds for eth1 node to startup before connecting.
CRIT Invalid eth1 chain id. Please switch to correct chain id.
- Allow your eth1 node to fully sync to mainnet. {% endhint %}
{% hint style="success" %} Nice work. Your beacon chain is now managed by the reliability and robustness of systemd. Below are some commands for using systemd. {% endhint %}
#view and follow the log
journalctl --unit=beacon-chain -f#view log since yesterday
journalctl --unit=beacon-chain --since=yesterday#view log since today
journalctl --unit=beacon-chain --since=today#view log between a date
journalctl --unit=beacon-chain --since='2020-12-01 00:00:00' --until='2020-12-02 12:00:00'sudo systemctl is-active beacon-chain
sudo systemctl status beacon-chain
sudo systemctl reload-or-restart beacon-chain
sudo systemctl stop beacon-chain
Setup your graffiti, a custom message included in blocks your validator successfully proposes, and earn a POAP token. Generate your POAP string by supplying an Ethereum 1.0 address here.
Run the following command to set the MY_GRAFFITI variable. Replace <my POAP string or message> between the single quotes.
MY_GRAFFITI='<my POAP string or message>'
# Examples
# MY_GRAFFITI='poapAAAAACGatUA1bLuDnL4FMD13BfoD'
# MY_GRAFFITI='eth2 rulez!'{% hint style="info" %} Learn more about POAP - The Proof of Attendance token. {% endhint %}
- Auto-start your validator when the computer reboots due to maintenance, power outage, etc.
- Automatically restart crashed validator processes.
- Maximize your validator up-time and performance.
Run the following to create a unit file to define yourvalidator.service configuration. Simply copy and paste.
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)
ExecStart = $(which lighthouse) vc --network mainnet --graffiti "${MY_GRAFFITI}" --metrics
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOFMove the unit file to /etc/systemd/system
sudo mv $HOME/validator.service /etc/systemd/system/validator.serviceUpdate file permissions.
sudo chmod 644 /etc/systemd/system/validator.serviceRun 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
{% hint style="success" %} Nice work. Your validator is now managed by the reliability and robustness of systemd. Below are some commands for using systemd. {% endhint %}
#view and follow the log
journalctl --unit=validator -f#view log since yesterday
journalctl --unit=validator --since=yesterday#view log since today
journalctl --unit=validator --since=today#view log between a date
journalctl --unit=validator --since='2020-12-01 00:00:00' --until='2020-12-02 12:00:00'sudo systemctl is-active validator
sudo systemctl status validator
sudo systemctl reload-or-restart validator
sudo systemctl stop validator
{% endtab %}
{% tab title="Nimbus" %} {% hint style="info" %} 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. {% endhint %}
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 NIMFLAGS="-d:insecure" nimbus_beacon_node{% hint style="info" %} The build process may take a few minutes. {% endhint %}
Verify Nimbus was installed properly by displaying the help.
cd $HOME/git/nimbus-eth2/build
./nimbus_beacon_node --helpCopy the binary file to /usr/bin
sudo cp $HOME/git/nimbus-eth2/build/nimbus_beacon_node /usr/binCreate a directory structure to store nimbus data.
sudo mkdir -p /var/lib/nimbusTake ownership of this directory and set the correct permission level.
sudo chown $(whoami):$(whoami) /var/lib/nimbus
sudo chmod 700 /var/lib/nimbusThe 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/eth2deposit-cli/validator_keysNow you can verify the accounts were imported successfully by doing a directory listing.
ll /var/lib/nimbus/validatorsYou should see a folder named for each of your validator's pubkey.
{% hint style="info" %}
When you import your keys into Nimbus, your validator signing key(s) are stored in the /var/lib/nimbus folder, under secrets and validators.
The secrets folder contains the common secret that gives you access to all your validator keys.
The validators folder contains your signing keystore(s) (encrypted keys). Keystores are used by validators as a method for exchanging keys.
For more on keys and keystores, see here. {% endhint %}
{% hint style="danger" %} WARNING: DO NOT USE THE ORIGINAL KEYSTORES TO VALIDATE WITH ANOTHER CLIENT, OR YOU WILL GET SLASHED. {% endhint %}
Specific to your networking setup or cloud provider settings, ensure your validator's firewall ports are open and reachable.
- Nimbus beacon chain node will use port 9000 for tcp and udp
- eth1 node requires port 30303 for tcp and udp
{% hint style="info" %} β¨ 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/ . {% endhint %}
{% hint style="info" %} Nimbus combines both the beacon chain and validator into one process. {% endhint %}
Setup your graffiti, a custom message included in blocks your validator successfully proposes, and earn a POAP token. Generate your POAP string by supplying an Ethereum 1.0 address here.
Run the following command to set the MY_GRAFFITI variable. Replace <my POAP string or message> between the single quotes.
MY_GRAFFITI='<my POAP string or message>'
# Examples
# MY_GRAFFITI='poapAAAAACGatUA1bLuDnL4FMD13BfoD'
# MY_GRAFFITI='eth2 rulez!'{% hint style="info" %} Learn more about POAP - The Proof of Attendance token. {% endhint %}
- Auto-start your beacon chain when the computer reboots due to maintenance, power outage, etc.
- Automatically restart crashed beacon chain processes.
- Maximize your beacon chain up-time and performance.
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 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 = $(whoami)
WorkingDirectory= /var/lib/nimbus
ExecStart = /bin/bash -c '/usr/bin/nimbus_beacon_node --network=mainnet --graffiti="${MY_GRAFFITI}" --data-dir=/var/lib/nimbus --web3-url=ws://127.0.0.1:8546 --metrics --metrics-port=8008 --rpc --rpc-port=9091 --validators-dir=/var/lib/nimbus/validators --secrets-dir=/var/lib/nimbus/secrets --log-file=/var/lib/nimbus/beacon.log'
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOF{% hint style="warning" %} Nimbus only supports websocket connections ("ws://" and "wss://") for the ETH1 node. Geth, OpenEthereum and Infura ETH1 nodes are verified compatible. {% endhint %}
Move the unit file to /etc/systemd/system
sudo mv $HOME/beacon-chain.service /etc/systemd/system/beacon-chain.serviceUpdate file permissions.
sudo chmod 644 /etc/systemd/system/beacon-chain.serviceRun 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
{% hint style="success" %} Nice work. Your beacon chain is now managed by the reliability and robustness of systemd. Below are some commands for using systemd. {% endhint %}
#view and follow the log
journalctl --unit=beacon-chain -f#view log since yesterday
journalctl --unit=beacon-chain --since=yesterday#view log since today
journalctl --unit=beacon-chain --since=today#view log between a date
journalctl --unit=beacon-chain --since='2020-12-01 00:00:00' --until='2020-12-02 12:00:00'sudo systemctl is-active beacon-chain
sudo systemctl status beacon-chain
sudo systemctl reload-or-restart beacon-chain
sudo systemctl stop beacon-chain
{% endtab %}
{% tab title="Teku" %} {% hint style="info" %} 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 materity & ubiquity. {% endhint %}
Install git.
sudo apt-get install git -y
Install Java 11.
For Ubuntu 20.x, use the following
sudo apt update
sudo apt install openjdk-11-jdk -y
For Ubuntu 18.x, use the following
sudo add-apt-repository ppa:linuxuprising/java
sudo apt update
sudo apt install oracle-java11-set-default -y
Verify Java 11+ is installed.
java --versionInstall and build Teku.
mkdir ~/git
cd ~/git
git clone https://github.com/ConsenSys/teku.git
cd teku
./gradlew distTar installDist{% hint style="info" %} This build process may take a few minutes. {% endhint %}
Verify Teku was installed properly by displaying the version.
cd $HOME/git/teku/build/install/teku/bin
./teku --versionCopy the teku binary file to /usr/bin/teku
sudo cp -r $HOME/git/teku/build/install/teku /usr/bin/tekuSpecific to your networking setup or cloud provider settings, ensure your validator's firewall ports are open and reachable.
- Teku beacon chain node will use port 9000 for tcp and udp
- eth1 node requires port 30303 for tcp and udp
{% hint style="info" %} ****β¨ 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/ . {% endhint %}
{% hint style="info" %} Teku combines both the beacon chain and validator into one process. {% endhint %}
Setup a directory structure for Teku.
sudo mkdir -p /var/lib/teku
sudo mkdir -p /etc/teku
sudo chown $(whoami):$(whoami) /var/lib/tekuCopy your validator_files directory to the data directory we created above and remove the extra deposit_data file.
cp -r $HOME/eth2deposit-cli/validator_keys /var/lib/teku
rm /var/lib/teku/validator_keys/deposit_data*{% hint style="danger" %} WARNING: DO NOT USE THE ORIGINAL KEYSTORES TO VALIDATE WITH ANOTHER CLIENT, OR YOU WILL GET SLASHED. {% endhint %}
Store your keystore password in a file and make it read-only. This is required so that Teku can decrypt and load your validators.
Update your keystore password between the quotation marks after echo.
echo 'my_password_goes_here' > $HOME/validators-password.txt
sudo mv $HOME/validators-password.txt /etc/teku/validators-password.txt
sudo chmod 600 /etc/teku/validators-password.txtSetup your graffiti, a custom message included in blocks your validator successfully proposes, and earn a POAP token. Generate your POAP string by supplying an Ethereum 1.0 address here.
Run the following command to set the MY_GRAFFITI variable. Replace <my POAP string or message> between the single quotes.
MY_GRAFFITI='<my POAP string or message>'
# Examples
# MY_GRAFFITI='poapAAAAACGatUA1bLuDnL4FMD13BfoD'
# MY_GRAFFITI='eth2 rulez!'{% hint style="info" %} Learn more about POAP - The Proof of Attendance token. {% endhint %}
Generate your Teku Config file. Simply copy and paste.
cat > $HOME/teku.yaml << EOF
# network
network: "mainnet"
# p2p
p2p-enabled: true
p2p-port: 9000
# validators
validator-keys: "/var/lib/teku/validator_keys:/var/lib/teku/validator_keys"
validators-graffiti: "${MY_GRAFFITI}"
# Eth 1
eth1-endpoint: "http://localhost:8545"
# metrics
metrics-enabled: true
metrics-port: 8008
# database
data-path: "$(echo $HOME)/tekudata"
data-storage-mode: "archive"
# rest api
rest-api-port: 5051
rest-api-docs-enabled: true
rest-api-enabled: true
# logging
log-include-validator-duties-enabled: true
log-destination: CONSOLE
EOFMove the config file to /etc/teku
sudo mv $HOME/teku.yaml /etc/teku/teku.yaml{% hint style="info" %} 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
{% endhint %}
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; doneVerify that your validator's keystore and validator's passwords are present by checking the following directory.
ll /var/lib/teku/validator_keysUse systemd to manage starting and stopping teku.
- Auto-start your beacon chain when the computer reboots due to maintenance, power outage, etc.
- Automatically restart crashed beacon chain processes.
- Maximize your beacon chain up-time and performance.
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)
ExecStart = /usr/bin/teku/bin/teku -c /etc/teku/teku.yaml
Restart = on-failure
Environment = JAVA_OPTS=-Xmx5g
[Install]
WantedBy = multi-user.target
EOFMove the unit file to /etc/systemd/system
sudo mv $HOME/beacon-chain.service /etc/systemd/system/beacon-chain.serviceUpdate file permissions.
sudo chmod 644 /etc/systemd/system/beacon-chain.serviceRun 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
{% hint style="success" %} Nice work. Your beacon chain is now managed by the reliability and robustness of systemd. Below are some commands for using systemd. {% endhint %}
#view and follow the log
journalctl --unit=beacon-chain -f#view log since yesterday
journalctl --unit=beacon-chain --since=yesterday#view log since today
journalctl --unit=beacon-chain --since=today#view log between a date
journalctl --unit=beacon-chain --since='2020-12-01 00:00:00' --until='2020-12-02 12:00:00'sudo systemctl is-active beacon-chain
sudo systemctl status beacon-chain
sudo systemctl reload-or-restart beacon-chain
sudo systemctl stop beacon-chain
{% endtab %}
{% tab title="Prysm" %} {% hint style="info" %} 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. {% endhint %}
mkdir ~/prysm && cd ~/prysm
curl https://raw.githubusercontent.com/prysmaticlabs/prysm/master/prysm.sh --output prysm.sh && chmod +x prysm.sh Specific to your networking setup or cloud provider settings, ensure your validator's firewall ports are open and reachable.
- Prysm beacon chain node will use port 12000 for udp and port 13000 for tcp
- eth1 node requires port 30303 for tcp and udp
{% hint style="info" %} β¨ 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/ . {% endhint %}
Accept terms of use, 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.
{% hint style="info" %} If you wish, you can use the same password for the keystore and prysm. {% endhint %}
$HOME/prysm/prysm.sh validator accounts import --mainnet --keys-dir=$HOME/eth2deposit-cli/validator_keysVerify your validators imported successfully.
$HOME/prysm/prysm.sh validator accounts list --mainnetConfirm 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
{% hint style="danger" %} WARNING: DO NOT USE THE ORIGINAL KEYSTORES TO VALIDATE WITH ANOTHER CLIENT, OR YOU WILL GET SLASHED. {% endhint %}
- Auto-start your beacon chain when the computer reboots due to maintenance, power outage, etc.
- Automatically restart crashed beacon chain processes.
- Maximize your beacon chain up-time and performance.
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 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 = $(whoami)
ExecStart = $(echo $HOME)/prysm/prysm.sh beacon-chain --mainnet --p2p-max-peers=75 --http-web3provider=http://127.0.0.1:8545 --accept-terms-of-use
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOF{% hint style="info" %}
****π₯ Prysm Pro Tip: On the ExecStart line, adding the --fallback-web3provider flag allows for a backup eth1 node. May use flag multiple times. Make sure the endpoint does not end with a trailing slash or/ Remove it.
--fallback-web3provider=<http://<alternate eth1 provider one> --fallback-web3provider=<http://<alternate eth1 provider two>
# Example
# --fallback-web3provider=https://nodes.mewapi.io/rpc/eth --fallback-web3provider=https://mainnet.infura.io/v3/YOUR-PROJECT-IDπΈ Find free ethereum fallback nodes at https://ethereumnodes.com/ {% endhint %}
Move the unit file to /etc/systemd/system
sudo mv $HOME/beacon-chain.service /etc/systemd/system/beacon-chain.serviceUpdate file permissions.
sudo chmod 644 /etc/systemd/system/beacon-chain.serviceRun 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
{% hint style="success" %} Nice work. Your beacon chain is now managed by the reliability and robustness of systemd. Below are some commands for using systemd. {% endhint %}
#view and follow the log
journalctl --unit=beacon-chain -f#view log since yesterday
journalctl --unit=beacon-chain --since=yesterday#view log since today
journalctl --unit=beacon-chain --since=today#view log between a date
journalctl --unit=beacon-chain --since='2020-12-01 00:00:00' --until='2020-12-02 12:00:00'sudo systemctl is-active beacon-chain
sudo systemctl status beacon-chain
sudo systemctl reload-or-restart beacon-chain
sudo systemctl stop beacon-chain
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.
echo 'my_password_goes_here' > $HOME/.eth2validators/validators-password.txt
sudo chmod 600 $HOME/.eth2validators/validators-password.txtSetup your graffiti, a custom message included in blocks your validator successfully proposes, and earn a POAP token. Generate your POAP string by supplying an Ethereum 1.0 address here.
Run the following command to set the MY_GRAFFITI variable. Replace <my POAP string or message> between the single quotes.
MY_GRAFFITI='<my POAP string or message>'
# Examples
# MY_GRAFFITI='poapAAAAACGatUA1bLuDnL4FMD13BfoD'
# MY_GRAFFITI='eth2 rulez!'{% hint style="info" %} Learn more about POAP - The Proof of Attendance token. {% endhint %}
Your choice of running a validator manually from command line or automatically with systemd.
- Auto-start your validator when the computer reboots due to maintenance, power outage, etc.
- Automatically restart crashed validator processes.
- Maximize your validator up-time and performance.
Run the following to create a unit file to define yourvalidator.service configuration. Simply copy and paste.
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)
ExecStart = $(echo $HOME)/prysm/prysm.sh validator --mainnet --graffiti "${MY_GRAFFITI}" --accept-terms-of-use --wallet-password-file $(echo $HOME)/.eth2validators/validators-password.txt
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOFMove the unit file to /etc/systemd/system
sudo mv $HOME/validator.service /etc/systemd/system/validator.serviceUpdate file permissions.
sudo chmod 644 /etc/systemd/system/validator.serviceRun 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
#view and follow the log
journalctl --unit=validator -f#view log since yesterday
journalctl --unit=validator --since=yesterday#view log since today
journalctl --unit=validator --since=today#view log between a date
journalctl --unit=validator --since='2020-12-01 00:00:00' --until='2020-12-02 12:00:00'sudo systemctl is-active validator
sudo systemctl status validator
sudo systemctl reload-or-restart validator
sudo systemctl stop validator
Verify that your validator public key appears in the logs.
journalctl --unit=validator --since=today
# Example below
# INFO Enabled validator voting_pubkey: 0x2374.....7121{% endtab %}
{% tab title="Lodestar" %} {% hint style="info" %} ****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. {% endhint %}
{% hint style="danger" %} Lodestar may not be fully functional and stable yet. {% endhint %}
Install curl and git.
sudo apt-get install git curl -yInstall 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 yarnConfirm yarn is installed properly.
yarn --version
# Should output version >= 1.22.4Install nodejs.
curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -
sudo apt-get install -y nodejs
Confirm nodejs is installed properly.
nodejs -v
# Should output version >= v12.18.3Install and build Lodestar.
mkdir ~/git
cd ~/git
git clone https://github.com/chainsafe/lodestar.git
cd lodestar
yarn install
yarn run build{% hint style="info" %} This build process may take a few minutes. {% endhint %}
Verify Lodestar was installed properly by displaying the help menu.
yarn run cli --help
Specific to your networking setup or cloud provider settings, ensure your validator's firewall ports are open and reachable.
- Lodestar beacon chain node will use port 30607 for tcp and port 9000 for udp peer discovery.
- eth1 node requires port 30303 for tcp and udp
{% hint style="info" %} ****β¨ 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/ . {% endhint %}
yarn run cli account validator import \
--network mainnet \
--directory $HOME/eth2deposit-cli/validator_keysEnter your keystore password to import accounts.
Confirm your keys were imported properly.
yarn run cli account validator list --network mainnet
{% hint style="danger" %} WARNING: DO NOT USE THE ORIGINAL KEYSTORES TO VALIDATE WITH ANOTHER CLIENT, OR YOU WILL GET SLASHED. {% endhint %}
Run the beacon chain automatically with systemd.
- Auto-start your beacon chain when the computer reboots due to maintenance, power outage, etc.
- Automatically restart crashed beacon chain processes.
- Maximize your beacon chain up-time and performance.
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 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= $(echo $HOME)/git/lodestar
ExecStart = yarn run cli beacon --network mainnet --eth1.providerUrl http://localhost:8545 --metrics.serverPort 8008
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOFMove the unit file to /etc/systemd/system
sudo mv $HOME/beacon-chain.service /etc/systemd/system/beacon-chain.serviceUpdate file permissions.
sudo chmod 644 /etc/systemd/system/beacon-chain.serviceRun 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
{% hint style="success" %} Nice work. Your beacon chain is now managed by the reliability and robustness of systemd. Below are some commands for using systemd. {% endhint %}
#view and follow the log
journalctl --unit=beacon-chain -f#view log since yesterday
journalctl --unit=beacon-chain --since=yesterday#view log since today
journalctl --unit=beacon-chain --since=today#view log between a date
journalctl --unit=beacon-chain --since='2020-12-01 00:00:00' --until='2020-12-02 12:00:00'sudo systemctl is-active beacon-chain
sudo systemctl status beacon-chain
sudo systemctl reload-or-restart beacon-chain
sudo systemctl stop beacon-chain
Setup your graffiti, a custom message included in blocks your validator successfully proposes, and earn a POAP token. Generate your POAP string by supplying an Ethereum 1.0 address here.
Run the following command to set the MY_GRAFFITI variable. Replace <my POAP string or message> between the single quotes.
MY_GRAFFITI='<my POAP string or message>'
# Examples
# MY_GRAFFITI='poapAAAAACGatUA1bLuDnL4FMD13BfoD'
# MY_GRAFFITI='eth2 rulez!'{% hint style="info" %} Learn more about POAP - The Proof of Attendance token. {% endhint %}
Run the validator automatically with systemd.
- Auto-start your validator when the computer reboots due to maintenance, power outage, etc.
- Automatically restart crashed validator processes.
- Maximize your validator up-time and performance.
Run the following to create a unit file to define yourvalidator.service configuration. Simply copy and paste.
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= $(echo $HOME)/git/lodestar
ExecStart = yarn run cli validator run --network mainnet --graffiti "${MY_GRAFFITI}"
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOFMove the unit file to /etc/systemd/system
sudo mv $HOME/validator.service /etc/systemd/system/validator.serviceUpdate file permissions.
sudo chmod 644 /etc/systemd/system/validator.serviceRun 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
{% hint style="success" %} Nice work. Your validator is now managed by the reliability and robustness of systemd. Below are some commands for using systemd. {% endhint %}
#view and follow the log
journalctl --unit=validator -f#view log since yesterday
journalctl --unit=validator --since=yesterday#view log since today
journalctl --unit=validator --since=today#view log between a date
journalctl --unit=validator --since='2020-12-01 00:00:00' --until='2020-12-02 12:00:00'sudo systemctl is-active validator
sudo systemctl status validator
sudo systemctl reload-or-restart validator
sudo systemctl stop validator
{% endtab %} {% endtabs %}
{% hint style="info" %} 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. {% endhint %}
Setup Chrony with the following guide.
{% page-ref page="../../overview-ada/guide-how-to-build-a-haskell-stakepool-node/how-to-setup-chrony.md" %}
{% hint style="info" %} chrony is an implementation of the Network Time Protocol and helps to keep your computer's time synchronized with NTP. {% endhint %}
{% hint style="warning" %} Running multiple time synchronization services is known to cause issues. Ensure only either Chrony or only 1 NTP service is running. {% endhint %}
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.
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 grafanaEnable services so they start automatically.
sudo systemctl enable grafana-server.service prometheus.service prometheus-node-exporter.serviceCreate the prometheus.yml config file. Choose the tab for your eth2 client. Simply copy and paste.
{% tabs %} {% tab title="Lighthouse" %}
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']
- job_name: 'validators'
metrics_path: /metrics
static_configs:
- targets: ['localhost:5064']
EOF{% endtab %}
{% tab title="Nimbus" %}
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:8008']
EOF{% endtab %}
{% tab title="Teku" %}
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:8008']
EOF{% endtab %}
{% tab title="Prysm" %}
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: 'validator'
static_configs:
- targets: ['localhost:8081']
- job_name: 'beacon node'
static_configs:
- targets: ['localhost:8080']
- job_name: 'slasher'
static_configs:
- targets: ['localhost:8082']
EOF{% endtab %}
{% tab title="Lodestar" %}
cat > $HOME/prometheus.yml << EOF
scrape_configs:
- job_name: 'node_exporter'
static_configs:
- targets: ['localhost:9100']
- job_name: 'Lodestar'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8008']
EOF{% endtab %} {% endtabs %}
Setup prometheus for your eth1 node. Start by editing prometheus.yml
nano $HOME/prometheus.ymlAppend the applicable job snippet for your eth1 node to the end of prometheus.yml. Save the file.
{% hint style="warning" %}
Spacing matters. Ensure all job_name snippets are in alignment.
{% endhint %}
{% tabs %} {% tab title="Geth" %}
- job_name: 'geth'
scrape_interval: 15s
scrape_timeout: 10s
metrics_path: /debug/metrics/prometheus
scheme: http
static_configs:
- targets: ['localhost:6060']{% endtab %}
{% tab title="Besu" %}
- job_name: 'besu'
scrape_interval: 15s
scrape_timeout: 10s
metrics_path: /metrics
scheme: http
static_configs:
- targets:
- localhost:9545{% endtab %}
{% tab title="Nethermind" %}
- job_name: 'nethermind'
scrape_interval: 15s
scrape_timeout: 10s
honor_labels: true
static_configs:
- targets: ['localhost:9091']Nethermind monitoring requires Prometheus Pushgateway. Install with the following command.
sudo apt-get install -y prometheus-pushgateway{% hint style="info" %} Pushgateway listens for data from Nethermind on port 9091. {% endhint %} {% endtab %}
{% tab title="OpenEthereum" %}
- job_name: 'openethereum'
scrape_interval: 15s
scrape_timeout: 10s
metrics_path: /metrics
scheme: http
static_configs:
- targets: ['localhost:6060']{% endtab %} {% endtabs %}
Move it to /etc/prometheus/prometheus.yml
sudo mv $HOME/prometheus.yml /etc/prometheus/prometheus.ymlUpdate file permissions.
sudo chmod 644 /etc/prometheus/prometheus.ymlFinally, restart the services.
sudo systemctl restart grafana-server.service prometheus.service prometheus-node-exporter.serviceVerify that the services are running properly:
sudo systemctl status grafana-server.service prometheus.service prometheus-node-exporter.service
{% hint style="info" %} π‘ Reminder: Ensure port 3000 is open on the firewall and/or port forwarded if you intend to view monitoring info from a different machine. {% endhint %}
- Open http://localhost:3000 or http://<your validator's ip address>:3000 in your local browser.
- Login with admin / admin
- Change password
- Click the configuration gear icon, then Add data Source
- Select Prometheus
- Set Name to "Prometheus"
- Set URL to http://localhost:9090
- Click Save & Test
- Download and save your ETH2 Client's json file. [ Lighthouse BC | Lighthouse VC | Teku | Nimbus | Prysm | Prysm > 10 Validators | Lodestar ]
- Download and save your ETH1 Client's json file [ Geth | Besu | Nethermind | OpenEthereum ]
- Download and save a node-exporter dashboard for general system monitoring
- Click Create + icon > Import
- Add the ETH2 client dashboard via Upload JSON file
- If needed, select Prometheus as Data Source.
- Click the Import button.
- Repeat steps 12-15 for the ETH1 client dashboard.
- Repeat steps 12-15 for the node-exporter dashboard.
{% hint style="info" %} ****π₯ Troubleshooting common Grafana issues:
The dashboards do not display eth1 node data.
- In the eth1 unit file under located at
/etc/systemd/system/eth1.service, make sure your eth1 node/geth is started with the correct parameters so that reporting metrics and pprof http server are enabled.- Example:
ExecStartPre = /usr/bin/geth --http --metrics --pprof{% endhint %}
- Example:
{% tabs %}
{% tab title="Lighthouse" %}
Credits: https://github.com/sigp/lighthouse-metrics/ {% endtab %}
{% tab title="Nimbus" %}
Credits: https://github.com/status-im/nimbus-eth2/ {% endtab %}
{% tab title="Teku" %}
Credits: https://grafana.com/grafana/dashboards/13457 {% endtab %}
{% tab title="Prysm" %}
Credits: https://github.com/GuillaumeMiralles/prysm-grafana-dashboard {% endtab %}
{% tab title="Lodestar" %} Work in progress. {% endtab %} {% endtabs %}
{% tabs %}
{% tab title="Geth" %}
Credits: https://gist.github.com/karalabe/e7ca79abdec54755ceae09c08bd090cd {% endtab %}
{% tab title="Besu" %}
Credits: https://grafana.com/dashboards/10273 {% endtab %}
{% tab title="Nethermind" %}
Credits: https://github.com/NethermindEth/metrics-infrastructure {% endtab %}
{% tab title="OpenEthereum" %}
{% endtab %}
{% endtabs %}
{% tabs %} {% tab title="Node-Exporter Dashboard by starsliao" %} General system monitoring
Includes: CPU, memory, disk IO, network, temperature and other monitoring metricsγ
Credits: starsliao {% endtab %} {% endtabs %}
{% hint style="info" %} Setup alerts to get notified if your validators go offline. {% endhint %}
Get notified of problems with your validators. Choose between email, telegram, discord or slack.
{% tabs %} {% tab title="Email Notifications" %}
- Visit https://beaconcha.in/
- Sign up for an account.
- Verify your email
- Search for your validator's public address
- Add validators to your watchlist by clicking the bookmark symbol. {% endtab %}
{% tab title="Telegram Notifications" %}
-
On the menu of Grafana, select Notification channels under the bell icon.
-
Click on Add channel.
-
Give the notification channel a name.
-
Select Telegram from the Type list.
-
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. You need to create a BOT API token. -
Create a new telegram group.
-
Invite the bot to your new group.
-
Type at least 1 message into the group to initialize it.
-
Visit
https://api.telegram.org/botXXX:YYY/getUpdateswhereXXX:YYYis your BOT API Token. -
In the JSON response, find and copy the Chat ID. Find it between chat and title. Example of Chat ID:
-1123123123"chat":{"id":-123123123,"title": -
Paste the Chat ID into the corresponding field in Grafana.
-
Save and test the notification channel for your alerts.
-
Now you can create custom alerts from your dashboards. Visit here to learn how to create alerts. {% endtab %}
{% tab title="Discord Notifications" %}
- On the menu of Grafana, select Notification channels under the bell icon.
- Click on Add channel.
- Add a name to the notification channel.
- Select Discord from the Type list.
- 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.
- Enter the Webhook URL in the Discord notification settings panel.
- Click Send Test, which will push a confirmation message to the Discord channel. {% endtab %}
{% tab title="Slack Notifications" %}
- On the menu of Grafana, select Notification channels under the bell icon.
- Click on Add channel.
- Add a name to the notification channel.
- Select Slack from the Type list.
- For instructions on setting up a Slack's Incoming Webhooks, see this section of their documentation.
- Enter the Slack Incoming Webhook URL in the URL field.
- Click Send Test, which will push a confirmation message to the Slack channel. {% endtab %} {% endtabs %}
{% hint style="info" %} Who watches the watcher? With an external 3rd party tool like Uptime Check, you can have greater reassurance your validator is functioning in case of disasters such as power failure, hardware failure or internet outage. In these scenarios, the previously mentioned monitoring by Prometheus and Grafana would likely cease to function as well.
Credits to Mohamed Mansour for inspiring this how-to guide. {% endhint %}
Here's how to setup a no-cost monitoring service called Uptime Check by Google.
{% hint style="info" %} For a video demo, watch MohamedMansour's eth2 education videos. Please support his GITCOIN grant. π {% endhint %}
- Visit cloud.google.com
- Search for Monitoring in the search field.
- Click Select a Project to Start Monitoring.
- Click New Project.
- Name your project and click Create.
- From the notifications menu, select your new project.
- On the right column, there's a Monitoring Card. Click Go to Monitoring.
- On the left menu, click Uptime checks and then CREATE UPTIME CHECK.
- Type in a title i.e. Geth node
- Select protocol as TCP
- Enter your public IP address and port number. i.e. ip=7.55.6.3 and port=30303
- Select your desired frequency to check i.e. 5 minutes.
- Choose the region closest to you to check from. Click Next.
- Create a Notification Channel. Click Manage Notification Channels.
- Choose your desired settings. Pick from any or all of Slack, Webhook, Email or SMS.
- Go back to Create Uptime Check window.
- Within the notifications field, click the refresh button to load your new notification channels.
- Select desired notifications.
- Click TEST to verify your notifications are setup correctly.
- Click CREATE to finish.
{% hint style="success" %} Once your beacon chain is sync'd, validator up and running, you just wait for activation. This process can take 24+ hours. Only 900 new validators can join per day. When you're assigned, your validator will begin creating and voting on blocks while earning staking rewards.
Use https://beaconcha.in/ to create alerts and track your validator's performance. {% endhint %}
{% hint style="info" %} Be sure to review the Checklist | How to confirm a healthy functional ETH2 validator. {% endhint %}
{% hint style="success" %} πCongrats on setting up your validator! You're good to go on eth2.0.
Did you find our guide useful? Send us a signal 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 Discord @
https://discord.gg/w8Bx8W2HPW π {% endhint %}
When a new release is cut, you will want to update to the latest stable release. The following shows you how to update your eth2 beacon chain and validator.
{% hint style="info" %}
Always review the git logs with commandgit log or release notes before updating. There may be changes requiring your attention.
{% endhint %}
{% hint style="success" %} ****π₯ Pro tip: Plan your update to overlap with the longest attestation gap. Learn how here. {% endhint %}
Select your ETH2 client.
{% tabs %} {% tab title="Lighthouse" %} Review release notes and check for breaking changes/features.
https://github.com/sigp/lighthouse/releases
Pull the latest source and build it.
cd $HOME/git/lighthouse
git fetch --all && git checkout stable && git pull
makeVerify the build completed by checking the new version number.
lighthouse --versionRestart beacon chain and validator as per normal operating procedures.
sudo systemctl reload-or-restart beacon-chain validator
{% endtab %}
{% tab title="Nimbus" %} Review release notes and check for breaking changes/features.
https://github.com/status-im/nimbus-eth2/releases
Pull the latest source and build it.
cd $HOME/git/nimbus-eth2
git pull && make update
make NIMFLAGS="-d:insecure" nimbus_beacon_nodeVerify the build completed by checking the new version number.
cd $HOME/git/nimbus-eth2/build
./nimbus_beacon_node --versionStop, copy new binary, and restart beacon chain and validator as per normal operating procedures.
sudo systemctl stop beacon-chain
sudo rm /usr/bin/nimbus_beacon_node
sudo cp $HOME/git/nimbus-eth2/build/nimbus_beacon_node /usr/bin
sudo systemctl reload-or-restart beacon-chain{% endtab %}
{% tab title="Teku" %} Review release notes and check for breaking changes/features.
https://github.com/ConsenSys/teku/releases
Pull the latest source and build it.
cd $HOME/git/teku
git pull
./gradlew distTar installDistVerify the build completed by checking the new version number.
cd $HOME/git/teku/build/install/teku/bin
./teku --versionRestart beacon chain and validator as per normal operating procedures.
sudo systemctl stop beacon-chain
sudo rm -rf /usr/bin/teku
sudo cp -r $HOME/git/teku/build/install/teku /usr/bin/teku
sudo systemctl reload-or-restart beacon-chain{% endtab %}
{% tab title="Prysm" %} Review release notes and check for breaking changes/features. https://github.com/prysmaticlabs/prysm/releases
#Simply restart the processes
sudo systemctl reload-or-restart beacon-chain validator{% endtab %}
{% tab title="Lodestar" %} Review release notes and check for breaking changes/features.
https://github.com/ChainSafe/lodestar/releases
Pull the latest source and build it.
cd $HOME/git/lodestar
git pull
yarn install
yarn run buildVerify the build completed by checking the new version number.
yarn run cli --versionRestart beacon chain and validator as per normal operating procedures.
sudo systemctl reload-or-restart beacon-chain validator
{% endtab %} {% endtabs %}
Check the logs to verify the services are working properly and ensure there are no errors.
{% tabs %} {% tab title="Lighthouse | Prysm | Lodestar" %}
sudo systemctl status beacon-chain validator{% endtab %}
{% tab title="Nimbus | Teku" %}
sudo systemctl status beacon-chain
{% endtab %} {% endtabs %}
{% hint style="info" %} 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. {% endhint %}
{% tabs %} {% tab title="Lighthouse" %}
lighthouse account validator exit \
--keystore $HOME/.lighthouse/mainnet/validators \
--beacon-node http://localhost:5052 \
--network mainnet{% endtab %}
{% tab title="Teku" %}
teku voluntary-exit \
--epoch=<epoch number to exit> \
--beacon-node-api-endpoint=http://127.0.0.1:5051 \
--validator-keys=<path to keystore.json>:<path to password.txt file>{% endtab %}
{% tab title="Nimbus" %}
build/nimbus_beacon_node deposits exit --validator=<VALIDATOR_PUBLIC_KEY> --data-dir=/var/lib/nimbus{% endtab %}
{% tab title="Prysm" %}
$HOME/prysm/prysm.sh validator accounts voluntary-exit{% endtab %}
{% tab title="Lodestar" %}
#TO BE DETERMINED{% endtab %} {% endtabs %}
Using the eth2deposit-cli tool, ensure you can regenerate the same eth2 key pairs by restoring your validator_keys
cd $HOME/eth2deposit-cli
./deposit.sh existing-mnemonic --chain mainnet{% hint style="info" %} When the pubkey in both keystore files are identical, this means your mnemonic phrase is veritably correct. Other fields will be different because of salting. {% endhint %}
Backup and move your existing validator_key directory and append the date to the end.
# Adjust your eth2deposit-cli directory accordingly
cd $HOME/eth2deposit-cli
# Renames and append the date to the existing validator_key directory
mv validator_key validator_key_$(date +"%Y%d%m-%H%M%S")
# Optional: you can also delete this folder since it can be regenerated.{% hint style="info" %}
Using the eth2deposit-cli tool, you can add more validators by creating a new deposit data file and validator_keys
{% endhint %}
- For example, in case we originally created 3 validators but now wish to add 5 more validators, we could use the following command. Select the tab depending on how you acquired eth2deposit tool.
{% hint style="warning" %} Security recommendation reminder: For best security practices, key management and other activities where you type your 24 word mnemonic seed should be completed on an air-gapped offline cold machine booted from USB drive. {% endhint %}
{% hint style="danger" %} Reminder to use the same keystore password. {% endhint %}
{% tabs %} {% tab title="Build from source code" %}
# Generate from an existing mnemonic 5 more validators when 3 were previously already made
./deposit.sh existing-mnemonic --validator_start_index 3 --num_validators 5 --chain mainnet{% endtab %}
{% tab title="Pre-built eth2deposit-cli binaries" %}
# Generate from an existing mnemonic 5 more validators when 3 were previously already made
./deposit existing-mnemonic --validator_start_index 3 --num_validators 5 --chain mainnet{% endtab %}
{% tab title="Advanced - Most Secure" %} {% hint style="warning" %} π₯Pro Security Tip: Run the eth2deposit-cli tool and generate your mnemonic seed for your validator keys on an air-gapped offline machine booted from usb. {% endhint %}
Follow this ethstaker.cc exclusive for the low down on making a bootable usb.
{% embed url="https://www.youtube.com/watch?v=DTR3PzRRtYU" %}
{% embed url="https://www.youtube.com/watch?v=C97\_6MrufCE" %}
You can copy via USB key the pre-built eth2deposit-cli binaries from an online machine to an air-gapped offline machine booted from usb. Make sure to disconnect the ethernet cable and/or WIFI.
Run the existing-mnemonic command in the previous tabs. {% endtab %} {% endtabs %}
-
Complete the steps of uploading the
deposit_data-#########.jsonto the official Eth2 launch pad site and making your corresponding 32 ETH deposit transactions. -
Finish by stopping your validator, importing the new validator key(s), restarting your validator and verifying the logs ensuring everything still works without error. Review steps 2 and onward of the main guide if you need a refresher.
-
Finally, verify your existing validator's attestations are working with public block explorer such as
https://beaconcha.in/ or https://beaconscan.com/
Enter your validator's pubkey to view its status.
{% hint style="info" %} Your additional validators are now in the activation queue waiting their turn. Check your estimated activation time at https://eth2-validator-queue.web.app/ {% endhint %}
{% hint style="info" %} The key takeaway in this process is to avoid running two eth2 clients simultaneously. You want to avoid being punished by a slashing penalty, which causes a loss of ether. {% endhint %}
In order to export the slashing database, the validator needs to be stopped.
{% tabs %} {% tab title="Lighthouse | Prysm | Lodestar" %}
sudo systemctl stop beacon-chain validator{% endtab %}
{% tab title="Nimbus | Teku" %}
sudo systemctl stop beacon-chain
{% endtab %} {% endtabs %}
{% hint style="info" %} EIP-3076 implements a standard to safety migrate validator keys between eth2 clients. This is the exported contents of the slashing database. {% endhint %}
Update the export .json file location and name.
{% tabs %} {% tab title="Lighthouse" %}
lighthouse account validator slashing-protection export <lighthouse_interchange.json>{% endtab %}
{% tab title="Nimbus" %} To be implemented {% endtab %}
{% tab title="Teku" %}
teku slashing-protection export --to=<FILE>{% endtab %}
{% tab title="Prysm" %} To be implemented {% endtab %}
{% tab title="Lodestar" %} To be implemented {% endtab %} {% endtabs %}
Now you need to setup/install your new validator but do not start running the systemd processes. Be sure to thoroughly follow your new validator's Section 4. Configure a ETH2 beacon chain and validator. You will need to build/install the client, configure port forwarding/firewalls, and new systemd unit files.
{% hint style="warning" %} ****β¨ Pro Tip: During the process of re-importing validator keys, wait at least 13 minutes or two epochs to prevent slashing penalties. You must avoid running two eth2 clients with same validator keys at the same time. {% endhint %}
{% hint style="danger" %} π Critical Step: Do not start any systemd processes until either you have imported the slashing database or you have waited at least 13 minutes or two epochs. {% endhint %}
Using your new eth2 client, run the following command and update the relevant path to import your slashing database from 2 steps ago.
{% tabs %} {% tab title="Lighthouse" %}
lighthouse account validator slashing-protection import <my_interchange.json>{% endtab %}
{% tab title="Nimbus" %} To be implemented {% endtab %}
{% tab title="Teku" %}
teku slashing-protection import --from=<FILE>{% endtab %}
{% tab title="Prysm" %} To be implemented {% endtab %}
{% tab title="Lodestar" %} To be implemented {% endtab %} {% endtabs %}
{% tabs %} {% tab title="Lighthouse | Prysm | Lodestar" %}
sudo systemctl start beacon-chain validator{% endtab %}
{% tab title="Nimbus | Teku" %}
sudo systemctl start beacon-chain
{% endtab %} {% endtabs %}
Check the logs to verify the services are working properly and ensure there are no errors.
{% tabs %} {% tab title="Lighthouse | Prysm | Lodestar" %}
sudo systemctl status beacon-chain validator{% endtab %}
{% tab title="Nimbus | Teku" %}
sudo systemctl status beacon-chain
{% endtab %} {% endtabs %}
Finally, verify your validator's attestations are working with public block explorer such as
Enter your validator's pubkey to view its status.
Review section 6 and change your prometheus.yml. Ensure prometheus is connected to your new eth2 client's metrics port. You will also want to import your new eth2 client's dashboard.
During installation of Ubuntu Server, a common issue arises where your hard drive's space is not fully available for use.
# View your disk drives
sudo -s lvm
# Change the logical volume filesystem path if required
lvextend -l +100%FREE /dev/ubuntu-vg/ubuntu-lv
#exit lvextend
exit
# Resize file system to use the new available space in the logical volume
resize2fs /dev/ubuntu-vg/ubuntu-lv
## Verify new available space
df -h
# Example output of a 2TB drive where 25% is used
# Filesystem Size Used Avail Use% Mounted on
# /dev/ubuntu-vg/ubuntu-lv 2000G 500G 1500G 25% /Source reference:
{% embed url="https://askubuntu.com/questions/1106795/ubuntu-server-18-04-lvm-out-of-space-with-improper-default-partitioning" %}
{% hint style="info" %} Hosting your own ETH1 node can consume hundreds of gigabytes of data per day. Because data plans can be limited or costly, you might desire to slow down data usage but still maintain good connectivity to the network. {% endhint %}
Edit your eth1.service unit file.
sudo nano /etc/systemd/system/eth1.serviceAdd the following flag to limit the number of peers on the ExecStart line.
{% tabs %} {% tab title="Geth" %}
--maxpeers 10
# Example
# ExecStart = /usr/bin/geth --maxpeers 10 --http --ws{% endtab %}
{% tab title="OpenEthereum (Parity)" %}
--max-peers 10
# Example
# ExecStart = <home directory>/openethereum/openethereum --max-peers 10{% endtab %}
{% tab title="Besu" %}
--max-peers 10
# Example
# ExecStart = <home directory>/besu/bin/besu --max-peers 10 --rpc-http-enabled{% endtab %}
{% tab title="Nethermind" %}
--Network.ActivePeersMaxCount 10
# Example
# ExecStart = <home directory>/nethermind/Nethermind.Runner --Network.ActivePeersMaxCount 10 --JsonRpc.Enabled true{% endtab %} {% endtabs %}
Finally, reload the new unit file and restart the eth1 node.
sudo systemctl daemon-reload
sudo systemctl restart eth1{% hint style="info" %} In case you need to locate your validator keys, database directories or other important files. {% endhint %}
{% tabs %} {% tab title="Lighthouse" %}
# Validator Keys
~/.lighthouse/mainnet/validators
# Beacon Chain Data
~/.lighthouse/mainnet/beacon
# List of all validators and passwords
~/.lighthouse/mainnet/validators/validator_definitions.yml
#Slash protection db
~/.lighthouse/mainnet/validators/slashing_protection.sqlite{% endtab %}
{% tab title="Nimbus" %}
# Validator Keys
/var/lib/nimbus/validators
# Beacon Chain Data
/var/lib/nimbus/db
#Slash protection db
/var/lib/nimbus/validators/slashing_protection.sqlite3
#Logs
/var/lib/nimbus/beacon.log{% endtab %}
{% tab title="Teku" %}
# Validator Keys
/var/lib/teku
# Beacon Chain Data
~/tekudata/beacon
#Slash protection db
~/tekudata/validator/slashprotection{% endtab %}
{% tab title="Prysm" %}
# Validator Keys
~/.eth2validators/prysm-wallet-v2/direct
# Beacon Chain Data
~/.eth2/beaconchaindata{% endtab %}
{% tab title="Lodestar" %} TBD {% endtab %} {% endtabs %}
{% tabs %} {% tab title="Geth" %}
# database location
$HOME/.ethereum{% endtab %}
{% tab title="OpenEthereum (Parity)" %}
# database location
$HOME/.local/share/openethereum{% endtab %}
{% tab title="Besu" %}
# database location
$HOME/.besu/database{% endtab %}
{% tab title="Nethermind" %}
#database location
$HOME/.nethermind/nethermind_db/mainnet{% endtab %} {% endtabs %}
{% hint style="info" %} Hosting your own ETH1 node on a different machine than where your beacon-chain and validator resides, can allow some extra modularity and flexibility. {% endhint %}
On the eth1 node machine, edit your eth1.service unit file.
sudo nano /etc/systemd/system/eth1.serviceAdd the following flag to allow remote incoming http and or websocket api requests on the ExecStart line.
{% hint style="info" %} If not using websockets, there's no need to include ws parameters. Only Nimbus requires websockets. {% endhint %}
{% tabs %} {% tab title="Geth" %}
--http.addr 0.0.0.0 --ws.addr 0.0.0.0
# Example
# ExecStart = /usr/bin/geth --http.addr 0.0.0.0 --ws.addr 0.0.0.0 --http --ws{% endtab %}
{% tab title="OpenEthereum (Parity)" %}
--jsonrpc-interface=all --ws-interface=all
# Example
# ExecStart = <home directory>/openethereum/openethereum --jsonrpc-interface=all --ws-interface=all{% endtab %}
{% tab title="Besu" %}
--rpc-http-host=0.0.0.0 --rpc-ws-enabled --rpc-ws-host=0.0.0.0
# Example
# ExecStart = <home directory>/besu/bin/besu --rpc-http-host=0.0.0.0 --rpc-ws-enabled --rpc-ws-host=0.0.0.0 --rpc-http-enabled{% endtab %}
{% tab title="Nethermind" %}
--JsonRpc.Host 0.0.0.0 --WebSocketsEnabled
# Example
# ExecStart = <home directory>/nethermind/Nethermind.Runner --JsonRpc.Host 0.0.0.0 --WebSocketsEnabled --JsonRpc.Enabled true{% endtab %} {% endtabs %}
Reload the new unit file and restart the eth1 node.
sudo systemctl daemon-reload
sudo systemctl restart eth1On the separate machine hosting the beacon-chain, update the beacon-chain unit file with the eth1 node's IP address.
{% tabs %} {% tab title="Lighthouse" %}
# edit beacon-chain unit file
nano /etc/systemd/system/beacon-chain.service
# add the --eth1-endpoints parameter
# example
# --eth1-endpoints=http://192.168.10.22{% endtab %}
{% tab title="Nimbus" %}
# edit beacon chain unit file
nano /etc/systemd/system/beacon-chain.service
# modify the --web-url parameter
# example
# --web3-url=ws://192.168.10.22{% endtab %}
{% tab title="Teku" %}
# edit teku.yaml
nano /etc/teku/teku.yaml
# change the eth1-endpoint
# example
# eth1-endpoint: "http://192.168.10.20:8545"{% endtab %}
{% tab title="Prysm" %}
# edit beacon-chain unit file
nano /etc/systemd/system/beacon-chain.service
# add the --http-web3provider parameter
# example
# --http-web3provider=http://192.168.10.20:8545{% endtab %}
{% tab title="Lodestar" %}
tbd.
{% endtab %} {% endtabs %}
Reload the updated unit file and restart the beacon-chain.
sudo systemctl daemon-reload
sudo systemctl restart beacon-chainSetup your graffiti, a custom message included in blocks your validator successfully proposes, and earn an early beacon chain validator POAP token. Generate your POAP string by supplying an Ethereum 1.0 address here.
Run the following command to set the MY_GRAFFITI variable. Replace <my POAP string or message> between the single quotes.
MY_GRAFFITI='<my POAP string or message>'
# Examples
# MY_GRAFFITI='poapAAAAACGatUA1bLuDnL4FMD13BfoD'
# MY_GRAFFITI='eth2 rulez!'{% hint style="info" %} Learn more about POAP - The Proof of Attendance token. {% endhint %}
{% tabs %}
{% tab title="Lighthouse" %}
Run the following to re-create a unit file to define yourvalidator.service configuration. Simply copy and paste.
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)
ExecStart = $(which lighthouse) vc --network mainnet --graffiti "${MY_GRAFFITI}"
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOFMove the unit file to /etc/systemd/system
sudo mv $HOME/validator.service /etc/systemd/system/validator.serviceUpdate file permissions.
sudo chmod 644 /etc/systemd/system/validator.service{% endtab %}
{% tab title="Nimbus" %}
Run the following to re-create a unit file to define yourbeacon-chain.service configuration. Simply copy and paste.
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]
Type = simple
User = $(whoami)
WorkingDirectory= /var/lib/nimbus
ExecStart = /usr/bin/nimbus_beacon_node --network=mainnet --graffiti="${MY_GRAFFITI}" --data-dir=/var/lib/nimbus --web3-url=ws://127.0.0.1:8546 --metrics --metrics-port=8008 --rpc --rpc-port=9091 --validators-dir=/var/lib/nimbus/validators --secrets-dir=/var/lib/nimbus/secrets --log-file=/var/lib/nimbus/beacon.log
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOF{% hint style="warning" %} Nimbus only supports websocket connections ("ws://" and "wss://") for the ETH1 node. Geth, OpenEthereum and Infura ETH1 nodes are verified compatible. {% endhint %}
Move the unit file to /etc/systemd/system
sudo mv $HOME/beacon-chain.service /etc/systemd/system/beacon-chain.serviceUpdate file permissions.
sudo chmod 644 /etc/systemd/system/beacon-chain.service{% endtab %}
{% tab title="Teku" %} Re-generate your Teku Config file. Simply copy and paste.
cat > $HOME/teku.yaml << EOF
# network
network: "mainnet"
# p2p
p2p-enabled: true
p2p-port: 9000
# validators
validator-keys: "/var/lib/teku/validator_keys:/var/lib/teku/validator_keys"
validators-graffiti: "${MY_GRAFFITI}"
# Eth 1
eth1-endpoint: "http://localhost:8545"
# metrics
metrics-enabled: true
metrics-categories: ["BEACON","LIBP2P","NETWORK"]
metrics-port: 8008
# database
data-path: "$(echo $HOME)/tekudata"
data-storage-mode: "archive"
# rest api
rest-api-port: 5051
rest-api-docs-enabled: true
rest-api-enabled: true
# logging
log-include-validator-duties-enabled: true
log-destination: CONSOLE
EOFMove the config file to /etc/teku
sudo mv $HOME/teku.yaml /etc/teku/teku.yaml{% endtab %}
{% tab title="Prysm" %}
Re-create a unit file to define yourvalidator.service configuration. Simply copy and paste.
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)
ExecStart = $(echo $HOME)/prysm/prysm.sh validator --mainnet --graffiti "${MY_GRAFFITI}" --accept-terms-of-use --wallet-password-file $(echo $HOME)/.eth2validators/validators-password.txt
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOFMove the unit file to /etc/systemd/system
sudo mv $HOME/validator.service /etc/systemd/system/validator.serviceUpdate its permissions.
sudo chmod 644 /etc/systemd/system/validator.service{% endtab %}
{% tab title="Lodestar" %}
Run the following to re-create a unit file to define yourvalidator.service configuration. Simply copy and paste.
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= $(echo $HOME)/git/lodestar
ExecStart = yarn run cli validator run --network mainnet --graffiti "${MY_GRAFFITI}"
Restart = on-failure
[Install]
WantedBy = multi-user.target
EOFMove the unit file to /etc/systemd/system
sudo mv $HOME/validator.service /etc/systemd/system/validator.serviceUpdate its permissions.
sudo chmod 644 /etc/systemd/system/validator.service{% endtab %} {% endtabs %}
Reload the updated unit file and restart the validator process for your graffiti to take effect.
{% tabs %} {% tab title="Lighthouse | Prysm | Lodestar" %}
sudo systemctl daemon-reload
sudo systemctl restart validator{% endtab %}
{% tab title="Teku | Nimbus" %}
sudo systemctl daemon-reload
sudo systemctl restart beacon-chain
{% endtab %} {% endtabs %}
{% hint style="info" %} From time to time, be sure to update to the latest ETH1 releases to enjoy new improvements and features. {% endhint %}
{% hint style="success" %} ****π₯ Pro tip: Plan your update to overlap with the longest attestation gap. Learn how here. {% endhint %}
Stop your eth1 node process.
# This can take a few minutes.
sudo systemctl stop eth1Update the eth1 node package or binaries.
{% tabs %} {% tab title="Geth" %} Review the latest release notes at https://github.com/ethereum/go-ethereum/releases
sudo apt update
sudo apt upgrade -y{% endtab %}
{% tab title="OpenEthereum (Parity)" %} Review the latest release at https://github.com/openethereum/openethereum/releases
Automatically download the latest linux release, un-zip, add execute permissions and cleanup.
cd $HOME
# backup previous openethereum version in case of rollback
mv openethereum openethereum_backup_$(date +"%Y%d%m-%H%M%S")
# store new version in openethreum directory
mkdir openethereum && cd openethereum
# download latest version
curl -s https://api.github.com/repos/openethereum/openethereum/releases/latest | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux | xargs wget -q --show-progress
# unzip
unzip openethereum*.zip
# add execute permission
chmod +x openethereum
# cleanup
rm openethereum*.zip{% endtab %}
{% tab title="Besu" %} Review the latest release at https://github.com/hyperledger/besu/releases
File can be downloaded from https://dl.bintray.com/hyperledger-org/besu-repo
Manually find the desired file from above repo and modify the wget command with the URL.
Example:
wget -O besu.tar.gz https://dl.bintray.com/hyperledger-org/besu-repo/besu-20.10.1.tar.gz
cd $HOME
# backup previous besu version in case of rollback
mv besu besu_backup_$(date +"%Y%d%m-%H%M%S")
# download latest besu
wget -O besu.tar.gz <https URL to latest tax.gz linux file>
# untar
tar -xvf besu.tar.gz
# cleanup
rm besu.tar.gz
# rename besu to standard folder location
mv besu* besu{% endtab %}
{% tab title="Nethermind" %} Review the latest release at https://github.com/NethermindEth/nethermind/releases
Automatically download the latest linux release, un-zip and cleanup.
cd $HOME
# backup previous nethermind version in case of rollback
mv nethermind nethermind_backup_$(date +"%Y%d%m-%H%M%S")
# store new version in nethermind directory
mkdir nethermind && cd nethermind
# download latest version
curl -s https://api.github.com/repos/NethermindEth/nethermind/releases/latest | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux | xargs wget -q --show-progress
# unzip
unzip -o nethermind*.zip
# cleanup
rm nethermind*linux*.zip{% endtab %} {% endtabs %}
Start your eth1 node process.
sudo systemctl start eth1Check the logs to verify the services are working properly and ensure there are no errors.
{% tabs %} {% tab title="Lighthouse | Prysm | Lodestar" %}
sudo systemctl status eth1 status beacon-chain validator{% endtab %}
{% tab title="Nimbus | Teku" %}
sudo systemctl status eth1 beacon-chain
{% endtab %} {% endtabs %}
Finally, verify your validator's attestations are working with public block explorer such as
Enter your validator's pubkey to view its status.
{% hint style="info" %} Learn about attestation effectiveness from Attestant.io {% endhint %}
{% hint style="info" %} This change will result in increased bandwidth and memory usage. Tweak and tailor appropriately for your hardware.
Kudos to RΓ©my Roy for this strat. {% endhint %}
Edit your beacon-chain.service unit file (except for Teku).
sudo nano /etc/systemd/system/beacon-chain.serviceAdd the following flag to increase peers on the ExecStart line.
{% tabs %} {% tab title="Lighthouse" %}
--target-peers 100
# Example
# lighthouse bn --target-peers 100 --staking --metrics --network mainnet{% endtab %}
{% tab title="Nimbus" %}
--max-peers=100
# Example
# /usr/bin/nimbus_beacon_node --network=mainnet --max-peers=100{% endtab %}
{% tab title="Teku" %}
# Edit teku.yaml
sudo nano /etc/teku/teku.yaml
# add the following line to teku.yaml and save the file
p2p-peer-upper-bound: 100{% endtab %}
{% tab title="Prysm" %}
--p2p-max-peers=100
# Example
# prysm.sh beacon-chain --mainnet --p2p-max-peers=100 --http-web3provider=http://127.0.0.1:8545 --accept-terms-of-use {% endtab %}
{% tab title="Lodestar" %}
--network.maxPeers 100
# Example
# yarn run cli beacon --network.maxPeers 100 --network mainnet{% endtab %} {% endtabs %}
Reload the updated unit file and restart the beacon-chain process to complete this change.
sudo systemctl daemon-reload
sudo systemctl restart beacon-chain{% hint style="info" %} Especially useful during eth1 upgrades, when your primary node is temporarily unavailable. {% endhint %}
Edit your beacon-chain.service unit file.
sudo nano /etc/systemd/system/beacon-chain.serviceAdd the following flag on the ExecStart line.
{% tabs %} {% tab title="Lighthouse" %}
--eth1-endpoints <http://alternate eth1 endpoints>
# Example, separate endpoints with commas.
# --eth1-endpoints http://localhost:8545,https://nodes.mewapi.io/rpc/eth,https://mainnet.eth.cloud.ava.do,https://mainnet.infura.io/v3/xxx{% endtab %}
{% tab title="Prysm" %}
--fallback-web3provider=<http://<alternate eth1 provider one> --fallback-web3provider=<http://<alternate eth1 provider two>
# Example, repeat flag for multiple eth1 providers
# --fallback-web3provider=https://nodes.mewapi.io/rpc/eth --fallback-web3provider=https://mainnet.infura.io/v3/YOUR-PROJECT-ID{% endtab %} {% endtabs %}
{% hint style="info" %} πΈ Find free ethereum fallback nodes at https://ethereumnodes.com/ {% endhint %}
Reload the updated unit file and restart the beacon-chain process to complete this change.
sudo systemctl daemon-reload
sudo systemctl restart beacon-chainLearn how to at the following quick guide.
{% page-ref page="how-to-find-longest-attestation-slot-gap.md" %}
{% hint style="info" %} Allows the VC (validator client) to connect to multiple BN (beacon nodes). This means your validator client can use multiple BNs. Whenever a BN fails to respond, the VC will try again with the next BN.
Must install a BN of the same eth2 client on another server.
Currently only works for Lighthouse. {% endhint %}
Edit your validator.service unit file.
sudo nano /etc/systemd/system/validator.serviceAdd the following flag on the ExecStart line.
{% tabs %} {% tab title="Lighthouse" %}
--beacon-nodes <BEACON-NODE ENDPOINTS>
# Example, separate endpoints with commas.
# lighthouse vc --beacon-nodes http://localhost:5052,http://192.168.1.100:5052
# If localhost is not responsive (perhaps during an update), the VC will attempt to use 192.168.1.100 instead.{% endtab %} {% endtabs %}
Reload the updated unit file and restart the validator process to complete this change.
sudo systemctl daemon-reload
sudo systemctl restart validator{% tabs %} {% tab title="Lighthouse" %} {% embed url="https://discord.gg/cyAszAh" %} {% endtab %}
{% tab title="Nimbus" %} {% embed url="https://discord.gg/XRxWahP" %} {% endtab %}
{% tab title="Teku" %} {% embed url="https://discord.gg/7hPv2T6" %} {% endtab %}
{% tab title="Prysm" %} {% embed url="https://discord.gg/XkyZSSk4My" %} {% endtab %}
{% tab title="Lodestar" %} {% embed url="https://discord.gg/aMxzVcr" %} {% endtab %}
{% tab title="CoinCashew" %} {% embed url="https://discord.gg/w8Bx8W2HPW" %} {% endtab %} {% endtabs %}
{% embed url="https://www.reddit.com/r/ethstaker/" %}
Appreciate the hard work done by the fine folks at the following links which served as a foundation for creating this guide.
{% embed url="https://launchpad.ethereum.org/" %}
{% embed url="https://pegasys.tech/teku-ethereum-2-for-enterprise/" %}
{% embed url="https://docs.teku.pegasys.tech/en/latest/HowTo/Get-Started/Build-From-Source/" %}
{% embed url="https://lighthouse-book.sigmaprime.io/intro.html" caption="" %}
{% embed url="https://status-im.github.io/nimbus-eth2/intro.html" %}
{% embed url="https://prylabs.net/participate" %}
{% embed url="https://docs.prylabs.network/docs/getting-started/" %}
{% embed url="https://chainsafe.github.io/lodestar/installation/" %}
{% embed url="https://beaconcha.in/" %}
{% embed url="https://beaconscan.com/" caption="" %}
{% embed url="https://hackmd.io/@benjaminion/eth2\_news/" caption="" %}
{% embed url="https://www.reddit.com/r/ethstaker" caption="" %}
{% embed url="https://blog.ethereum.org/" caption="" %}
{% embed url="https://someresat.medium.com/" %}
{% embed url="https://github.com/metanull-operator/eth2-ubuntu" %}
{% embed url="https://agstakingco.gitbook.io/eth-2-0-staking-guide-medalla/" %}
Hardware Staking Guide https://www.reddit.com/r/ethstaker/comments/j3mlup/a_slightly_updated_look_at_hardware_for_staking/
{% embed url="https://medium.com/@RaymondDurk/how-to-stake-for-ethereum-2-0-with-dappnode-231fa7689c02" %}
{% embed url="https://kb.beaconcha.in/" %}