eRPC is a fault-tolerant EVM RPC proxy and re-org aware permanent caching solution. It is built with read-heavy use-cases in mind, such as data indexing and high-load frontend usage.

With the below setup, you get immediate access to 2,000+ chains and 4,000+ public free EVM RPC endpoints.

Using npx:

npx start-erpc

Or, using Docker:

docker run -p 4000:4000 ghcr.io/erpc/erpc

Or, using Railway:

curl 'http://localhost:4000/main/evm/42161' \
--header 'Content-Type: application/json' \
--data '{
    "method": "eth_getBlockByNumber",
    "params": ["latest", false],
    "id": 9199,
    "jsonrpc": "2.0"
}'

This setup is ideal for development and testing purposes. For production environments, we recommend extending your configuration with dedicated premium providers and advanced failover settings. See our Configuration Guide for more details.

• Retries, circuit breakers, failovers, and hedged requests: Ensures the fastest, most reliable upstream is always used
• Configurable rate limits: Set hourly or daily rate limits per upstream to control usage and costs
• Local re-org aware cache: Avoid redundant upstream calls and maintain data consistency when blockchain reorgs occur
• Automatic method routing: No need to worry which provider supports which eth_* method
• Unified error handling: Consistent error codes and detailed messages across multiple providers
• Single dashboard: Observe throughput (RPS), errors, and average latency across all providers
• Flexible authentication: Supports basic auth, secrets, JWT, SIWE and more
• Smart batching: Aggregate multiple RPC or contract calls into one
• Selection policy: Allows you to influence how upstreams are selected to serve traffic (or not) w/ selection policies.
• Data integrity: Ensures accurate, up-to-date responses by levering several data integrity mechanisms.
• Consensus policy: Compares results from multiple upstreams and punishes nodes that consistently disagree.

• 🔵 Moonwell: How eRPC slashed RPC calls by 67%
• 🟢 Chronicle: How eRPC reduced RPC cost by 45%

eRPC provides several CLI commands beyond the default server start:

Validate a configuration file (TS, JS, or YAML) and report any errors, warnings, or notices. Useful in CI pipelines to catch misconfigurations before deployment.

erpc validate erpc.yaml
erpc validate erpc.ts

Parse a configuration file and output the fully resolved configuration with all eRPC defaults applied. Supports YAML and JSON output. This is useful for inspecting what your final config looks like after eRPC fills in all default values (retry policies, timeouts, selection policies, etc.).

# Output as YAML (default)
erpc dump erpc.yaml

# Output as JSON
erpc dump --format json erpc.ts

# Compare two configs (e.g. before/after a migration)
diff <(erpc dump old-config.yaml) <(erpc dump new-config.yaml)

1. Clone this repository:

git clone https://github.com/erpc/erpc.git

2. Install Go dependencies:

make setup

3. Create a configuration file:

cp erpc.dist.yaml erpc.yaml
vi erpc.yaml

4. Run the eRPC server:

make run

By contributing to this project, you agree that your contributions may be used in both the open-source and enterprise versions of the software. Please review our Contributing Guidelines and Contributor License Agreement before submitting your contributions.

Apache 2.0