TLDR:
eRPC is a fault-tolerant EVM RPC proxy with permanent caching and reorg awareness. One of its most powerful features is the built-in support for multiple blockchain infrastructure providers, including Chainstack.
What makes Chainstack unique in eRPC?
Unlike other providers that require you to manually configure each blockchain network endpoint, Chainstack’s integration with eRPC uses the Chainstack Platform API to automatically discover and configure all your deployed nodes.
This means:
This tutorial will guide you through setting up eRPC as a fault-tolerant proxy for your Chainstack RPC endpoints, providing enhanced reliability, caching, and failover capabilities.
Before starting, ensure you have:
And that’s about it.
You don’t need to clone the eRPC repository. This tutorial uses the pre-built Docker image and creates configuration files from scratch.
The key difference with Chainstack is that you need a Platform API key, not a regular node endpoint API key.
This is different from the authorization keys you get with individual node endpoints. The Platform API key lets eRPC discover and manage all your nodes automatically.
Deploy Global Nodes for EVM networks.
For this tutorial, let’s deploy nodes on a few different networks: Ethereum Mainnet, Polygon Mainnet, Arbitrum Mainnet.
If you want a quick start, you can just stick with the basic configuration and explore other options later.
Create or edit your erpc.yaml
file:
Replace YOUR_CHAINSTACK_PLATFORM_API_KEY
with your actual Platform API key.
Chainstack’s integration supports powerful filtering options:
Replace YOUR_CHAINSTACK_PLATFORM_API_KEY
with your actual Platform API key and PROJECT-ID
with the ID of your project—for example, PR-123-456
.
Start eRPC using Docker:
Test the proxy with a simple request:
For more advanced configurations and features, refer to the eRPC documentation and the eRPC GitHub repository. Don’t forget to give them a star :star: for this awesome solution.
TLDR:
eRPC is a fault-tolerant EVM RPC proxy with permanent caching and reorg awareness. One of its most powerful features is the built-in support for multiple blockchain infrastructure providers, including Chainstack.
What makes Chainstack unique in eRPC?
Unlike other providers that require you to manually configure each blockchain network endpoint, Chainstack’s integration with eRPC uses the Chainstack Platform API to automatically discover and configure all your deployed nodes.
This means:
This tutorial will guide you through setting up eRPC as a fault-tolerant proxy for your Chainstack RPC endpoints, providing enhanced reliability, caching, and failover capabilities.
Before starting, ensure you have:
And that’s about it.
You don’t need to clone the eRPC repository. This tutorial uses the pre-built Docker image and creates configuration files from scratch.
The key difference with Chainstack is that you need a Platform API key, not a regular node endpoint API key.
This is different from the authorization keys you get with individual node endpoints. The Platform API key lets eRPC discover and manage all your nodes automatically.
Deploy Global Nodes for EVM networks.
For this tutorial, let’s deploy nodes on a few different networks: Ethereum Mainnet, Polygon Mainnet, Arbitrum Mainnet.
If you want a quick start, you can just stick with the basic configuration and explore other options later.
Create or edit your erpc.yaml
file:
Replace YOUR_CHAINSTACK_PLATFORM_API_KEY
with your actual Platform API key.
Chainstack’s integration supports powerful filtering options:
Replace YOUR_CHAINSTACK_PLATFORM_API_KEY
with your actual Platform API key and PROJECT-ID
with the ID of your project—for example, PR-123-456
.
Start eRPC using Docker:
Test the proxy with a simple request:
For more advanced configurations and features, refer to the eRPC documentation and the eRPC GitHub repository. Don’t forget to give them a star :star: for this awesome solution.