Running on Linux

This page contains instructions for running the QRL 2.0 Testnet V2 on Linux

Download configuration and genesis files

Download the config.yml and genesis.ssz files from the go-qrl-metadata repository to the same directory as your gqrl executable.

curl

curl -LO https://raw.githubusercontent.com/theQRL/go-qrl-metadata/refs/heads/main/testnet/testnetv2/genesis.ssz
curl -LO https://raw.githubusercontent.com/theQRL/go-qrl-metadata/refs/heads/main/testnet/testnetv2/config.yml

wget

wget https://raw.githubusercontent.com/theQRL/go-qrl-metadata/refs/heads/main/testnet/testnetv2/genesis.ssz
wget https://raw.githubusercontent.com/theQRL/go-qrl-metadata/refs/heads/main/testnet/testnetv2/config.yml

Run the Execution Engine (gqrl)

./gqrl \
  --nat=extip:0.0.0.0 \
  --testnet \
  --http \
  --http.api "web3,net,qrl,engine" \
  --datadir=gqrldata console \
  --syncmode=full

Run the Consensus Engine (Beacon Chain)

./beacon-chain \
  --datadir=beacondata \
  --min-sync-peers=1 \
  --genesis-state=genesis.ssz \
  --chain-config-file=config.yml \
  --config-file=config.yml \
  --execution-endpoint=http://localhost:8551 \
  --accept-terms-of-use \
  --jwt-secret=gqrldata/gqrl/jwtsecret \
  --contract-deployment-block=0 \
  --minimum-peers-per-subnet=0 \
  --p2p-static-id \
  --bootstrap-node "qnr:-Me4QKAyB33PkhFM0zY3r5i9GC7aSP_Zm39U8Y2rOIzr6443SngB1yhgGh7eFwNK0WNvDWjUbNksuJqME3ZEnwS9qJSGAZ1Gb_3yh2F0dG5ldHOIAAAAAAAAAACJY29uc2Vuc3VzkJCnUX4gAACJ__________-CaWSCdjSCaXCEI7LKF4lzZWNwMjU2azGhA7Z8d7NnIyueM0N06PyRt8jcnKvuRkMTmtzoDOw081ouiHN5bmNuZXRzAIN0Y3CCMsiDdWRwgi7g" \
  --bootstrap-node "qnr:-Me4QE7keK-7ViWaDwpa0GtR12qbe9ZiVvKX95z7A2hkJHA6L-2A0n8G6dn8M1kubmxAeVw7Nwaa6IBPCX9765zNi56GAZ1Gb-8uh2F0dG5ldHOIAAAAAAAAAACJY29uc2Vuc3VzkJCnUX4gAACJ__________-CaWSCdjSCaXCEDSlCUolzZWNwMjU2azGhA9t_KLMx2GyZcw7tncC7iLdJpKBS_tCp9CavD6LXd5ZaiHN5bmNuZXRzAIN0Y3CCMsiDdWRwgi7g" \
  --verbosity debug \
  --log-file beacon.log \
  --log-format text

TIP

You might want to save this to different files for easier reference (ie 1-gqrl.sh, 2-beacon.sh)

Next steps

Once your node is running, check out the Checking Status page to verify everything is syncing correctly.