Ethereum Classic Full Node: Complete Guide

What is an Ethereum Classic full node?

A Ethereum Classic 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 Ethereum Classic Full Node RPC over HTTPS so applications can read ETC balances, simulate contracts, and submit signed transactions without self-hosting Erigon/Geth and companion services.

Why Ethereum Classic full nodes matter

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

Ethereum Classic in the RpcNode catalog: Ethereum Classic (geth classic / core-geth).

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

When to run your own Ethereum Classic node

Self-hosting a Ethereum Classic 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 Ethereum Classic 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 Ethereum Classic before dedicating hardware — start on RpcNode, or self-host with Toolkit in a few clicks

Ethereum Classic full node server requirements

Ethereum Classic full node server requirements follow typical EVM patterns: Geth, Reth, Erigon, or a chain-specific geth fork for execution. If the chain is post-merge Ethereum-like L1, budget a consensus client too.

Size minimum specs for a pruned/full node first. Archive hardware requirements are a different purchase — often 10+ TB NVMe.

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

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

• CPU: 4–8+ cores for snappy eth_call under load
• RAM: 16–32 GB common; 64 GB+ for heavier clients
• Disk: NVMe 1–2+ TB for full; archive is multi-TB
• Bandwidth: 1 Gbps recommended for peers + RPC
• OS: Ubuntu 22.04/24.04 LTS
• Full vs archive: RpcNode positions as Full Node RPC, not archive

Install an Ethereum Classic full node in a few clicks

Ethereum Classic is in the free RpcNode Toolkit catalog (mainnet, mordor). 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 Ethereum Classic 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 toolkit.rpcnode.dev).
2. Add server: paste IP and AGENT_API_TOKEN, Check connection, then add.
3. Add node: network Ethereum Classic → environment (mainnet, mordor) → that server.
4. Open the node page — install, sync %, logs, restart, client update, fullnode RPC.

Self-host Ethereum Classic with Toolkit

How to run an Ethereum Classic full node

How to run an Ethereum Classic full node (EVM family): install the chain’s supported execution client (Geth/Reth/Erigon or a fork / L2 stack), configure a non-archive full profile, and expose JSON-RPC only through an allowlisted proxy.

If Ethereum Classic is a post-merge L1 style network, run a consensus client beside execution with a shared JWT.

If you mainly need HTTPS Ethereum Classic 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 NVMe sized for full (non-archive) growth. 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. Install the official or widely supported Ethereum Classic client(s) from upstream releases — pin versions and read release notes before upgrades.
5. Configure full-node sync/pruning defaults suitable for tip RPC. Do not enable archive unless you need deep historical state.
6. Bind HTTP JSON-RPC to localhost (commonly `8545`); keep Engine/auth APIs local.
7. Create systemd services with automatic restart and log rotation.
8. Open only the documented P2P ports publicly; whitelist RPC.
9. Verify with `eth_syncing` / `eth_blockNumber` (or the chain’s equivalent) against a public explorer tip.

• Target: full node RPC, not validator keys (unless you intentionally stake)
• Confirm exact flags in official docs — chain forks differ

Using Ethereum Classic RPC without self-hosting

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

Catalog environments for Ethereum Classic: Mainnet, Mordor 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.

Ethereum Classic integration checklist

Use this short checklist when wiring Ethereum Classic into production.

• Pick the correct environment (Mainnet, Mordor 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 Ethereum Classic server requirements (CPU/RAM/disk) before self-hosting
• Or install with RpcNode Toolkit in a few clicks — free self-hosted panel

Ethereum Classic full node FAQ