> For the complete documentation index, see [llms.txt](https://docs.envio.dev/llms.txt).

# Any EVM with RPC 🐌

---

Any EVM-compatible chain can be indexed using an RPC as a source. This means that you can use any EVM-compatible chain as a data source for your indexer. This is particularly useful for chains that do not have a native HyperSync or HyperRPC solution.

### Defining Chain Configurations

```yaml
name: IndexerName # Specify indexer name
description: Indexer Description # Include indexer description
chains:
  - id: 1234567890
    rpc: https://custom-chain-rpc.com # RPC URL for that custom chain
    start_block: 0 # Specify the starting block
    contracts:
      - name: ContractName
        address:
          - "0xYourContractAddress1" # Replace with your contract addresses
          - "0xYourContractAddress2"
        events:
          - event: "Transfer(address indexed from, address indexed to, uint256 value)" # Event signature
```

### Choosing an RPC Provider

Envio's RPC partner [Dwellir](https://www.dwellir.com/networks?utm_source=envio.dev) provides endpoints for many EVM chains and is a good place to start if you need an RPC for a network without HyperSync support. See [RPC as Data Source](/docs/HyperIndex/rpc-sync) for more configuration options.

### Support

Can’t find what you’re looking for or need support? Reach out to us on [Discord](https://discord.gg/envio); we’re always happy to help!

:::info
The backbone of HyperIndex’s blazing-fast indexing speed lies in using HyperSync as a more performant and cost-effective data source to RPC for data retrieval. While RPCs are functional, and can be used in HyperIndex as a data source, they are far from efficient when it comes to querying large amounts of data (a time-consuming and resource-intensive endeavour).

HyperSync is significantly faster and more cost-effective than traditional RPC methods, allowing the retrieval of multiple blocks at once, and enabling sync speeds up to 1000x faster than RPC.
:::

---