Skip to main content

Documentation Index

Fetch the complete documentation index at: https://base-a060aa97-meyer9-discv5-p2p-protocol-id.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

This guide provides recommendations for hardware, client software, and configuration settings to optimize the performance of your Base node.

​
Hardware

Running a performant Base node requires adequate hardware. We recommend the following minimum specifications:
  1. A modern multi-core (8+) CPU with good single-core performance.
  2. At least 32 GB RAM (64 GB recommended).
  3. A locally attached NVMe SSD drive. RAID 0 configurations can improve performance.
  4. Sufficient storage capacity calculated as:
(2 × [current chain size] + [snapshot size] + 20% buffer)
This accounts for chain data growth and snapshot restoration space. Refer to Base Stats for current chain size and Base Chain Data for snapshot size.
If utilizing Amazon Elastic Block Store (EBS), io2 Block Express volumes are recommended to ensure sufficient disk read speeds, preventing latency issues during initial sync. However, locally attached NVMe SSDs are strongly recommended over networked storage for optimal performance.

​
Production Hardware Examples

The following are the hardware specifications used for Base production nodes:
  • Reth Archive Node:
    • Instance: AWS i7i.12xlarge or larger
    • Storage: RAID 0 of all local NVMe drives (/dev/nvme*)
    • Filesystem: ext4

​
Initial Sync

Using a recent snapshot can significantly reduce the time required for the initial node synchronization process.

​
Client Software

The Base Node repository contains the current stable configurations and instructions for running different client implementations. Reth is currently the most performant client for running Base nodes. Future optimizations will primarily focus on Reth. You can read more about the migration to Reth here.