The goal is not to reproduce an existing implementation.
Most networks that share an architecture begin as a fork: take working source code, change it, deploy it. ONX begins one step earlier, with the published design. Each requirement is restated as an ONX specification, every ambiguity or gap gets a recorded decision, and only then is code written, followed by tests that try to prove it wrong.
Existing implementationfork
- Source codeBehaviour starts from what the code already does.
- ModificationChanges are made against that behaviour.
- Deployment
ONXindependent
- Reference specificationThe original white paper, kept unmodified.WHITEPAPER.md
- Protocol requirement15 ONX specifications, separating what the paper requires from what ONX interprets.docs/specification/
- Engineering decisionGaps and ambiguities are written down: 20 accepted decision records.docs/decisions/
- ImplementationA Rust workspace; protocol, node and tooling crates kept apart.crates/
- TestGolden vectors, cross-process checks, crash and corruption probes in CI.ci.yml
Existing implementations may be studied for research and interoperability. ONX does not treat any of them as its specification.