Skip to main content
Run Your Own Node

ETC Node Clients

Run your own Ethereum Classic node for maximum decentralization and independence. Choose from multiple client implementations in Go, Java, and Scala.

Why Run Your Own Node?

Full Verification

Independently verify every transaction and block without trusting third parties.

Privacy

Your transactions and queries stay private - no external RPC provider sees your activity.

Network Support

Help strengthen the ETC network by adding another independent node.

Reliable Access

Never depend on external services for blockchain access - your node is always available.

Available Clients

Core-Geth

RecommendedGo

A go-ethereum derivative maintained for Ethereum Classic, released from the ethereumclassic community organization. The v1.12.x line went 21 months without security maintenance; Core-Geth v1.13.0, prepared by White B0x, fixes six CVEs, one of them exploited against ETC mainnet bootnodes in March 2026, and moves the client to Go 1.26.

Features

  • Snap and full sync, with archive mode
  • JSON-RPC, WebSocket and GraphQL APIs
  • EVM tracing and debugging
  • Built-in Etchash mining support
  • MESS (ECBP-1100) chain-selection defense, on by default
  • Build attestation on every release file
WindowsmacOSLinuxDocker

Quick Start

Install

docker pull ghcr.io/ethereumclassic/core-geth:latest

Configuration

Run with --classic, or no network flag, for Ethereum Classic mainnet, and --mordor for the Mordor testnet.

Fukuii

ETC-nativeEnterpriseScala

Ethereum Classic's first native client — an EVM execution client in Scala 3 LTS on Pekko Typed Actors, running on the JVM. One binary runs several networks at once in one JVM process, each isolated with its own state, its own metrics registry, and its own configuration; a further network is configuration, not a new client.

Features

  • Several networks at once in one JVM process, each fully isolated
  • Consensus selected per deployment: native Proof-of-Work for ETC mainnet and Mordor
  • Proof-of-Stake with a built-in consensus layer, or an external client over the Engine API V1–V4
  • SNAP, fast, and regular sync; JSON-RPC, GraphQL, and an MCP server exposing node state to AI agents
  • JVM-native end to end for institutions already on the JVM: JFR, async-profiler, JMX and heap dumps work as on any JVM process, with no foreign-language bridge
  • Prometheus metrics, Grafana dashboards, and liveness and readiness endpoints in the binary
  • Apache 2.0, with Cosign-signed build provenance and a CycloneDX SBOM on release artifacts
WindowsmacOSLinuxDocker

Quick Start

Configuration

Select the network with --network=etc for ETC mainnet or --network=mordor for the ETC testnet. Requires a current JDK LTS (25); the Docker image bundles one.

Network Configuration

Ethereum Classic

Chain ID61
SymbolETC
Core-Geth Flag--classic
Fukuii Flagnetwork=etc

Mordor Testnet

Chain ID63
SymbolMETC
Core-Geth Flag--mordor
Fukuii Flagnetwork=mordor

Hardware Requirements

Minimum (Full Node)

  • CPU2+ cores
  • RAM4 GB
  • Storage500 GB SSD
  • Network10 Mbps+

Recommended (Archive Node)

  • CPU4+ cores
  • RAM8+ GB
  • Storage2+ TB NVMe SSD
  • Network25+ Mbps

Execution Client Plugins

Post-Olympia Roadmap

Upstream Ethereum clients separated the consensus engine from the execution engine to support Proof-of-Stake. ETC plugins leverage this separation to add Ethereum Classic chain support to the execution layer only. No mining, no PoW consensus. Products and infrastructure built on Go-Ethereum, Nethermind, Erigon, Besu, or Reth can add ETC support via a lightweight plugin without running a separate PoW consensus client. Core-Geth carries the Proof-of-Work consensus and mining path for the ecosystem.

Ready to Run a Node?

Core-Geth is the recommended client for Ethereum Classic, released and maintained in the ethereumclassic organization. For upgrade-specific guidance, see the client upgrade guides.