Clone, build, prove, verify -- real commands, in order.
Diagram, invariants, source, tests -- the real AIR explained end to end.
The complete real instruction set and the forward-only jump rule.
The three real .zkasm programs -- branching, register state, arithmetic.
Every capability labeled IMPLEMENTED, ROADMAP, or RESEARCH.
Is this actually zero-knowledge? Plainly answered.
Every HTTP route -- exact request/response fields.
The real prove/verify MCP tools, and why they run on their own port.
IProofVerifier, AttestedVerifier, and the 8 real Foundry tests.
The real workflow that proves and verifies every example before a PR merges.
Every zkvm subcommand -- run, prove, verify, deploy, demo.
The proof is trustless. The on-chain payment is not.
The five real pieces a trustless verifier needs.
What recursive compression would take -- research scope, nothing built.
Loops, then addressable memory, then RV32I -- the real order.
20 real capabilities, searchable and filterable -- implemented, roadmap, research, or not planned.
Setup, the real PR checklist, and what this project won't take.
Not audited. What counts as a real finding, and how to disclose it.
What actually shipped in v0.1.0, and every real change since.
The one-page funding case -- what it is, and the four scoped asks.
None of these are built integrations. This is what "prove a program executed correctly" is useful for in general — not a product roadmap.
Would need a secret-witness AIR this project does not implement -- today’s design is public-input only, on purpose.
The general shape rollups use validity proofs for -- not integrated with any rollup stack here.
Proving a model ran correctly is the same problem shape as proving any program did -- no ML-specific tooling exists in this repo.
Proving an arithmetic pipeline executed as claimed, without a trading-specific AIR.
Proving a data-processing pipeline ran as claimed -- the same accumulator/register model, applied to a different program.
A verifiable record that a specific computation happened, for contexts that need it checkable rather than just logged.
Open source and MIT licensed. Bug reports, .zkasm programs that break something, and small honestly-scoped PRs are welcome.
A real STARK-verifiable virtual machine, with every gap named in the open.