Contributing to Zeko Development

Zeko development spans protocol infrastructure, public packages, examples, and documentation. The best place to start depends on what you want to change.

Where To Contribute

• Zeko GitHub organization - public repositories for Zeko protocol code, examples, tools, and package mirrors.
• Zeko protocol repository - sequencer, prover, data availability, and protocol infrastructure work.
• Examples & Boilerplates - starting points for application examples and integration demos.
• Community & Support - Discord and social channels for questions before opening an issue.

Contribution Checklist

1. Reproduce the behavior or define the documentation gap clearly.
2. Open an issue or draft pull request when the change affects protocol behavior, public APIs, or deployment guidance.
3. Keep examples and docs aligned with the currently documented network, bridge, and faucet tools.
4. Include validation notes in the pull request so reviewers can see how the change was checked.

For application code, prefer small pull requests with a focused scope. For documentation, update the page that users are most likely to read first and link to deeper references instead of duplicating long explanations across sections.