How do I install the Running A Base Node skill?

Run npx skillmds@latest add jiayaoqijia/running-a-base-node in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Running A Base Node safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Running A Base Node?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Running A Base Node free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Running A Base Node?

jiayaoqijia (@jiayaoqijia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Running A Base Node by jiayaoqijia — Agent Skill

Name: Running A Base Node
Author: jiayaoqijia

Running A Base Node

Runs a Base node for production environments. Covers hardware requirements, Reth client setup, networking, and sync troubleshooting. Use when setting up self-hosted RPC infrastructure or running archive nodes. Covers phrases like "run a Base node", "set up Base RPC", "Base node hardware requirements", "Reth Base setup", "sync Base node", "self-host Base", or "run my own node".

jiayaoqijia Updated Sep 17, 2026

File contents

Running a Base Node

For production apps requiring reliable, unlimited RPC access.

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

Hardware Requirements

CPU: 8-Core minimum
RAM: 16 GB minimum
Storage: NVMe SSD, formula: (2 × chain_size) + snapshot_size + 20% buffer

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.

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

Syncing

Initial sync takes days
Consumes significant RPC quota if using external providers
Use snapshots to accelerate (check Base docs for URLs)

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

---name: running-a-base-nodedescription: Runs a Base node for production environments. Covers hardware requirements, Reth client setup, networking, and sync troubleshooting. Use when setting up self-hosted RPC infrastructure or running archive nodes. Covers phrases like "run a Base node", "set up Base RPC", "Base node hardware requirements", "Reth Base setup", "sync Base node", "self-host Base", or "run my own node".---# Running a Base NodeFor production apps requiring reliable, unlimited RPC access.## 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## Hardware Requirements- **CPU**: 8-Core minimum- **RAM**: 16 GB minimum- **Storage**: NVMe SSD, formula: `(2 × chain_size) + snapshot_size + 20% buffer`## Networking**Required Ports:**- **Port 9222**: Critical for Reth Discovery v5- **Port 30303**: P2P Discovery & RLPxIf these ports are blocked, the node will have difficulty finding peers and syncing.## Client SelectionUse **Reth** for Base nodes. Geth Archive Nodes are no longer supported.Reth provides:- Better performance for high-throughput L2- Built-in archive node support## Syncing- Initial sync takes **days**- Consumes significant RPC quota if using external providers- Use snapshots to accelerate (check Base docs for URLs)## 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

Frequently asked questions