The Graph currently supports about 80+ EVM chains. As an important part of the web3 stack, The Graph is willing to add more EVM chain support. There are some requirements and assurances to be fulfilled before the team is confident enough to initiate a new EVM chain integration.

RPC requirements

Note - A dedicated RPC needs to be provided by the chain for integrations with the following specifications:

• Requests per second: Usually below 10 rps. May reach 300+ rps during peak usage.
• Total monthly calls: Usually below 20M/month. Large chains use over 300M.
• Archive call support including Genesis block
• 99.99% uptime/response success

Note: We mark new chains as Beta for the first 6 months. If the 99% uptime/response success rate is not met for this period, the chain stays beta until this threshold is met.

Estimated RPC Usage & Costs

| | Starting | Low Volume Chains | Medium Volume (Top 16-30) | High Volume (Top 15 chains) | | --- | --- | --- | --- | --- | | Avg requests per sec* | 1.3 | 7 | 22 | 130 | | Total requests per month | 3M | 18M | 57M | 330M | | Approx. Cost per month | $0-$45 | $45-$250 | $250-$800 | <$3000 |

• This is an average over a month. RPS may be a lot higher during peak usage, so we request no rate limits on the RPC.

The following eth calls are supported by the rpc

• eth_getLogs
• eth_call (for historical blocks, with EIP-1898) - {requires archive node}
• eth_getBlockByNumber
• eth_getBlockByHash
• net_version