Contribute
This is a small, open project that needs people more than it needs a waitlist. You do not have to be a cryptographer to help. You do have to be willing to read code and tell us where it is wrong.
Start in fifteen minutes
The reference implementation is bassrehab/oconsent. Clone it, install it, and run the CLI against a local chain. If you get stuck, that is itself a useful bug report, because it means the setup docs are not good enough yet.
git clone https://github.com/bassrehab/oconsent.git
cd oconsent
pip install -e .
oconsent --help
Where help matters most
- Break the model. Read how it works and the paper, then try to find the case where the consent record proves nothing. Adversarial reading is the most valuable thing you can do here.
- The proofs. The zero-knowledge step is a placeholder today. If you know your way around ZK-SNARKs, this is the headline open problem.
- Beyond Ethereum. The sidechain module is an empty stub and the Bitcoin path is unfinished. Pick a chain and make it real.
- Licensing. The contracts are MIT and the project-wide license is unsettled. If you have done open-source licensing properly before, help us close this.
- Docs. The reference docs need a rebuild, and the explanations on this site can always be sharper and more honest.
Good first issues
If you are new, the friendliest places to start are the CLI ergonomics, the test coverage, and the setup instructions. Small, real, and they make the next person’s life easier.
How to reach us
Open an issue or a pull request on GitHub. If you would rather talk first, email dev@oconsent.io. Starring the repository genuinely helps, because right now visibility is the difference between this getting contributors and not.
Follow along
No newsletter machine, no tracking. Drop your email and you will get the occasional honest note when something real ships. One-click unsubscribe, always.