> For the complete documentation index, see [llms.txt](https://docs.lilypad.tech/lilypad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lilypad.tech/lilypad/archive/setup-arbitrum-rpc/alchemy-rpc.md).
# Alchemy RPC
Setup a personal Arbitrum Sepolia RPC for a Lilypad Resource Provider.
This guide walks through the steps of setting up a personal RPC endpoint for Arbitrum Sepolia using [Alchemy](https://www.alchemy.com/).
{% hint style="info" %}
This guide demonstrates how to use Alchemy's RPC, but this can be substituted for any Arbitrum Sepolia RPC that supports WebSockets.
{% endhint %}
## Setup Alchemy account
[Create an account](https://dashboard.alchemy.com/) 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
{% hint style="info" %}
This is guide is for individuals running a Lilypad Resource provider, find more info [here](https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node).
{% endhint %}
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
```
Use this command to start the lilypad-resource-provider.service with the new RPC:
```
docker run -d --gpus all -e WEB3_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
```
### **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](https://docs.lilypad.tech/lilypad/hardware-providers/run-a-node/linux#install-systemd-unit-for-bacalhau) 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
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.lilypad.tech/lilypad/archive/setup-arbitrum-rpc/alchemy-rpc.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media&token=14d16707-18d2-46bf-b2f3-1b9e5cb8a896)