Back to Details

running-a-base-node

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Running a Base Node

运行Base节点

For production apps requiring reliable, unlimited RPC access.
适用于需要可靠、无限制RPC访问的生产级应用。

Security

安全配置

  • Restrict RPC access — bind to 
    127.0.0.1
    or a private interface, never expose RPC ports (
    8545
    /
    8546
    ) to the public internet without authentication
  • Firewall rules — only open ports 9222 (Discovery v5) and 30303 (P2P) to the public; block all other inbound traffic
  • Run as a non-root user with minimal filesystem permissions
  • Use TLS termination (reverse proxy with nginx/caddy) if exposing the RPC endpoint to remote clients
  • Monitor for unauthorized access — log and alert on unexpected RPC calls or connection spikes
  • 限制RPC访问 — 将服务绑定到
    127.0.0.1
    或私有网络接口，未经认证切勿将RPC端口（
    8545
    /
    8546
    ）暴露至公网
  • 防火墙规则 — 仅对外开放9222端口（Discovery v5）和30303端口（P2P）；拦截所有其他入站流量
  • 以非root用户运行，并配置最小化的文件系统权限
  • 若需向远程客户端暴露RPC端点，请使用TLS终止（通过nginx/caddy配置反向代理）
  • 监控未授权访问 — 记录并告警异常RPC调用或连接量激增情况

Hardware Requirements

硬件要求

  • CPU: 8-Core minimum
  • RAM: 16 GB minimum
  • Storage: NVMe SSD, formula: 
    (2 × chain_size) + snapshot_size + 20% buffer
  • CPU：最低8核
  • 内存：最低16GB
  • 存储：NVMe固态硬盘，计算公式：
    (2 × 链数据大小) + 快照大小 + 20% 缓冲空间

Networking

网络配置

Required Ports:
  • Port 9222: Critical for Reth Discovery v5
  • Port 30303: P2P Discovery & RLPx
If these ports are blocked, the node will have difficulty finding peers and syncing.
必填端口：
  • 9222端口：对Reth Discovery v5至关重要
  • 30303端口：P2P发现与RLPx协议
若这些端口被封禁，节点将难以发现对等节点并完成同步。

Client Selection

客户端选择

Use Reth for Base nodes. Geth Archive Nodes are no longer supported.
Reth provides:
  • Better performance for high-throughput L2
  • Built-in archive node support
Base节点请使用Reth客户端。Geth归档节点已不再受支持。
Reth具备以下优势：
  • 针对高吞吐量L2网络性能更优
  • 原生支持归档节点

Syncing

同步设置

  • Initial sync takes days
  • Consumes significant RPC quota if using external providers
  • Use snapshots to accelerate (check Base docs for URLs)
  • 初始同步耗时数天
  • 若使用外部服务提供商，将消耗大量RPC配额
  • 可使用快照加速同步（请查看Base官方文档获取快照链接）

Sync Status

同步状态检查

Incomplete sync indicator: 
Error: nonce has already been used
when deploying.
Verify sync:
  • Compare latest block with explorer
  • Check peer connections
  • Monitor logs for progress
同步未完成标识：部署时出现
Error: nonce has already been used
错误。
验证同步状态的方法：
  • 对比节点最新区块与区块浏览器数据
  • 检查对等节点连接情况
  • 监控日志查看同步进度