The four pages below walk through the proof from the outside in: what stages a developer runs, what's inside versus outside the proof, what's in the prover, and how the work scales when no single proof can hold it.
Start here
The pipeline
The six developer-facing stages — compile, setup, execute, prove, optionally wrap, verify. What each does and what command runs it.
Read more →Concept
Trust boundary
What runs inside the zkVM (the guest), what runs outside (the host), and what flows between them — inputs, hints, public outputs.
Read more →Concept
Specialized chips
What's inside the prover at a high level — the Main chip, the Memory chip, the precompile chips, and the buses they use to talk to each other.
Read more →Concept
Segments
How a long program gets proved when no single proof can hold it — per-chip trace splitting plus a recursive aggregation tree.
Read more →When you want to go one notch deeper — the contract programs run against, how RISC-V code becomes ZisK code, and the hard limits the current setup imposes — head to ZisK internals.