Network guides

EVM L2 checklist (Base, Arb, OP, …)

If your app already speaks eth_*, pointing it at another RpcNode EVM endpoint is mostly a URL + chainId change. Credits and RPS are per endpoint.

basearbitrumoptimismpolygonbsc

← All guides

Steps

  1. Create one endpoint per chain you need (do not reuse an Ethereum UUID on Base).
  2. Configure your wallet/SDK chainId to match the network (Base 8453, Arbitrum One 42161, OP Mainnet 10, Polygon PoS 137, BSC 56 — verify current values in chain docs).
  3. Keep method calls identical: eth_blockNumber, eth_getLogs, eth_call, …
  4. Retest allowlists and RPS — each endpoint has its own limits.

Base tip (curl)

curl

curl https://holy-burned-sky-base-mainnet.rpcnode.dev/7c9e6679-7425-40de-944b-e07fc1f90ae7 \
  -X POST \
  -H 'content-type: application/json' \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_blockNumber",
  "params": []
}'

Base tip (JavaScript)

fetch

const response = await fetch('https://holy-burned-sky-base-mainnet.rpcnode.dev/7c9e6679-7425-40de-944b-e07fc1f90ae7', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({
    jsonrpc: '2.0',
    id: 1,
    method: 'eth_blockNumber',
    params: [],
  }),
});

const data = await response.json();
console.log(data);

Optimism tip (curl)

curl

curl https://holy-burned-sky-optimism-mainnet.rpcnode.dev/7c9e6679-7425-40de-944b-e07fc1f90ae7 \
  -X POST \
  -H 'content-type: application/json' \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_blockNumber",
  "params": []
}'

Optimism tip (JavaScript)

fetch

const response = await fetch('https://holy-burned-sky-optimism-mainnet.rpcnode.dev/7c9e6679-7425-40de-944b-e07fc1f90ae7', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({
    jsonrpc: '2.0',
    id: 1,
    method: 'eth_blockNumber',
    params: [],
  }),
});

const data = await response.json();
console.log(data);

BSC tip (curl)

curl

curl https://holy-burned-sky-bsc-mainnet.rpcnode.dev/7c9e6679-7425-40de-944b-e07fc1f90ae7 \
  -X POST \
  -H 'content-type: application/json' \
  -d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_blockNumber",
  "params": []
}'

BSC tip (JavaScript)

fetch

const response = await fetch('https://holy-burned-sky-bsc-mainnet.rpcnode.dev/7c9e6679-7425-40de-944b-e07fc1f90ae7', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({
    jsonrpc: '2.0',
    id: 1,
    method: 'eth_blockNumber',
    params: [],
  }),
});

const data = await response.json();
console.log(data);

Tips

  • Some L2s expose extra eth_ namespaces or sequencer-specific delays — stick to standard eth_* for portability.
  • Bridge and messaging contracts differ per L2; RPC alone does not move funds across chains.
  • See /errors/evm for family-specific failure modes.

Related