GitHub - Diffusion-Labs/erpc: eRPC — fault-tolerant evm rpc proxy

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.

⚠️ Note: eRPC is still under development. We recommend using it for testnets or as a fallback provider for production RPC calls.

Quick Start

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

Run an eRPC instance:

Using npx:

npx start-erpc

Or, using Docker:

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

Or, using Railway:

Send a request to your eRPC instance:

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

Next Steps:

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.

Key Features

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.

Case Studies

Local Development

Clone this repository:

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

Install Go dependencies:

make setup

Create a configuration file:

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

Run the eRPC server:

make run

Contributors

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.

License

Apache 2.0

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.

⚠️ Note: eRPC is still under development. We recommend using it for testnets or as a fallback provider for production RPC calls.

Quick Start

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

Run an eRPC instance:

Using npx:

npx start-erpc

Or, using Docker:

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

Or, using Railway:

Send a request to your eRPC instance:

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

Next Steps:

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.

Key Features

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.

Case Studies

Local Development

Clone this repository:

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

Install Go dependencies:

make setup

Create a configuration file:

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

Run the eRPC server:

make run

Contributors

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.

License

Apache 2.0

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.

⚠️ Note: eRPC is still under development. We recommend using it for testnets or as a fallback provider for production RPC calls.

Quick Start

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

Run an eRPC instance:

Using npx:

npx start-erpc

Or, using Docker:

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

Or, using Railway:

Send a request to your eRPC instance:

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

Next Steps:

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.

Key Features

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.

Case Studies

Local Development

Clone this repository:

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

Install Go dependencies:

make setup

Create a configuration file:

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

Run the eRPC server:

make run

Contributors

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.

License

Apache 2.0

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.

⚠️ Note: eRPC is still under development. We recommend using it for testnets or as a fallback provider for production RPC calls.

Quick Start

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

Run an eRPC instance:

Using npx:

npx start-erpc

Or, using Docker:

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

Or, using Railway:

Send a request to your eRPC instance:

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

Next Steps:

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.

Key Features

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.

Case Studies

Local Development

Clone this repository:

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

Install Go dependencies:

make setup

Create a configuration file:

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

Run the eRPC server:

make run

Contributors

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.

License

Apache 2.0

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.

⚠️ Note: eRPC is still under development. We recommend using it for testnets or as a fallback provider for production RPC calls.

Quick Start

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

Run an eRPC instance:

Using npx:

npx start-erpc

Or, using Docker:

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

Or, using Railway:

Send a request to your eRPC instance:

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

Next Steps:

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.

Key Features

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.

Case Studies

Local Development

Clone this repository:

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

Install Go dependencies:

make setup

Create a configuration file:

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

Run the eRPC server:

make run

Contributors

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.

License

Apache 2.0

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.

⚠️ Note: eRPC is still under development. We recommend using it for testnets or as a fallback provider for production RPC calls.

Quick Start

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

Run an eRPC instance:

Using npx:

npx start-erpc

Or, using Docker:

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

Or, using Railway:

Send a request to your eRPC instance:

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

Next Steps:

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.

Key Features

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.

Case Studies

Local Development

Clone this repository:

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

Install Go dependencies:

make setup

Create a configuration file:

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

Run the eRPC server:

make run

Contributors

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.

License

Apache 2.0

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.

⚠️ Note: eRPC is still under development. We recommend using it for testnets or as a fallback provider for production RPC calls.

Quick Start

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

Run an eRPC instance:

Using npx:

npx start-erpc

Or, using Docker:

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

Or, using Railway:

Send a request to your eRPC instance:

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

Next Steps:

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.

Key Features

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.

Case Studies

Local Development

Clone this repository:

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

Install Go dependencies:

make setup

Create a configuration file:

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

Run the eRPC server:

make run

Contributors

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.

License

Apache 2.0

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.

⚠️ Note: eRPC is still under development. We recommend using it for testnets or as a fallback provider for production RPC calls.

Quick Start

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

Run an eRPC instance:

Using npx:

npx start-erpc

Or, using Docker:

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

Or, using Railway:

Send a request to your eRPC instance:

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

Next Steps:

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.

Key Features

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.

Case Studies

Local Development

Clone this repository:

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

Install Go dependencies:

make setup

Create a configuration file:

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

Run the eRPC server:

make run

Contributors

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.

License

Apache 2.0

Name		Name	Last commit message	Last commit date
.github		.github
.vscode		.vscode
architecture/evm		architecture/evm
assets		assets
auth		auth
clients		clients
cmd/erpc		cmd/erpc
common		common
consensus		consensus
data		data
docs		docs
erpc		erpc
health		health
kube		kube
monitoring		monitoring
scylla		scylla
test		test
thirdparty		thirdparty
typescript		typescript
upstream		upstream
util		util
.dockerignore		.dockerignore
.gitignore		.gitignore
.goreleaser.yaml		.goreleaser.yaml
.semrelrc		.semrelrc
CLA.md		CLA.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile		Dockerfile
Dockerfile.fake		Dockerfile.fake
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
biome.json		biome.json
codecov.yml		codecov.yml
docker-compose.yml		docker-compose.yml
erpc.dist.ts		erpc.dist.ts
erpc.dist.yaml		erpc.dist.yaml
erpc.yaml		erpc.yaml
go.mod		go.mod
go.sum		go.sum
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
prometheus.yaml		prometheus.yaml
tsconfig.json		tsconfig.json
tygo.yaml		tygo.yaml

Name		Name	Last commit message	Last commit date
.github		.github
.vscode		.vscode
architecture/evm		architecture/evm
assets		assets
auth		auth
clients		clients
cmd/erpc		cmd/erpc
common		common
consensus		consensus
data		data
docs		docs
erpc		erpc
health		health
kube		kube
monitoring		monitoring
scylla		scylla
test		test
thirdparty		thirdparty
typescript		typescript
upstream		upstream
util		util
.dockerignore		.dockerignore
.gitignore		.gitignore
.goreleaser.yaml		.goreleaser.yaml
.semrelrc		.semrelrc
CLA.md		CLA.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile		Dockerfile
Dockerfile.fake		Dockerfile.fake
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
biome.json		biome.json
codecov.yml		codecov.yml
docker-compose.yml		docker-compose.yml
erpc.dist.ts		erpc.dist.ts
erpc.dist.yaml		erpc.dist.yaml
erpc.yaml		erpc.yaml
go.mod		go.mod
go.sum		go.sum
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
prometheus.yaml		prometheus.yaml
tsconfig.json		tsconfig.json
tygo.yaml		tygo.yaml

Name		Name	Last commit message	Last commit date
.github		.github
.vscode		.vscode
architecture/evm		architecture/evm
assets		assets
auth		auth
clients		clients
cmd/erpc		cmd/erpc
common		common
consensus		consensus
data		data
docs		docs
erpc		erpc
health		health
kube		kube
monitoring		monitoring
scylla		scylla
test		test
thirdparty		thirdparty
typescript		typescript
upstream		upstream
util		util
.dockerignore		.dockerignore
.gitignore		.gitignore
.goreleaser.yaml		.goreleaser.yaml
.semrelrc		.semrelrc
CLA.md		CLA.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile		Dockerfile
Dockerfile.fake		Dockerfile.fake
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
biome.json		biome.json
codecov.yml		codecov.yml
docker-compose.yml		docker-compose.yml
erpc.dist.ts		erpc.dist.ts
erpc.dist.yaml		erpc.dist.yaml
erpc.yaml		erpc.yaml
go.mod		go.mod
go.sum		go.sum
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
prometheus.yaml		prometheus.yaml
tsconfig.json		tsconfig.json
tygo.yaml		tygo.yaml

Name		Name	Last commit message	Last commit date
.github		.github
.vscode		.vscode
architecture/evm		architecture/evm
assets		assets
auth		auth
clients		clients
cmd/erpc		cmd/erpc
common		common
consensus		consensus
data		data
docs		docs
erpc		erpc
health		health
kube		kube
monitoring		monitoring
scylla		scylla
test		test
thirdparty		thirdparty
typescript		typescript
upstream		upstream
util		util
.dockerignore		.dockerignore
.gitignore		.gitignore
.goreleaser.yaml		.goreleaser.yaml
.semrelrc		.semrelrc
CLA.md		CLA.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile		Dockerfile
Dockerfile.fake		Dockerfile.fake
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
biome.json		biome.json
codecov.yml		codecov.yml
docker-compose.yml		docker-compose.yml
erpc.dist.ts		erpc.dist.ts
erpc.dist.yaml		erpc.dist.yaml
erpc.yaml		erpc.yaml
go.mod		go.mod
go.sum		go.sum
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
prometheus.yaml		prometheus.yaml
tsconfig.json		tsconfig.json
tygo.yaml		tygo.yaml

Name		Name	Last commit message	Last commit date
.github		.github
.vscode		.vscode
architecture/evm		architecture/evm
assets		assets
auth		auth
clients		clients
cmd/erpc		cmd/erpc
common		common
consensus		consensus
data		data
docs		docs
erpc		erpc
health		health
kube		kube
monitoring		monitoring
scylla		scylla
test		test
thirdparty		thirdparty
typescript		typescript
upstream		upstream
util		util
.dockerignore		.dockerignore
.gitignore		.gitignore
.goreleaser.yaml		.goreleaser.yaml
.semrelrc		.semrelrc
CLA.md		CLA.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile		Dockerfile
Dockerfile.fake		Dockerfile.fake
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
biome.json		biome.json
codecov.yml		codecov.yml
docker-compose.yml		docker-compose.yml
erpc.dist.ts		erpc.dist.ts
erpc.dist.yaml		erpc.dist.yaml
erpc.yaml		erpc.yaml
go.mod		go.mod
go.sum		go.sum
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
prometheus.yaml		prometheus.yaml
tsconfig.json		tsconfig.json
tygo.yaml		tygo.yaml

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Quick Start

Run an eRPC instance:

Send a request to your eRPC instance:

Next Steps:

Key Features

Case Studies

Local Development

Contributors

License

About

Resources

Code of conduct

Contributing

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Quick Start

Run an eRPC instance:

Send a request to your eRPC instance:

Next Steps:

Key Features

Case Studies

Local Development

Contributors

License

About

Resources

Code of conduct

Contributing

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Quick Start

Run an eRPC instance:

Send a request to your eRPC instance:

Next Steps:

Key Features

Case Studies

Local Development

Contributors

License

About

Resources

Code of conduct

Contributing

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation