Projects

A single instance of eRPC can be used for various projects, any number of chains, and any number of upstreams.

You can have separate backend, indexer and frontend projects, so that you control self-imposed rate-limits, or supported methods. This allows you to decide different "cost" vs "reliability" strategies for each project.

Config

The projects: array is the top-most configuration, and it is required to have at least 1 project. Each project has the following properties:

• id: a unique identifier used in logs and metrics.
• rateLimitBudget: a budget for the total number of requests that this project is allowed to serve.
• networks: an array of custom configuration for one or more of the supported networks.
• upstreams: an array of all upstreams to use in this project.

Example

Refer to erpc.yaml and "projects" section.