Let's set up a local eth1-eth2 merge testnet!
Note: Python (incl. python-dev
) and Go (1.16+) standard installs assumed
# Create, start and install python venv
python -m venv venv
. venv/bin/activate
pip install -r requirements.txt
# Install eth2-testnet-genesis tool (Go 1.16+ required)
go install github.com/protolambda/eth2-testnet-genesis@latest
# Install eth2-val-tools
go install github.com/protolambda/eth2-val-tools@latest
Tweak mergenet.yaml
as you like.
Get current timestamp as eth1 genesis timestamp, then change the eth2-genesis delay to offset the chain start:
date +%s
# Create output
export TESTNET_NAME="mynetwork"
mkdir "$TESTNET_NAME"
mkdir "$TESTNET_NAME/public"
mkdir "$TESTNET_NAME/private"
# Configure Eth1 chain
python generate_eth1_conf.py > "$TESTNET_NAME/public/eth1_config.json"
# Configure Eth2 chain
python generate_eth2_conf.py > "$TESTNET_NAME/public/eth2_config.yaml"
Configure tranche(s) of validators, edit genesis_validators.yaml
.
Note: defaults test-purpose mnemonic and configuration is included already, no need to edit for minimal local setup.
Make sure that total of count
entries is more than the configured MIN_GENESIS_ACTIVE_VALIDATOR_COUNT
(eth2 config).
# Generate Genesis Beacon State
eth2-testnet-genesis merge \
--eth1-config "$TESTNET_NAME/public/eth1_config.json" \
--eth2-config "$TESTNET_NAME/public/eth2_config.yaml" \
--mnemonics genesis_validators.yaml \
--state-output "$TESTNET_NAME/public/genesis.ssz" \
--tranches-dir "$TESTNET_NAME/private/tranches"
# Build validator keystore for nodes
#
# Prysm likes to consume bundled keystores. Use `--prysm-pass` to encrypt the bundled version.
# For the other eth2 clients, a different secret is generated per validator keystore.
#
# You can change the range of validator accounts, to split keys between nodes.
# The mnemonic and key-range should match that of a tranche of validators in the beacon-state genesis.
export VALIDATOR_NODE_NAME="valclient0"
eth2-val-tools keystores \
--out-loc "$TESTNET_NAME/private/$VALIDATOR_NODE_NAME" \
--prysm-pass="foobar" \
--source-min=0 \
--source-max=64 \
--source-mnemonic="lumber kind orange gold firm achieve tree robust peasant april very word ordinary before treat way ivory jazz cereal debate juice evil flame sadness"
This documents how to build the binaries from source, so you can make changes and check out experimental git branches. It's possible to build docker images (or use pre-built ones) as well. Ask the client devs for alternative install instructions.
mkdir clients
mkdir "$TESTNET_NAME/nodes"
Download and install deps:
git clone https://github.com/ethereum/go-ethereum.git clients/catalyst
cd clients/catalyst
go build -o ./build/bin/catalyst ./cmd/geth
cd ../..
Prepare chaindata:
mkdir -p "$TESTNET_NAME/nodes/catalyst0/chaindata"
./clients/catalyst/build/bin/catalyst --datadir "./$TESTNET_NAME/nodes/catalyst0/chaindata" init "./$TESTNET_NAME/public/eth1_config.json"
Run:
# block proposal rewards/fees go to the below 'etherbase', change it if you like to spend them
./clients/catalyst/build/bin/catalyst --catalyst --http --http.api net,eth,consensus --nodiscover \
--miner.etherbase 0x1000000000000000000000000000000000000000 --datadir "./$TESTNET_NAME/nodes/catalyst0/chaindata"
Use the following command to run Catalyst from docker:
docker run -v "$(pwd)/$TESTNET_NAME:/testnet" -u $(id -u):$(id -g) --net host \
ethereum/client-go --catalyst --http --http.api net,eth,consensus --nodiscover \
--miner.etherbase 0x1000000000000000000000000000000000000000 \
--datadir "/testnet/nodes/catalyst0/chaindata"
Note:
--net host
to map container's network to the host-u $(id -u):$(id -g)
to allow for writing to the chain data folder- works on Linux but might require some tweaks to run it on Mac and Windows
You can run Nethermind natively on linux-x64, linux-arm64, macOS and Windows or you can run it through Docker image.
Note: Both Geth-style chain configuration and Nethermind chain configurations are needed. Other general steps in this tutorial are dependent on Geth-style chain configuration.
# Configure Eth1 chain for Nethermind
python generate_eth1_nethermind_conf.py > "$TESTNET_NAME/public/eth1_nethermind_config.json"
Use the following command to run Nethermind from docker:
docker run \
--name nethermind \
-p 8545:8545 \
-v ${PWD}/$TESTNET_NAME/public/eth1_nethermind_config.json:/nethermind/chainspec/catalyst.json \
-v ${PWD}/$TESTNET_NAME/nodes/nethermind0/db:/nethermind/nethermind_db \
-v ${PWD}/$TESTNET_NAME/nodes/nethermind0/logs:/nethermind/logs \
-itd nethermind/nethermind \
-c catalyst \
--JsonRpc.Port 8545 \
--JsonRpc.Host 0.0.0.0 \
--Merge.BlockAuthorAccount 0x1000000000000000000000000000000000000000
linux-x64(linux-amd64)/linux-arm64:
sudo apt-get update && sudo apt-get install libsnappy-dev libc6-dev libc6 unzip
macOS:
brew install rocksdb
Download package from Nethermind releases page make sure you are downloading version >= 1.10.62
Unzip the package to /clients/nethermind/
Use the following command to run Nethermind natively:
./clients/nethermind/Nethermind.Runner -c catalyst.cfg \
--Init.ChainSpecPath ./$TESTNET_NAME/public/eth1_nethermind_config.json \
--Merge.BlockAuthorAccount 0x1000000000000000000000000000000000000000 \
--baseDbPath "./$TESTNET_NAME/nodes/nethermind0/db" \
--Init.LogDirectory "./$TESTNET_NAME/nodes/nethermind0/logs"
Customise paths and communication ports per instance:
./clients/nethermind/Nethermind.Runner -c catalyst.cfg \
--Init.ChainSpecPath ./$TESTNET_NAME/public/eth1_nethermind_config.json \
--Merge.BlockAuthorAccount 0x1000000000000000000000000000000000000000 \
--baseDbPath "./$TESTNET_NAME/nodes/nethermind<id>/db" \
--Init.LogDirectory "./$TESTNET_NAME/nodes/nethermind<id>/logs" \
--JsonRpc.Port <rpc_port> \
--JsonRpc.WebSocketsPort <rpc_websocket_port> \
--Network.DiscoveryPort <network_discovery_port> \
--Network.P2PPort <network_p2p_port>
Besu requires a Java JVM. We recommend the latest long term support version, Java 11, e.g.
- install (linux)
sudo apt-get install openjdk-11-jdk
- check your java version
java --version
Download and install deps:
git clone https://github.com/garyschulte/besu.git clients/besu-rayonism
cd clients/besu-rayonism
./gradlew installDist
cd ../..
Prepare chaindata:
mkdir -p "$TESTNET_NAME/nodes/besu0/chaindata"
Run:
clients/besu-rayonism/build/install/besu/bin/besu --data-path="./$TESTNET_NAME/nodes/besu0/chaindata" \
--genesis-file="./$TESTNET_NAME/public/eth1_config.json" \
--rpc-http-enabled --rpc-http-api=ETH,NET,CONSENSUS --Xmerge-support=true \
--discovery-enabled=false
Use the following command to run besu from docker:
docker run -v "$(pwd)/$TESTNET_NAME:/testnet" -u $(id -u):$(id -g) --net host \
suburbandad/besu:rayonism \
--data-path="/testnet/nodes/besu0/chaindata" --genesis-file="/testnet/public/eth1_config.json" \
--rpc-http-enabled --rpc-http-api=ETH,NET,CONSENSUS --Xmerge-support=true --discovery-enabled=false
Note:
--net host
to map container's network to the host-u $(id -u):$(id -g)
to allow for writing to the chain data folder- works on Linux but might require some tweaks to run it on Mac and Windows
Install (assumes openjdk 15 is installed, openjdk 16 is currently not supported by gradlew):
git clone -b rayonism-merge https://github.com/txrx-research/teku.git clients/teku
cd clients/teku
./gradlew installDist
cd ../..
Run (omit the --validator-keys
if you prefer the stand-alone Teku validator-client mode):
mkdir -p "./$TESTNET_NAME/nodes/teku0/beacondata"
./clients/teku/build/install/teku/bin/teku \
--network "./$TESTNET_NAME/public/eth2_config.yaml" \
--data-path "./$TESTNET_NAME/nodes/teku0/beacondata" \
--p2p-enabled=false \
--initial-state "./$TESTNET_NAME/public/genesis.ssz" \
--eth1-endpoint http://127.0.0.1:8545 \
--metrics-enabled=true --metrics-interface=127.0.0.1 --metrics-port=8008 \
--p2p-discovery-enabled=false \
--p2p-peer-lower-bound=0 \
--p2p-port=9000 \
--rest-api-enabled=true \
--rest-api-docs-enabled=true \
--rest-api-interface=127.0.0.1 \
--rest-api-port=5051 \
--Xdata-storage-non-canonical-blocks-enabled=true \
--validator-keys "./$TESTNET_NAME/private/$VALIDATOR_NODE_NAME/teku-keys:./$TESTNET_NAME/private/$VALIDATOR_NODE_NAME/teku-secrets"
Note:
--p2p-discovery-enabled=false
to disable Discv5, to not advertise your local network to any external discv5 node.--p2p-static-peers
for multi-addr list (comma separated) to other eth2 nodes--p2p-discovery-bootnodes
for ENR list (comma separated), if working with discovery, public net etc.--Xdata-storage-non-canonical-blocks-enabled
is added to store non-canonical blocks for debugging purposes.
Use the following command to run Teku from docker:
docker run -v "$(pwd)/$TESTNET_NAME:/testnet" -e VALIDATOR_NODE_NAME=$VALIDATOR_NODE_NAME -u $(id -u):$(id -g) --net host \
mkalinin/teku:rayonism \
--network "/testnet/public/eth2_config.yaml" \
--data-path "/testnet/nodes/teku0/beacondata" \
--p2p-enabled=false \
--initial-state "/testnet/public/genesis.ssz" \
--eth1-endpoint http://127.0.0.1:8545 \
--metrics-enabled=true --metrics-interface=127.0.0.1 --metrics-port=8008 \
--p2p-discovery-enabled=false \
--p2p-peer-lower-bound=0 \
--p2p-port=9000 \
--rest-api-enabled=true \
--rest-api-docs-enabled=true \
--rest-api-interface=127.0.0.1 \
--rest-api-port=5051 \
--Xdata-storage-non-canonical-blocks-enabled=true \
--validator-keys "/testnet/private/$VALIDATOR_NODE_NAME/teku-keys:/testnet/private/$VALIDATOR_NODE_NAME/teku-secrets"
Lighthouse is started via one-liner scripts in ./lh_scripts
.
There are two options:
- Docker: downloads an image from Docker Hub (easy).
- Build from source: compile the Rust code to a binary (slightly less easy).
Docker:
./lh_scripts/start_beacon.sh docker
...OR... Build from source:
- Install deps:
# System deps (assuming Ubuntu, you may need to parse to your OS)
sudo apt install -y git gcc g++ make cmake pkg-config
# Install Rust
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
- Build Lighthouse from source:
git clone -b rayonism https://github.com/sigp/lighthouse.git clients/lighthouse
cd clients/lighthouse
make
cd ../..
- Start Lighthouse
./lh_scripts/start_beacon.sh binary
For now, Prysm provides instructions for building from source, but in the future can provide binaries and Docker containers for the merge testnet.
Required dependencies:
- UNIX operating system
- Version 3.7.0 of Bazel installed
- The
cmake
package installed - The git package installed
libssl-dev
installedlibgmp-dev
installedlibtinfo5
installed
Then, clone the repo and checkout the branch
git clone -b merge https://github.com/prysmaticlabs/prysm.git clients/prysm && cd clients/prysm
Build the beacon node and validator
bazel build //beacon-chain:beacon-chain
bazel build //validator:validator
Run the beacon node
bazel run //beacon-chain -- \
--datadir="./$TESTNET_NAME/nodes/prysm0/beacondata" \
--min-sync-peers=0 \
--http-web3provider=http://127.0.0.1:8545 \
--bootstrap-node= \
--chain-config-file="./$TESTNET_NAME/public/eth2_config.yaml" \
--genesis-state="./$TESTNET_NAME/public/genesis.ssz" \
--clear-db
The bootstrap node option is empty to disable any type of networking.
If you include --validator-keys
in the beacon node, it will run a validator-client as part of the node, and you do not have to run a separate validator.
However, if you want to run a separate validator client, use:
mkdir -p "./$TESTNET_NAME/nodes/teku0/validatordata"
./clients/teku/build/install/teku/bin/teku validator-client \
--network "./$TESTNET_NAME/public/eth2_config.yaml" \
--data-path "./$TESTNET_NAME/nodes/teku0/validatordata" \
--beacon-node-api-endpoint "http://127.0.0.1:5051" \
--validator-keys "./$TESTNET_NAME/private/$VALIDATOR_NODE_NAME/teku-keys:./$TESTNET_NAME/private/$VALIDATOR_NODE_NAME/teku-secrets
bazel run //validator -- \
--wallet-dir="./$TESTNET_NAME/private/valclient0/prysm" \
--chain-config-file="./$TESTNET_NAME/public/eth2_config.yaml" \
--clear-db
The instructions are effectively the same as the Lighthouse Beacon Node.
Note: permissions issues may prevent switching between the docker
and
binary
options. For maximal ease of use, pick an option and stick with it.
Docker:
./lh_scripts/start_validator.sh docker
...OR... Build from source:
Follow steps 1, 2 in the Lighthouse Beacon Node, then run:
./lh_scripts/start_validator.sh binary
Now wait for the genesis of the chain!
actual_genesis_timestamp = eth1_genesis_timestamp + eth2_genesis_delay
Import a pre-mined account into some web3 wallet (e.g. metamask), connect to local RPC, and send a transaction with a GUI.
Run example_transaction.py
.
TODO
TODO