Custom RPC

Use your own RPC endpoints for faster speeds and no wallet limits.

Why Custom RPCs?

By default the bot uses shared Alchemy endpoints. Custom RPCs let you bring your own nodes for better speeds, privacy, and higher rate limits.

When using custom RPCs on a chain, the per-contract wallet limit (25) is removed. You are not consuming the shared RPC quota, so the cap does not apply.

Setting Up

On the main menu, tap RPC : Default next to the chain selector. This opens the RPC config screen for your current chain.

  1. Tap Add RPC and paste one or more HTTPS RPC URLs (one per line or comma-separated).
  2. The bot dials each URL and checks its eth_chainId. If the chain ID does not match your selected chain, the URL is rejected.
  3. On success, the RPCs are saved (encrypted) and the mode automatically switches to Custom.
Your message containing RPC URLs is auto-deleted from chat immediately, regardless of whether validation passes or fails.

Switching Modes

Use the Switch to Default / Switch to Custom button to toggle. Your saved custom URLs are preserved when you switch back to default — you can re-enable them at any time.

Test Latency

Tap Test Latency to ping each custom RPC with eth_blockNumber. The bot reports the round-trip time in milliseconds for each endpoint, helping you identify slow or dead nodes.

Removing RPCs

Tap Remove RPC to pick individual URLs to delete, or Remove All to clear every custom RPC for the current chain. Removing all RPCs automatically switches back to default.

How It Works

  • Custom RPCs are per-chain, per-user. Setting custom RPCs for ETH does not affect Base or any other chain.
  • The bot uses round-robin load balancing across your custom URLs, just like the default pool.
Only HTTPS URLs are supported. WebSocket URLs are not accepted.
Custom RPCs are not supported for ETH-FLASHBOT. That chain always uses Flashbots Protect for broadcasting — failed transactions are dropped instead of being included on-chain, so you never lose gas fees on reverts.