Find the endpoint for your network, confirm it supports the transport you need, and check whether it serves archive data and execution traces.
Supported endpoints
| Network | Network ID (CAIP-2) | HTTPS endpoint | WebSocket endpoint | Archive | Tracing |
|---|---|---|---|---|---|
| Ethereum Mainnet | eip155:1 | https://rpc.graphops.xyz/v1/evm/1 | wss://rpc.graphops.xyz/v1/evm/1 | Yes | Yes |
| Ethereum Sepolia | eip155:11155111 | https://rpc.graphops.xyz/v1/evm/11155111 | wss://rpc.graphops.xyz/v1/evm/11155111 | Yes | No |
| Gnosis | eip155:100 | https://rpc.graphops.xyz/v1/evm/100 | wss://rpc.graphops.xyz/v1/evm/100 | Yes | No |
| Base | eip155:8453 | https://rpc.graphops.xyz/v1/evm/8453 | wss://rpc.graphops.xyz/v1/evm/8453 | Yes | Yes |
| Base Sepolia Testnet | eip155:84532 | https://rpc.graphops.xyz/v1/evm/84532 | wss://rpc.graphops.xyz/v1/evm/84532 | Yes | Yes |
| Arbitrum One | eip155:42161 | https://rpc.graphops.xyz/v1/evm/42161 | wss://rpc.graphops.xyz/v1/evm/42161 | Yes | No |
| Arbitrum Sepolia | eip155:421614 | https://rpc.graphops.xyz/v1/evm/421614 | wss://rpc.graphops.xyz/v1/evm/421614 | Yes | No |
| Bitcoin Mainnet | bip122:000000000019d6689c085ae165831e93 | https://rpc.graphops.xyz/v1/bitcoin/mainnet | — | Yes | — |
| Bitcoin Signet | bip122:00000008819873e925422c1ff0f99f7c | https://rpc.graphops.xyz/v1/bitcoin/signet | — | Yes | — |
This catalog includes currently published mainnet and testnet endpoints. Copy the generated endpoint for your network when configuring a connection. The CAIP-2 ID identifies the network; the endpoint contains its service-specific routing reference.
Need a network that isn't listed? Request it.
EVM endpoints
The EVM RPC endpoint path ends in the EVM chain ID:
Reference
https://rpc.graphops.xyz/v1/evm/<CHAIN_ID>
wss://rpc.graphops.xyz/v1/evm/<CHAIN_ID>
Bitcoin endpoints
Bitcoin RPC uses HTTPS and a network name instead of an EVM chain ID:
Reference
https://rpc.graphops.xyz/v1/bitcoin/<NETWORK>
Choose a Bitcoin network from the catalog above.
Network notes
| Network | Notes |
|---|---|
| Ethereum Mainnet | Use safe, finalized, or explicit block references when user-facing workflows need more stability than latest. See Consistency and finality. |
| Arbitrum One | L2 transaction visibility and finality can differ from Ethereum L1. Use explicit block references for multi-call workflows. |
| Base | L2 transaction visibility and finality can differ from Ethereum L1. Use explicit block references for multi-call workflows. |
Archive support
Check the Archive column above for each network’s published capability. On an EVM network,
Yes means historical state, such as eth_call at a past block, and
historical event logs are available; see Archive reads. On a Bitcoin
network, it means the node keeps every block since genesis, so getblock returns any block.
Historical state reads and broad log backfills are heavier than current-state reads. Use bounded
ranges and split large jobs into resumable chunks.
Tracing support
Check the Tracing column above. Yes means the network serves execution
traces through the trace_* methods; see Execution traces. Tracing applies to
EVM networks only.
Next steps
Last updated