# Guide | Ethereum Staking on Zhejiang Testnet
## Your Mission - #TestingTheWithdrawalsShanghai
* **Overview**: To participate in the public testnet known as **Zhejiang**, the first public effort to test Ethereum’s upgrade to enabling validator withdrawals with a hardfork called "Shanghai-Capella" or also known as [EIP 4855](https://eips.ethereum.org/EIPS/eip-4895).
* **Goals**: To test your staking setups, practice voluntary exits and validator withdrawals.
* **Staked ETH:** With the new ability to withdraw staked ETH since beacon chain genesis on December 1 2020, this upgrade to Ethereum POS will add flexibility and attract the next wave of stakers and innovation.
* **Client Diversity**: Within the Ethereum network of nodes, you want to improve [Ethereum's client diversity](https://ethereum.org/en/developers/docs/nodes-and-clients/client-diversity/) by choosing a minority execution and consensus client combination.
* **Timeline**: Assuming this testnet is thoroughly tested, mainnet Ethereum could be upgraded sometime in March 2023.
{% hint style="warning" %}
As of early February 2023, Besu is the most minority execution client with 6.8% of nodes. Lodestar is by far the most minority consensus client with 0.29% representation.
{% endhint %}
Client Diversity
## How Staking on Ethereum Works
1. Acquire some hardware (laptop, desktop, server) or rent a VPS (cloud server): You need to run a node to stake.
2. Sync an execution layer client
3. Sync a consensus layer client
4. Generate your validator keys and import them into your validator client
5. Monitor and maintain your node
A Ethereum node consists of the Execution Layer + Consensus Layer.
A Ethereum Staking node is the previous plus a Validator client.
Client Stack
Big picture: Execution / Consensus / Validator
## Prerequisites
This guide was written for aspiring Ethereum stakers who have basic familiarity with command line tools and it was tested against Ubuntu 22.04.1 LTS client. You’ll want a dedicated cloud VPS or local desktop/server/laptop running a clean install of Ubuntu preferably.
If using a VPS or remote server, install and start the SSH client for your operating system:
**Windows**: [PuTTY](https://www.puttygen.com/download-putty)
**MacOS and Linux**: from the Terminal, use the native command:
```
ssh @
```
## How to Run Commands
* Commands are to be run in a terminal window or ssh terminal.
* Commands preceded by `sudo` will prompt for your password at first, and periodically afterwards.
## **Minimum Hardware Requirements**
* **Operating system:** 64-bit Linux (i.e. Ubuntu 22.04 LTS Server or Desktop)
* **Processor:** Dual core CPU, Intel Core i5–760 or AMD FX-8100 or better
* **Memory:** 16GB RAM
* **Storage:** 40GB SSD
## **Recommended Hardware Requirements**
{% hint style="info" %}
Once done with testnet staking, this hardware configuration would be suitable for a mainnet staking node.
{% endhint %}
* **Operating system:** 64-bit Linux (i.e. Ubuntu 22.04 LTS Server or Desktop)
* **Processor:** Intel i5 or AMD Ryzen 5 or better.
* **Memory:** 32GB RAM
* **Storage:** 2TB SSD or NVME
* **Network**: 100 Mbit or faster connection with at least 2TB per month data plan
{% hint style="info" %}
For examples of actual staking hardware builds, check out [RocketPool’s hardware guide](https://github.com/rocket-pool/docs.rocketpool.net/blob/main/src/guides/node/local/hardware.md).
{% endhint %}
Ethereum Staking Node
{% hint style="success" %}
**Pro Staking Tip**: Highly recommend you begin with a brand new instance of an OS, VM, and/or machine. Avoid headaches by NOT reusing testnet keys, wallets, or databases for your validator.
{% endhint %}
## How to participate with Zhejiang
Step 1. Install dependencies and updates
Install packages and update OS.
```
sudo apt-get update && sudo apt-get upgrade -y
sudo apt-get install git ufw curl ccze -y
```
Reboot your machine to update installation.
```
sudo reboot
```
Step 2. Configure Firewall
Initialize the firewall with Ethereum’s p2p ports and ssh.
Confirm the settings are in effect.
```
sudo ufw status numbered
```
Example output:
```
Status: active
To Action From
-- ------ ----
[ 1] 9000/udp ALLOW IN Anywhere
[ 2] 22/tcp ALLOW IN Anywhere
[ 3] 30303/tcp ALLOW IN Anywhere
[ 4] 9000/tcp ALLOW IN Anywhere
[ 5] 9000/udp (v6) ALLOW IN Anywhere (v6)
[ 6] 22/tcp (v6) ALLOW IN Anywhere (v6)
[ 7] 30303/tcp (v6) ALLOW IN Anywhere (v6)
[ 8] 9000/tcp (v6) ALLOW IN Anywhere (v6)
```
{% hint style="info" %}
For optimal connectivity, ensure Port Forwarding is setup for your router. Learn to port foward with guides found at [https://portforward.com/how-to-port-forward](https://portforward.com/how-to-port-forward/)
{% endhint %}
Step 3. Synchronize Time with Chrony
Install Chrony with the following.
```
sudo apt-get install chrony -y
```
Wait a few seconds, then verify that Chrony is syncing time.
```
chronyc tracking
```
Step 4. Download Zhejiang configuration files
#Setup git directory
mkdir ~/git && cd ~/git
#Clone the testnet config files
git clone https://github.com/ethpandaops/withdrawals-testnet.git
#Make a directory to store config files
sudo mkdir -p /var/lib/ethereum/zhejiang
#Copy config files to default location
sudo cp -R ~/git/withdrawals-testnet/zhejiang-testnet/custom_config_data /var/lib/ethereum/zhejiang
### Step 5. Setup Execution Layer Client
Setup your execution layer client, your choice of **Nethermind, Erigon, Geth or Besu.**
{% hint style="warning" %}
Only one execution layer client is required per node.
{% endhint %}
{% hint style="info" %}
[**Hyperledger Besu**](https://besu.hyperledger.org/) is an open-source Ethereum client designed for demanding enterprise applications requiring secure, high-performance transaction processing in a private network. It's developed under the Apache 2.0 license and written in **Java**.
[**Nethermind**](https://docs.nethermind.io/nethermind/) is all about performance and flexibility. Built on .NET core, a widespread, enterprise-friendly platform, Nethermind makes integration with existing infrastructures simple, without losing sight of stability, reliability, data integrity, and security.
[**Erigon**](https://github.com/ledgerwatch/erigon) is an implementation of Ethereum innovating on the efficiency frontier, written in Go.
[**Geth**](https://geth.ethereum.org/) - Go-ethereum (aka Geth) is an Ethereum client built in [Go](https://go.dev). It is one of the original and most popular Ethereum clients.
{% endhint %}
Install Nethermind
Install dependencies.
```bash
sudo apt-get update
sudo apt-get install curl libsnappy-dev libc6-dev jq libc6 unzip -y
```
Review the latest release at
Run the following to automatically download the latest linux release, un-zip and cleanup.
```bash
cd $HOME
curl -s https://api.github.com/repos/NethermindEth/nethermind/releases/latest | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux-x64 | xargs wget -q --show-progress
unzip -o nethermind*.zip -d $HOME/nethermind
rm nethermind*linux*.zip
```
Install the binaries.
sudo cp -a $HOME/nethermind /usr/local/bin/nethermind
Download the testnet configs.
```bash
cd /usr/local/bin/nethermind/configs
wget https://raw.githubusercontent.com/NethermindEth/nethermind/master/src/Nethermind/Nethermind.Runner/configs/withdrawals_devnet.cfg
```
Create a service user for the execution service, as this improves security, then create data directories.
Generate the JWT secret, a file used by both the execution and consensus client, add read access privileges for the consensus client and setup ownership permissions
```bash
openssl rand -hex 32 | tr -d "\n" | sudo tee "/var/lib/ethereum/zhejiang/jwtsecret"
sudo chmod +r /var/lib/ethereum/zhejiang/jwtsecret
```
Create a **systemd unit file** to define your `execution.service` configuration.
```
sudo nano /etc/systemd/system/execution.service
```
Paste the following configuration into the file.
```shell
[Unit]
Description=Nethermind Execution Layer Client service for Zhejiang
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
WorkingDirectory=/var/lib/nethermind/zhejiang
Environment="DOTNET_BUNDLE_EXTRACT_BASE_DIR=/var/lib/nethermind/zhejiang"
ExecStart=/usr/local/bin/nethermind/Nethermind.Runner \
--config withdrawals_devnet \
--datadir="/var/lib/nethermind/zhejiang" \
--JsonRpc.JwtSecretFile="/var/lib/ethereum/zhejiang/jwtsecret" \
--Init.ChainSpecPath="/var/lib/ethereum/zhejiang/custom_config_data/chainspec.json" \
--Discovery.Bootnodes="enode://691c66d0ce351633b2ef8b4e4ef7db9966915ca0937415bd2b408df22923f274873b4d4438929e029a13a680140223dcf701cabe22df7d8870044321022dfefa@64.225.78.1:30303,enode://89347b9461727ee1849256d78e84d5c86cc3b4c6c5347650093982b726d71f3d08027e280b399b7b6604ceeda863283dcfe1a01e93728b4883114e9f8c7cc8ef@146.190.238.212:30303,enode://c2892072efe247f21ed7ebea6637ade38512a0ae7c5cffa1bf0786d5e3be1e7f40ff71252a21b36aa9de54e49edbcfc6962a98032adadfa29c8524262e484ad3@165.232.84.160:30303,enode://71e862580d3177a99e9837bd9e9c13c83bde63d3dba1d5cea18e89eb2a17786bbd47a8e7ae690e4d29763b55c205af13965efcaf6105d58e118a5a8ed2b0f6d0@68.183.13.170:30303,enode://2f6cf7f774e4507e7c1b70815f9c0ccd6515ee1170c991ce3137002c6ba9c671af38920f5b8ab8a215b62b3b50388030548f1d826cb6c2b30c0f59472804a045@161.35.147.98:30303"
[Install]
WantedBy=multi-user.target
```
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Install Besu
Install dependencies.
```bash
sudo apt install -y openjdk-17-jdk libjemalloc-dev
```
Build the binaries.
```bash
cd $HOME/git
git clone -b main https://github.com/hyperledger/besu.git
cd besu
./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.1.0-dev-e18e407c/linux-x86_64/openjdk-java-17`
`2023-02-02 01:22:12.000+00:00 | main | INFO | Besu | Using jemalloc`
Install the binaries.
sudo cp -a $HOME/git/besu/build/install/besu /usr/local/bin/besu
Create a service user for the execution service, as this improves security, then create data directories.
Generate the JWT secret, a file used by both the execution and consensus client, add read access privileges for the consensus client and setup ownership permissions
```bash
openssl rand -hex 32 | tr -d "\n" | sudo tee "/var/lib/ethereum/zhejiang/jwtsecret"
sudo chmod +r /var/lib/ethereum/zhejiang/jwtsecret
```
Create a **systemd unit file** to define your `execution.service` configuration.
```bash
sudo nano /etc/systemd/system/execution.service
```
Paste the following configuration into the file.
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
**Initialize database**
```bash
sudo -u execution /usr/local/bin/geth init \
--datadir=/var/lib/geth/zhejiang /var/lib/ethereum/zhejiang/custom_config_data/genesis.json
```
Run the following to enable auto-start at boot time.
```bash
sudo systemctl daemon-reload
sudo systemctl enable execution
```
Finally, start your execution layer client and check it's status.
```bash
sudo systemctl start execution
sudo systemctl status execution
```
Press `Ctrl` + `C` to exit the status.
### Step 6. Setup Consensus Layer Client
{% hint style="info" %}
To strengthen Ethereum's resilience against potential attacks or consensus bugs, it's best practice to run a minority client in order to increase client diversity. Find the latest distribution of consensus clients here: [https://clientdiversity.org](https://clientdiversity.org/)
{% endhint %}
Set up your consensus layer client. Your choice of [Lighthouse](https://github.com/sigp/lighthouse), [Nimbus](https://github.com/status-im/nimbus-eth2), [Teku](https://consensys.net/knowledge-base/ethereum-2/teku/), [Prysm](https://github.com/prysmaticlabs/prysm) or [Lodestar](https://lodestar.chainsafe.io).
{% hint style="warning" %}
[**Lodestar**](https://lodestar.chainsafe.io/) **is a Typescript implementation** by the Chainsafe.io team. In addition to the beacon chain client, the team is also working on 22 packages and libraries. Finally, the Lodestar team is leading the Ethereum space in light client research and development and has received funding from the EF and Moloch DAO for this purpose.
[**Lighthouse**](https://github.com/sigp/lighthouse) is an Ethereum client with a heavy focus on speed and security. The team behind it, [Sigma Prime](https://sigmaprime.io/) is an information security and software engineering firm who have funded Lighthouse along with the Ethereum Foundation, Consensys, and private individuals. Lighthouse is built in Rust and offered under an Apache 2.0 License.
[**Teku**](https://consensys.net/knowledge-base/ethereum-2/teku/) is a Java-based Ethereum 2.0 client designed & built to meet institutional needs and security requirements. Dedicated to building enterprise-ready clients and tools for interacting with the core Ethereum platform, Teku is Apache 2 licensed and written in Java, a language notable for its maturity & ubiquity.
[**Nimbus**](https://our.status.im/tag/nimbus/) is a research project and a client implementation for Ethereum 2.0 designed to perform well on embedded systems and personal mobile devices, including older smartphones with resource-restricted hardware. The Nimbus team are from [Status](https://status.im/about/) the company best known for [their messaging app/wallet/Web3 browser](https://status.im) by the same name. Nimbus (Apache 2) is written in Nim, a language with Python-like syntax that compiles to C.
[**Prysm**](https://github.com/prysmaticlabs/prysm) is a Go implementation of Ethereum 2.0 protocol with a focus on usability, security, and reliability. Prysm is developed by [Prysmatic Labs](https://prysmaticlabs.com), a company with the sole focus on the development of their client. Prysm is written in Go and released under a GPL-3.0 license.
{% endhint %}
Install Lighthouse Consensus Client
**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.
```
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 ~/git
cd ~/git
git clone -b capella https://github.com/sigp/lighthouse.git
cd lighthouse
make
```
Verify lighthouse was built properly by checking the version number.
```
lighthouse --version
```
Install the binary.
```shell
sudo cp $HOME/.cargo/bin/lighthouse /usr/local/bin/lighthouse
```
Create a service user for the consensus service, as this improves security, then create data directories.
```
sudo adduser --system --no-create-home --group consensus
sudo mkdir -p /var/lib/lighthouse/zhejiang
```
Setup ownership permissions.
```
sudo chown -R consensus:consensus /var/lib/lighthouse
```
Create a **systemd unit file** to define your `consensus.service` configuration.
sudo nano /etc/systemd/system/consensus.service
Paste the following configuration into the file. Replace `` with your suggested fee recipient ETH address.
```bash
[Unit]
Description=Lighthouse Consensus Layer Client service for Zhejiang
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/lighthouse bn \
--datadir /var/lib/lighthouse/zhejiang \
--testnet-dir /var/lib/ethereum/zhejiang/custom_config_data \
--http \
--validator-monitor-auto \
--metrics \
--port 9000 \
--checkpoint-sync-url=https://beacon.zhejiang.ethpandaops.io \
--execution-endpoint http://127.0.0.1:8551 \
--execution-jwt /var/lib/ethereum/zhejiang/jwtsecret \
--boot-nodes="enr:-Iq4QMCTfIMXnow27baRUb35Q8iiFHSIDBJh6hQM5Axohhf4b6Kr_cOCu0htQ5WvVqKvFgY28893DHAg8gnBAXsAVqmGAX53x8JggmlkgnY0gmlwhLKAlv6Jc2VjcDI1NmsxoQK6S-Cii_KmfFdUJL2TANL3ksaKUnNXvTCv1tLwXs0QgIN1ZHCCIyk,enr:-Ly4QOS00hvPDddEcCpwA1cMykWNdJUK50AjbRgbLZ9FLPyBa78i0NwsQZLSV67elpJU71L1Pt9yqVmE1C6XeSI-LV8Bh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhEDhTgGJc2VjcDI1NmsxoQIgMUMFvJGlr8dI1TEQy-K78u2TJE2rWvah9nGqLQCEGohzeW5jbmV0cwCDdGNwgiMog3VkcIIjKA,enr:-MK4QMlRAwM7E8YBo6fqP7M2IWrjFHP35uC4pWIttUioZWOiaTl5zgZF2OwSxswTQwpiVCnj4n56bhy4NJVHSe682VWGAYYDHkp4h2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhJK-7tSJc2VjcDI1NmsxoQLDq7LlsXIXAoJXPt7rqf6CES1Q40xPw2yW0RQ-Ly5S1YhzeW5jbmV0cwCDdGNwgiMog3VkcIIjKA"
[Install]
WantedBy=multi-user.target
```
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Install Teku Consensus Client
Install Java 17 LTS.
```bash
sudo apt update
sudo apt install openjdk-17-jdk -y
```
Verify Java 17+ is installed.
```bash
java --version
```
Build the binaries.
```bash
mkdir ~/git
cd ~/git
git clone -b master https://github.com/ConsenSys/teku.git
cd teku
./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
```
Create a service user for the consensus service, as this improves security, then create data directories.
```bash
sudo adduser --system --no-create-home --group consensus
sudo mkdir -p /var/lib/teku/zhejiang
```
Setup ownership permissions.
```bash
sudo chown -R consensus:consensus /var/lib/teku
```
Create a **systemd unit file** to define your `consensus.service` configuration.
sudo nano /etc/systemd/system/consensus.service
Paste the following configuration into the file. Replace `` with your suggested fee recipient ETH address.
```bash
[Unit]
Description=Teku Consensus Layer Client service for Zhejiang
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
Environment=JAVA_OPTS=-Xmx5g
ExecStart=/usr/local/bin/teku-dev/bin/teku \
--network /var/lib/ethereum/zhejiang/custom_config_data/config.yaml \
--data-path /var/lib/teku/zhejiang \
--data-storage-mode="prune" \
--initial-state="https://beacon.zhejiang.ethpandaops.io/eth/v2/debug/beacon/states/finalized" \
--ee-endpoint http://127.0.0.1:8551 \
--ee-jwt-secret-file /var/lib/ethereum/zhejiang/jwtsecret \
--validator-keys /var/lib/teku/validator_keys/zhejiang:/var/lib/teku/validator_keys/zhejiang \
--rest-api-enabled true \
--metrics-enabled true \
--metrics-port 8008 \
--p2p-discovery-bootnodes="enr:-Iq4QMCTfIMXnow27baRUb35Q8iiFHSIDBJh6hQM5Axohhf4b6Kr_cOCu0htQ5WvVqKvFgY28893DHAg8gnBAXsAVqmGAX53x8JggmlkgnY0gmlwhLKAlv6Jc2VjcDI1NmsxoQK6S-Cii_KmfFdUJL2TANL3ksaKUnNXvTCv1tLwXs0QgIN1ZHCCIyk,enr:-Ly4QOS00hvPDddEcCpwA1cMykWNdJUK50AjbRgbLZ9FLPyBa78i0NwsQZLSV67elpJU71L1Pt9yqVmE1C6XeSI-LV8Bh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhEDhTgGJc2VjcDI1NmsxoQIgMUMFvJGlr8dI1TEQy-K78u2TJE2rWvah9nGqLQCEGohzeW5jbmV0cwCDdGNwgiMog3VkcIIjKA,enr:-MK4QMlRAwM7E8YBo6fqP7M2IWrjFHP35uC4pWIttUioZWOiaTl5zgZF2OwSxswTQwpiVCnj4n56bhy4NJVHSe682VWGAYYDHkp4h2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhJK-7tSJc2VjcDI1NmsxoQLDq7LlsXIXAoJXPt7rqf6CES1Q40xPw2yW0RQ-Ly5S1YhzeW5jbmV0cwCDdGNwgiMog3VkcIIjKA,enr:-MS4QCgiQisRxtzXKlBqq_LN1CRUSGIpDKO4e2hLQsffp0BrC3A7-8F6kxHYtATnzcrsVOr8gnwmBnHYTFvE9UmT-0EHh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhKXoVKCJc2VjcDI1NmsxoQK6J-uvOXMf44iIlilx1uPWGRrrTntjLEFR2u-lHcHofIhzeW5jbmV0c4gAAAAAAAAAAIN0Y3CCIyiDdWRwgiMo,enr:-LK4QOQd-elgl_-dcSoUyHDbxBFNgQ687lzcKJiSBtpCyPQ0DinWSd2PKdJ4FHMkVLWD-oOquXPKSMtyoKpI0-Wo_38Bh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhES3DaqJc2VjcDI1NmsxoQNIf37JZx-Lc8pnfDwURcHUqLbIEZ1RoxjZuBRtEODseYN0Y3CCIyiDdWRwgiMo,enr:-KG4QLNORYXUK76RPDI4rIVAqX__zSkc5AqMcwAketVzN9YNE8FHSu1im3qJTIeuwqI5JN5SPVsiX7L9nWXgWLRUf6sDhGV0aDKQ7ijXswAAAHJGBQAAAAAAAIJpZIJ2NIJpcIShI5NiiXNlY3AyNTZrMaECpA_KefrVAueFWiLLDZKQPPVOxMuxGogPrI474FaS-x2DdGNwgiMog3VkcIIjKA" \
--p2p-static-peers="/ip4/64.225.78.1/tcp/9000/p2p/16Uiu2HAkwbLbPXhPua835ErpoywHmgog4oydobcj3uKtww8UmW3b,/ip4/146.190.238.212/tcp/9000/p2p/16Uiu2HAm8bVLELrPczXQesjUYF8EetaKokgrdgZKj8814ZiGNggk,/ip4/165.232.84.160/tcp/9000/p2p/16Uiu2HAm7xM7nYVz3U9iWGH6NwExZTWtJGGeZ7ejQrcuUFUwtQmH,/ip4/68.183.13.170/udp/9000/p2p/16Uiu2HAmHXzTmWAtVexas5YskEpbcyDQ5Qck3jdLgErWumjKExUx" \
--validators-graffiti "" \
--validators-proposer-default-fee-recipient
[Install]
WantedBy=multi-user.target
```
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Install Nimbus Consensus Client
Install dependencies.
```bash
sudo apt-get update
sudo apt-get install curl build-essential git -y
```
Build the binary.
```bash
mkdir ~/git
cd ~/git
git clone -b unstable https://github.com/status-im/nimbus-eth2
cd nimbus-eth2
make update
make -j$(nproc) nimbus_beacon_node
```
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
```
Create a service user for the consensus service, as this improves security, then create data directories.
```
sudo adduser --system --no-create-home --group consensus
sudo mkdir -p /var/lib/nimbus/zhejiang
```
Setup ownership permissions.
```
sudo chown -R consensus:consensus /var/lib/nimbus
```
Create a **systemd unit file** to define your `consensus.service` configuration.
sudo nano /etc/systemd/system/consensus.service
Paste the following configuration into the file. Replace `` with your suggested fee recipient ETH address.
```bash
[Unit]
Description=Nimbus Consensus Layer Client service for Zhejiang
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/nimbus_beacon_node \
--data-dir="/var/lib/nimbus/zhejiang" \
--network="/var/lib/ethereum/zhejiang/custom_config_data" \
--web3-url=ws://127.0.0.1:8551 \
--rest \
--metrics \
--metrics-port=8008 \
--jwt-secret="/var/lib/ethereum/zhejiang/jwtsecret" \
--bootstrap-node=enr:-Iq4QMCTfIMXnow27baRUb35Q8iiFHSIDBJh6hQM5Axohhf4b6Kr_cOCu0htQ5WvVqKvFgY28893DHAg8gnBAXsAVqmGAX53x8JggmlkgnY0gmlwhLKAlv6Jc2VjcDI1NmsxoQK6S-Cii_KmfFdUJL2TANL3ksaKUnNXvTCv1tLwXs0QgIN1ZHCCIyk \
--bootstrap-node=enr:-Ly4QOS00hvPDddEcCpwA1cMykWNdJUK50AjbRgbLZ9FLPyBa78i0NwsQZLSV67elpJU71L1Pt9yqVmE1C6XeSI-LV8Bh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhEDhTgGJc2VjcDI1NmsxoQIgMUMFvJGlr8dI1TEQy-K78u2TJE2rWvah9nGqLQCEGohzeW5jbmV0cwCDdGNwgiMog3VkcIIjKA \
--bootstrap-node=enr:-MK4QMlRAwM7E8YBo6fqP7M2IWrjFHP35uC4pWIttUioZWOiaTl5zgZF2OwSxswTQwpiVCnj4n56bhy4NJVHSe682VWGAYYDHkp4h2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhJK-7tSJc2VjcDI1NmsxoQLDq7LlsXIXAoJXPt7rqf6CES1Q40xPw2yW0RQ-Ly5S1YhzeW5jbmV0cwCDdGNwgiMog3VkcIIjKA \
--bootstrap-node=enr:-MS4QCgiQisRxtzXKlBqq_LN1CRUSGIpDKO4e2hLQsffp0BrC3A7-8F6kxHYtATnzcrsVOr8gnwmBnHYTFvE9UmT-0EHh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhKXoVKCJc2VjcDI1NmsxoQK6J-uvOXMf44iIlilx1uPWGRrrTntjLEFR2u-lHcHofIhzeW5jbmV0c4gAAAAAAAAAAIN0Y3CCIyiDdWRwgiMo \
--bootstrap-node=enr:-LK4QOQd-elgl_-dcSoUyHDbxBFNgQ687lzcKJiSBtpCyPQ0DinWSd2PKdJ4FHMkVLWD-oOquXPKSMtyoKpI0-Wo_38Bh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhES3DaqJc2VjcDI1NmsxoQNIf37JZx-Lc8pnfDwURcHUqLbIEZ1RoxjZuBRtEODseYN0Y3CCIyiDdWRwgiMo \
--bootstrap-node=enr:-KG4QLNORYXUK76RPDI4rIVAqX__zSkc5AqMcwAketVzN9YNE8FHSu1im3qJTIeuwqI5JN5SPVsiX7L9nWXgWLRUf6sDhGV0aDKQ7ijXswAAAHJGBQAAAAAAAIJpZIJ2NIJpcIShI5NiiXNlY3AyNTZrMaECpA_KefrVAueFWiLLDZKQPPVOxMuxGogPrI474FaS-x2DdGNwgiMog3VkcIIjKA \
--suggested-fee-recipient=
[Install]
WantedBy=multi-user.target
```
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Run the following to quickly sync with Checkpoint Sync.
Build the binaries.
```bash
cd $HOME/git
git clone -b unstable https://github.com/chainsafe/lodestar.git
cd lodestar
yarn install --ignore-optional
yarn run build
```
Verify Lodestar was built properly by displaying the version.
```shell
./lodestar --version
```
Sample output of a compatible version.
🌟 Lodestar: TypeScript Implementation of the Ethereum Consensus Beacon Chain.
* Version: v1.4.1/bff1438
* by ChainSafe Systems, 2018-2022
Install the binaries.
```shell
sudo cp -a $HOME/git/lodestar /usr/local/bin/lodestar
```
Create a service user for the consensus service, as this improves security, then create data directories.
```
sudo adduser --system --no-create-home --group consensus
sudo mkdir -p /var/lib/lodestar/zhejiang
```
Setup ownership permissions.
```
sudo chown -R consensus:consensus /var/lib/lodestar
```
Create a **systemd unit file** to define your `consensus.service` configuration.
sudo nano /etc/systemd/system/consensus.service
Paste the following configuration into the file. Replace `` with your suggested fee recipient ETH address.
```bash
[Unit]
Description=Lodestar Consensus Layer Client service for Zhejiang
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
WorkingDirectory=/usr/local/bin/lodestar
ExecStart=/usr/local/bin/lodestar/lodestar beacon \
--dataDir="/var/lib/lodestar/zhejiang" \
--paramsFile="/var/lib/ethereum/zhejiang/custom_config_data/config.yaml" \
--genesisStateFile="/var/lib/ethereum/zhejiang/custom_config_data/genesis.ssz" \
--execution.urls="http://127.0.0.1:8551" \
--checkpointSyncUrl=https://beacon.zhejiang.ethpandaops.io \
--jwt-secret="/var/lib/ethereum/zhejiang/jwtsecret" \
--bootnodes="enr:-Iq4QMCTfIMXnow27baRUb35Q8iiFHSIDBJh6hQM5Axohhf4b6Kr_cOCu0htQ5WvVqKvFgY28893DHAg8gnBAXsAVqmGAX53x8JggmlkgnY0gmlwhLKAlv6Jc2VjcDI1NmsxoQK6S-Cii_KmfFdUJL2TANL3ksaKUnNXvTCv1tLwXs0QgIN1ZHCCIyk,enr:-Ly4QOS00hvPDddEcCpwA1cMykWNdJUK50AjbRgbLZ9FLPyBa78i0NwsQZLSV67elpJU71L1Pt9yqVmE1C6XeSI-LV8Bh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhEDhTgGJc2VjcDI1NmsxoQIgMUMFvJGlr8dI1TEQy-K78u2TJE2rWvah9nGqLQCEGohzeW5jbmV0cwCDdGNwgiMog3VkcIIjKA,enr:-MK4QMlRAwM7E8YBo6fqP7M2IWrjFHP35uC4pWIttUioZWOiaTl5zgZF2OwSxswTQwpiVCnj4n56bhy4NJVHSe682VWGAYYDHkp4h2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhJK-7tSJc2VjcDI1NmsxoQLDq7LlsXIXAoJXPt7rqf6CES1Q40xPw2yW0RQ-Ly5S1YhzeW5jbmV0cwCDdGNwgiMog3VkcIIjKA" \
--metrics=true \
--suggestedFeeRecipient=
[Install]
WantedBy=multi-user.target
```
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Install Prysm Consensus Client
Install Bazel
```bash
wget -O bazel https://github.com/bazelbuild/bazelisk/releases/download/v1.16.0/bazelisk-linux-amd64
sudo mv bazel /usr/local/bin
```
Build the binaries.
```bash
cd $HOME/git
git clone -b develop https://github.com/prysmaticlabs/prysm.git
cd prysm
bazel build //cmd/beacon-chain:beacon-chain --config=release
bazel build //cmd/validator:validator --config=release
```
Verify Prysm was built properly by displaying the help menu.
```shell
bazel run //beacon-chain -- --help
```
Install the binaries.
```shell
sudo cp -a $HOME/git/prysm /usr/local/bin/prysm
```
Create a service user for the consensus service, as this improves security, then create data directories.
```bash
sudo adduser --system --group consensus
sudo mkdir -p /var/lib/prysm/zhejiang
```
Setup ownership permissions.
```bash
sudo chown -R consensus:consensus /var/lib/prysm
```
Update firewall rules for Prysm, then verify.
```bash
sudo ufw delete allow 9000/tcp
sudo ufw allow 13000/tcp
sudo ufw allow 12000/udp
#Verify
sudo ufw status numbered
```
Example of firewall status.
```bash
Status: active
To Action From
-- ------ ----
[ 1] 22/tcp ALLOW IN Anywhere
[ 2] 30303 ALLOW IN Anywhere
[ 3] 13000/tcp ALLOW IN Anywhere
[ 4] 12000/udp ALLOW IN Anywhere
[ 5] 22/tcp (v6) ALLOW IN Anywhere (v6)
[ 6] 30303 (v6) ALLOW IN Anywhere (v6)
[ 7] 13000/tcp (v6) ALLOW IN Anywhere (v6)
[ 8] 12000/udp (v6) ALLOW IN Anywhere (v6)
```
Create a **systemd unit file** to define your `consensus.service` configuration.
sudo nano /etc/systemd/system/consensus.service
Paste the following configuration into the file. Replace `` with your suggested fee recipient ETH address.
```bash
[Unit]
Description=Prysm Consensus Layer Client service for Zhejiang
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
WorkingDirectory=/usr/local/bin/prysm
ExecStart=bazel run //cmd/beacon-chain --config=release -- \
--accept-terms-of-use=true \
--genesis-state=/var/lib/ethereum/zhejiang/custom_config_data/genesis.ssz \
--genesis-beacon-api-url=https://beacon.zhejiang.ethpandaops.io \
--checkpoint-sync-url=https://beacon.zhejiang.ethpandaops.io \
--datadir=/var/lib/prysm/zhejiang \
--chain-config-file=/var/lib/ethereum/zhejiang/custom_config_data/config.yaml \
--execution-endpoint=http://localhost:8551 \
--jwt-secret=/var/lib/ethereum/zhejiang/jwtsecret \
--contract-deployment-block=0 \
--bootstrap-node=enr:-Iq4QMCTfIMXnow27baRUb35Q8iiFHSIDBJh6hQM5Axohhf4b6Kr_cOCu0htQ5WvVqKvFgY28893DHAg8gnBAXsAVqmGAX53x8JggmlkgnY0gmlwhLKAlv6Jc2VjcDI1NmsxoQK6S-Cii_KmfFdUJL2TANL3ksaKUnNXvTCv1tLwXs0QgIN1ZHCCIyk \
--bootstrap-node=enr:-Ly4QOS00hvPDddEcCpwA1cMykWNdJUK50AjbRgbLZ9FLPyBa78i0NwsQZLSV67elpJU71L1Pt9yqVmE1C6XeSI-LV8Bh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhEDhTgGJc2VjcDI1NmsxoQIgMUMFvJGlr8dI1TEQy-K78u2TJE2rWvah9nGqLQCEGohzeW5jbmV0cwCDdGNwgiMog3VkcIIjKA \
--bootstrap-node=enr:-MK4QMlRAwM7E8YBo6fqP7M2IWrjFHP35uC4pWIttUioZWOiaTl5zgZF2OwSxswTQwpiVCnj4n56bhy4NJVHSe682VWGAYYDHkp4h2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhJK-7tSJc2VjcDI1NmsxoQLDq7LlsXIXAoJXPt7rqf6CES1Q40xPw2yW0RQ-Ly5S1YhzeW5jbmV0cwCDdGNwgiMog3VkcIIjKA \
--bootstrap-node=enr:-MS4QCgiQisRxtzXKlBqq_LN1CRUSGIpDKO4e2hLQsffp0BrC3A7-8F6kxHYtATnzcrsVOr8gnwmBnHYTFvE9UmT-0EHh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhKXoVKCJc2VjcDI1NmsxoQK6J-uvOXMf44iIlilx1uPWGRrrTntjLEFR2u-lHcHofIhzeW5jbmV0c4gAAAAAAAAAAIN0Y3CCIyiDdWRwgiMo \
--bootstrap-node=enr:-LK4QOQd-elgl_-dcSoUyHDbxBFNgQ687lzcKJiSBtpCyPQ0DinWSd2PKdJ4FHMkVLWD-oOquXPKSMtyoKpI0-Wo_38Bh2F0dG5ldHOIAAAAAAAAAACEZXRoMpDuKNezAAAAckYFAAAAAAAAgmlkgnY0gmlwhES3DaqJc2VjcDI1NmsxoQNIf37JZx-Lc8pnfDwURcHUqLbIEZ1RoxjZuBRtEODseYN0Y3CCIyiDdWRwgiMo \
--bootstrap-node=enr:-KG4QLNORYXUK76RPDI4rIVAqX__zSkc5AqMcwAketVzN9YNE8FHSu1im3qJTIeuwqI5JN5SPVsiX7L9nWXgWLRUf6sDhGV0aDKQ7ijXswAAAHJGBQAAAAAAAIJpZIJ2NIJpcIShI5NiiXNlY3AyNTZrMaECpA_KefrVAueFWiLLDZKQPPVOxMuxGogPrI474FaS-x2DdGNwgiMog3VkcIIjKA \
--suggested-fee-recipient=
[Install]
WantedBy=multi-user.target
```
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Run the following to enable auto-start at boot time.
```bash
sudo systemctl daemon-reload
sudo systemctl enable consensus
```
Finally, start your consensus layer client and check it's status.
```bash
sudo systemctl start consensus
sudo systemctl status consensus
```
Press `Ctrl` + `C` to exit the status.
Check your logs to confirm that the execution and consensus clients are up and syncing.
```bash
journalctl -fu execution | ccze
```
```bash
journalctl -fu consensus | ccze
```
#### Example of Synced Execution Client Logs
Nethermind
A properly functioning **Nethermind** execution client will indicate "block nnn ... was processed". For example,
```markup
Nethermind.Runner[2]: 2023-02-03 00:01:36.2643|FCU - block 16001 (fd781...c2e19f) was processed.
Nethermind.Runner[2]: 2023-02-03 00:01:36.2643|Block 0xd78eaabc854f4e4a844c5c0f9ccf45bed0b2f13d77ea978af62d0eef2210c2e19f was set as head.
```
Erigon
A properly functioning **Erigon** execution client will indicate "Handling new payload". For example,
```markup
erigon[41]: [INFO] [02-04|01:36:50.362] [2/15 Headers] Waiting for Consensus Layer...
erigon[41]: [INFO] [02-04|01:37:00.273] [2/15 Headers] Handling new payload height=14001 hash=0x1b2476a50d976536c2846a907ceb4f88cff4d0129ad...
```
Geth
A properly functioning **Geth** execution client will indicate "Imported new potential chain segment". For example,
```markup
geth[4531]: INFO [02-04|01:20:48.280] Chain head was updated number=16000 hash=2317ae..c41107
geth[4531]: INFO [02-04|01:20:49.648] Imported new potential chain segment number=16000 hash=ab173f..33a21b
```
Besu
A properly functioning **Besu** execution client will indicate "Fork-Choice-Updates". For example,
```bash
2022-03-19 04:09:36.315+00:00 | vert.x-worker-thread-0 | INFO | EngineForkchoiceUpdated | Consensus fork-choice-update: head: 0xcd2a_8b32..., finalized: 0xfa22_1142...
2022-03-19 04:09:48.328+00:00 | vert.x-worker-thread-0 | INFO | EngineForkchoiceUpdated | Consensus fork-choice-update: head: 0xff1a_f12a..., finalized: 0xfa22_1142...
```
**Known error in Lodestar/Besu consensus logs**: As noted in [Lodestar's discord](https://discord.com/channels/593655374469660673/743858262864167062/1066771696394191039), there will be a noisy error about updating eth1 chain cache. This does not seem to affect node syncing or validator duties.
Example error output:
```
error: Error updating eth1 chain cache JSON RPC error: Number of requests exceeds max batch size, batch Error: JSON RPC error: Number of requests exceeds max batch size, batch at JsonRpcHttpClient.fetchBatch (file:///usr/local/bin/lodestar/packages/beacon-node/src/eth1/provider/jsonRpcHttpClient.ts:151:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Eth1Provider.getBlocksByNumber...
```
#### Example of Synced Consensus Client Logs
Lodestar Consensus
A properly functioning **Lodestar** consensus client will indicate "info: Synced". For example,
```bash
Mar-19 04:09:49.000 info: Synced - slot: 3338 - head: 3355 0x5abb_ac30 - execution: valid(0x1a3c_2ca5) - finalized: 0xfa22_1142:3421 - peers: 25
Mar-19 04:09:52.000 info: Synced - slot: 3339 - head: 3356 0xcd2a_8b32 - execution: valid(0xab34_fa32) - finalized: 0xfa22_1142:3421 - peers: 25
Mar-19 04:09:04.000 info: Synced - slot: 3340 - head: 3357 0xff1a_f12a - execution: valid(0xfaf1_b35f) - finalized: 0xfa22_1142:3421 - peers: 25
```
Lighthouse Consensus
```bash
Feb 03 01:02:36.000 INFO New block received root: 0xb5ccb2f85d981ca9e1c0d904f967403ddf8c47532c195fe213c94a28ffaf6a2e, slot: 2138
Feb 03 01:02:42.000 INFO Synced slot: 2138, block: 0x1cb281a, epoch: 121, finalized_epoch: 120, finalized_root: 0x1dce0, exec_hash: 0x6827aeb (verified), peers: 50, service: slot_notifier
```
Teku Consensus
```bash
teku[64122]: 02:24:28.010 INFO - Slot Event *** Slot: 19200, Block: 1468A43F874EDE790DB6B499A51003500B5BA85226E9500A7A187DB9A169DE20, Justified: 1132, Finalized: 1133, Peers: 70
teku[64122]: 02:24:40.010 INFO - Slot Event *** Slot: 19200, Block: 72B092AADFE146F5D3F395A720C0AA3B2354B2095E3F10DC18F0E9716D286DCB, Justified: 1132, Finalized: 1133, Peers: 70
```
Nimbus Consensus
```bash
nimbus_beacon_node[292966]: INF 2023-02-05 01:20:00.000+00:00 Slot start topics="beacnde" slot=31205 epoch=903 sync=synced peers=80 head=13a131:31204 finalized=1111:cdba33411 delay=69us850ns
nimbus_beacon_node[292966]: INF 2023-02-05 01:20:08.000+00:00 Slot end topics="beacnde" slot=31205 nextActionWait=7m27s985ms126us530ns nextAttestationSlot=31235 nextProposalSlot=-1 syncCommitteeDuties=none head=13a131:31204
```
Press `Ctrl` + `C` to exit the logs.
{% hint style="info" %}
Since the network is relatively new, syncing both the execution and consensus layers should take less than an hour.
{% endhint %}
Syncing is complete when your latest block and slot number matches the public block explorers.
**Consensus client**: check latest slot number with
**Execution client**: check latest block number with[\
https://blockscout.com/eth/zhejiang-testnet](https://blockscout.com/eth/zhejiang-testnet)
### Step 7. Configure MetaMask and Use the Testnet Faucet
Configure your [MetaMask](https://metamask.io/) to point to the Zhejiang testnet or use your own node.
Use remote RPC from ethpandaops.io
1\) Visit website
2\) Click the "**Add Network to MetaMask**" button
Use my node
**1) Setup SSH tunnel**
**Note**: If your node and where metamask resides is on the same local laptop/desktop/server, skip step 1.
If your node is remote or on another machine, open a SSH tunnel to your node.
For Mac/Linux,
Typically you an open a ssh tunnel with the following:
```
ssh -N -v @ -L 8545:localhost:8545
```
For Windows using Putty, configure the SSH Tunnel as follows:
1\) Navigate to`Connection > SSH > Tunnels`
2\) Set Source port: **8545**
3\) Set Destination: **localhost:8545**
4\) Click **Add** button, then **Open** Button
**2) Add a network to Metamask:**
Go to `Metamask > Settings> Networks > Add a network > Localhost 8545`
Configure your Metamask as follows:
* **Network name**: Zhejiang Localhost 8545
* **New RPC URL**:
* **Chain ID**: 1337803
* **Currency symbol**: ETH
* **Block explorer URL**:
Use the [Testnet faucet](https://faucet.zhejiang.ethpandaops.io/) to acquire at least 32 Zhejiang testnet ETH for 1 validator. It may take a few moments, sometimes up to an hour, for the funds to appear in your wallet. Or request funds from the [ethStaker Discord](http://discord.io/ethstaker) in the #request-zhejiang-eth channel. Alternatively, use the [POW faucet by pk910](https://zhejiang-faucet.pk910.de/)
{% hint style="info" %}
For security and privacy reasons, it is best practice to use a brand new unused ETH address for these testnet activities. Avoid re-using any of your existing mainnet ETH addresses.
{% endhint %}
### Step 8. Generate Validator Keys
With two easy methods, your can setup your mnemonic keys with either:
* [Wagyu - a friendly graphical UI key gen app](https://github.com/stake-house/wagyu-key-gen)
* [staking-deposit-cli](https://github.com/ethereum/staking-deposit-cli/releases) - the original command line based key generator
Staking Deposit CLI Instructions
For the command line method,
```shell
cd $HOME
wget https://github.com/ethereum/staking-deposit-cli/releases/download/v2.4.0/staking_deposit-cli-ef89710-linux-amd64.tar.gz
```
Verify the SHA256 Checksum matches the checksum on the [releases page](https://github.com/ethereum/staking-deposit-cli/releases/tag/v2.3.0).
```bash
echo "c2b12a9e515f904ca359ec39dfbd7022dfefe881c1796ce42319df0a2da05560 *staking_deposit-cli-ef89710-linux-amd64.tar.gz" | shasum -a 256 --check
```
Example valid output:
staking\_deposit-cli-ef89710-linux-amd64.tar.gz: OK
Only proceed if the sha256 check passes with **OK**!
Extract the archive.
```
tar xvf staking_deposit-cli-ef89710-linux-amd64.tar.gz
mv staking_deposit-cli-ef89710-linux-amd64 staking-deposit-cli
cd staking-deposit-cli
```
Make a new mnemonic and replace `` with your [ethereum withdrawal address](https://notes.ethereum.org/@launchpad/withdrawals-faq#Q-If-I-used---eth1_withdrawal_address-when-making-my-initial-deposit-which-type-of-withdrawal-credentials-do-I-have), ideally from a Trezor, Ledger or comparable hardware wallet. Adjust number of validators accordingly.
```
./deposit new-mnemonic --num_validators 1 --chain zhejiang --eth1_withdrawal_address
```
Run the following, in case of this error: `RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment.`
```
export LC_ALL=C.UTF-8
export LANG=C.UTF-8
```
Wagyu Instructions
For the Wagyu key gen app, make sure to select the *Zhejiang* network and follow the guided steps.
Wagyu (formerly known as StakeHouse) is an application aimed at lowering the technical bar to staking on Ethereum 2.0.
Download Wagyu: [https://wagyu.gg](https://wagyu.gg/)
Github:
After creating the validator keys locally, you'll want to copy these validator keys via USB key or rsync file transfer to your staking node.
To align with this guide's steps, first make a default path to store your validator keys
```
mkdir -p $HOME/staking-deposit-cli/validator_keys
```
If using USB key, mount the key then copy.
```
cp /*.json $HOME/staking-deposit-cli/validator_keys
```
If using rsync, copy your validator keys from your local computer to your staking node with the following command. Change ssh port if needed.
```
rsync -a "ssh -p 22" /*.json @:/home//staking-deposit-cli/validator_keys
```
Don't lose your **keystore password** and write down your **24 word secret mnemonic key**! Ideally keep this offline but for testnet purposes it's okay to save digitally for your convenience.
### Step 9. Sign up to be a Validator at the Launchpad
After running the staking deposit tool, you will have a **deposit\_data-##########.json** file which you'll upload to the [Launchpad](https://zhejiang.launchpad.ethereum.org/).
Your deposit\_data file is located in the following location:
```shell
ls $HOME/staking-deposit-cli/validator_keys
```
{% hint style="danger" %}
Ensure your MetaMask is switched to the Zhejiang Testnet network.
{% endhint %}
Follow along the instructions at the [Launchpad](https://zhejiang.launchpad.ethereum.org/). You'll complete this process when you've uploaded your **deposit\_data-##########.json** file and sent the corresponding 32 Zhejiang testnet ETH deposit to the Zhejiang staking deposit address.
{% hint style="info" %}
The Zhejiang network staking deposit address is 0x4242424242424242424242424242424242424242
{% endhint %}
After sending the deposit with Metamask, verify your deposit was completed on a [block explorer](https://blockscout.com/eth/zhejiang-testnet/address/0x4242424242424242424242424242424242424242).
### Step 10. Setup Validator Client
Setup Lighthouse Validator
Create a service user for the validator service, as this improves security, then create data directories.
```
sudo adduser --system --no-create-home --group validator
sudo mkdir -p /var/lib/lighthouse/validators/zhejiang
```
Import your validator keys by importing your **keystore file**. Be sure to enter your **keystore password** correctly.
```shell
sudo lighthouse account validator import \
--testnet-dir /var/lib/ethereum/zhejiang/custom_config_data \
--datadir /var/lib/lighthouse/validators/zhejiang \
--directory=$HOME/staking-deposit-cli/validator_keys
```
Setup ownership permissions, including hardening the access to this directory.
```
sudo chown -R validator:validator /var/lib/lighthouse/validators/zhejiang
sudo chmod 700 /var/lib/lighthouse/validators/zhejiang
```
Verify that your keystore file was imported successfully.
Once successful, you will be shown your **validator's public key**.
For example, `0x8d9138fcf5676e2031dc4eae30a2c92e3306903eeec83ca83f4f851afbd4cb3b33f710e6f4ac516b4598697b30b04302`
Monitor your validator's status and performance at by entering your **validator's public key**.
Create a **systemd unit file** to define your `validator.service` configuration.
```
sudo nano /etc/systemd/system/validator.service
```
Paste the following configuration into the file. Replace `` with your suggested fee recipient ETH address.
If you wish to customize a graffiti message that is included when you produce a block, add your message between the double quotes after `--graffiti`.
```bash
[Unit]
Description=Lighthouse validator Client service for Zhejiang
Wants=network-online.target
After=network-online.target
Documentation=https://www.coincashew.com
[Service]
Type=simple
User=validator
Group=validator
Restart=on-failure
RestartSec=3
KillSignal=SIGINT
TimeoutStopSec=900
ExecStart=/usr/local/bin/lighthouse vc \
--testnet-dir /var/lib/ethereum/zhejiang/custom_config_data \
--beacon-nodes http://localhost:5052 \
--datadir /var/lib/lighthouse/validators/zhejiang \
--graffiti="" \
--suggested-fee-recipient=
[Install]
WantedBy=multi-user.target
```
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Setup Teku Validator
**Note: Teku combines consensus and validator clients into one binary and service.**
First, copy your `validator_keys` to the data directory.
```bash
mkdir -p /var/lib/teku/validator_keys/zhejiang
cp $HOME/staking-deposit-cli/validator_keys/keystore* /var/lib/teku/validator_keys/zhejiang
```
Storing your **keystore password** in a text file is required so that Teku can decrypt and load your validators automatically.
Create a file to store your **keystore password**. Type your password in this file.
```bash
nano $HOME/validators-password.txt
```
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Confirm that your **keystore password** is correct.
```bash
cat $HOME/validators-password.txt
```
When specifying directories for your validator-keys, Teku expects to find identically named keystore and password files.
For example `keystore-m_12221_3600_1_0_0-11222333.json` and `keystore-m_12221_3600_1_0_0-11222333.txt`
Run the following command to create a corresponding password file for every one of your validators.
```bash
for f in /var/lib/teku/validator_keys/zhejiang/keystore*.json; do cp $HOME/validators-password.txt /var/lib/teku/validator_keys/zhejiang/$(basename $f .json).txt; done
```
Setup ownership permissions, including hardening the access to this directory.
Verify that your validator's keystore .json files and validator's passwords .txt files are present by checking the following directory.
```bash
ll /var/lib/teku/validator_keys/zhejiang
```
Setup Nimbus Validator
**Note: Nimbus combines consensus and validator clients into one binary and service.**
The following command will import your validator keys.
Enter your **keystore password** to import accounts.
```bash
sudo /usr/local/bin/nimbus_beacon_node deposits import \
--data-dir=/var/lib/nimbus/zhejiang $HOME/staking-deposit-cli/validator_keys
```
Setup ownership permissions, including hardening the access to this directory.
Now you can verify the accounts were imported successfully by doing a directory listing.
```
ll /var/lib/nimbus/zhejiang/validators
```
You should see a folder named for each of your validator's pubkey.
Setup Lodestar Validator
Create a service user for the validator service, as this improves security, then create data directories.
Import your validator keys by importing your **keystore file**. Be sure to enter your **keystore password** correctly.
```shell
cd /usr/local/bin/lodestar
sudo ./lodestar validator import \
--dataDir="/var/lib/lodestar/validators/zhejiang" \
--keystore=$HOME/staking-deposit-cli/validator_keys
```
Setup ownership permissions, including hardening the access to this directory.
```
sudo chown -R validator:validator /var/lib/lodestar/validator/zhejiang
sudo chmod 700 /var/lib/lodestar/validator/zhejiang
```
Verify that your keystore file was imported successfully.
cd /usr/local/bin/lodestar
sudo ./lodestar validator list \
--dataDir="/var/lib/lodestar/validators/zhejiang"
Once successful, you will be shown your **validator's public key**.
For example, `0x8d9138fcf5676e2031dc4eae30a2c92e3306903eeec83ca83f4f851afbd4cb3b33f710e6f4ac516b4598697b30b04302`
Monitor your validator's status and performance at by entering your **validator's public key**.
Create a **systemd unit file** to define your `validator.service` configuration.
```
sudo nano /etc/systemd/system/validator.service
```
Paste the following configuration into the file. Replace `` with your suggested fee recipient ETH address.
If you wish to customize a graffiti message that is included when you produce a block, add your message between the double quotes after `--graffiti`.
```bash
[Unit]
Description=Lodestar validator Client service for Zhejiang
Wants=network-online.target
After=network-online.target
Documentation=https://www.coincashew.com
[Service]
Type=simple
User=validator
Group=validator
Restart=on-failure
RestartSec=3
KillSignal=SIGINT
TimeoutStopSec=300
WorkingDirectory=/usr/local/bin/lodestar
ExecStart=/usr/local/bin/lodestar/lodestar validator \
--dataDir="/var/lib/lodestar/validators/zhejiang" \
--paramsFile="/var/lib/ethereum/zhejiang/custom_config_data/config.yaml" \
--graffiti="" \
--suggested-fee-recipient=
[Install]
WantedBy=multi-user.target
```
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Setup Prysm Validator
Create a service user for the validator service, as this improves security, then create data directories.
Storing your **keystore password** in a text file is required so that Prysm can decrypt and load your validators automatically.
Create a file to store your **keystore password**. Type your password in this file.
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Confirm that your **keystore password** is correct.
```bash
sudo cat /var/lib/prysm/zhejiang/validator-data/validators-password.txt
```
Import your validator keys by importing your **keystore file**. Be sure to enter your **keystore password** correctly.
```shell
cd /usr/local/bin/prysm
sudo bazel run //validator:validator -- accounts import \
--accept-terms-of-use \
--wallet-dir=/var/lib/prysm/zhejiang/validator-data \
--keys-dir=$HOME/staking-deposit-cli/validator_keys
```
Setup ownership permissions, including hardening the access to this directory.
```
sudo chown -R validator:validator /var/lib/prysm/zhejiang/validator-data
sudo chmod 700 /var/lib/prysm/zhejiang/validator-data
```
Verify that your keystore file was imported successfully.
cd /usr/local/bin/prysm
sudo bazel run //validator:validator -- accounts list \
--wallet-dir=/var/lib/prysm/zhejiang/validator-data
Once successful, you will be shown your **validator's public key**. For example:
```
Showing 1 validator account
View the eth1 deposit transaction data for your accounts by running `validator accounts list --show-deposit-data`
Account 0 | strictly-pro-puma
[validating public key] 0x8d9138fcf5676e2031dc4eae30a2c92e3306903eeec83ca83f4f851afbd4cb3b33f710e6f4ac516b4598697b30b04302
```
Monitor your validator's status and performance at by entering your **validator's public key**.
Create a **systemd unit file** to define your `validator.service` configuration.
```
sudo nano /etc/systemd/system/validator.service
```
Paste the following configuration into the file. Replace `` with your suggested fee recipient ETH address.
If you wish to customize a graffiti message that is included when you produce a block, add your message between the double quotes after `--graffiti`.
```bash
[Unit]
Description=Prysm validator Client service for Zhejiang
Wants=network-online.target
After=network-online.target
Documentation=https://www.coincashew.com
[Service]
Type=simple
User=validator
Group=validator
Restart=on-failure
RestartSec=3
KillSignal=SIGINT
TimeoutStopSec=900
WorkingDirectory=/usr/local/bin/prysm
ExecStart=bazel run //cmd/validator --config=release -- \
--accept-terms-of-use=true \
--datadir=/var/lib/prysm/zhejiang \
--chain-config-file=/var/lib/ethereum/zhejiang/custom_config_data/config.yaml \
--beacon-rpc-provider=http://localhost:4000 \
--wallet-dir=/var/lib/prysm/zhejiang/validator-data \
--wallet-password-file=/var/lib/prysm/zhejiang/validator-data/validators-password.txt \
--suggested-fee-recipient=
[Install]
WantedBy=multi-user.target
```
To exit and save, press `Ctrl` + `X`, then `Y`, then `Enter`.
Run the following to enable auto-start at boot time.
```
sudo systemctl daemon-reload
sudo systemctl enable validator
```
Finally, start your validator client and check it's status.
```
sudo systemctl start validator
sudo systemctl status validator
```
Check your logs to confirm that the validator clients are up and functioning.
```
journalctl -fu validator | ccze
```
#### Example of Synced Validator Client Logs
Lodestar Validator
A properly functioning Lodestar validator will indicate publishing of attestations. For example,
```bash
Feb-1 03:33:30.228 info: Published aggregateAndProofs slot=2662, index=13, count=1
Feb-1 03:37:48.393 info: Published attestations slot=2699, index=20, count=1
Feb-1 03:46:36.450 info: Published attestations slot=2713, index=2, count=1
Feb-1 03:53:48.944 info: Published attestations slot=2765, index=21, count=1
Feb-1 04:01:48.812 info: Published attestations slot=2809, index=17, count=1
```
Lighthouse Validator
```
Feb 08 01:01:0 INFO Successfully published attestations type: unaggregated, slot: 12422, committee_index: 3, head_block: 0xabc111daedf1281..., validator_indices: [12345], count:1, service: attestation
Feb 08 01:01:30 INFO Connected to beacon node(s) synced: 1, available: 1, total: 1, service: notifier
```
Teku Validator
```bash
teku[65367]: 03:50:51.761 INFO - Validator cc1f3ade status is active_ongoing.
teku[65367]: 03:50:52.203 INFO - Validator *** Published attestation Count: 1, Slot: 31362, Root: 90FC0DF4D5958E469134A015203B53B3FB94A0FC1038FB2462882906D4A729A2
```
Nimbus Validator
```
nimbus_beacon_node[292966]: INF 2023-02-05 01:25:26.263+00:00 Attestation sent attestation="(aggregation_bits: 0b00000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000, data: (slot: 31235, index: 3, beacon_block_root: \"ca3213f1\", source: \"1901:9deza1289\", target: \"1901:6ab1fafff\"), signature: \"32173064\")" delay=46ms543us294ns subnet_id=20
```
Press `Ctrl` + `C` to exit the logs.
{% hint style="info" %}
After making your 32 ETH deposit, your validator is placed into queue for activation which typically takes 6-24 hours. Once activated, your validator begins staking and attestation duties. Learn more about the [depositing process.](https://kb.beaconcha.in/ethereum-2.0-and-depositing-process)
{% endhint %}
{% hint style="success" %}
:tada:Congrats on setting up your Zhejiang “Withdrawals” staking node!
{% endhint %}
### Step 11. Next Steps
As a newly minted Zhejiang Ethereum Staker,
* Learn more about [what features are introduced and being tested on Zhejiang](https://notes.ethereum.org/@launchpad/zhejiang#What-is-in-the-Zhejiang-testnet).
* Monitor your validator's earnings and performance at by entering your validator's public key.
* Learn to connect your MetaMask wallet to your own execution layer node. See [step 7, use my own node.](#use-my-node)
#### Additional Commands
Stopping the execution, consensus and validator clients
```
sudo systemctl stop execution
```
```
sudo systemctl stop consensus
```
```
sudo systemctl stop validator
```
Viewing logs / troubleshooting
```bash
#View Besu
journalctl -fu execution | ccze
#View Lodestar Beacon Chain
journalctl -fu consensus | ccze
#View Lodestar Validator
journalctl -fu validator | ccze
```
## Extra Testing Commands
Perform a Voluntary Exit
Stop Lodestar validator
```
sudo systemctl stop validator
```
Run the voluntary exit command and follow the instructions
# change directories to binary folder
cd /usr/local/bin/lodestar
# the voluntary exit command
./lodestar validator voluntary-exit
Restart validator
```
sudo systemctl restart validator
```
## Your Github Contributions Welcome
This guide is fully open source and fully powered by home stakers like you. 🙏
Pull requests or issues can be submitted on [github](https://github.com/coincashew/coincashew):
{% embed url="" %}
## Support Us
These guides are solely supported by [Gitcoin Grants](https://gitcoin.co/grants/1653/eth2-staking-guides-by-coincashew) and donations to our [Cointr.ee](https://cointr.ee/coincashew) by stakers like you. 🙏
{% embed url="" %}
{% embed url="" %}
## Marvelous Reference Material
* [Ethpandaops](https://zhejiang.ethpandaops.io)
* [Ethereum.org How to Run a Node](https://notes.ethereum.org/@launchpad/zhejiang)
* [Testing Beacon Chain Withdrawals with Docker by Ladislaus](https://mirror.xyz/ladislaus.eth/nYZCmrO7ZndrP92kGyJG0-wzbnIsd3HwxsII-gT1zu8)
* [Ethereum.org Withrdrawals Guide](https://notes.ethereum.org/@launchpad/withdrawals-guide)
* [Ethstaker's Zhejiang Testnet Geth Lighthouse Guide by remyroy](https://github.com/eth-educators/ethstaker-guides/blob/main/zhejiang.md)
## Technical Support and Community
* Reddit >
* Discord > [ethStaker](http://discord.io/ethstaker) > #zhejiang channel
## Last Words
> I stand upon the shoulders of giants and as such, invite you to stand upon mine. Use my work with or without attribution; I make no claim of "intellectual property." My ideas are the result of countless millenia of evolution - they belong to humanity.
This is Leslie, the official mascot of Eth Staking
**2) Add a network to Metamask:**
Go to `Metamask > Settings> Networks > Add a network > Localhost 8545`
Configure your Metamask as follows:
* **Network name**: Zhejiang Localhost 8545
* **New RPC URL**: 
