blockchain-rpc-nodes
Self-hosted RPC and archive nodes for EVM chains, packaged as Docker Compose setups. Supports BSC, Arbitrum, Optimism, Linea, and many other chains with regular updates.
Ficha actualizada 22 sept 2026, 18:33 · upstream 22 sept 2026, 16:53 · release sin release detectada
Qué es blockchain-rpc-nodes
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
Blockchain RPC & archive nodes designed for self-hosting on local or cloud infrastructure. The project provides pre-configured Docker Compose environments for popular EVM-compatible blockchains including Ethereum, Polygon, Solana, and others. Each chain has its own directory structure containing configuration files, client binaries, database setups, and deployment scripts. The architecture is modular, allowing users to select their preferred execution engine (e.g., reth, op-reth, bsc-geth) while maintaining a consistent data storage layer.
- Run full-featured Ethereum-compatible RPC services locally for development or testing
- Archive and query blockchain data without relying on centralized providers like Infura or Alchemy
- Deploy custom EVM chains with their own consensus mechanisms (e.g., Plasma, BFT)
- Build private networks or testnets with full node capabilities
- Run lightweight archive nodes for historical chain data retrieval
- Supports over 30+ different blockchain clients and chains out of the box
- Uses PostgreSQL as a shared database layer across all chains, reducing infrastructure complexity
- Designed with low resource requirements (1 CPU core, 1GB RAM) for development environments
- Includes optional scripts for genesis initialization, JWT generation, and environment configuration
- Maintained by the w3arise team with regular client updates and chain additions
- No Dockerfile or docker-compose.yml files are present in the repository; setup requires manual installation of dependencies per chain
- Chain-specific configurations (genesis, rollup params, JWT keys) must be managed externally via .env files stored locally
- OP Stack and Morph chains require a shared L1 RPC URL for execution nodes to communicate with the mainnet
- Some chains like Celo have deprecated or separate client versions that may need manual selection
- No built-in monitoring, health checks, or auto-scaling mechanisms are included
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
To deploy a chain: cd into its directory (e.g., neox) and follow the README.md instructions. The docker-compose.yml file is not present in this repository; you must create it manually based on the provided structure. Ensure your .env files contain valid configuration for each client. For OP Stack chains, set the shared L1 RPC URL before starting execution nodes. Chain data persists under $HOME/.chain/<chain-name>/datadir. Always back up your database and private keys.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.