The Lilypad Network uses the Arbitrum Sepolia Testnet to settle compute transactions.

This personal RPC endpoint allows Resource Providers (RP) to avoid reliability issues with the RPC endpoints used by Lilypad ensuring rewards can be earned and jobs can be run consistently. RPs running a personal RPC endpoint contribute to the fault tolerance and decentralization of the Lilypad Network! Read more in the Alchemy Arbitrum docs.

Setup RPC video guide

This guide walks through the steps of setting up a personal RPC endpoint for Arbitrum Sepolia using Infura.

Setup Infura account

Create an account on Infura and choose your plan based on how many APIs you need.

Select the “free” tier as the compute units provided should be sufficient to run a Lilypad RP.

Setup RPC endpoint for Arbitrum Sepolia

In the Infura dashboard, a new API key will usually generate automatically. If not, select "Create New API Key". Navigate to "Configure" to setup the API key.

Scroll down the list to the Arbitrum network and ensure the Sepolia testnet box is checked, then save changes.

In the API key dashboard, select "Active Endpoints" and navigate to "WebSockets".

Scroll down the page to find the Arbitrum Sepolia URL. The RPC endpoint for Arbitrum Sepolia is ready to be used with the Lilypad Resource Provider:

Use the new RPC endpoint

Lilypad RPs can use a personal RPC endpoint with a few simple steps. Only Web-socket (WSS) connections are supported.

Docker users

Stop the existing Lilypad Resource Provider (RP) before setting up the new RPC.

Locate the Lilypad RP Docker container using:

docker ps

Stop the container using the PID:

docker stop <container ID>

Use this command to start the lilypad-resource-provider.service with the new RPC:

docker run -d --gpus all -e WEB3_PRIVATE_KEY=<private-key> -e WEB3_RPC_URL=wss://arbitrum-sepolia.infura.io/ws/v3/some-id-from-infura --restart always ghcr.io/lilypad-tech/resource-provider:latest

Check the status of the container:

docker logs <container ID>

Ubuntu users

Stop the existing Lilypad RP (if the node is not running, disregard this first step):

sudo systemctl stop bacalhau
sudo systemctl stop lilypad-resource-provider

Update lilypad-resource-provider.service with the new RPC:

sudo nano /etc/systemd/system/lilypad-resource-provider.service

Add following line to [Service] section:

Environment="WEB3_RPC_URL=wss://arbitrum-sepolia.infura.io/ws/v3/some-id-from-infura"

Reboot the node:

sudo reboot

If the Lilypad RP was setup properly as a systemd service, the RP will reboot using the new RPC. Once the reboot is complete, the RP should be running with the updated configuration. To verify your node is back online and running correctly, run the following:

sudo systemctl status lilypad-resource-provider
sudo systemctl status bacalhau

This guide walks through the steps of setting up a personal RPC endpoint for Arbitrum Sepolia using Alchemy.

Setup Alchemy account

Create an account and login to the Alchemy dashboard.

Select the “free” tier as the compute units provided should be sufficient to run a Lilypad RP. The free service provides 300 million compute units per month.

Select “skip bonus” or input a credit card with billing info (the card will not be charged unless the compute credits in the free tier are used).

Setup RPC endpoint for Arbitrum Sepolia

In the “Overview” section of the Alchemy dashboard, navigate to “My app” and select “Endpoints”. If an app was not created upon login, create a new one by selecting "Create new app".

By selecting “Endpoints”, the “Networks” tab will open providing an option to configure the Arbitrum API.

• Select “Sepolia”

• Select “Websockets”

The RPC endpoint for Arbitrum Sepolia is ready to be used with the Lilypad Resource Provider:

Metrics for the RPC can be viewed in the “Metrics” tab.

Use the new RPC endpoint

Lilypad RPs can use a personal RPC endpoint with a few simple steps. Only Web-socket (WSS) connections are supported.

Docker users

Stop the existing Lilypad Resource Provider (RP) before setting up the new RPC.

Locate the Lilypad RP Docker container using:

docker ps

Stop the container using the PID:

docker stop <container ID>

Use this command to start the lilypad-resource-provider.service with the new RPC:

docker run -d --gpus all -e WEB3_PRIVATE_KEY=<private-key> -e WEB3_RPC_URL=wss://arb-sepolia.g.alchemy.com/v2/some-id-from-alchemy --restart always ghcr.io/lilypad-tech/resource-provider:latest

Check the status of the container:

docker logs <container ID>

Ubuntu users

Stop the existing Lilypad RP (if the node is not running, disregard this first step):

sudo systemctl stop bacalhau
sudo systemctl stop lilypad-resource-provider

Update lilypad-resource-provider.service with the new RPC:

sudo nano /etc/systemd/system/lilypad-resource-provider.service

Add following line to [Service] section:

Environment="WEB3_RPC_URL=wss://arb-sepolia.g.alchemy.com/v2/some-alchemy-id"

Reboot the node:

sudo reboot

If the Lilypad RP was setup properly as a systemd service, the RP will reboot using the new RPC. Once the reboot is complete, the RP should be running with the updated configuration. To verify your node is back online and running correctly, run the following:

sudo systemctl status lilypad-resource-provider
sudo systemctl status bacalhau