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
Fukuii
PrimaryEnterpriseETC-nativeScalaEthereum 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
Quick Start
Install
docker pull ghcr.io/fukuii-project/fukuii-cli:latestConfiguration
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.
Core-Geth
MaintainedGoA go-ethereum derivative maintained for Ethereum Classic, carried through the Olympia upgrade for network continuity. etclabscore/core-geth v1.12.x was unmaintained June 2024–March 2026 (21 months), accumulating six unpatched CVEs that were actively exploited against ETC mainnet bootnodes. All CVEs patched by White B0x at ethereumclassic/core-geth, pending release as v1.13.0.
Features
- Full and light sync modes
- JSON-RPC and WebSocket APIs
- EVM tracing and debugging
- Built-in mining support
- MEV-free transaction ordering
Quick Start
Install
docker pull ghcr.io/ethereumclassic/core-geth:latestConfiguration
Use --classic flag for ETC mainnet, --mordor for testnet
Network Configuration
Ethereum Classic
61ETC--classicnetwork=etcMordor Testnet
63METC--mordornetwork=mordorHardware 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. Fukuii remains the primary and long-term supported Proof-of-Work client for the mining ecosystem.
A plugin that adds Ethereum Classic chain support to the Besu codebase, an enterprise-grade Java client.
A plugin that adds Ethereum Classic chain support to the Erigon codebase, a storage-optimized archival client.
A plugin that adds Ethereum Classic chain support to the Ethrex codebase, a minimalist Rust client.
A plugin that adds Ethereum Classic chain support to the Go-Ethereum codebase, the most widely deployed EVM client.
A plugin that adds Ethereum Classic chain support to the Nethermind codebase, a high-performance .NET client.
A plugin that adds Ethereum Classic chain support to the Reth codebase, a modular, performance-focused Rust client.
Ready to Run a Node?
Fukuii is the recommended client for Ethereum Classic — native PoW consensus for ETC and Mordor, Engine API V1–V4 for post-Merge Ethereum. For upgrade-specific guidance, see the client upgrade guides.