Skip to content

docs(barretenberg): document Prover.toml fixture regen for proof-length changes#23014

Merged
ledwards2225 merged 1 commit into
merge-train/barretenbergfrom
lde/document-prover-toml-regen
May 7, 2026
Merged

docs(barretenberg): document Prover.toml fixture regen for proof-length changes#23014
ledwards2225 merged 1 commit into
merge-train/barretenbergfrom
lde/document-prover-toml-regen

Conversation

@ledwards2225
Copy link
Copy Markdown
Contributor

@ledwards2225 ledwards2225 commented May 7, 2026

Adds a "Prover.toml Fixtures" subsection to barretenberg/cpp/CLAUDE.md documenting the AZTEC_GENERATE_TEST_DATA=1 FAKE_PROOFS=1 yarn workspace @aztec/end-to-end test full.test regen step that proof-length changes (e.g. CHONK_PROOF_LENGTH bumps) require. Without it, nargo execute fails type-checking on every protocol circuit using ChonkProofData.

…th changes

The "Proof Size Constants" section listed the C++/Noir/TS constant updates
needed when proof lengths change but didn't mention that the committed
Prover.toml fixtures (which carry hardcoded proof arrays) also need
regenerating. Without the regen, `nargo execute --program-dir <crate>`
fails type-checking on every protocol circuit using ChonkProofData.

Adds a "Prover.toml Fixtures" subsection covering:
  - the symptom (Type Array length mismatch in nargo execute)
  - the regen command (AZTEC_GENERATE_TEST_DATA=1 FAKE_PROOFS=1 ... full.test)
  - the FAKE_PROOFS=1 flag that keeps the run to ~2 min
  - the supplementary orchestrator_single_checkpoint test for circuits
    not exercised by full.test.ts
  - how to verify (nargo execute should print "Circuit witness successfully solved")
@ledwards2225 ledwards2225 enabled auto-merge (squash) May 7, 2026 01:12
@ledwards2225 ledwards2225 merged commit 65cc326 into merge-train/barretenberg May 7, 2026
17 checks passed
@ledwards2225 ledwards2225 deleted the lde/document-prover-toml-regen branch May 7, 2026 03:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants