07 / BUILD WITH US
A focused change.
A stronger collective.
Protocol engineering, testing, operations, documentation, and reproducible bug reports all move the project forward.
01. Choose a concrete problem
Read the client’s current status, find a relevant issue, and describe the behavior you want to change. For an existing bug, include the smallest useful reproduction and the expected result.
02. Keep the evidence with the change
Include build identity, a bounded reproduction or test, and the behavior before and after your change. For consensus and state work, retain the reference pin and replay range.
- Fix the underlying behavior and add a regression check when appropriate.
- Explain compatibility, storage, or configuration changes.
- Use the repository’s pinned toolchain and required checks.
- Attach benchmark methodology when claiming a performance gain.
03. Send a reviewable pull request
Keep a change focused enough to review. Link its issue, describe the user-visible effect, and explain how you verified it. Repository maintainers decide acceptance and release readiness.
More ways to help
Improve an operator guide, verify a build recipe, reproduce a replay result, or clarify a compatibility limit. You do not need to change consensus code to make a useful contribution.
Reviewed 14 November 2026. Repository guides hold the current implementation details.
KEEP THE CURIOSITY GOING