Help build a common language for trustworthy data.

Makoto is developed in public. The protocol, JSON Schemas, reference implementation, verifier, test vectors, runnable demo, and website are available for anyone to inspect, run, challenge, and improve.

No membership required. Start with a use case, a failing example, a schema question, a documentation correction, or a tested patch.

Choose a contribution path

1. Reproduce the proofClone the core repository, run the deterministic producer-to-receiver demo, and report unclear steps or nondeterministic results. Open the walkthrough
2. Bring a real handoffDescribe data moving between actual systems and teams. Name the source claim, transformation evidence, private rules, signer policy, and recipient checks the protocol must carry. Open a core issue
3. Add a denial caseTurn an ambiguity, attack, or interoperability edge case into a deterministic fixture and an expected diagnostic. Review open issues
4. Review schemas and profilesChallenge portability, private-profile resolution, bounded evaluation, and how organizational constraints compose with the small core. Inspect hosted schemas
5. Improve docs and examplesMake a concept clearer, contribute a real-world story, or repair the site without making unsupported release or package claims. Open a website issue
6. Send a tested patchKeep protocol and site changes in the right repository and include the evidence needed to review the change. Read CONTRIBUTING.md

Two public repositories, one project

What “open” means here