Prove · ModulePlanned (Phase 9)
Private verify
A zero-knowledge proof lets a closed-source job be verified without revealing the code.
The problem it prevents
Closed-source teams who cannot publish code but need a verifiable audit.
Who it is for
Teams with proprietary code or contracts under NDA.
How it works
- 01Run the job on a conforming node.
- 02A zk proof of a single random tile is produced (under 60 KB).
- 03Anyone verifies the proof without seeing the code.
What you get
- A proof file and a public verification result.
Limits and caveats
- Phase 9. Depends on the deterministic node (Phase 4).
Questions
What is verified?
That the job ran as stated on committed inputs, without revealing them.
When?
Last on the roadmap.
Does it replace the public log?
No; the proof is logged like any receipt.
Who sees the code?
Only the node that ran the job.