RPC
Add fast, healthy RPCs so your tasks land reliably.
Every onchain operation routes through the RPC page’s list. A good RPC list is the single biggest reliability lever you have.
Adding RPC Endpoints
Just like other manager in the app, RPC is separated in groups. Ideally you want to group it by chain.
- Click + Add Group and name it (e.g. ETH Mainnet).
- Click + Add RPC and paste the URL/s.
- The app will verify the chain, test the latency, and add them into the list.
If the probe fails, the endpoint stays in the list but is marked unhealthy, and tasks skip it.
Recommended RPC Providers
To bot competitively, ideally you’ll need RPC endpoints from private RPC providers. They usually have free and paid plan, you can get the free ones by registering an account, but we recommend to pick the paid one as they’re dirt cheap and rarely get rate-limited.
- Alchemy : has free plan, opt-in to pay-per-use.
- DRPC : has free plan, top-up credits for pay-per-use.
- ANKR : has free plan, top-up credits for pay-per-use
- Quicknode : has free plan, offers monthly paid subscription.
How many RPC do you need?
| Use case | Recommendation |
|---|---|
| Casual 3-5 wallets | 1-2 paid/free endpoints |
| 20+ wallets | 3-5 paid endpoints, more is better |
| Spam mode | Keep various paid providers at ready |
Public RPC Override
In Settings, each chain has a Public RPC override field. It replaces the built-in fallback public default for that chain only — handy when a baked-in public RPC has gone bad and you don’t want to add your own.