The root workspace (Cargo.toml) has these members:
| path | crate | what it is |
|---|---|---|
sdk/cli |
pico-cli |
the cargo pico subcommand: install, build, execute, prove, aot, new. It has no verify; prove --evm runs gnark (gnark/) for the Groth16 step |
sdk/prover |
pico-prover |
the host prover: Prover, ProverBuilder, Stdin, Phase, Proof, ProofArtifact, EvmBundle. Its crate documentation is the API guide |
sdk/sdk |
pico-sdk |
the guest SDK: entrypoint!, io (read_as, read_vec, commit, commit_bytes), syscalls (riscv_ecalls), Poseidon2 hashing |
sdk/patch-libs |
pico-patch-libs |
syscall wrappers used by the patched crates (sha2, keccak, curves, BLS12-381, BN254, ...) |
vm |
pico-vm |
the zkVM: compiler, emulator, chips, and the machines of every phase (see below) |
mle-core |
pico-mle-core |
the MLE/WHIR STARK backend core (KoalaBear only): config, transcript, symbolic AIR, interactions, PCS / sumcheck / LogUp / WHIR prover and verifier, reference device, StarkEngine, and the soundness calculator |
mle-cpu |
pico-mle-cpu |
the row-major CPU device backend (CpuBackend, CpuDevice) for pico-mle-core |
aot-codegen |
pico-aot-codegen |
ahead-of-time compilation of a guest's RISC-V code to Rust crates (cargo pico aot, bin/generate_crates) |
aot-runtime |
pico-aot-runtime |
runtime types for running AOT-compiled guests |
derive |
pico-derive |
procedural macros (aligned_borrow_derive, from Valida) |
gnark/field-ffi |
field-ffi |
KoalaBear arithmetic exposed to the gnark circuit's hint functions |
perf |
pico-perf |
shared benchmark code, with AOT glue behind its aot feature |
aot-generated (pico-aot-dispatch) is not a member: it is a bootstrap stub that cargo pico aot
or generate_crates replaces with code generated from a guest's ELF.
compiler: compiles RISC-V ELFs and recursion programs into the programs the emulators run.compiler/test_elfholds test ELFs.emulator: the RISC-V and recursion emulators, which turn a program and its input into the records the machines prove.chips: the AIRs (chips, gadgets and precompiles) the machines are built from.instances: the RISC-V and recursion chip-type lists, and the IR and circuit builder that recursion programs are written in.machine: machine-generic building blocks (chips, lookups, witnesses, emulation reports).mle: the MLE machines of every phase (riscv,convert,combine,embed,wrap), the recursion compiler for them, shape selection, and the verifying-key whitelist (mle/machine/vk_map.rs, shipped artifact inmle/shape_vk_bins/).configs: field and STARK configurations.primitives: constants and types shared across the crate.proverchain: the snapshot-based RISC-V emulation pipeline.iter,thread: parallel-iteration and channel helpers.examples: developer entry points.test_mle_e2e.rsruns the chain and can stop at a given phase (--step);mle_build_vk_map.rsbuilds the whitelist;mle_soundness_manifest.rsregenerates the soundness manifest.examples/patch-testing: a separate workspace with one guest/prover pair per patched crate underpatches/.tests: integration tests, including the RISC-V constraint parity test.
examples: a separate workspace with the fibonacci, tendermint and aggregator examples;examples/README.mdwalks through them from the CLI and from Rust.perf/aot: a separate workspace of AOT emulation harnesses and record-parity checks against the interpreter.perf/bench_apps: a separate workspace with the benchmark guests (fibonacci, reth, tendermint).perf/bench_data: the ELFs and block inputs the benchmarks and tests run.gnark: the Go Groth16 layer for the wrap-phase artifacts (pico-gnark), and its Dockerfile; seegnark/README.md.contracts: the Solidity verifier (PicoVerifier,IPicoVerifier) with Foundry tests and a Groth16 verifier from a test setup; seecontracts/README.md.audits: third-party security review reports.docs: project documentation..github/workflows/rust.yml: CI, run on pull requests tomainandrelease/v*and on pushes tomain.