Practical overview
When it fits
Use Nodecore when you operate a blockchain application and want a self-hosted layer between the application and one or more RPC providers, with routing and request-management policies configured centrally.
Who it is for
- Teams operating blockchain applications that need to route RPC traffic across multiple providers.
- Infrastructure engineers seeking a configurable gateway for blockchain APIs and operational monitoring.
Documented uses
- Distribute blockchain API requests across configured RPC providers.
- Select upstreams using performance measures such as latency, throughput and error rates.
- Apply caching, retries, hedged requests and rate limits to upstream traffic.
- Compare independently signed upstream responses through quorum verification.
Requirements & limits
The project is available as a public MIT-licensed GitHub repository. The README documents Docker and source-build approaches.
- Provider endpoints and a configuration file are required for the documented Docker setup.
- Supported interfaces and methods vary by chain specification; check the chain's method spec before relying on a particular RPC shape or method.
- The README describes the project as under active development.
- The repository documents Docker deployment and a source build using
make buildandmake run.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Configure and start Nodecore with Docker
Start the gateway using a YAML configuration with at least one blockchain RPC upstream.
Before you start
- Docker
- A Nodecore YAML configuration file
- At least one blockchain RPC provider URL and its chain and connector details
Steps
Create a configuration with an upstream entry specifying its ID, chain, connector type and provider URL.
Run the documented Docker image, publish port 9090 and mount the configuration at /nodecore.yml.
Send a JSON-RPC request to the local /queries/{chain} route, following the Ethereum example in the README.
Expected outcome
A locally running Nodecore gateway configured with an upstream, ready to receive a request in the documented format.
Guide limitations
- The example request uses Ethereum and JSON-RPC; available methods and interfaces depend on the chain's method specification.
- The project is described as under active development.
Build and run Nodecore from source
Build the repository binary and start it with a local configuration.
Before you start
- A Go development environment with the repository's build tooling
- A cloned Nodecore repository
- A Nodecore configuration file
Steps
Clone the repository from its GitHub URL.
Run the command below; the documented build command runs the command below automatically.
make buildmake generate-networksRun the command below to use ./nodecore.yml by default, or set NODECORE_CONFIG_PATH to specify another configuration path.
make run
Expected outcome
A locally built Nodecore binary started with the selected configuration.
Guide limitations
- The README notes that
make rundoes not regenerate chain data; runmake generate-networksfirst if needed. - The project is described as under active development.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- drpcorg/nodecore · Official homepage title · retained in its source language

