RpcNode Toolkit

Home/Networks/Ethereum Classic

etc

Ethereum Classic full node

Self-host an Ethereum Classic archive node with Core-Geth — mainnet or Mordor — managed from Toolkit.

Install ToolkitOfficial docs

Client

Core-Geth (archive)

RPC

Ethereum JSON-RPC (eth_* )

History

Archive mode. Tip-only is not Synced.

ETC on RpcNode is Core-Geth in archive mode so historical eth_call works. That is a different product from a pruned geth default.

Mordor is the public test environment. The panel uses eth_syncing the same way as other EVM chains — no empty warming-up bar.

Environments

mainnetmordor

Install

  1. On Ubuntu 24.04 LTS:
    bash
    curl -fsSL "https://toolkit.rpcnode.dev/install/agent.sh" | sudo bash
    Supported and recommended: Ubuntu 24.04 LTS (amd64 or arm64). Other operating systems have not been tested.
  2. Panel → Add server (Agent URL + token) → Add node → Ethereum Classic → mainnet.
  3. Confirm ports, choose install options if this chain has them, install Core-Geth (archive), snapshot if required, start. Watch sync on the node page.

Operate from the panel

After the node is up you manage it in the same UI — Node Config (edit the live files and apply), client updates, restart, logs, public RPC. You do not need SSH to change conf. Install-time choices (snapshot flavor, history window, disk layout) are stored on that node.

FAQ

How do I run a Ethereum Classic full node?
Install the host agent, add the server, then Add node → Ethereum Classic. Toolkit provisions Core-Geth (archive).
Can I change the Ethereum Classic config later?
Yes. Node page → Node Config. Edit and apply; restart from the same page. A different snapshot or history flavor is an Install choice — changing it later usually means wipe and Add node again.
Pruned or light?
Archive mode. Tip-only is not Synced.
Catalog
/clients/etc/ · catalog.json

Other networks