Next-gen RPC node

Screenshots

Problem Statement

The solution is applicable for Ethereum, Polygon, Scroll, Gnosis Chain, Mina, Arbitrum, zkSync, Filecoin EVM, Near’s Aurora EVM, Starknet, Mantle, Base, Neon EVM, Aztec and other EVM-compatible chains.The public RPC nodes offered by protocols are confined to their infrastructure, resulting in decreased uptime, heightened latency, and the absence of customizable logic for an RPC endpoint.Imagine a service that can aggregate multiple RPC endpoints from various providers, geographical regions, and cloud services to:Verify if a node is operational and accessible.Confirm if a node possesses the latest block height.Based on these criteria, the service would intelligently reroute to the optimal node. Additionally, for the selected node, our service would:Apply access-list capabilities to whitelist IP addresses or HTTP Referrer origin values.Implement custom rate-limiting and throttling parameters.This comprehensive service would significantly enhance:RPC node availabilityAssurance of the latest chain data on the node.Prevention of node congestion, ensuring adequate resources for RPC traffic.Introducing Next-gen RPC node, a ready-to-go, open-source service available for everyone. It proves beneficial for every DApp project, across any EVM-compatible chain, providing an unparalleled user experience for web3 developers.

Solution

The project is based on Cloudflare Workers (https://workers.cloudflare.com/), using Cloudflare KV Storage plugin and Cloudflare Caching API.The Cloudflare workers are written in Typescript. The RPC nodes are running in Chainstack.In Github repo there is an architecture diagram that show how these pieces combined together.