# Supported networks

Source: https://docs.graphops.xyz/substreams/networks

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. Replace placeholders with your identifier and API key before making requests.

```text
https://1.evm.substreams.graphops.xyz
x-api-key: <GRAPHOPS_API_KEY>
```

[Get query endpoint](https://platform.graphops.xyz/organizations/current/overview/endpoint?product=substreams&networkId=eip155%3A1)
[Supported networks](/substreams/networks)

## Supported endpoints

| Network | Network ID (CAIP-2) | gRPC endpoint |
| --- | --- | --- |
| Ethereum Mainnet | eip155:1 | https://1.evm.substreams.graphops.xyz |
| Ethereum Sepolia | eip155:11155111 | https://11155111.evm.substreams.graphops.xyz |
| Base | eip155:8453 | https://8453.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:

```text
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._

```text
https://8453.evm.substreams.graphops.xyz
x-api-key: <GRAPHOPS_API_KEY>
```

- EVM chain ID: `8453`
- Namespace: `evm`
- Substreams host: `substreams.graphops.xyz`

Need a network that isn't listed? [Request it](/platform/support-and-status#request-a-network-or-data).

## 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

* [Getting started](/substreams/getting-started): Stream USDC Transfer events from Ethereum mainnet.
* [Discover Substreams packages](/substreams/guides/discover-packages): Find packages that declare your network.
* [Backfill a range](/substreams/guides/backfill-a-range): Load a network's history into your database.