Skip to main content

Network Software

Client Implementations

Core-Geth is the recommended client for Ethereum Classic. Fukuii is an alternative to try beside it, and ETC plugins for upstream clients are planned.

163.5 TH/s

Live

Network Hashrate

Go

Core-Geth

Recommended

The recommended client for Ethereum Classic: a go-ethereum downstream released and maintained in the ethereumclassic GitHub organization. Run the v1.13 line, which closes all six client CVEs the audits found in the v1.12 client code and is built with a supported Go toolchain. Take the latest release from ethereumclassic/core-geth, where every release file carries a checksum and a build attestation.

Every v1.12 release ships known-vulnerable code, and one of those flaws was exploited against the Core-Geth v1.12 bootnodes in March 2026, so every node still on a v1.12 release should move to the v1.13 line. The migration guide on coregeth.com takes a node on v1.12.17 or later through the move one step at a time on each platform: its chain data carries over, and its P2P node key is rotated, which is required because CVE-2026-26315 leaks bits of that key. If a step goes wrong, the guide’s rollback puts the v1.12 binary back only while the cause is found, and its last step deletes that binary once the node is stable. A v1.12 node that cannot move yet can read the peer discovery lists and bootnodes the v1.13 line ships, a small step that closes none of the flaws the audits found in the v1.12 line.

Neither route works for a node on a release older than v1.12.17. Those releases do not schedule the Spiral upgrade, so such a node left the Ethereum Classic network at block 19,250,000, on February 5, 2024, and has followed an obsolete chain since. It cannot move in place, and resyncing is its only way back: remove the chain database, rename the P2P node key and install a v1.13 release, which syncs the chain again. The migration guide’s Check what your node runs gives those steps.

Sc

Fukuii

AlternativeAlpha

An EVM-compliant execution client in Scala 3 with pluggable consensus: native Proof-of-Work for Ethereum Classic and Mordor, and the Engine API for post-Merge Ethereum networks, paired with a consensus client. It continues IOHK's Mantis client and is maintained by Chippr Robotics LLC under Apache 2.0. Its maintainers mark it alpha, not yet recommended for production-critical workloads, so it is an alternative to try beside Core-Geth, the recommended client.

Core-Geth is one of the public goods maintained in the ethereumclassic organization, alongside the network’s bootnodes and peer discovery lists. What is maintained, and where →

ETC Plugins

Planned compatibility layers for Besu, Erigon, Ethrex, Go-Ethereum, Nethermind and Reth. A plugin is not a client implementation. It adds Ethereum Classic support to a client another project maintains, so that codebase and the decisions about it stay with that project, outside Ethereum Classic's control. A plugin is no substitute for Fukuii, an independent client, or for Core-Geth, a full implementation downstream of go-ethereum.

Ja

Besu

PluginPlanned

A plugin that would add ETC support to the Besu codebase.

Go

Erigon

PluginPlanned

A plugin that would add ETC support to the Erigon codebase.

Ru

Ethrex

PluginPlanned

A plugin that would add ETC support to the Ethrex codebase.

Go

Go-Ethereum

PluginPlanned

A plugin that would add ETC support to the Go-Ethereum codebase.

C#

Nethermind

PluginPlanned

A plugin that would add ETC support to the Nethermind codebase.

Ru

Reth

PluginPlanned

A plugin that would add ETC support to the Reth codebase.