Base Full Node: Complete Guide

What is a Base full node?

A Base full node syncs an execution client (and, where applicable, the L1/L2 stack behind it), verifies blocks, and serves standard Ethereum JSON-RPC: eth_blockNumber, eth_getBalance, eth_call, eth_getLogs, and eth_sendRawTransaction.

RpcNode offers managed Base Full Node RPC over HTTPS so applications can read ETH balances, simulate contracts, and submit signed transactions without self-hosting Erigon/Geth and companion services.

Why Base full nodes matter

Every wallet balance, payment confirmation, and contract read ultimately depends on nodes that agree on Base state. Public endpoints rate-limit and flake; your product’s reliability tracks the quality of the full nodes behind your RPC URL.

Base in the RpcNode catalog: Base (Coinbase L2).

• Native asset: ETH
• Environments: Mainnet, Sepolia Testnet
• API family: EVM JSON-RPC
• Listed in the RpcNode network catalog

When to run your own Base node

Self-hosting a Base full node makes sense when you need custom indexing, ultra-low latency next to your app, or compliance constraints that forbid third-party RPC. For most product teams, managed Full Node RPC is faster to ship and cheaper to operate.

• Building wallets, payments, or address watchers that need reliable Base reads and writes
• Avoiding multi-terabyte disks, peer tuning, and 24/7 pager duty for chain upgrades
• Preferring HTTPS JSON-RPC with allowlists, keys, and usage metering
• Evaluating Base before dedicating hardware — start on RpcNode, or self-host with Toolkit in a few clicks

Base full node server requirements

Base full node server requirements cover a full (non-archive) OP Stack rollup node: op-geth + op-node. You also need a reliable Ethereum L1 execution + beacon endpoint (self-hosted or provider).

Hardware minimum specs below are for the L2 host only — L1 disk/CPU is separate if you run Ethereum yourself.

Looking up "Base server requirements", "Base hardware requirements", or "Base minimum specs"? Use the checklist below as the planning baseline for a self-hosted full node.

If you mainly need HTTPS Base RPC for wallets or backends, prefer RpcNode managed Full Node RPC instead of sizing and babysitting this hardware yourself.

• CPU: 4+ cores (8+ for archive L2)
• RAM: 16 GB+ (32 GB+ archive)
• Disk: plan 1 TB NVMe for full L2 (~500 GB+ growing); archive is multi-TB
• Bandwidth: 1 Gbps recommended; keep Engine API on localhost
• OS: Ubuntu 24.04 LTS
• Dependency: Ethereum L1 RPC + beacon HTTP for derivation

Install a Base full node in a few clicks

Base is in the free RpcNode Toolkit catalog (mainnet, sepolia). Skip the manual binary hunt: the self-hosted panel walks Add server → Add node → the node page.

On Linux (amd64/arm64) you install the host agent once, register the server, pick Base and an environment, then the node page handles ports, install, snapshot when the chain supports it, sync, logs, and the public RPC endpoint.

1. Install the host agent on the Linux server (curl one-liner from rpcnode.dev).
2. Add server: paste IP and AGENT_API_TOKEN, Check connection, then add.
3. Add node: network Base → environment (mainnet, sepolia) → that server.
4. Open the node page — install, sync %, logs, restart, client update, fullnode RPC.

Self-host Base with Toolkit

How to run a Base full node

How to run a Base full node: operate op-geth (L2 execution, `--gcmode full`) plus op-node for derivation from Ethereum L1. This is a full rollup node, not archive.

If you mainly need HTTPS Base RPC for wallets or backends, prefer RpcNode managed Full Node RPC instead of sizing and babysitting this hardware yourself.

1. Provision Ubuntu 24.04 LTS (or the OS your client documents) on bare metal or a dedicated VM. Create a system user such as `nodeop` — do not run the node as root.
2. Attach 1 TB NVMe under `/data/base` (plus L1 elsewhere). Mount it away from the root filesystem and give ownership to the operator user.
3. Apply OS hygiene: unattended-upgrades or a patch cadence, fail2ban/SSH keys, and raise file-descriptor limits if the client docs require it.
4. Obtain a reliable L1 execution RPC and beacon HTTP URL; store them in an env file (e.g. `/etc/base/env`).
5. Install `op-geth` and `op-node` binaries from Optimism/Base release channels; create JWT for Engine API.
6. Initialize op-geth once with Base genesis/rollup artifacts from the official Base node repository.
7. systemd: run op-geth with HTTP on `127.0.0.1:8545`, authrpc `8551`, P2P `30303`, non-archive gcmode.
8. systemd: run op-node pointed at L1 RPC/beacon + local Engine JWT; open op-node P2P `9003` if required.
9. Whitelist only the JSON-RPC port (often Nginx → `8545`). Keep Engine API local.
10. Verify with `eth_syncing` / `eth_blockNumber` on L2 and confirm op-node is deriving near tip.

• Stack: op-geth + op-node; dependency on Ethereum L1
• Ports: 30303 + 9003 P2P; 8545 RPC whitelist; 8551 localhost

Using Base RPC without self-hosting

RpcNode exposes managed EVM JSON-RPC for Base. Create an endpoint in the cabinet, restrict IPs if needed, and call the same methods your stack already uses.

Catalog environments for Base: Mainnet, Sepolia Testnet. Create an endpoint in the RpcNode cabinet for the environment you need, or use this guide to plan a self-hosted deployment.

Typical methods teams start with: eth_blockNumber, eth_getBalance, eth_call, eth_getLogs, eth_sendRawTransaction.

Self-hosting vs managed Full Node RPC

Self-hosting gives maximum control and can reduce per-request cost at huge scale, but you own upgrades, peers, disk growth, and incident response. RpcNode Toolkit cuts the install to a few clicks (agent → Add server → Add node → node page) while you still run the hardware.

Managed RpcNode Full Node RPC trades that ops burden for a stable HTTPS endpoint, usage visibility, and the same method surface your SDK already speaks. If you are comparing providers, also see RpcNode’s comparison page.

Base integration checklist

Use this short checklist when wiring Base into production.

• Pick the correct environment (Mainnet, Sepolia Testnet) — never mix testnet keys with mainnet funds
• Store RPC URLs and keys in secrets management; rotate on staff changes
• Add IP allowlisting for server-side backends
• Alert on tip lag / getHealth (or equivalent) failures
• Load-test eth_getLogs / getProgramAccounts-style heavy calls before launch
• Decide full vs archive needs early — RpcNode is Full Node oriented
• Confirm Base server requirements (CPU/RAM/disk) before self-hosting
• Or install with RpcNode Toolkit in a few clicks — free self-hosted panel

Base full node FAQ