Fukuii
Ethereum Classic's first native client, built for this network from the start rather than adapted from an existing Ethereum client.
- Role
- Primary client for the Olympia era
- Language
- Scala 3 LTS on the JVM
- License
- Apache 2.0
- Maintainer
- The Fukuii Authors
What Fukuii is
Fukuii is an execution client. It holds a copy of the chain, checks every block against the rules, keeps the account state that results, and answers questions about it over a public interface. That is the job every node on the network is there to do.
What makes it unusual for Ethereum Classic is where it came from. Every client this network has run until now began life as an Ethereum client and had Ethereum Classic support added to it afterward. Fukuii was written for Ethereum Classic from the start, which is why it is described as the first client native to this network.
It is written in Scala 3 and runs on the Java Virtual Machine. That choice is not incidental: the language's type system makes a class of consensus mistake impossible to write down, so it is caught when the code is compiled rather than when a block is processed.
One binary, several networks
Fukuii can run more than one network at the same time, inside one process. Each network keeps its own state, its own metrics and its own configuration, and each is supervised on its own, so a failure in one of them does not take the others down with it.
The practical result is that adding a network is configuration rather than a new client to install, learn and audit. For an operator that means fewer machines to run and one supply chain to check.
- Ethereum Classic
- chain 61, Proof-of-Work, the network Olympia upgrades
- Mordor
- chain 63, the Ethereum Classic test network, which activates first
- Ethereum mainnet
- chain 1, Proof-of-Stake, from the same binary
- Sepolia
- chain 11155111, the Ethereum test network
How it reaches agreement
Consensus is selected per deployment and sits behind a single interface, so the rest of the client does not change when that choice changes.
On Ethereum Classic and Mordor that is native Proof-of-Work. Fukuii implements ETChash and the ECIP-1099 epoch schedule, and it serves the work interface that mining software connects to, so it can be the node behind a mining operation rather than only a node beside one.
On Proof-of-Stake networks it can run a consensus layer inside the same process, which makes a node one thing to deploy instead of two. That is an option rather than a requirement: the Engine API is implemented either way, so an external consensus client can drive Fukuii instead.
What it exposes to the outside
The interfaces an operator actually integrates against are in the binary rather than in a sidecar.
- JSON-RPC and GraphQL
- the standard query surface, plus a typed alternative to it
- SNAP, full and archive
- state sync modes, so a node can be brought up fast or kept complete
- Prometheus and Grafana
- metrics, dashboards, and liveness and readiness endpoints
- An MCP server
- node state, sync progress, peer counts and block data offered as structured tools to any Model Context Protocol agent
Who maintains it, and how
Fukuii is maintained by The Fukuii Authors, an organization whose members are Chippr Robotics LLC and White B0x Inc. The authors maintain the repository, review what lands in it, and publish the releases. There is no foundation or steering body sitting between the code and the people who are accountable for what it does.
Development happens in the open on GitHub. Changes arrive as pull requests and ship in tagged releases, and each release carries a build signature and a software bill of materials, so a running binary can be traced back to the commit and the build that produced it. The license is Apache 2.0, which permits commercial use, modification and redistribution, and carries a patent grant from the contributors.
The authors' work extends past the client itself: they include a credited contributor to the EEA Enterprise Ethereum Client Specification, the document that sets out implementation requirements for Enterprise Ethereum clients. That is a contribution to the specification, and it is not a conformance claim about Fukuii itself.
Report a vulnerability privatelyWhat running it needs
Fukuii is distributed for Windows, macOS and Linux, and as a container image. The container bundles a Java runtime, so it is the shortest path from nothing to a running node.
Instructions for upgrading an existing node through the Olympia hard fork, including which release to take and when, live on the upgrade page.
- docker pull ghcr.io/fukuii-project/fukuii-cli:latest
- the published container image
- --network=etc
- run Ethereum Classic mainnet
- --network=mordor
- run the Mordor test network
- Current JDK LTS (25)
- required for the platform distributions; the container image bundles one