Deploy the Devnet

A Devnet will generally have two or more nodes. Each node will required an execution client and a consensus client. To set up the two client you need to follow a series of steps and create reasonably complex configuration files, repeating the process for each node.

To simplify this process we have created a script that guides you through the steps required, allows you to make some configuration choice, but largely pre-configures and automates the tasks required to get a Devnet up and running.

For this project we need four nodes, so the script will have to be run four times. One node uses the Prysm consensus client while the other three nodes use the Lighthouse consensus client.

Running the scripts

Download the scripts and templates in the working folder (we have named it devnet) and run the following command to make the two script files executable:

chmod +x ./deploy_nodes.sh
chmod +x ./reset_devnet.sh

Note that the templates should be stored in the same folder as the scripts. You should run the scripts from the working folder.

Every execution of the script will create a node, and all the node data will be stored in folder named node1, node2, and so on.

Refer to the file structure below:

/devnet
/node1
/node2
/node3
/node4
- deploy_nodes.sh
- reset_devnet.sh
- genesis_template.json
- config_template.yaml