Run a node
Instructions for setting up a Resource Provider (node) on the public Lilypad testnet using Docker, including obtaining necessary funds and installing required software.
Last updated
Was this helpful?
Instructions for setting up a Resource Provider (node) on the public Lilypad testnet using Docker, including obtaining necessary funds and installing required software.
Last updated
Was this helpful?
Linux (Ubuntu 22.04 LTS)
Nvidia GPU
(Ubuntu install)
(NVIDIA Container Toolkit)
The testnet has a base currency of ETH, as well as a utility token called LP. Both are used for running nodes. To add a node to the testnet, follow these steps:
We recommend using MetaMask with custom settings to make things easier. Once you have it installed and setup, here are the settings you need to use:
The faucet will give you both ETH (to pay for gas) and LP (to stake and pay for jobs).
The Lilypad Network uses the Arbitrum Sepolia Testnet to settle compute transactions. When a transaction is ready to be saved on-chain, Lilypad cycles through a list of public Arbitrum Sepolia RPC endpoints using the endpoint that settles first to save the compute transaction.
Before starting, export your private key from MetaMask. Follow the official MetaMask guide for instructions on safely exporting your private key.
Use curl
to download the docker-compose.yml
file from the Lilypad GitHub repository.
If any containers named resource-provider
, ipfs
, or watchtower
are already in use, they will need to be stopped before running this setup to avoid naming conflicts.
You can check if these containers are running with:
If they are running, stop them with:
If there are still conflicts when trying to running with the docker-compose file, remove the containers:
Start the Lilypad containers using Docker Compose:
To include a custom RPC URL:
You must not reuse your compute node key as a client, even for testing: this will result in failed jobs and will negatively impact your compute node since the wallet address is how nodes are identified on the network.
Use the following command to check the status of the resource provider and bacalhau.
Use the following command to view the containers running after starting Docker Compose.
When a new version of Lilypad is released, it is critical for Resource Providers to update their installations to ensure compatibility and ability to run Lilypad jobs.
To view your Lilybit_ rewards, visit one of the following dashboards and paste your node's public address into the input:
For a step by step guide on adding the network, please refer to our .
To obtain testnet LP, use the and enter your ETH address.
To obtain testnet ETH, use a third party and enter your ETH address.
If you need more tokens and already have Sepolia ETH, use the to transfer tokens over to Arbitrum Sepolia.
Resource Providers have the option to using Alchemy instead of using the default public RPC endpoints.
A personal RPC endpoint helps RPs to avoid reliability issues with the public 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 .
Before we start the Rp with the Docker setup, retrieve the private key from the wallet set up earlier in this guide. For guidance on exporting your private key, refer to . Once the private key has been retrieved, proceed to initialize the Docker containers using the commands provided below.
The same WEB3_PRIVATE_KEY cannot be used for both a RP and using the Lilypad CLI. If a WEB3_PRIVATE_KEY has already been used to run jobs with the CLI, make a new one and . You can `unset $WEB3_PRIVATE_KEY` if you want to use a different one to run your RP.
Before moving to the next step, ensure older versions of lilypad and bacalhau as systemd services.
Using the Lilypad Docker setup a new RP and run.
are some common troubleshooting techniques when it comes to your resource provider using Docker.