OnFinality
New RPC users get 35% off their first monthView the offer
RPC Assistant

How do I configure an Arbitrum RPC endpoint?

Summary

Configure an Arbitrum wallet or application with the correct network ID, RPC URL and gas token. This tutorial covers connection checks; use the OnFinality Arbitrum RPC service page for authenticated access, method costs and plans.

Arbitrum wallet settings

Arbitrum One uses chain ID 42161 and ETH for gas. The official public RPC is https://arb1.arbitrum.io/rpc, and the block explorer is https://arbiscan.io. In your wallet's custom-network settings, enter the network name Arbitrum One, this RPC URL, chain ID 42161, ETH and the explorer URL. ARB is a governance token, not the gas token.

For a provider endpoint, use the URL supplied by that provider with the same chain ID. OnFinality Arbitrum RPC endpoints and plans lists public and authenticated access, WebSocket support and response-unit costs. Do not mix a mainnet chain ID with a testnet URL.

Check the chain ID with curl

curl 'https://arb1.arbitrum.io/rpc' \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

For Arbitrum One, result should be 0xa4b1 (42161). For Arbitrum Sepolia, use https://sepolia-rollup.arbitrum.io/rpc, chain ID 421614 (0x66eee), ETH and https://sepolia.arbiscan.io. Testnet ETH has no mainnet value. Arbitrum Nova is a separate network with chain ID 42170; its endpoint is not interchangeable with Arbitrum One.

Confirm block reads before connecting your application

curl 'https://arb1.arbitrum.io/rpc' \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

A successful response contains a changing hexadecimal block height in result. Inspect both HTTP status and the JSON body: HTTP 200 can still contain a JSON-RPC error. A chain ID response alone does not verify block reads or historical access.

After these checks, set the same RPC URL in your application's provider configuration. Validate the actual contract reads, receipts and log ranges your application needs before sending production traffic.

Troubleshoot the connection

  • Wrong network: compare the returned chain ID with your wallet and application settings. Keep One, Nova and Sepolia configurations separate.
  • HTTP 429: pause requests and retry later with backoff. Use an authenticated provider endpoint when anonymous access is too limited. OnFinality may also return JSON-RPC code -32029 for throttling.
  • No WebSocket connection: Arbitrum's official public RPC does not provide WebSocket. Use the provider's specific wss:// URL when subscriptions are required.
  • Unsupported or expensive methods: verify method support and weights before using archive or Trace/Debug. Authentication does not automatically include every paid feature.

See official Arbitrum chain information for network parameters. To configure OnFinality access after this tutorial, open the Arbitrum RPC service page for endpoint URLs, plan limits and a worked billing example.

RPC Knowledge Base

Related RPC details

Never Worry about Infrastructure Again

OnFinality takes away the heavy lifting of DevOps so you can build smarter and faster.

Get Started