Skip to content

Supported networks

Supported GraphOps Substreams network endpoints and CAIP-2 network IDs.

Pick the endpoint for the chain your package reads. Each GraphOps Substreams endpoint serves one network, and its hostname starts with that network's decimal EVM chain ID.

Endpoint preview

The CLI uses SUBSTREAMS_API_KEY.

Replace placeholders with your identifier and API key before making requests.

Supported endpoints

NetworkNetwork ID (CAIP-2)gRPC endpoint
Ethereum Mainneteip155:1https://1.evm.substreams.graphops.xyz
Baseeip155:8453https://8453.evm.substreams.graphops.xyz
Arbitrum Oneeip155:42161https://42161.evm.substreams.graphops.xyz

This catalog lists the currently published mainnet and testnet endpoints. Copy the generated endpoint for your network. The CAIP-2 ID identifies the network in the catalog; the hostname uses the decimal chain ID:

https://<CHAIN_ID>.evm.substreams.graphops.xyz
A Substreams endpoint names the network in its hostname: the EVM chain ID, then the namespace. This example is Base (8453). Send the API key in the x-api-key header.

Check package compatibility

A network in the catalog does not make every package work on it. Before you run a package against a network:

  • Confirm the package was built for that chain's block model. Its package page lists the network it declares.
  • Check module assumptions such as contract addresses and start blocks, which differ by network.

Backfills and live streaming are available on every supported network, with standard Substreams cursor and reorg behavior.

Next steps