Arbitrum RPCs

Arbitrum One RPC endpoint options for Livepeer orchestrators – provider comparison, rate limits, and configuration.

Livepeer orchestrators require an Arbitrum One RPC endpoint to interact with the protocol – staking, reward calls, ticket redemption, and service registration all happen on Arbitrum. The endpoint is configured via the -ethUrl flag.

Requirements

Your RPC endpoint must:

• Connect to Arbitrum One (chain ID 42161 / 0xa4b1) – not Ethereum L1
• Support standard JSON-RPC methods (eth_call, eth_sendRawTransaction, eth_getBlockByNumber, eth_getLogs)
• Handle the request volume your orchestrator generates – active orchestrators with frequent reward calls and ticket redemptions may exceed free-tier limits

Provider Options

Configuration

Set the endpoint when starting your orchestrator:

livepeer \
  -network arbitrum-one-mainnet \
  -ethUrl https://arb-mainnet.g.alchemy.com/v2/YOUR_API_KEY \
  -orchestrator \
  -transcoder \
  ...

Verify Your Endpoint

Test that the endpoint is reachable and returns the correct chain ID:

curl -X POST -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}' \
  YOUR_ETH_URL

Expected response includes "result":"0xa4b1" (42161 in decimal = Arbitrum One).

Common Issues

For detailed troubleshooting, see the FAQ.

See Also

Arbitrum Exchanges

Contract Addresses

FAQ