For successfully setting up and running Ritual’s Infernet Node, the following is required:

The requirements of an Infernet Node depend to a great degree on the type of compute workflows it is running. Ritual states in their docs that memory-enhanced machines are preferred.

To install and run your Infernet node at an optimal level, you need a VPS (Virtual Private Server). For the sake of simplicity, we’re going to use Contabo but feel free to use the VPS provider of your choice.

Ritual recommends getting a VPS with 4 vCPUs, 16GB RAM and 500GB SSD, which is covered by Contabo’s CLOUD VPS 2 plan. If you are planning to run GPU-heavy workloads, you’ll have to purchase a more powerful machine.

Please select the following configurations.

Once you’ve purchased a VPS package, you can use SSH to connect to it. Feel free to select the SSH client of your choice:

Enter the IP address & port of your VPS in the section Host Name (or IP Address) and click on Open.

Specify your user name as root and enter your password to log into your server.

Once you’re logged into your VPS, we can install all the required tools for running a Ritual node.

The packages on your server may not be up-to-date so let’s update these first via:

Next, we are going to install the build tools needed to run a node (curl, git, jq, lz4, and build-essential):

We can now install Docker via the following command:

Once Docker is installed, we can install Docker Compose next. Please visit github.com/docker/compose/releases for the latest version. At the time of writing this, the latest version is v2.29.2. You may have to replace the version number in the command below once a newer version is live.

We also need to assign the Docker Compose directory higher permissions.

Make plugin executable

Verify installation

If you are not working from root, please add your user to the Docker group:

Reboot system to apply changes:

Log back in and verify everything works fine:

We’ve now successfully installed all the tools we need. In the next step, you’ll clone the starter repository to your local machine. Clone locally:

After cloning it, please navigate to the repository via:

In this step, we are going to run the hello-world container.

We are starting a new screen session with the name “ritual” so that the Docker container continues running even if we lose connection with the VPS. 

We are going to deploy the hello-world container inside this session:

Detach from your session with:

We can now check if everything is working correctly. To do so, open a new terminal window where we can see a list of all active Docker containers. Establish a new SSH connection to your VPS (open new PuTTY instance, enter IP of your VPS, click on Open and enter your password. Then enter this command:

Everything is going great if the output looks like this:

Open the config.json file in the second terminal window that you have just opened:

Update the config file as follows (either by using arrow down ↓ and right/left → ← to get to where you want to make a change or via CTRL+_ and specifying the line number). You can then delete the existing content and insert the new variables via CTRL+SHIFT+V:

Please also edit the snapshot sync settings in both config files (/hello-world/container/config.json and /deploy/config.json) to increase sleep (makes node less aggressive) and to avoid RPC rate limits (decrease batch size for public RPCs to 50):

Save and close the file by pressing CTRL + X. Confirm changes with Y and hit ENTER to exit.

Now change RPC URL, registry, and private key in this file as well:

Then change registry address in this file as well:

Open the Makefile:

Go to deployment script:

Change coordinator address to 0x8D871Ef2826ac9001fB2e33fDD6379b6aaBF449c

Change registry address to 0x3B1554f346DFe5c482Bb4BA31b880c1C18412170

Save and close via CTRL + X.

Change the node’s image to the latest version (today, this is 1.2.0 but be sure to check for the latest version).

Restart Docker containers one by one (in second terminal session):

Verify the restart was successful listing all running containers:

You can now check if changes are active via (replace <Container ID> with ID of deploy-node-1 container. You can get the ID via docker ps.

We can now install Foundry in the second terminal window. (Foundry is a modular toolkit for Ethereum application development). Change to home directory:

Create a new folder:

Navigate into it:

Execute the script from Foundry’s official source

Update your shell configuration by sourcing the .bashrc file

Run foundryup to ensure Foundry is fully installed:

We then install the necessary dependencies by navigating into the directory of the contract and installing required libraries and SDKs. Navigate to the contracts directory:

Install the forge-std library:

Install the infernet-sdk:

Go to the directory three levels up

Open a third terminal window for monitoring the logs. (Open new PuTTY instance, enter IP of your VPS, click on Open and enter your password). Then print the logs via:

Next, we can deploy a consumer contract that will interact with the Infernet SDK. To do this, we are using the SaysGM example by Ritual. It is designed to request a compute output from your node and prints the compute result. To deploy SaysGM, enter your second terminal session and enter this command. Navigate to the repository:

Deploy the SaysGM contract:

You can check the result in your third terminal window. If everything was successful, you will see a new transaction. If so: Congratulations! Your deployment was successful and has interacted with the blockchain. 

You can also check via Basescan.

Look at the logs and check to which address your SaysGM contract was deployed to.

Edit your CallContract.s.sol file by inserting the new contract address. The preconfigured address is SaysGM saysGm = SaysGM(0x13D69Cf7d6CE4218F646B759Dcf334D82c023d8e), change it to the address that was generated when calling SaysGM:

Switch back to your second terminal session and initiate a new request for the Infernet Node:

This will trigger the SaysGm contract (via an initiation transaction). You can monitor this process in your third terminal window. A new message will confirm the transaction, confirming that the contract interaction was successful.

Please wait for a few moments. You will then see a new contact from the Infernet Node.

Can now register and activate your node.

You should now see two transactions in your wallet on Basescan. The first one is for registering your node and the second one is for activating it.

Please check your Docker looks to ensure everything is running smoothly.