Main Menu
Execution Client
Consensus Client
Validator
Tools
Plugins
Mevboost
System Administration
All types of node operators: Solo staking, Full node, CSM Staking Node
**Step 1: Configure your network, port forwarding and firewall.** * With EthPillar, configuration can be changed at: * **Tools > UFW Firewall > Enable firewall with default settings** * Port forwarding is [manually configured](/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet/part-i-installation/step-2-configuring-node#configure-port-forwarding), depending on your router. * Confirm port forwarding is working with **Tools** > **Port Checker** * Alternatively configure manually per the manual guide. [Click here for detailed network configuration.](/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet/part-i-installation/step-2-configuring-node#network-configuration) **Step 2: Configure your BIOS to auto power on after power loss** Actual steps vary depending on your computer's BIOS. General idea here:Lido CSM Staking Node Operators
**Step 1: Generate Validator Keys:** * Generate new CSM validator keys for the Lido withdrawal vault * `Ethpillar > Validator Client > Generate / Import Validator Keys` **Step 2: Upload JSON Deposit Data:** * Upload the newly generated deposit data file for your CSM keystores to the Lido CSM Widget. [CSM Holesky](https://csm.testnet.fi/?ref=ethpillar) or [CSM Mainnet](https://csm.lido.fi/?ref=ethpillar) * Provide the required bond amount in ETH/stETH/wstETH. **Step 3: Monitor Validator Key Deposit:** * Wait for your CSM validator keys to be deposited by Lido. * Ensure your node remains online during the process.Additional steps for Solo Stakers
**Step 1: Setup Validator Keys** * Familarize yourself with the main guide's section on [setting up your validator keys.](/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet/part-i-installation/step-5-installing-validator/setting-up-validator-keys) * When ready to generate your keys, go to **EthPillar > Validator Client > Generate / Import Validator Keys** **Step 2: Upload deposit\_data.json to Launchpad** * To begin staking on Ethereum as a validator, you need to submit to the Launchpad your deposit\_data.json file, which includes crucial withdrawal address details, and pay the required deposit of 32ETH per validator. **Step 3: Congrats!** * Now you're waiting in the Entry Queue [https://www.validatorqueue.com](https://www.validatorqueue.com/) * Check out the [next steps from the main guide](https://www.coincashew.com/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet/part-i-installation/step-5-installing-validator/next-steps) for further knowledge. Especially the FAQ's "Wen staking rewards?"Change Networks: How to switch between testnet and mainnet with EthPillar ?
To switch to mainnet, there are two recommended methods. * **Cleanest and most problem-free option**: Reformat Ubuntu OS and re-install EthPillar. * **Use EthPillar:** Navigate to **System Administration > Change Network**Exit Validator: How do I exit a validator?
If you already have VEMs created, skip to step 2. Step 1: Navigate to EthPillar > Validator > Generate Voluntary Exit Message Step 2: Broadcast Voluntary Exit MessageAdd Validators: I already have validators running. I want to add one more validator. How do I do that?
Navigate to, **EthPillar > Validator Client > Generate / Import Validator Keys** From there you will pick 1 of 2 options. * Import validator keys from offline key generation or backup * Add new or regenerate existing validator keys from Secret Recovery PhraseNode Types: What is a failover staking node?
**Purpose**: To provide high availability, you would run TWO (or more) failover staking nodes on separate machines. Point your validator client to your two failover staking nodes. **What**: A failover staking node is made up of an execution client, consensus client and mevboost. **How to**: To configure for nimbus validator client, edit your validator client configuration.Withdrawal Address: Can I have different withdraw addresses per validator or only 1 per setup?
Different withdrawal addresses per validator are possible if you run the ./deposit tool separately for each validator.Generating Keystores: Can I generate 10 validator keystores and activate them one by one at the launchpad?
You can but it would require manual editing as you'll need to change the deposit\_data json.Migrate or Upgrade Staking Setup: How to switch to EthPillar from a V1 Staking setup or other staking tool
To migrate from a different staking setup, find your most applicable situation: **Cleanest and most problem-free option**: * 1\) Reformat Ubuntu Operating System * 2\) Install EthPillar * 3\) Import validator keys **Existing V1 Staking Setup:** OGs and genesis stakers :saluting\_face: * 1\) [Uninstall V1 Staking Setup](/coins/overview-eth/archived-guides/guide-or-how-to-setup-a-validator-on-eth2-mainnet/part-ii-maintenance/uninstalling-v1-staking-node) * 2\) Install EthPillar * 3\) Import validator keys **Other staking automation tools or cloud hosted setups:** * 1\) Uninstall / cancel / existing tool or service provider * 2\) Install EthPillar * 3\) Import validator keys :white\_check\_mark: **To avoid slashing penalties**, ensure your validator keys are deleted from existing staking setups.EthPillar's TUI - Navigate the menu to control your node
Client Stack
Big picture: Execution / Consensus / Validator
Ethereum Staking Node
Plus - Can re-use or re-purpose existing hardware
Minus - Initial cost to purchase new computer equipment
Plus - Enterprise-grade, professional data centers.
Minus - Not your hardware, not your node. It's possible the hosting provide can view your node's contents.
| | Freedom |Plus - Do whatever you want. Plan your own upgrades.
Minus - With great freedom and power, you are solely responsible for your node.
Plus - Professionally managed.
Minus - At the mercy of the host's actions, data center outages are possible.
Creating a user called ethereum
Create a new user called `ethereum` ```bash sudo useradd -m -s /bin/bash ethereum ``` Set the password for ethereum user ```bash sudo passwd ethereum ``` Add ethereum to the sudo group ```bash sudo usermod -aG sudo ethereum ``` Log out and log back in as this new user. **Using Ubuntu Server**: Use the following commands. ```bash exit ssh ethereum@staking.node.ip.address ``` **Using Ubuntu Desktop**: Log out can be found in the top right corner under the Power Icon. Click the `ethereum` user account and enter password.Creating a new SSH Key
Create a new SSH key pair on **your client machine (i.e. local laptop)**. Run this on **your client machine,** not remote node. Update the comment with your email or a comment. ``` ssh-keygen -t ed25519 -C "name@email.com" ``` You'll see this next: ``` Generating public/private ed25519 key pair. Enter file in which to save the key (/home/Option 1: Transferring with ssh-copy-id
Works with Linux or MacOS. Use option 2 for Windows. ```bash ssh-copy-id -i ~/.ssh/id_ed25519 ethereum@staking.node.ip.address ```Option 2: Copying the key manually
First, begin by obtaining your SSH Public key. For Linux/Mac, ``` cat ~/.ssh/id_ed25519.pub ``` For Windows, Open a command prompt (Windows Key + R, then `cmd`, finally press enter). ``` type %USERPROFILE%\.ssh\id_ed25519.pub ``` The output will look similar to the following: ``` ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAoc78lv+XDh2znunKXUF/9zBNJrM4Nh67yut9RN14SX name@email.com ``` Copy into your clipboard this output, also known as your public SSH key. On your **remote node**, run the following: ``` mkdir -p ~/.ssh nano ~/.ssh/authorized_keys ``` First, a directory called **.ssh** is created, then `Nano` is a text editor for editing a special file called **authorized\_keys** With nano opening the authorized\_keys file, right-click your mouse to paste your public SSH key into this file. To exit and save, press `Ctrl` + `X`, then `Y`, then`Enter`. Verify your public SSH key was properly pasted into the file. ``` cat ~/.ssh/authorized_keys ```Disabling root login and password based login
:information\_source: With SSH key authentication enabled, there's still the possibility to connect to your remote node with login and password, a much less secure and brute force-able attack vector. Login via ssh with your new ethereum user ``` ssh ethereum@staking.node.ip.address ``` Edit the ssh configuration file ``` sudo nano /etc/ssh/sshd_config ``` Locate **PubkeyAuthentication** and update to yes. Delete the # in front. ``` PubkeyAuthentication yes ``` Locate **PasswordAuthentication** and update to no. Delete the # in front. ``` PasswordAuthentication no ``` Locate **PermitRootLogin** and update to prohibit-password. Delete the # in front. ``` PermitRootLogin prohibit-password ``` Locate **PermitEmptyPasswords** and update to no. Delete the # in front. ``` PermitEmptyPassword no ``` To exit and save, press `Ctrl` + `X`, then `Y`, then`Enter`. Validate the syntax of your new SSH configuration. ``` sudo sshd -t ``` If no errors with the syntax validation, restart the SSH process. ``` sudo systemctl restart sshd ``` Verify the login still works. ``` ssh ethereum@staking.node.ip.address ``` **Optional**: Make logging in easier by updating your local ssh config. To simplify the ssh command needed to log in to your server, consider updating on your local client machine the `$HOME/myUserName/.ssh/config` file: ```bash Host ethereum-server User ethereum HostNameEL Diversity as of Dec 2024
| Client | RAM Use | Minimum Database Size | Database Growth | Time to sync |
|---|---|---|---|---|
| Nethermind | 8 GB | 0.95 TB | 18 GB/week | Fastest, 2hrs+ |
| Besu | 12 GB | 1.2 TB | 10 GB/week | Medium, 16hrs+ |
| Geth | 8 GB | 1.2 TB | 8 GB/week | Fast, 8hrs+ |
| Erigon 3 | 8 GB | 0.92 GB | 8 GB/week | Medium, 16hrs+ |
| Reth | 10 GB | 1.2 TB | 4GB/week | Medium, 16hrs+ |
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-zip and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/NethermindEth/nethermind/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux-x64)" echo Downloading URL: $BINARIES_URL cd $HOME wget -O nethermind.zip $BINARIES_URL unzip -o nethermind.zip -d $HOME/nethermind rm nethermind.zip ``` Install the binaries.sudo mv $HOME/nethermind /usr/local/bin/nethermind
Option 2 - Build from source code
Install .NET SDK build dependencies. ```bash # Get latest .net sdk curl -L https://dot.net/v1/dotnet-install.sh -o dotnet-install.sh chmod +x ./dotnet-install.sh ./dotnet-install.sh --channel 9.0 --runtime aspnetcore ``` Build the binaries. ```bash mkdir -p ~/git cd ~/git # Clone the repo git clone https://github.com/NethermindEth/nethermind.git cd nethermind # Get new tags git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build dotnet publish src/Nethermind/Nethermind.Runner -c release -o nethermind ``` Verify Nethermind was properly built by checking the version. ```shell ./nethermind/nethermind --version ``` Sample output of a compatible version. ``` Version: 1.25.2+78c7bf5f Commit: 78c7bf5f2c0819f23e248ee6d108c17cd053ffd3 Build Date: 2024-01-23 06:34:53Z OS: Linux x64 Runtime: .NET 8.0.1 ``` Install the binaries.sudo mv $HOME/git/nethermind/nethermind /usr/local/bin
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/hyperledger/besu/releases/latest" TAG=$(curl -s $RELEASE_URL | jq -r .tag_name) BINARIES_URL="https://github.com/hyperledger/besu/releases/download/$TAG/besu-$TAG.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME wget -O besu.tar.gz $BINARIES_URL tar -xzvf besu.tar.gz -C $HOME rm besu.tar.gz sudo mv $HOME/besu-${TAG} besu ``` Install the binaries.sudo mv $HOME/besu /usr/local/bin/besu
Option 2 - Build from source code
Build the binaries. ```bash mkdir -p ~/git cd ~/git # Clone the repo git clone https://github.com/hyperledger/besu.git cd besu # Get new tags git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build ./gradlew installDist ``` Verify Besu was properly built by checking the version. ```shell ./build/install/besu/bin/besu --version ``` Sample output of a compatible version. ``` besu/v23.4.0/linux-x86_64/openjdk-java-17 ``` Install the binaries.sudo cp -a $HOME/git/besu/build/install/besu /usr/local/bin/besu
Option 1 - Download binaries
RELEASE_URL="https://geth.ethereum.org/downloads"
FILE="https://gethstore.blob.core.windows.net/builds/geth-linux-amd64[a-zA-Z0-9./?=_%:-]*.tar.gz"
BINARIES_URL="$(curl -s $RELEASE_URL | grep -Eo $FILE | head -1)"
echo Downloading URL: $BINARIES_URL
cd $HOME
wget -O geth.tar.gz $BINARIES_URL
tar -xzvf geth.tar.gz -C $HOME
rm geth.tar.gz
sudo mv $HOME/geth-* geth
Option 2 - Build from source code
Install Go dependencies. Latest version [available here](https://go.dev/dl/). ```bash wget -O go.tar.gzsudo cp $HOME/git/go-ethereum/build/bin/geth /usr/local/bin
[Unit]
Description=Geth Execution Layer Client service for Mainnet
Wants=network-online.target
After=network-online.target
Documentation=https://www.coincashew.com
[Service]
Type=simple
User=execution
Group=execution
Restart=on-failure
RestartSec=3
KillSignal=SIGINT
TimeoutStopSec=900
ExecStart=/usr/local/bin/geth \
--mainnet \
--port 30303 \
--http.port 8545 \
--authrpc.port 8551 \
--maxpeers 50 \
--metrics \
--http \
--datadir=/var/lib/geth \
--pprof \
--state.scheme=path \
--authrpc.jwtsecret=/secrets/jwtsecret
[Install]
WantedBy=multi-user.target
sudo journalctl -fu execution | ccze
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/erigontech/erigon/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux_amd64.tar.gz)" echo Downloading URL: $BINARIES_URL cd $HOME wget -O erigon.tar.gz $BINARIES_URL tar -xzvf erigon.tar.gz -C $HOME mv erigon_* erigon ``` Install the binaries and cleanup. ```bash sudo mv $HOME/erigon/erigon /usr/local/bin rm -rf erigon erigon.tar.gz ```Option 2 - Build from source code
Install Go dependencies. Latest version [available here](https://go.dev/dl/). ```bash wget -O go.tar.gzsudo cp $HOME/git/erigon/build/bin/erigon /usr/local/bin
Option 1 - Download binaries
```bash RELEASE_URL="https://api.github.com/repos/paradigmxyz/reth/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r '.assets[] | select(.name | startswith ("reth")) | .browser_download_url' | grep x86_64-unknown-linux-gnu.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME wget -O reth.tar.gz $BINARIES_URL tar -xzvf reth.tar.gz -C $HOME rm reth.tar.gz ``` Install the binaries and display the version. ```bash sudo mv $HOME/reth /usr/local/bin reth --version ```Option 2 - Build from source code
**Install rust dependency** ```bash curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh ``` When prompted, enter '1' to proceed with the default install. Update your environment variables. ```bash echo export PATH="$HOME/.cargo/bin:$PATH" >> ~/.bashrc source ~/.bashrc ``` Install rust dependencies. ```bash sudo apt-get update sudo apt install -y git libclang-dev pkg-config build-essential ``` Build the binaries. ```bash mkdir -p ~/git cd ~/git git clone https://github.com/paradigmxyz/reth.git cd reth git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build the release cargo build --release --features jemalloc ``` In case of compilation errors, run the following sequence. ```bash rustup update cargo clean cargo build --release --features jemalloc ``` Verify Reth was built properly by checking the version number. ```bash ~/git/reth/target/release/reth --version ``` Install the binary. ```bash sudo cp ~/git/reth/target/release/reth /usr/local/bin ```[Unit]
Description=Reth Execution Layer Client service for Mainnet
Wants=network-online.target
After=network-online.target
Documentation=https://www.coincashew.com
[Service]
Type=simple
User=execution
Group=execution
Restart=on-failure
RestartSec=3
KillSignal=SIGINT
TimeoutStopSec=900
Environment=RUST_LOG=info
ExecStart=/usr/local/bin/reth node \
--full \
--chain mainnet \
--datadir=/var/lib/reth \
--metrics 127.0.0.1:6060 \
--port 30303 \
--discovery.port 30303 \
--enable-discv5-discovery \
--discovery.v5.port 30304 \
--http \
--http.port 8545 \
--http.api="rpc,eth,web3,net,debug" \
--log.file.directory=/var/lib/reth/logs \
--max-outbound-peers 25 \
--max-inbound-peers 25 \
--authrpc.jwtsecret=/secrets/jwtsecret
[Install]
WantedBy=multi-user.target
sudo journalctl -fu execution | ccze
CL Diversity as of Dec 2024
| Client | CPU Use | RAM Use | Database Size | Time to sync head |
|---|---|---|---|---|
| Lighthouse | Medium | 6 GB | 120 - 150 GB | Instant via checkpoint |
| Lodestar | Medium | 8 GB | 120 - 150 GB | Instant via checkpoint |
| Teku | Medium | 10 GB | 120 - 150 GB | Instant via checkpoint |
| Nimbus | Low | 3 GB | 120 - 150 GB | Instant via checkpoint |
| Prysm | Medium | 6 GB | 120 - 150 GB | Instant via checkpoint |
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/sigp/lighthouse/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep x86_64-unknown-linux-gnu.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O lighthouse.tar.gz $BINARIES_URL # Untar tar -xzvf lighthouse.tar.gz -C $HOME # Cleanup rm lighthouse.tar.gz ``` Install the binaries.sudo mv $HOME/lighthouse /usr/local/bin/lighthouse
Option 2 - Build from source code
**Install rust dependency** ```bash curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh ``` When prompted, enter '1' to proceed with the default install. Update your environment variables. ```bash echo export PATH="$HOME/.cargo/bin:$PATH" >> ~/.bashrc source ~/.bashrc ``` Install rust dependencies. ```bash sudo apt-get update sudo apt install -y git gcc g++ make cmake pkg-config libssl-dev libclang-dev clang protobuf-compiler ``` Build the binaries. ```bash mkdir -p ~/git cd ~/git git clone -b stable https://github.com/sigp/lighthouse.git cd lighthouse make ``` In case of compilation errors, run the following sequence. ```bash rustup update cargo clean make ``` Verify lighthouse was built properly by checking the version number. ``` lighthouse --version ``` Install the binary. ```bash sudo cp $HOME/.cargo/bin/lighthouse /usr/local/bin/lighthouse ```Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/ChainSafe/lodestar/releases/latest" LATEST_TAG="$(curl -s $RELEASE_URL | jq -r ".tag_name")" BINARIES_URL="https://github.com/ChainSafe/lodestar/releases/download/${LATEST_TAG}/lodestar-${LATEST_TAG}-linux-amd64.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O lodestar.tar.gz $BINARIES_URL # Untar tar -xzvf lodestar.tar.gz -C $HOME # Cleanup rm lodestar.tar.gz ``` Install the binaries. ```bash sudo mkdir -p /usr/local/bin/lodestar sudo mv $HOME/lodestar /usr/local/bin/lodestar ```Option 2 - Build from source code
Install yarn. ```bash curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list sudo apt update sudo apt install yarn -y ``` Confirm yarn is installed properly. ```bash yarn --version # Should output version >= 1.22.19 ``` Install nodejs. ```bash #Download and import the Nodesource GPG key sudo apt-get update sudo apt-get install -y ca-certificates curl gnupg sudo mkdir -p /etc/apt/keyrings curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg #Create deb repository NODE_MAJOR=20 echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list #Run Update and Install sudo apt-get update sudo apt-get install nodejs -y ``` Install and build Lodestar. ```bash mkdir -p ~/git cd ~/git git clone -b stable https://github.com/chainsafe/lodestar.git cd lodestar yarn install yarn run build ``` Verify Lodestar was installed properly by displaying the version. ```bash ./lodestar --version ``` Sample output of a compatible version. ``` π Lodestar: TypeScript Implementation of the Ethereum Consensus Beacon Chain. * Version: v1.8.0/stable/a4b29cf * by ChainSafe Systems, 2018-2022 ``` Install the binaries. ```bash sudo cp -a $HOME/git/lodestar /usr/local/bin/lodestar ```Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/ConsenSys/teku/releases/latest" LATEST_TAG="$(curl -s $RELEASE_URL | jq -r ".tag_name")" BINARIES_URL="https://artifacts.consensys.net/public/teku/raw/names/teku.tar.gz/versions/${LATEST_TAG}/teku-${LATEST_TAG}.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O teku.tar.gz $BINARIES_URL # Untar tar -xzvf teku.tar.gz -C $HOME # Rename folder mv teku-${LATEST_TAG} teku # Cleanup rm teku.tar.gz ``` Install the binaries.sudo mv $HOME/teku /usr/local/bin/teku
Option 2 - Build from source code
Build the binaries. ```bash mkdir -p ~/git cd ~/git git clone https://github.com/ConsenSys/teku.git cd teku # Get new tags git fetch --tags RELEASETAG=$(curl -s https://api.github.com/repos/ConsenSys/teku/releases/latest | jq -r .tag_name) git checkout tags/$RELEASETAG ./gradlew distTar installDist ``` Verify Teku was built properly by displaying the version. ```shell cd $HOME/git/teku/build/install/teku/bin ./teku --version ``` Install the binaries. ```shell sudo cp -a $HOME/git/teku/build/install/teku /usr/local/bin/teku ```Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/status-im/nimbus-eth2/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep _Linux_amd64.*.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O nimbus.tar.gz $BINARIES_URL # Untar tar -xzvf nimbus.tar.gz -C $HOME # Rename folder mv nimbus-eth2_Linux_amd64_* nimbus # Cleanup rm nimbus.tar.gz ``` Install the binaries, display version and cleanup.sudo mv nimbus/build/nimbus_beacon_node /usr/local/bin
sudo mv nimbus/build/nimbus_validator_client /usr/local/bin
nimbus_beacon_node --version
rm -r nimbus
Option 2 - Build from source code
Install dependencies. ```bash sudo apt-get update sudo apt-get install curl build-essential git -y ``` Build the binary. ```bash mkdir -p ~/git cd ~/git git clone -b stable https://github.com/status-im/nimbus-eth2 cd nimbus-eth2 make -j$(nproc) update make -j$(nproc) nimbus_beacon_node make -j$(nproc) nimbus_validator_client ``` Verify Nimbus was built properly by displaying the version. ```bash cd $HOME/git/nimbus-eth2/build ./nimbus_beacon_node --version ``` Install the binary.sudo cp $HOME/git/nimbus-eth2/build/nimbus_beacon_node /usr/local/bin
sudo cp $HOME/git/nimbus-eth2/build/nimbus_validator_client /usr/local/bin
Option 1 - Download binaries
Run the following to automatically download the latest binaries. ```bash cd $HOME prysm_version=$(curl -f -s https://prysmaticlabs.com/releases/latest) file_beacon=beacon-chain-${prysm_version}-linux-amd64 file_validator=validator-${prysm_version}-linux-amd64 curl -f -L "https://prysmaticlabs.com/releases/${file_beacon}" -o beacon-chain curl -f -L "https://prysmaticlabs.com/releases/${file_validator}" -o validator chmod +x beacon-chain validator ``` Install the binaries.sudo mv beacon-chain validator /usr/local/bin
Option 2 - Build from source code
Install Go dependencies. Latest version [available here](https://go.dev/dl/). ```bash wget -O go.tar.gz[Unit]
Description=Prysm Consensus Layer Client service for Mainnet
Wants=network-online.target
After=network-online.target
Documentation=https://www.coincashew.com
[Service]
Type=simple
User=consensus
Group=consensus
Restart=on-failure
RestartSec=3
KillSignal=SIGINT
TimeoutStopSec=900
ExecStart=/usr/local/bin/beacon-chain \
--mainnet \
--datadir=/var/lib/prysm/beacon \
--grpc-gateway-port 5052 \
--p2p-tcp-port 13000 \
--p2p-udp-port 12000 \
--p2p-max-peers 80 \
--monitoring-port 8008 \
--checkpoint-sync-url=https://beaconstate.info \
--execution-endpoint=http://localhost:8551 \
--jwt-secret=/secrets/jwtsecret \
--accept-terms-of-use=true \
--suggested-fee-recipient=<0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS>
[Install]
WantedBy=multi-user.target
Example of Vitalik's address in checksum format
Option 1 for Ubuntu - ethstaker_deposit-cli
#### 1. Download ethstaker\_deposit-cli from Github. ```bash #Install dependencies sudo apt install jq curl -y #Setup variables RELEASE_URL="https://api.github.com/repos/eth-educators/ethstaker-deposit-cli/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux-amd64.tar.gz$)" BINARY_FILE="ethstaker_deposit-cli.tar.gz" echo "Downloading URL: $BINARIES_URL" cd $HOME #Download binary wget -O $BINARY_FILE $BINARIES_URL #Extract archive tar -xzvf $BINARY_FILE -C $HOME #Rename mv ethstaker_deposit*amd64 ethstaker_deposit-cli cd ethstaker_deposit-cli ``` #### 2. Make a new mnemonic Replace `
##### #####
## ##### ##
### ## ####### #########################
## ## ##### ## ##
## ##### ## ##
## ## ## ###
######## ## ####
## ## ### ##### #####
# ## # #####
# # # #####
## ## ##
## ## ##
## ### ## ##
############### ## ##
### ## ##
############################# ##
## ###
####### ################# ###
## ## ## ## ## ###
############## #############
Creating your keys: [####################################] <N>/<N>
Creating your keystores: [####################################] <N>/<N>
Verifying your keystores: [####################################] <N>/<N>
Verifying your deposits: [####################################] <N>/<N>
Success!
Your keys can be found at: /home/username/ethstaker_deposit-cli/validator_keys
Option 2 for Windows/Linux/Mac - Wagyu GUI
**Wagyu** is an application aimed at lowering the technical bar to staking on Ethereum. As a 'one-click installer', it provides a clean UI automating the setup and management of all the infrastructure necessary to stake without the user needing to have any technical knowledge. **Download Wagyu**: [https://wagyu.gg](https://wagyu.gg/) 1. Click create new secret recovery phrase 2. Select your network 3. Click create 4. Write down your 24 word secret recovery phrase 5. Check your phrase to confirm you copied it correctly 6. Specify number of new keys to generate 7. Specify your keystore password 8. Specify your Withdrawal address 9. Click next 10. Re-type your keystore password 11. Browse to where you want to save your keys 12. Review information and closeOption 3 - Offline Tails with ethstaker_deposit-cli
You will learn how to boot up a windows PC into an airgapped [Tails operating system](https://tails.boum.org/index.en.html). The Tails OS is an *amnesic* operating system, meaning it will save nothing and *leave no tracks behind* each time you boot it. #### **1. Prerequisites** You need: * 2 storage mediums (can be USB stick, SD cards or external hard drives) * One of them must be > 8GB * Windows or Mac computer * 30 minutes or longer depending on your download speed #### **2. Download Tails OS** Download the official image from the [Tails website](https://tails.boum.org/install/index.en.html). Might take a while, go grab a coffee. Make sure you follow the guide on the Tails website to verify your download of Tails. #### **3. Download and install the software to transfer your Tails image on your USB stick** For Windows, use one of * [Etcher](https://tails.boum.org/etcher/Etcher-Portable.exe) * [Win32 Disk Imager](https://win32diskimager.org/#download) * [Rufus](https://rufus.ie/en_US/) For Mac, download [Etcher](https://tails.boum.org/etcher/Etcher.dmg) #### **4. Making your bootable USB stick** Run the above software. This is an example how it looks like on Mac OS with etcher, but other software should be similar.
##### #####
## ##### ##
### ## ####### #########################
## ## ##### ## ##
## ##### ## ##
## ## ## ###
######## ## ####
## ## ### ##### #####
# ## # #####
# # # #####
## ## ##
## ## ##
## ### ## ##
############### ## ##
### ## ##
############################# ##
## ###
####### ################# ###
## ## ## ## ## ###
############## #############
Creating your keys: [####################################] <N>/<N>
Creating your keystores: [####################################] <N>/<N>
Verifying your keystores: [####################################] <N>/<N>
Verifying your deposits: [####################################] <N>/<N>
Success!
Your keys can be found at: /home/username/ethstaker_deposit-cli/validator_keys
Keystore file(s)
\[i.e.. keystore-16945983.json]
|- Controls the validator's ability to sign transactions
- Imported and loaded into your validator
- Keep private. Do not share with anyone
- Can be recreated from your mnemonic seed/secret recovery phrase
Deposit data file(s)
\[i.e. deposit\_data-16945983.json]
|- Public information about your validator
- Required to execute your deposit through the Ethereum Launchpad
- Can be recreated from your mnemonic seed/secret recovery phrase
mkdir -p $HOME/ethstaker_deposit-cli/validator_keys
Option 1 - File Transfer
* File transfer * Windows OS - use [WinSCP](https://winscp.net) or [FileZilla](https://filezilla-project.org/download.php?type=client) * Mac or Linux - use [FileZilla](https://filezilla-project.org/download.php?type=client) or [SFTP](https://www.digitalocean.com/community/tutorials/how-to-use-sftp-to-securely-transfer-files-with-a-remote-server) or [rsync](https://linuxize.com/post/how-to-use-rsync-for-local-and-remote-data-transfer-and-synchronization/) Transfer the **keystore-m\_xxxxxxxx.json** files to the following location on your node. ```bash $HOME/ethstaker_deposit-cli/validator_keys ```Option 2 - USB Key
### **Step 1: From OFFLINE machine, copy validator keys to a USB key.** Plug the USB key into offline machine, then locate the device name. ```bash # Locate the usb key sudo fdisk -l ``` Upon executing the above command you will get an output similar to the one below: ```bash Disk /dev/sdc: 7.4 GiB, 7948206080 bytes, 15523840 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 8192 15555555 25555555 7.4G b W95 FAT32 ``` Mount the key. Change the device name accordingly. ```bash # Create a mount point sudo mkdir -p /media/usb-drive # Mount the usb key sudo mount /dev/sdc1 /media/usb-drive ``` Copy the keys. Adjust the path names if needed. ```bash # Create a directory on the usb drive to copy the keys into sudo mkdir -p /media/usb-drive/ethstaker_deposit-cli/validator_keys # Copy the keys to the usb drive sudo cp $HOME/ethstaker_deposit-cli/validator_keys/*.json /media/usb-drive/ethstaker_deposit-cli/validator_keys # Cleanup sudo umount /media/usb-drive ``` ### **Step 2: From a USB key, copy validator keys to the NODE.** Plug the USB key into node, then locate the device name. ```bash # Locate the usb key sudo fdisk -l ``` Upon executing the above command you will get an output similar to the one below: ```bash Disk /dev/sdc: 7.4 GiB, 7948206080 bytes, 15523840 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 8192 15555555 25555555 7.4G b W95 FAT32 ``` Mount the key. Change the device name accordingly. ```bash # Create a mount point sudo mkdir -p /media/usb-drive # Mount the usb key sudo mount /dev/sdc1 /media/usb-drive ``` Copy the keys. Adjust the path names if needed. ```bash # Create a directory copy the keys into sudo mkdir -p $HOME/ethstaker_deposit-cli/validator_keys # Copy the keys to the default path sudo cp /media/usb-drive/ethstaker_deposit-cli/validator_keys/*.json $HOME/ethstaker_deposit-cli/validator_keys # Cleanup sudo umount /media/usb-drive ```sudo lighthouse account_manager validator list \
--network mainnet \
--datadir /var/lib/lighthouse
sudo adduser --system --no-create-home --group validator
sudo mkdir -p /var/lib/lodestar/validators
sudo adduser --system --no-create-home --group validator
sudo mkdir -p /var/lib/nimbus_validator
sudo adduser --system --no-create-home --group validator
sudo mkdir -p /var/lib/prysm/validators
sudo nano /var/lib/prysm/validators/password.txt
sudo /usr/local/bin/validator accounts list \
--wallet-dir=/var/lib/prysm/validators \
--mainnet
Wen staking rewards?
**Activation Queue**: Once your EL+CL is synced, validator up and running, you just wait for activation. This process can take 24+ hours. Only 900 new validators can join per day. Check the queue length: [https://wenmerge.com ](Sync Timeline
Syncing the consensus client is instantaneous with checkpoint sync but the execution client can take up to a day. On nodes with fast NVME drives and gigabit internet, expect your node to be fully synced in a few hours. **How do I know I'm fully synced?** * Check your execution client's logs and compare the block number against the most recent block on [https://etherscan.io](https://etherscan.io/) * Check EL logs: `journalctl -fu execution` * Thanks to checkpoint sync, your consensus client's is instantly synched. You can compare the slot number against the most recent slot on [https://beaconcha.in](https://beaconcha.in/) * Check CL logs: `journalctl -fu consensus`This is Leslie, the official mascot of Eth Staking
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: 'beacon'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8008']
- job_name: 'validator'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8009']
Option 1: Email Notifications
1. Visit [https://beaconcha.in/](https://beaconcha.in) 2. Sign up for an account 3. Verify your **email** 4. Search for your **validator's public address** 5. Add validators to your watchlist by clicking the **bookmark symbol**.Option 2: Telegram Notifications
1. On the menu of Grafana, select **Alerting.** 2. Click on **Contact points menu,** then **+Create contact point** button**.** 3. Give the contact point a **name**. 4. Select **Telegram** from the Integration list. 5. To complete the **Telegram API settings**, a **Telegram channel** and \*\*bot \*\*are required. For instructions on setting up a bot with `@Botfather`, see [this section](https://core.telegram.org/bots#6-botfather) of the Telegram documentation. You need to create a BOT API token. 6. Create a new telegram group. 7. Invite the bot to your new group. 8. Type at least 1 message into the group to initialize it. 9. Visit [`https://api.telegram.org/botXXX:YYY/getUpdates`](https://api.telegram.org/botXXX:YYY/getUpdates) where `XXX:YYY` is your BOT API Token. 10. 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": ``` 11. Paste the **Chat ID** into the corresponding field in **Grafana**. 12. **Save and test** the notification channel for your alerts. 13. Now you can create custom alerts from your dashboards. [Visit here to learn how to create alerts.](https://grafana.com/docs/grafana/latest/alerting/create-alerts/)Option 3: Discord Notifications
1. On the menu of Grafana, select **Alerting.** 2. Click on **Contact points menu,** then **+Create contact point** button**.** 3. Give the contact point a **name**. 4. Select **Discord** from the Integration list. 5. To complete the set up, a Discord server (and a text channel available) as well as a Webhook URL are required. For instructions on setting up a Discord's Webhooks, see [this section](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks) of their documentation. 6. Enter the Webhook **URL** in the Discord notification settings panel. 7. Click **Send Test**, which will push a confirmation message to the Discord channel. 8. Now you can create custom alerts from your dashboards. [Visit here to learn how to create alerts.](https://grafana.com/docs/grafana/latest/alerting/create-alerts/)Option 4: Slack Notifications
1. On the menu of Grafana, select **Alerting.** 2. Click on **Contact points menu,** then **+Create contact point** button**.** 3. Give the contact point a **name**. 4. Select **Slack** from the Integration list. 5. For instructions on setting up a Slack's Incoming Webhooks, see [this section](https://api.slack.com/messaging/webhooks) of their documentation. 6. Enter the Slack Incoming Webhook URL in the **URL** field. 7. Click **Send Test**, which will push a confirmation message to the Slack channel. 8. Now you can create custom alerts from your dashboards. [Visit here to learn how to create alerts.](https://grafana.com/docs/grafana/latest/alerting/create-alerts/)EthPillar Update
:rocket: [**EthPillar**](/coins/overview-eth/ethpillar): your node's buddy for easy and fast node management! Update your software with a keystroke.
#### :arrow\_forward: EthPillar Quickstart: Ubuntu One-liner Install ``` /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/coincashew/EthPillar/main/install.sh)" ``` {% endhint %} ### Nethermind
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-zip and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/NethermindEth/nethermind/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux-x64)" echo Downloading URL: $BINARIES_URL cd $HOME wget -O nethermind.zip $BINARIES_URL unzip -o nethermind.zip -d $HOME/nethermind rm nethermind.zip ``` Stop the services.sudo systemctl stop execution
Option 2 - Build from source code
Build the binaries. ```bash cd ~/git/nethermind # Get new tags git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build dotnet publish src/Nethermind/Nethermind.Runner -c release -o nethermind ``` Verify Nethermind was properly built by checking the version. ```shell ./nethermind/nethermind --version ``` Sample output of a compatible version. ``` Version: 1.25.2+78c7bf5f Commit: 78c7bf5f2c0819f23e248ee6d108c17cd053ffd3 Build Date: 2024-01-23 06:34:53Z OS: Linux x64 Runtime: .NET 8.0.1 ``` Stop the services.sudo systemctl stop execution
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/hyperledger/besu/releases/latest" TAG=$(curl -s $RELEASE_URL | jq -r .tag_name) BINARIES_URL="https://github.com/hyperledger/besu/releases/download/$TAG/besu-$TAG.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME wget -O besu.tar.gz $BINARIES_URL tar -xzvf besu.tar.gz -C $HOME rm besu.tar.gz sudo mv $HOME/besu-${TAG} besu ``` Stop the services.sudo systemctl stop execution
Option 2 - Build from source code
Build the binaries. ```bash cd ~/git/besu # Get new tags git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build ./gradlew installDist ``` Verify Besu was properly built by checking the version. ```shell ./build/install/besu/bin/besu --version ``` Sample output of a compatible version. ``` besu/v23.4.0/linux-x86_64/openjdk-java-17 ``` Stop the services.sudo systemctl stop execution
Option 1 - Download binaries
RELEASE_URL="https://geth.ethereum.org/downloads"
FILE="https://gethstore.blob.core.windows.net/builds/geth-linux-amd64[a-zA-Z0-9./?=_%:-]*.tar.gz"
BINARIES_URL="$(curl -s $RELEASE_URL | grep -Eo $FILE | head -1)"
echo Downloading URL: $BINARIES_URL
cd $HOME
wget -O geth.tar.gz $BINARIES_URL
tar -xzvf geth.tar.gz -C $HOME --strip-components=1
sudo systemctl stop execution
Option 2 - Build from source code
Build the binary. ```bash cd $HOME/git/go-ethereum # Get new tags git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build make geth ``` Stop the services.sudo systemctl stop execution
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup.RELEASE_URL="https://api.github.com/repos/erigontech/erigon/releases/latest"
BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux_amd64.tar.gz)"
echo Downloading URL: $BINARIES_URL
cd $HOME
wget -O erigon.tar.gz $BINARIES_URL
tar -xzvf erigon.tar.gz -C $HOME
mv erigon_* erigon
sudo systemctl stop execution
Option 2 - Build from source code
Build the binary. ```bash cd $HOME/git/erigon git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag make erigon ``` Stop the services.sudo systemctl stop execution
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/paradigmxyz/reth/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r '.assets[] | select(.name | startswith ("reth")) | .browser_download_url' | grep x86_64-unknown-linux-gnu.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME wget -O reth.tar.gz $BINARIES_URL tar -xzvf reth.tar.gz -C $HOME rm reth.tar.gz ``` Stop the services.sudo systemctl stop execution
Option 2 - Build from source code
Build the binaries. ```bash cd ~/git/reth git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build the release cargo build --release ``` Verify Reth was built properly by checking the version number. ```bash ~/git/reth/target/release/reth --version ``` In case of compilation errors, run the following sequence. ```bash rustup update cargo clean cargo build --release --features jemalloc ``` Stop the services.sudo systemctl stop execution
EthPillar Update
:rocket: [**EthPillar**](/coins/overview-eth/ethpillar): your node's buddy for easy and fast node management! Update your software with a keystroke.
#### :arrow\_forward: EthPillar Quickstart: Ubuntu One-liner Install ``` /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/coincashew/EthPillar/main/install.sh)" ``` {% endhint %} ### Lighthouse
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/sigp/lighthouse/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep x86_64-unknown-linux-gnu.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O lighthouse.tar.gz $BINARIES_URL # Untar tar -xzvf lighthouse.tar.gz -C $HOME # Cleanup rm lighthouse.tar.gz ``` Stop the services.sudo systemctl stop consensus validator
sudo rm /usr/local/bin/lighthouse
sudo mv $HOME/lighthouse /usr/local/bin/lighthouse
sudo systemctl start consensus validator
Option 2 - Build from source code
Build the binaries. ```bash cd ~/git/lighthouse git fetch --all && git checkout stable && git pull make ``` :bulb:**Tip**: Improve some Lighthouse benchmarks by around 20% at the expense of increased compile time? Use `maxperf` profile. * To compile with maxperf, replace the above `make` command with ```bash PROFILE=maxperf make ``` In case of compilation errors, run the following sequence. ```bash rustup update cargo clean make ``` Verify lighthouse was built properly by checking the version number. ``` lighthouse --version ``` Stop the services.sudo systemctl stop consensus validator
sudo rm /usr/local/bin/lighthouse
sudo cp $HOME/.cargo/bin/lighthouse /usr/local/bin/lighthouse
sudo systemctl start consensus validator
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/ChainSafe/lodestar/releases/latest" LATEST_TAG="$(curl -s $RELEASE_URL | jq -r ".tag_name")" BINARIES_URL="https://github.com/ChainSafe/lodestar/releases/download/${LATEST_TAG}/lodestar-${LATEST_TAG}-linux-amd64.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O lodestar.tar.gz $BINARIES_URL # Untar tar -xzvf lodestar.tar.gz -C $HOME # Cleanup rm lodestar.tar.gz ``` Stop the services.sudo systemctl stop consensus validator
Option 2 - Build from source code
Pull the latest source and build Lodestar. ```bash cd ~/git/lodestar git checkout stable && git pull yarn install yarn run build ``` :warning: In case of build errors or missing dependencies, run the following command. ```bash yarn clean:nm && yarn install ``` Verify Lodestar was installed properly by displaying the version. ```bash ./lodestar --version ``` Sample output of a compatible version. ``` π Lodestar: TypeScript Implementation of the Ethereum Consensus Beacon Chain. * Version: v1.8.0/stable/a4b29cf * by ChainSafe Systems, 2018-2022 ``` Stop the services.sudo systemctl stop consensus validator
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/ConsenSys/teku/releases/latest" LATEST_TAG="$(curl -s $RELEASE_URL | jq -r ".tag_name")" BINARIES_URL="https://artifacts.consensys.net/public/teku/raw/names/teku.tar.gz/versions/${LATEST_TAG}/teku-${LATEST_TAG}.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O teku.tar.gz $BINARIES_URL # Untar tar -xzvf teku.tar.gz -C $HOME # Rename folder mv teku-${LATEST_TAG} teku # Cleanup rm teku.tar.gz ``` Stop the services.sudo systemctl stop consensus
# If running Standalone Teku Validator
sudo systemctl stop validator
Option 2 - Build from source code
Fetch the latest tags and build the binaries. ```bash cd ~/git/teku # Get new tags git fetch --tags RELEASETAG=$(curl -s https://api.github.com/repos/ConsenSys/teku/releases/latest | jq -r .tag_name) git checkout tags/$RELEASETAG ./gradlew distTar installDist ``` Verify Teku was built properly by displaying the version. ```shell cd $HOME/git/teku/build/install/teku/bin ./teku --version ``` Stop the services.sudo systemctl stop consensus
# If running Standalone Teku Validator
sudo systemctl stop validator
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/status-im/nimbus-eth2/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep _Linux_amd64.*.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O nimbus.tar.gz $BINARIES_URL # Untar tar -xzvf nimbus.tar.gz -C $HOME # Rename folder mv nimbus-eth2_Linux_amd64_* nimbus # Cleanup rm nimbus.tar.gz ``` Stop the services.sudo systemctl stop consensus
# If running standalone Nimbus Validator
sudo systemctl stop validator
Option 2 - Build from source code
Pull the latest source code and build the binary.cd ~/git/nimbus-eth2
git checkout stable && git pull
make -j$(nproc) update
make -j$(nproc) nimbus_beacon_node
make -j$(nproc) nimbus_validator_client
Option 1 - Download binaries
Run the following to automatically download the latest binaries. ```bash cd $HOME prysm_version=$(curl -f -s https://prysmaticlabs.com/releases/latest) file_beacon=beacon-chain-${prysm_version}-linux-amd64 file_validator=validator-${prysm_version}-linux-amd64 curl -f -L "https://prysmaticlabs.com/releases/${file_beacon}" -o beacon-chain curl -f -L "https://prysmaticlabs.com/releases/${file_validator}" -o validator chmod +x beacon-chain validator ``` Stop the services.sudo systemctl stop consensus validator
Option 2 - Build from source code
Pull the latest source code and build the binaries. ```bash cd $HOME/git/prysm git fetch --tags RELEASETAG=$(curl -s https://api.github.com/repos/OffchainLabs/prysm/releases/latest | jq -r .tag_name) git checkout tags/$RELEASETAG go build -o=./build/beacon-chain ./cmd/beacon-chain go build -o=./build/validator ./cmd/validator ``` Stop the services.sudo systemctl stop consensus validator
Given your validator's public key, the index number is shown. Example of Validator 12345 from https://beaconcha.in/validator/12345
Ensure your node's block number matches the tip block of a public block explorer. Find your execution client block # with command journalctl -fu execution
Example log output:INFO \[12-06
Confirm ports are reachable with an external port checker such as
| | Check execution client logs for errors | Use the command `journalctl -fu eth1` | | Understand how to stop/start Execution client |sudo systemctl stop execution
sudo systemctl start execution
Check for a response with the command:curl -H "Content-Type: application/json" -X POST --data '{"jsonrpc":"2.0","method":"web3\_clientVersion","params":\[],"id":67}'
You should receive a response similar to:
{"jsonrpc":"2.0","id":67,"result":"Geth/v1.9.24-stable-cc05b050/linux-amd64/go1.15.5"}
Confirm ports are reachable with an external port checker such as
Click here for Port # information.
| | Understand how to stop/start consensus client |sudo systemctl stop consensus
sudo systemctl start consensus
sudo systemctl stop validator
sudo systemctl start validator
Voluntary exit procedures involve multiple steps and potential delays. For a complete overview of these steps and delays, refer to Ladislaus's informative graphic.
# change directories to binary folder
cd /usr/local/bin/lodestar
# the voluntary exit command
sudo ./lodestar validator voluntary-exit
Critically important: Your Ethereum Address from a Hardware Wallet.
Withdrawals will be sent to this address. If you stop validating and exit your validator, your 32 ETH will be sent here.
This ETH withdrawal address is one such that you control the private keys to, ideally one from a hardware wallet.
πDO NOT USE A EXCHANGE ADDRESS!π
| ### Step 2: Deposit 32 ETH per validator **Option 1**: Visit the [official Ethereum Launchpad site](https://launchpad.ethereum.org) Two important tasks to complete at the launchpad. * Upload the `deposit_data-#########.json` * Make the 32 ETH deposit transaction(s), 32 ETH per validator. 1 deposit transaction per validator. **Option 2**: Use [Abyss's Batch Ethereum Depositor](https://abyss.finance/eth2depositor) to combine many validator deposits into just 1 transaction. ### Step 3: Import New Validator Keys This step assumes your new validator keys are located in ```bash $HOME/staking-deposit-cli/validator_keys ``` If Wagyu was used to generate validator keys, move the keystore files to the above location. {% tabs %} {% tab title="Lighthouse" %} Stop your validator client. ```bash sudo systemctl stop validator ``` Import your validator keys by importing your **keystore file**. Be sure to enter your **keystore password** correctly. ```bash sudo lighthouse account validator import \ --network mainnet \ --datadir /var/lib/lighthouse \ --directory=$HOME/ethstaker_deposit-cli/validator_keys \ --reuse-password ``` Verify that your keystore file was imported successfully.sudo lighthouse account_manager validator list \
--network mainnet \
--datadir /var/lib/lighthouse
Option 1: For standalone validator
Stop your Teku client. ```bash sudo systemctl stop validator ``` Storing your **keystore password** in a text file is required so that Teku can decrypt and load your validators automatically. Create a temporary file to store your **keystore password**. Type your password in this file. ```bash sudo nano $HOME/validators-password.txt ``` To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`. Confirm that your **keystore password** is correct. ```bash sudo cat $HOME/validators-password.txt ``` Run the following command to create a corresponding password file for every one of your validators. ```bash for f in $HOME/ethstaker_deposit-cli/validator_keys/keystore*.json; do sudo cp $HOME/validators-password.txt $HOME/ethstaker_deposit-cli/validator_keys/$(basename $f .json).txt; done ``` Copy keystores to validator folder ```bash sudo cp $HOME/ethstaker_deposit-cli/validator_keys/keystore* /var/lib/teku_validator/validator_keys ``` Setup ownership permissions, including hardening the access to this directory. ```bash sudo chown -R validator:validator /var/lib/teku_validator sudo chmod -R 700 /var/lib/teku_validator ``` Verify that your validator's keystore .json files and validator's passwords .txt files are present by checking the following directory. ```bash sudo ls -l /var/lib/teku_validator/validator_keys ``` Example output of two validator's keystore.json files with matching password.txt files. ``` -rwx------ 1 consensus consensus 710 Sep 19 23:39 keystore-m_12381_3600_1_0_0-1695165818.json -rwx------ 1 consensus consensus 43 Sep 19 23:39 keystore-m_12381_3600_1_0_0-1695165818.txt -rwx------ 1 consensus consensus 710 Sep 19 23:39 keystore-m_12381_3600_2_0_0-1695165819.json -rwx------ 1 consensus consensus 43 Sep 19 23:39 keystore-m_12381_3600_2_0_0-1695165819.txt ``` Delete the temporary **keystore password** file. ```bash sudo rm $HOME/validators-password.txt ``` Finally, restart Teku to use the new validators. ```bash sudo systemctl restart validator ``` Check your logs to confirm that the validators are up and functioning. ```bash sudo journalctl -fu validator | ccze ``` For example when using 2 validators, logs will show the following: ```bash INFO - Loading 2 validator keys... INFO - Loaded 2 Validators: 95d3986, 82b225f ```Option 2: For Combined CL+VC
Stop your Teku client. ```bash sudo systemctl stop consensus ``` Storing your **keystore password** in a text file is required so that Teku can decrypt and load your validators automatically. Create a temporary file to store your **keystore password**. Type your password in this file. ```bash sudo nano $HOME/validators-password.txt ``` To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`. Confirm that your **keystore password** is correct. ```bash sudo cat $HOME/validators-password.txt ``` Run the following command to create a corresponding password file for every one of your validators. ```bash for f in $HOME/ethstaker_deposit-cli/validator_keys/keystore*.json; do sudo cp $HOME/validators-password.txt $HOME/ethstaker_deposit-cli/validator_keys/$(basename $f .json).txt; done ``` Copy keystores to validator folder ```bash sudo cp $HOME/ethstaker_deposit-cli/validator_keys/keystore* /var/lib/teku/validator_keys ``` Setup ownership permissions, including hardening the access to this directory.sudo chown -R consensus:consensus /var/lib/teku/
sudo chmod -R 700 /var/lib/teku/validator_keys
Option 1: For standalone validator
Stop your Nimbus client. ```bash sudo systemctl stop validator ``` Enter your **keystore password** to import accounts. ```bash sudo /usr/local/bin/nimbus_beacon_node deposits import \ --data-dir=/var/lib/nimbus_validator $HOME/ethstaker_deposit-cli/validator_keys ``` Now you can verify the accounts were imported successfully by doing a directory listing. ```bash sudo ls -l /var/lib/nimbus_validator/validators ``` You should see a folder named for each of your validator's pubkey. Setup ownership permissions, including hardening the access to this directory. ```bash sudo chown -R validator:validator /var/lib/nimbus_validator sudo chmod -R 700 /var/lib/nimbus_validator ``` Finally, restart Nimbus to use the new validators. ```bash sudo systemctl restart validator ``` Check your logs to confirm that the validators are up and functioning. ```bash sudo journalctl -fu validator | ccze ``` For example when using 2 validators, logs will show the following: ```bash Loading validators topics="beacval" validatorsDir=/var/lib/nimbus/validators keystore_cache_available=true Local validator attached topics="val_pool" pubkey=95d39860a0d6ea3b92cba78069d21f3a validator=95d39860 initial_fee_recipient=81ba8d5c4ae850 Local validator attached topics="val_pool" pubkey=82b225f66476962b161ed015786df00f validator=82b225f6 initial_fee_recipient=81ba8d5c4ae850 ```Option 2: For Combined CL+VC
Stop your Nimbus client. ```bash sudo systemctl stop consensus ``` Enter your **keystore password** to import accounts. ```bash sudo /usr/local/bin/nimbus_beacon_node deposits import \ --data-dir=/var/lib/nimbus $HOME/ethstaker_deposit-cli/validator_keys ``` Now you can verify the accounts were imported successfully by doing a directory listing. ```bash sudo ls -l /var/lib/nimbus/validators ``` You should see a folder named for each of your validator's pubkey. Setup ownership permissions, including hardening the access to this directory. ```bash sudo chown -R consensus:consensus /var/lib/nimbus sudo chmod -R 700 /var/lib/nimbus ``` Finally, restart Nimbus to use the new validators. ```bash sudo systemctl restart consensus ``` Check your logs to confirm that the validators are up and functioning. ```bash sudo journalctl -fu consensus | ccze ``` For example when using 2 validators, logs will show the following: ```bash Loading validators topics="beacval" validatorsDir=/var/lib/nimbus/validators keystore_cache_available=true Local validator attached topics="val_pool" pubkey=95d39860a0d6ea3b92cba78069d21f3a validator=95d39860 initial_fee_recipient=81ba8d5c4ae850 Local validator attached topics="val_pool" pubkey=82b225f66476962b161ed015786df00f validator=82b225f6 initial_fee_recipient=81ba8d5c4ae850 ```cd /usr/local/bin/prysm
sudo bazel run //validator:validator -- accounts list \
--wallet-dir=/var/lib/prysm/validator \
--mainnet
Entry Queue
One-liner screenshot
Step 1: Remove OLD Execution Client
Stop execution client and remove the service user, data paths, binaries and service files. ```bash # Stop Execution Client sudo systemctl stop execution sudo systemctl disable execution # Remove service file sudo rm /etc/systemd/system/execution.service # Nethermind sudo rm -rf /usr/local/bin/nethermind sudo rm -rf /var/lib/nethermind # Besu sudo rm -rf /usr/local/bin/besu sudo rm -rf /var/lib/besu # Geth sudo rm -rf /usr/local/bin/geth sudo rm -rf /var/lib/geth # Erigon sudo rm -rf /usr/local/bin/erigon sudo rm -rf /var/lib/erigon # Reth sudo rm -rf /usr/local/bin/reth sudo rm -rf /var/lib/reth # Remove service user sudo userdel execution ```Step 2: Install NEW Execution Client
Follow the instructions found under section: [Installing a new Execution Client.](/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet/part-i-installation/step-3-installing-execution-client) *** :fire:**Tip**: As well as being a minority client, **Nethermind** is known to be incredibly fast at syncing, often as quick as 2 hours with fast NVME drives.Step 3: Restart Consensus Client
Ensure the consensus client establishes a connection to the new execution client. ```bash sudo systemctl restart consensus ```Step 4: Update Monitoring tools
**Promentheus and Grafana**: * Revisit the [monitoring guide](/coins/overview-eth/guide-or-how-to-setup-a-validator-on-eth2-mainnet/part-i-installation/monitoring-your-validator-with-grafana-and-prometheus) and update your `prometheus.yml`configuration for the new execution client. * Ensure prometheus is connected to your new execution client's metrics port 6060. * Also import your new execution client's dashboard. **Beaconcha.in Mobile App:** * To receive new notifications, update your app's settings to indicate you're using a different execution clientRabby
Download from [https://rabby.io](https://rabby.io/) 1. Click **More** 2. Click **Custom RPC** 3. Click **Add RPC** 4. Select the network. If testnet, you might need to go back a menu and enable testnets. 5. Fill in the **RPC URL** as **Frame
Download from [https://frame.sh](https://frame.sh/) 1. Open **Chains** 2. Either add to an existing chain (i.e. Mainnet) or Click "**Add New Chain"** 3. Fill in **Primary (if new chain) or Secondary (if existing chain) RPC URL** as **Metamask
Download from [https://metamask.io](https://metamask.io/) 1. Open **Settings** 2. Open **Networks** 3. Click "**Add a network**" > **Add a network manually** 4. Fill in **New RPC URL** as **# View your disk drives
sudo -s lvm
# Change the logical volume filesystem path if required
sudo 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
sudo 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% /
Step 1: Stop consensus client
``` sudo systemctl stop consensus ```Step 2: Remove consensus client database directory
Prysm ``` sudo rm -r /var/lib/prysm/beacon/beaconchaindata ``` Lodestar ``` sudo rm -r /var/lib/lodestar/chain-db ``` Teku ``` sudo rm -r /var/lib/teku/beacon ``` Nimbus ``` sudo rm -r /var/lib/nimbus/db ``` Lighthouse ``` sudo rm -r /var/lib/lighthouse/beacon ```Step 3: Ensure a checkpoint sync server is configured
* Below examples use the default checkpoint sync endpointStep 4: Start consensus client
``` sudo systemctl daemon-reload sudo systemctl restart consensus ```Step 5: Check the beacon chain logs and ensure sync is on right chain
Verify that you are on the correct chain by visiting [https://eth-clients.github.io/checkpoint-sync-endpoints](https://eth-clients.github.io/checkpoint-sync-endpoints/) and selecting a **different** endpoint link. Verify that your log's are in agreement with the other endpoint's `epoch / slot / state root / block root` View your logs: ``` sudo journalctl -fu consensus ``` Checkpoint sync should take no more than a few minutes to re-sync. Your execution client may take longer to catch up.Mainnet tldr
**Least disk space use:** Besu/Teku 577GB **Most disk space use**: Erigon/Lodestar 1.6TBTestnet Goerli tldr
**Least disk space use:** Besu/Prysm **Most disk space use**: Erigon/Nimbusethpillar
EthPillar's TUI - Navigate the menu to control your node
Client Stack
Big picture: Execution / Consensus / Validator
Ethereum Staking Node
Plus - Can re-use or re-purpose existing hardware
Minus - Initial cost to purchase new computer equipment
Plus - Enterprise-grade, professional data centers.
Minus - Not your hardware, not your node. It's possible the hosting provide can view your node's contents.
| | Freedom |Plus - Do whatever you want. Plan your own upgrades.
Minus - With great freedom and power, you are solely responsible for your node.
Plus - Professionally managed.
Minus - At the mercy of the host's actions, data center outages are possible.
Creating a user called ethereum
Create a new user called `ethereum` ```bash sudo useradd -m -s /bin/bash ethereum ``` Set the password for ethereum user ```bash sudo passwd ethereum ``` Add ethereum to the sudo group ```bash sudo usermod -aG sudo ethereum ``` Log out and log back in as this new user. **Using Ubuntu Server**: Use the following commands. ```bash exit ssh ethereum@staking.node.ip.address ``` **Using Ubuntu Desktop**: Log out can be found in the top right corner under the Power Icon. Click the `ethereum` user account and enter password.Creating a new SSH Key
Create a new SSH key pair on **your client machine (i.e. local laptop)**. Run this on **your client machine,** not remote node. Update the comment with your email or a comment. ``` ssh-keygen -t ed25519 -C "name@email.com" ``` You'll see this next: ``` Generating public/private ed25519 key pair. Enter file in which to save the key (/home/Option 1: Transferring with ssh-copy-id
Works with Linux or MacOS. Use option 2 for Windows. ```bash ssh-copy-id -i ~/.ssh/id_ed25519 ethereum@staking.node.ip.address ```Option 2: Copying the key manually
First, begin by obtaining your SSH Public key. For Linux/Mac, ``` cat ~/.ssh/id_ed25519.pub ``` For Windows, Open a command prompt (Windows Key + R, then `cmd`, finally press enter). ``` type %USERPROFILE%\.ssh\id_ed25519.pub ``` The output will look similar to the following: ``` ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAoc78lv+XDh2znunKXUF/9zBNJrM4Nh67yut9RN14SX name@email.com ``` Copy into your clipboard this output, also known as your public SSH key. On your **remote node**, run the following: ``` mkdir -p ~/.ssh nano ~/.ssh/authorized_keys ``` First, a directory called **.ssh** is created, then `Nano` is a text editor for editing a special file called **authorized\_keys** With nano opening the authorized\_keys file, right-click your mouse to paste your public SSH key into this file. To exit and save, press `Ctrl` + `X`, then `Y`, then`Enter`. Verify your public SSH key was properly pasted into the file. ``` cat ~/.ssh/authorized_keys ```Disabling root login and password based login
:information\_source: With SSH key authentication enabled, there's still the possibility to connect to your remote node with login and password, a much less secure and brute force-able attack vector. Login via ssh with your new ethereum user ``` ssh ethereum@staking.node.ip.address ``` Edit the ssh configuration file ``` sudo nano /etc/ssh/sshd_config ``` Locate **PubkeyAuthentication** and update to yes. Delete the # in front. ``` PubkeyAuthentication yes ``` Locate **PasswordAuthentication** and update to no. Delete the # in front. ``` PasswordAuthentication no ``` Locate **PermitRootLogin** and update to prohibit-password. Delete the # in front. ``` PermitRootLogin prohibit-password ``` Locate **PermitEmptyPasswords** and update to no. Delete the # in front. ``` PermitEmptyPassword no ``` To exit and save, press `Ctrl` + `X`, then `Y`, then`Enter`. Validate the syntax of your new SSH configuration. ``` sudo sshd -t ``` If no errors with the syntax validation, restart the SSH process. ``` sudo systemctl restart sshd ``` Verify the login still works. ``` ssh ethereum@staking.node.ip.address ``` **Optional**: Make logging in easier by updating your local ssh config. To simplify the ssh command needed to log in to your server, consider updating on your local client machine the `$HOME/myUserName/.ssh/config` file: ```bash Host ethereum-server User ethereum HostNameEL Diversity as of Dec 2024
| Client | RAM Use | Minimum Database Size | Database Growth | Time to sync |
|---|---|---|---|---|
| Nethermind | 8 GB | 0.95 TB | 18 GB/week | Fastest, 2hrs+ |
| Besu | 12 GB | 1.2 TB | 10 GB/week | Medium, 16hrs+ |
| Geth | 8 GB | 1.2 TB | 8 GB/week | Fast, 8hrs+ |
| Erigon 3 | 8 GB | 0.92 GB | 8 GB/week | Medium, 16hrs+ |
| Reth | 10 GB | 1.2 TB | 4GB/week | Medium, 16hrs+ |
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-zip and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/NethermindEth/nethermind/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux-x64)" echo Downloading URL: $BINARIES_URL cd $HOME wget -O nethermind.zip $BINARIES_URL unzip -o nethermind.zip -d $HOME/nethermind rm nethermind.zip ``` Install the binaries.sudo mv $HOME/nethermind /usr/local/bin/nethermind
Option 2 - Build from source code
Install .NET SDK build dependencies. ```bash #Get latest .net sdk curl -L https://dot.net/v1/dotnet-install.sh -o dotnet-install.sh chmod +x ./dotnet-install.sh ./dotnet-install.sh --channel 9.0 --runtime aspnetcore ``` Build the binaries. ```bash mkdir -p ~/git cd ~/git # Clone the repo git clone https://github.com/NethermindEth/nethermind.git cd nethermind # Get new tags git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build dotnet publish src/Nethermind/Nethermind.Runner -c release -o nethermind ``` Verify Nethermind was properly built by checking the version. ```shell ./nethermind/nethermind --version ``` Sample output of a compatible version. ``` Version: 1.25.2+78c7bf5f Commit: 78c7bf5f2c0819f23e248ee6d108c17cd053ffd3 Build Date: 2024-01-23 06:34:53Z OS: Linux x64 Runtime: .NET 8.0.1 ``` Install the binaries.sudo mv $HOME/git/nethermind/nethermind /usr/local/bin
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/hyperledger/besu/releases/latest" TAG=$(curl -s $RELEASE_URL | jq -r .tag_name) BINARIES_URL="https://github.com/hyperledger/besu/releases/download/$TAG/besu-$TAG.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME wget -O besu.tar.gz $BINARIES_URL tar -xzvf besu.tar.gz -C $HOME rm besu.tar.gz sudo mv $HOME/besu-${TAG} besu ``` Install the binaries.sudo mv $HOME/besu /usr/local/bin/besu
Option 2 - Build from source code
Build the binaries. ```bash mkdir -p ~/git cd ~/git # Clone the repo git clone https://github.com/hyperledger/besu.git cd besu # Get new tags git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build ./gradlew installDist ``` Verify Besu was properly built by checking the version. ```shell ./build/install/besu/bin/besu --version ``` Sample output of a compatible version. ``` besu/v23.4.0/linux-x86_64/openjdk-java-17 ``` Install the binaries.sudo cp -a $HOME/git/besu/build/install/besu /usr/local/bin/besu
Option 1 - Download binaries
RELEASE_URL="https://geth.ethereum.org/downloads"
FILE="https://gethstore.blob.core.windows.net/builds/geth-linux-amd64[a-zA-Z0-9./?=_%:-]*.tar.gz"
BINARIES_URL="$(curl -s $RELEASE_URL | grep -Eo $FILE | head -1)"
echo Downloading URL: $BINARIES_URL
cd $HOME
wget -O geth.tar.gz $BINARIES_URL
tar -xzvf geth.tar.gz -C $HOME
rm geth.tar.gz
sudo mv $HOME/geth-* geth
Option 2 - Build from source code
Install Go dependencies. Latest version [available here](https://go.dev/dl/). ```bash wget -O go.tar.gzsudo cp $HOME/git/go-ethereum/build/bin/geth /usr/local/bin
[Unit]
Description=Geth Execution Layer Client service for Hoodi
Wants=network-online.target
After=network-online.target
Documentation=https://www.coincashew.com
[Service]
Type=simple
User=execution
Group=execution
Restart=on-failure
RestartSec=3
KillSignal=SIGINT
TimeoutStopSec=900
ExecStart=/usr/local/bin/geth \
--hoodi \
--port 30303 \
--http.port 8545 \
--authrpc.port 8551 \
--maxpeers 50 \
--metrics \
--http \
--datadir=/var/lib/geth \
--pprof \
--state.scheme=path \
--authrpc.jwtsecret=/secrets/jwtsecret
[Install]
WantedBy=multi-user.target
sudo journalctl -fu execution | ccze
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/erigontech/erigon/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux_amd64.tar.gz)" echo Downloading URL: $BINARIES_URL cd $HOME wget -O erigon.tar.gz $BINARIES_URL tar -xzvf erigon.tar.gz -C $HOME mv erigon_* erigon ``` Install the binaries and cleanup. ```bash sudo mv $HOME/erigon/erigon /usr/local/bin rm -rf erigon erigon.tar.gz ```Option 2 - Build from source code
Install Go dependencies. Latest version [available here](https://go.dev/dl/). ```bash wget -O go.tar.gzsudo cp $HOME/git/erigon/build/bin/erigon /usr/local/bin
Option 1 - Download binaries
```bash RELEASE_URL="https://api.github.com/repos/paradigmxyz/reth/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r '.assets[] | select(.name | startswith ("reth")) | .browser_download_url' | grep x86_64-unknown-linux-gnu.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME wget -O reth.tar.gz $BINARIES_URL tar -xzvf reth.tar.gz -C $HOME rm reth.tar.gz ``` Install the binaries and display the version. ```bash sudo mv $HOME/reth /usr/local/bin reth --version ```Option 2 - Build from source code
**Install rust dependency** ```bash curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh ``` When prompted, enter '1' to proceed with the default install. Update your environment variables. ```bash echo export PATH="$HOME/.cargo/bin:$PATH" >> ~/.bashrc source ~/.bashrc ``` Install rust dependencies. ```bash sudo apt-get update sudo apt install -y git libclang-dev pkg-config build-essential ``` Build the binaries. ```bash mkdir -p ~/git cd ~/git git clone https://github.com/paradigmxyz/reth.git cd reth git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build the release cargo build --release --features jemalloc ``` In case of compilation errors, run the following sequence. ```bash rustup update cargo clean cargo build --release --features jemalloc ``` Verify Reth was built properly by checking the version number. ```bash ~/git/reth/target/release/reth --version ``` Install the binary. ```bash sudo cp ~/git/reth/target/release/reth /usr/local/bin ```[Unit]
Description=Reth Execution Layer Client service for Hoodi
Wants=network-online.target
After=network-online.target
Documentation=https://www.coincashew.com
[Service]
Type=simple
User=execution
Group=execution
Restart=on-failure
RestartSec=3
KillSignal=SIGINT
TimeoutStopSec=900
Environment=RUST_LOG=info
ExecStart=/usr/local/bin/reth node \
--full \
--chain hoodi \
--datadir=/var/lib/reth \
--metrics 127.0.0.1:6060 \
--port 30303 \
--discovery.port 30303 \
--enable-discv5-discovery \
--discovery.v5.port 30304 \
--http \
--http.port 8545 \
--http.api="rpc,eth,web3,net,debug" \
--log.file.directory=/var/lib/reth/logs \
--max-outbound-peers 25 \
--max-inbound-peers 25 \
--authrpc.jwtsecret=/secrets/jwtsecret
[Install]
WantedBy=multi-user.target
sudo journalctl -fu execution | ccze
CL Diversity as of Dec 2024
| Client | CPU Use | RAM Use | Database Size | Time to sync head |
|---|---|---|---|---|
| Lighthouse | Medium | 6 GB | 120 - 150 GB | Instant via checkpoint |
| Lodestar | Medium | 8 GB | 120 - 150 GB | Instant via checkpoint |
| Teku | Medium | 10 GB | 120 - 150 GB | Instant via checkpoint |
| Nimbus | Low | 3 GB | 120 - 150 GB | Instant via checkpoint |
| Prysm | Medium | 6 GB | 120 - 150 GB | Instant via checkpoint |
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/sigp/lighthouse/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep x86_64-unknown-linux-gnu.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O lighthouse.tar.gz $BINARIES_URL # Untar tar -xzvf lighthouse.tar.gz -C $HOME # Cleanup rm lighthouse.tar.gz ``` Install the binaries.sudo mv $HOME/lighthouse /usr/local/bin/lighthouse
Option 2 - Build from source code
**Install rust dependency** ```bash curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh ``` When prompted, enter '1' to proceed with the default install. Update your environment variables. ```bash echo export PATH="$HOME/.cargo/bin:$PATH" >> ~/.bashrc source ~/.bashrc ``` Install rust dependencies. ```bash sudo apt-get update sudo apt install -y git gcc g++ make cmake pkg-config libssl-dev libclang-dev clang protobuf-compiler ``` Build the binaries. ```bash mkdir -p ~/git cd ~/git git clone -b stable https://github.com/sigp/lighthouse.git cd lighthouse make ``` In case of compilation errors, run the following sequence. ```bash rustup update cargo clean make ``` Verify lighthouse was built properly by checking the version number. ``` lighthouse --version ``` Install the binary. ```bash sudo cp $HOME/.cargo/bin/lighthouse /usr/local/bin/lighthouse ```Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/ChainSafe/lodestar/releases/latest" LATEST_TAG="$(curl -s $RELEASE_URL | jq -r ".tag_name")" BINARIES_URL="https://github.com/ChainSafe/lodestar/releases/download/${LATEST_TAG}/lodestar-${LATEST_TAG}-linux-amd64.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O lodestar.tar.gz $BINARIES_URL # Untar tar -xzvf lodestar.tar.gz -C $HOME # Cleanup rm lodestar.tar.gz ``` Install the binaries.sudo mkdir -p /usr/local/bin/lodestar
sudo mv $HOME/lodestar /usr/local/bin/lodestar
Option 2 - Build from source code
Install yarn. ```bash curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list sudo apt update sudo apt install yarn -y ``` Confirm yarn is installed properly. ```bash yarn --version # Should output version >= 1.22.19 ``` Install nodejs. ```bash #Download and import the Nodesource GPG key sudo apt-get update sudo apt-get install -y ca-certificates curl gnupg sudo mkdir -p /etc/apt/keyrings curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg #Create deb repository NODE_MAJOR=20 echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list #Run Update and Install sudo apt-get update sudo apt-get install nodejs -y ``` Install and build Lodestar. ```bash mkdir -p ~/git cd ~/git git clone -b stable https://github.com/chainsafe/lodestar.git cd lodestar yarn install yarn run build ``` Verify Lodestar was installed properly by displaying the version. ```bash ./lodestar --version ``` Sample output of a compatible version. ``` π Lodestar: TypeScript Implementation of the Ethereum Consensus Beacon Chain. * Version: v1.8.0/stable/a4b29cf * by ChainSafe Systems, 2018-2022 ``` Install the binaries. ```bash sudo cp -a $HOME/git/lodestar /usr/local/bin/lodestar ```Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/ConsenSys/teku/releases/latest" LATEST_TAG="$(curl -s $RELEASE_URL | jq -r ".tag_name")" BINARIES_URL="https://artifacts.consensys.net/public/teku/raw/names/teku.tar.gz/versions/${LATEST_TAG}/teku-${LATEST_TAG}.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O teku.tar.gz $BINARIES_URL # Untar tar -xzvf teku.tar.gz -C $HOME # Rename folder mv teku-${LATEST_TAG} teku # Cleanup rm teku.tar.gz ``` Install the binaries.sudo mv $HOME/teku /usr/local/bin/teku
Option 2 - Build from source code
Build the binaries. ```bash mkdir -p ~/git cd ~/git git clone https://github.com/ConsenSys/teku.git cd teku # Get new tags git fetch --tags RELEASETAG=$(curl -s https://api.github.com/repos/ConsenSys/teku/releases/latest | jq -r .tag_name) git checkout tags/$RELEASETAG ./gradlew distTar installDist ``` Verify Teku was built properly by displaying the version. ```shell cd $HOME/git/teku/build/install/teku/bin ./teku --version ``` Install the binaries. ```shell sudo cp -a $HOME/git/teku/build/install/teku /usr/local/bin/teku ```Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/status-im/nimbus-eth2/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep _Linux_amd64.*.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O nimbus.tar.gz $BINARIES_URL # Untar tar -xzvf nimbus.tar.gz -C $HOME # Rename folder mv nimbus-eth2_Linux_amd64_* nimbus # Cleanup rm nimbus.tar.gz ``` Install the binaries, display version and cleanup. ```bash sudo mv nimbus/build/nimbus_beacon_node /usr/local/bin sudo mv nimbus/build/nimbus_validator_client /usr/local/bin nimbus_beacon_node --version rm -r nimbus ```Option 2 - Build from source code
Install dependencies. ```bash sudo apt-get update sudo apt-get install curl build-essential git -y ``` Build the binary. ```bash mkdir -p ~/git cd ~/git git clone -b stable https://github.com/status-im/nimbus-eth2 cd nimbus-eth2 make -j$(nproc) update make -j$(nproc) nimbus_beacon_node make -j$(nproc) nimbus_validator_client ``` Verify Nimbus was built properly by displaying the version. ```bash cd $HOME/git/nimbus-eth2/build ./nimbus_beacon_node --version ``` Install the binary. ```bash sudo cp $HOME/git/nimbus-eth2/build/nimbus_beacon_node /usr/local/bin sudo cp $HOME/git/nimbus-eth2/build/nimbus_validator_client /usr/local/bin ```Option 1 - Download binaries
Run the following to automatically download the latest binaries. ```bash cd $HOME prysm_version=$(curl -f -s https://prysmaticlabs.com/releases/latest) file_beacon=beacon-chain-${prysm_version}-linux-amd64 file_validator=validator-${prysm_version}-linux-amd64 curl -f -L "https://prysmaticlabs.com/releases/${file_beacon}" -o beacon-chain curl -f -L "https://prysmaticlabs.com/releases/${file_validator}" -o validator chmod +x beacon-chain validator ``` Install the binaries.sudo mv beacon-chain validator /usr/local/bin
Option 2 - Build from source code
Install Go dependencies. Latest version [available here](https://go.dev/dl/). ```bash wget -O go.tar.gz[Unit]
Description=Prysm Consensus Layer Client service for Hoodi
Wants=network-online.target
After=network-online.target
Documentation=https://www.coincashew.com
[Service]
Type=simple
User=consensus
Group=consensus
Restart=on-failure
RestartSec=3
KillSignal=SIGINT
TimeoutStopSec=900
ExecStart=/usr/local/bin/beacon-chain \
--hoodi \
--datadir=/var/lib/prysm/beacon \
--grpc-gateway-port 5052 \
--p2p-tcp-port 13000 \
--p2p-udp-port 12000 \
--p2p-max-peers 80 \
--monitoring-port 8008 \
--checkpoint-sync-url=https://hoodi.beaconstate.ethstaker.cc \
--execution-endpoint=http://localhost:8551 \
--jwt-secret=/secrets/jwtsecret \
--accept-terms-of-use=true \
--suggested-fee-recipient=<0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS>
[Install]
WantedBy=multi-user.target
Option 1: Ethstaker's #cheap-hoodi-validator Channel
* **Step 1**: Visit the [Ethstaker Discord](https://discord.io/ethstaker) and join the #cheap-hoodi-validator channel * **Step 2**: Use the `/cheap-hoodi-deposit` slash command and follow the instructions from the bot. You need to start typing the slash command and it will show above your input box where you can use it. * **Requirement**: In order to use the cheap hoodi validator process, you must now set your withdrawal address to `0x4D496CcC28058B1D74B7a19541663E21154f9c84` when creating your validator keys and deposit file. This is to prevent abuses of this service.Option 2: Use faucets from pk910 / axol.io
* pk910:Example of Vitalik's address in checksum format
Option 1 for Ubuntu - ethstaker_deposit-cli
**1. Download ethstaker\_deposit-cli from Github.** ```bash #Install dependencies sudo apt install jq curl -y #Setup variables RELEASE_URL="https://api.github.com/repos/eth-educators/ethstaker-deposit-cli/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux-amd64.tar.gz$)" BINARY_FILE="ethstaker_deposit-cli.tar.gz" echo "Downloading URL: $BINARIES_URL" cd $HOME #Download binary wget -O $BINARY_FILE $BINARIES_URL #Extract archive tar -xzvf $BINARY_FILE -C $HOME #Rename mv ethstaker_deposit*amd64 ethstaker_deposit-cli cd ethstaker_deposit-cli ``` **2. Make a new mnemonic** Replace `Option 2 for Windows/Linux/Mac - Wagyu GUI
**Wagyu** is an application aimed at lowering the technical bar to staking on Ethereum. As a 'one-click installer', it provides a clean UI automating the setup and management of all the infrastructure necessary to stake without the user needing to have any technical knowledge. **Download Wagyu**: [https://wagyu.gg](https://wagyu.gg/) 1. Click create new secret recovery phrase 2. Select your network 3. Click create 4. Write down your 24 word secret recovery phrase 5. Check your phrase to confirm you copied it correctly 6. Specify number of new keys to generate 7. Specify your keystore password 8. Specify your Withdrawal address 9. Click next 10. Re-type your keystore password 11. Browse to where you want to save your keys 12. Review information and closeOption 3 - Offline Tails with ethstaker_deposit-cli
You will learn how to boot up a windows PC into an airgapped [Tails operating system](https://tails.boum.org/index.en.html). The Tails OS is an *amnesic* operating system, meaning it will save nothing and *leave no tracks behind* each time you boot it. **1. Prerequisites** You need: * 2 storage mediums (can be USB stick, SD cards or external hard drives) * One of them must be > 8GB * Windows or Mac computer * 30 minutes or longer depending on your download speed **2. Download Tails OS** Download the official image from the [Tails website](https://tails.boum.org/install/index.en.html). Might take a while, go grab a coffee. Make sure you follow the guide on the Tails website to verify your download of Tails. **3. Download and install the software to transfer your Tails image on your USB stick** For Windows, use one of * [Etcher](https://tails.boum.org/etcher/Etcher-Portable.exe) * [Win32 Disk Imager](https://win32diskimager.org/#download) * [Rufus](https://rufus.ie/en_US/) For Mac, download [Etcher](https://tails.boum.org/etcher/Etcher.dmg) **4. Making your bootable USB stick** Run the above software. This is an example how it looks like on Mac OS with etcher, but other software should be similar.Keystore file(s)
\[i.e.. keystore-16945983.json]
|- Controls the validator's ability to sign transactions
- Imported and loaded into your validator
- Keep private. Do not share with anyone
- Can be recreated from your mnemonic seed/secret recovery phrase
Deposit data file(s)
\[i.e. deposit\_data-16945983.json]
|- Public information about your validator
- Required to execute your deposit through the Ethereum Launchpad
- Can be recreated from your mnemonic seed/secret recovery phrase
mkdir -p $HOME/ethstaker_deposit-cli/validator_keys
Option 1 - File Transfer
* File transfer * Windows OS - use [WinSCP](https://winscp.net) or [FileZilla](https://filezilla-project.org/download.php?type=client) * Mac or Linux - use [FileZilla](https://filezilla-project.org/download.php?type=client) or [SFTP](https://www.digitalocean.com/community/tutorials/how-to-use-sftp-to-securely-transfer-files-with-a-remote-server) or [rsync](https://linuxize.com/post/how-to-use-rsync-for-local-and-remote-data-transfer-and-synchronization/) Transfer the **keystore-m\_xxxxxxxx.json** files to the following location on your node. ```bash $HOME/ethstaker-deposit-cli/validator_keys ```Option 2 - USB Key
### **Step 1: From OFFLINE machine, copy validator keys to a USB key.** Plug the USB key into offline machine, then locate the device name. ```bash # Locate the usb key sudo fdisk -l ``` Upon executing the above command you will get an output similar to the one below: ```bash Disk /dev/sdc: 7.4 GiB, 7948206080 bytes, 15523840 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 8192 15555555 25555555 7.4G b W95 FAT32 ``` Mount the key. Change the device name accordingly. ```bash # Create a mount point sudo mkdir -p /media/usb-drive # Mount the usb key sudo mount /dev/sdc1 /media/usb-drive ``` Copy the keys. Adjust the path names if needed. ```bash # Create a directory on the usb drive to copy the keys into sudo mkdir -p /media/usb-drive/ethstaker-deposit-cli/validator_keys # Copy the keys to the usb drive sudo cp $HOME/ethstaker-deposit-cli/validator_keys/*.json /media/usb-drive/ethstaker-deposit-cli/validator_keys # Cleanup sudo umount /media/usb-drive ``` ### **Step 2: From a USB key, copy validator keys to the NODE.** Plug the USB key into node, then locate the device name. ```bash # Locate the usb key sudo fdisk -l ``` Upon executing the above command you will get an output similar to the one below: ```bash Disk /dev/sdc: 7.4 GiB, 7948206080 bytes, 15523840 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 8192 15555555 25555555 7.4G b W95 FAT32 ``` Mount the key. Change the device name accordingly. ```bash # Create a mount point sudo mkdir -p /media/usb-drive # Mount the usb key sudo mount /dev/sdc1 /media/usb-drive ``` Copy the keys. Adjust the path names if needed. ```bash # Create a directory copy the keys into sudo mkdir -p $HOME/ethstaker-deposit-cli/validator_keys # Copy the keys to the default path sudo cp /media/usb-drive/ethstaker-deposit-cli/validator_keys/*.json $HOME/ethstaker-deposit-cli/validator_keys # Cleanup sudo umount /media/usb-drive ```sudo lighthouse account_manager validator list \
--network hoodi \
--datadir /var/lib/lighthouse
sudo adduser --system --no-create-home --group validator
sudo mkdir -p /var/lib/lodestar/validators
sudo adduser --system --no-create-home --group validator
sudo mkdir -p /var/lib/nimbus_validator
sudo adduser --system --no-create-home --group validator
sudo mkdir -p /var/lib/prysm/validators
sudo nano /var/lib/prysm/validators/password.txt
sudo /usr/local/bin/validator accounts list \
--wallet-dir=/var/lib/prysm/validators \
--hoodi
Wen staking rewards?
**Activation Queue**: Once your EL+CL is synced, validator up and running, you just wait for activation. This process can take 24+ hours. Only 900 new validators can join per day. Check the queue length: [https://wenmerge.com ](Sync Timeline
Syncing the consensus client is instantaneous with checkpoint sync but the execution client can take up to a day. On nodes with fast NVME drives and gigabit internet, expect your node to be fully synced in a few hours. **How do I know I'm fully synced?** * Check your execution client's logs and compare the block number against the most recent block onThis is Leslie, the official mascot of Eth Staking
EthPillar Update
:rocket: [**EthPillar**](/coins/overview-eth/ethpillar): your node's buddy for easy and fast node management! Update your software with a keystroke.
#### :arrow\_forward: EthPillar Quickstart: Ubuntu One-liner Install ``` /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/coincashew/EthPillar/main/install.sh)" ``` {% endhint %} ### Nethermind
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-zip and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/NethermindEth/nethermind/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux-x64)" echo Downloading URL: $BINARIES_URL cd $HOME wget -O nethermind.zip $BINARIES_URL unzip -o nethermind.zip -d $HOME/nethermind rm nethermind.zip ``` Stop the services.sudo systemctl stop execution
Option 2 - Build from source code
Build the binaries. ```bash cd ~/git/nethermind # Get new tags git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build dotnet publish src/Nethermind/Nethermind.Runner -c release -o nethermind ``` Verify Nethermind was properly built by checking the version. ```shell ./nethermind/nethermind --version ``` Sample output of a compatible version. ``` Version: 1.25.2+78c7bf5f Commit: 78c7bf5f2c0819f23e248ee6d108c17cd053ffd3 Build Date: 2024-01-23 06:34:53Z OS: Linux x64 Runtime: .NET 8.0.1 ``` Stop the services.sudo systemctl stop execution
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/hyperledger/besu/releases/latest" TAG=$(curl -s $RELEASE_URL | jq -r .tag_name) BINARIES_URL="https://github.com/hyperledger/besu/releases/download/$TAG/besu-$TAG.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME wget -O besu.tar.gz $BINARIES_URL tar -xzvf besu.tar.gz -C $HOME rm besu.tar.gz sudo mv $HOME/besu-${TAG} besu ``` Stop the services.sudo systemctl stop execution
Option 2 - Build from source code
Build the binaries. ```bash cd ~/git/besu # Get new tags git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build ./gradlew installDist ``` Verify Besu was properly built by checking the version. ```shell ./build/install/besu/bin/besu --version ``` Sample output of a compatible version. ``` besu/v23.4.0/linux-x86_64/openjdk-java-17 ``` Stop the services.sudo systemctl stop execution
Option 1 - Download binaries
RELEASE_URL="https://geth.ethereum.org/downloads"
FILE="https://gethstore.blob.core.windows.net/builds/geth-linux-amd64[a-zA-Z0-9./?=_%:-]*.tar.gz"
BINARIES_URL="$(curl -s $RELEASE_URL | grep -Eo $FILE | head -1)"
echo Downloading URL: $BINARIES_URL
cd $HOME
wget -O geth.tar.gz $BINARIES_URL
tar -xzvf geth.tar.gz -C $HOME --strip-components=1
sudo systemctl stop execution
Option 2 - Build from source code
Build the binary. ```bash cd $HOME/git/go-ethereum # Get new tags git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build make geth ``` Stop the services.sudo systemctl stop execution
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup.RELEASE_URL="https://api.github.com/repos/erigontech/erigon/releases/latest"
BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux_amd64.tar.gz)"
echo Downloading URL: $BINARIES_URL
cd $HOME
wget -O erigon.tar.gz $BINARIES_URL
tar -xzvf erigon.tar.gz -C $HOME
mv erigon_* erigon
sudo systemctl stop execution
Option 2 - Build from source code
Build the binary. ```bash cd $HOME/git/erigon git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag make erigon ``` Stop the services.sudo systemctl stop execution
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/paradigmxyz/reth/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r '.assets[] | select(.name | startswith ("reth")) | .browser_download_url' | grep x86_64-unknown-linux-gnu.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME wget -O reth.tar.gz $BINARIES_URL tar -xzvf reth.tar.gz -C $HOME rm reth.tar.gz ``` Stop the services.sudo systemctl stop execution
Option 2 - Build from source code
Build the binaries. ```bash cd ~/git/reth git fetch --tags # Get latest tag name latestTag=$(git describe --tags `git rev-list --tags --max-count=1`) # Checkout latest tag git checkout $latestTag # Build the release cargo build --release --features jemalloc ``` Verify Reth was built properly by checking the version number. ```bash ~/git/reth/target/release/reth --version ``` In case of compilation errors, run the following sequence. ```bash rustup update cargo clean cargo build --release --features jemalloc ``` Stop the services.sudo systemctl stop execution
EthPillar Update
:rocket: [**EthPillar**](/coins/overview-eth/ethpillar): your node's buddy for easy and fast node management! Update your software with a keystroke.
#### :arrow\_forward: EthPillar Quickstart: Ubuntu One-liner Install ``` /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/coincashew/EthPillar/main/install.sh)" ``` {% endhint %} ### Lighthouse
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/sigp/lighthouse/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep x86_64-unknown-linux-gnu.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O lighthouse.tar.gz $BINARIES_URL # Untar tar -xzvf lighthouse.tar.gz -C $HOME # Cleanup rm lighthouse.tar.gz ``` Stop the services.sudo systemctl stop consensus validator
sudo rm /usr/local/bin/lighthouse
sudo mv $HOME/lighthouse /usr/local/bin/lighthouse
sudo systemctl start consensus validator
Option 2 - Build from source code
Build the binaries. ```bash cd ~/git/lighthouse git fetch --all && git checkout stable && git pull make ``` :bulb:**Tip**: Improve some Lighthouse benchmarks by around 20% at the expense of increased compile time? Use `maxperf` profile. * To compile with maxperf, replace the above `make` command with ```bash PROFILE=maxperf make ``` In case of compilation errors, run the following sequence. ```bash rustup update cargo clean make ``` Verify lighthouse was built properly by checking the version number. ``` lighthouse --version ``` Stop the services.sudo systemctl stop consensus validator
sudo rm /usr/local/bin/lighthouse
sudo cp $HOME/.cargo/bin/lighthouse /usr/local/bin/lighthouse
sudo systemctl start consensus validator
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/ChainSafe/lodestar/releases/latest" LATEST_TAG="$(curl -s $RELEASE_URL | jq -r ".tag_name")" BINARIES_URL="https://github.com/ChainSafe/lodestar/releases/download/${LATEST_TAG}/lodestar-${LATEST_TAG}-linux-amd64.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O lodestar.tar.gz $BINARIES_URL # Untar tar -xzvf lodestar.tar.gz -C $HOME # Cleanup rm lodestar.tar.gz ``` Stop the services.sudo systemctl stop consensus validator
Option 2 - Build from source code
Pull the latest source and build Lodestar. ```bash cd ~/git/lodestar git checkout stable && git pull yarn install yarn run build ``` :warning: In case of build errors or missing dependencies, run the following command. ```bash yarn clean:nm && yarn install ``` Verify Lodestar was installed properly by displaying the version. ```bash ./lodestar --version ``` Sample output of a compatible version. ``` π Lodestar: TypeScript Implementation of the Ethereum Consensus Beacon Chain. * Version: v1.8.0/stable/a4b29cf * by ChainSafe Systems, 2018-2022 ``` Stop the services.sudo systemctl stop consensus validator
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/ConsenSys/teku/releases/latest" LATEST_TAG="$(curl -s $RELEASE_URL | jq -r ".tag_name")" BINARIES_URL="https://artifacts.consensys.net/public/teku/raw/names/teku.tar.gz/versions/${LATEST_TAG}/teku-${LATEST_TAG}.tar.gz" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O teku.tar.gz $BINARIES_URL # Untar tar -xzvf teku.tar.gz -C $HOME # Rename folder mv teku-${LATEST_TAG} teku # Cleanup rm teku.tar.gz ``` Stop the services.sudo systemctl stop consensus
# If running Standalone Teku Validator
sudo systemctl stop validator
Option 2 - Build from source code
Fetch the latest tags and build the binaries. ```bash cd ~/git/teku # Get new tags git fetch --tags RELEASETAG=$(curl -s https://api.github.com/repos/ConsenSys/teku/releases/latest | jq -r .tag_name) git checkout tags/$RELEASETAG ./gradlew distTar installDist ``` Verify Teku was built properly by displaying the version. ```shell cd $HOME/git/teku/build/install/teku/bin ./teku --version ``` Stop the services.sudo systemctl stop consensus
# If running Standalone Teku Validator
sudo systemctl stop validator
Option 1 - Download binaries
Run the following to automatically download the latest linux release, un-tar and cleanup. ```bash RELEASE_URL="https://api.github.com/repos/status-im/nimbus-eth2/releases/latest" BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep _Linux_amd64.*.tar.gz$)" echo Downloading URL: $BINARIES_URL cd $HOME # Download wget -O nimbus.tar.gz $BINARIES_URL # Untar tar -xzvf nimbus.tar.gz -C $HOME # Rename folder mv nimbus-eth2_Linux_amd64_* nimbus # Cleanup rm nimbus.tar.gz ``` Stop the services.sudo systemctl stop consensus
# If running standalone Nimbus Validator
sudo systemctl stop validator
Option 2 - Build from source code
Pull the latest source code and build the binary.cd ~/git/nimbus-eth2
git checkout stable && git pull
make -j$(nproc) update
make -j$(nproc) nimbus_beacon_node
make -j$(nproc) nimbus_validator_client
Option 1 - Download binaries
Run the following to automatically download the latest binaries. ```bash cd $HOME prysm_version=$(curl -f -s https://prysmaticlabs.com/releases/latest) file_beacon=beacon-chain-${prysm_version}-linux-amd64 file_validator=validator-${prysm_version}-linux-amd64 curl -f -L "https://prysmaticlabs.com/releases/${file_beacon}" -o beacon-chain curl -f -L "https://prysmaticlabs.com/releases/${file_validator}" -o validator chmod +x beacon-chain validator ``` Stop the services.sudo systemctl stop consensus validator
Option 2 - Build from source code
Pull the latest source code and build the binaries. ```bash cd $HOME/git/prysm git fetch --tags RELEASETAG=$(curl -s https://api.github.com/repos/OffchainLabs/prysm/releases/latest | jq -r .tag_name) git checkout tags/$RELEASETAG go build -o=./build/beacon-chain ./cmd/beacon-chain go build -o=./build/validator ./cmd/validator ``` Stop the services.sudo systemctl stop consensus validator
EthPillar's TUI - Navigate the menu to control your node
Client Stack
Big picture: Execution / Consensus / Validator
Ethereum Staking Node
Plus - Can re-use or re-purpose existing hardware
Minus - Initial cost to purchase new computer equipment
Plus - Enterprise-grade, professional data centers.
Minus - Not your hardware, not your node. It's possible the hosting provide can view your node's contents.
| | Freedom |Plus - Do whatever you want. Plan your own upgrades.
Minus - With great freedom and power, you are solely responsible for your node.
Plus - Professionally managed.
Minus - At the mercy of the host's actions, data center outages are possible.