Repository: base/node
Stars: 68623
README.md
!Base
Base Node
Base is a secure, low-cost, developer-friendly Ethereum L2 built on Optimism's OP Stack. This repository contains Docker builds to run your own node on the Base network.





Quick Start
1. Ensure you have an Ethereum L1 full node RPC available
2. Choose your network:
- For mainnet: Use .env.mainnet
- For testnet: Use .env.sepolia
3. Configure your L1 endpoints in the appropriate .env file:
OP_NODE_L1_ETH_RPC=<your-preferred-l1-rpc>
OP_NODE_L1_BEACON=<your-preferred-l1-beacon>
OP_NODE_L1_BEACON_ARCHIVER=<your-preferred-l1-beacon-archiver>4. Start the node:
# For mainnet (default):
docker compose up --build # For testnet:
NETWORK_ENV=.env.sepolia docker compose up --build
# To use a specific client (optional):
CLIENT=reth docker compose up --build
# For testnet with a specific client:
NETWORK_ENV=.env.sepolia CLIENT=reth docker compose up --build
Supported Clients
- reth (default)
- geth
- nethermind
Requirements
Minimum Requirements
- Modern Multicore CPU
- 32GB RAM (64GB Recommended)
- NVMe SSD drive
- Storage: (2 \* current chain size + snapshot size + 20% buffer) (to accommodate future growth)
- Docker and Docker Compose
Production Hardware Specifications
The following are the hardware specifications we use in production:
#### Reth Archive Node (recommended)
- Instance: AWS i7i.12xlarge
- Storage: RAID 0 of all local NVMe drives (/dev/nvme*)
- Filesystem: ext4
#### Geth Full Node
- Instance: AWS i7i.12xlarge
- Storage: RAID 0 of all local NVMe drives (/dev/nvme*)
- Filesystem: ext4
[!NOTE]
To run the node using a supported client, you can use the following command:
CLIENT=supported_client docker compose up --buildSupported clients:
- reth (runs vanilla node by default, Flashblocks mode enabled by providing RETH_FB_WEBSOCKET_URL, see Reth Node README)
- geth
- nethermind
Configuration
Required Settings
- L1 Configuration:
- OP_NODE_L1_ETH_RPC: Your Ethereum L1 node RPC endpoint
- OP_NODE_L1_BEACON: Your L1 beacon node endpoint
- OP_NODE_L1_BEACON_ARCHIVER: Your L1 beacon archiver endpoint
- OP_NODE_L1_RPC_KIND: The type of RPC provider being used (default: "debug_geth"). Supported values:
- alchemy: Alchemy RPC provider
- quicknode: QuickNode RPC provider
- infura: Infura RPC provider
- parity: Parity RPC provider
- nethermind: Nethermind RPC provider
- debug_geth: Debug Geth RPC provider
- erigon: Erigon RPC provider
- basic: Basic RPC provider (standard receipt fetching only)
- any: Any available RPC method
- standard: Standard RPC methods including newer optimized methods
Network Settings
- Mainnet:
- RETH_CHAIN=base
- OP_NODE_NETWORK=base-mainnet
- Sequencer: https://mainnet-sequencer.base.org
Performance Settings
- Cache Settings:
- GETH_CACHE="20480" (20GB)
- GETH_CACHE_DATABASE="20" (4GB)
- GETH_CACHE_GC="12"
- GETH_CACHE_SNAPSHOT="24"
- GETH_CACHE_TRIE="44"
Optional Features
- EthStats Monitoring (uncomment to enable)
- Trusted RPC Mode (uncomment to enable)
- Snap Sync (experimental)
For full configuration options, see the .env.mainnet file.
Snapshots
Snapshots are available to help you sync your node more quickly. See docs.base.org for links and more details on how to restore from a snapshot.
Supported Networks
| Network | Status |
| ------- | ------ |
| Mainnet | β
|
| Testnet | β
|
Troubleshooting
For support please join our Discord post in π ο½node-operators. You can alternatively open a new GitHub issue.
Disclaimer
THE NODE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. We make no guarantees about asset protection or security. Usage is subject to applicable laws and regulations.
For more information, visit docs.base.org.