The name
Chordodes fukuii is a nematomorph, a horsehair worm. It infects a mantis, takes over its nervous system, and drives the host toward water. It emerges as something else entirely, and leaves the mantis behind.
The name is the lifecycle.
Maintainers
Fukuii is maintained by The Fukuii Authors, including Chippr Robotics LLC and White B0x Inc. The authors maintain the repository, review what lands in it, and publish the releases.
Standards
Fukuii's authors include a credited contributor to the EEA Enterprise Ethereum Client Specification, the document that sets out implementation requirements for Enterprise Ethereum clients. It covers the permissioning, privacy and operational interfaces a private deployment expects on top of the base protocol.
Governance
Development happens in the open on GitHub: changes arrive as pull requests, are reviewed there, and ship in signed releases. There is no separate foundation or steering body between the maintainers and the code. Design discussion that predates a pull request happens in issues and in discussions, in public.
Releases
Releases are tagged in the repository and published as container images alongside the JVM artifacts. Each one 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.
License
Apache 2.0. The copyright holders are named in the NOTICE file alongside the license in the repository. The license permits commercial use, modification and redistribution, and carries an express patent grant from the contributors.
Security
Report a suspected vulnerability through GitHub's private advisory form rather than the public issue tracker, and hold the details until the maintainers have investigated and there is a fix to publish.
Report a vulnerability →Repositories
The client is one repository of several. The others hold what is tested against it and what is built on top of it, kept separate so each can move at its own pace.
- fukuii-cli →
The client itself: the node, its build, and the workflow that publishes each release.
- fukuii-tests →
Test fixtures and execution vectors, organized by network, plus the client configurations and simulators used to run the shared Ethereum test suites. The upstream suites are tracked as pinned submodules rather than copied in.
- fukuii-gui →
The graphical interface for running and watching a node, for operators who would rather not work through a terminal.
Contributing
Fukuii is open source and takes outside contributions. Fork the repository, make the change, and open a pull request against the default branch. Small fixes are as welcome as large ones, and a typo in the documentation is worth a pull request.
Changes that alter consensus behavior, the wire protocol, or the supply-chain workflow get more review than changes that do not, so raising an issue before starting on one will save time. The same is true of a change that adds a dependency, which is reviewed on its own terms rather than as part of whatever needed it.
Building the client from source needs a JDK and nothing else; the build fetches what it depends on. If you are looking for somewhere to start, the test corpus takes fixtures for cases it does not cover, and those are self-contained.
- Source →
The client, its build, and its release workflow.
- Issues →
Bug reports and feature requests.
- Discussions →
Questions, ideas, and operator help.