en un clic
chonk-inputs
// Manage pinned Chonk IVC inputs and the Chonk/rollup UltraHonk proving checks. Use when updating, testing, benchmarking, or reviewing the CI flow for Chonk input refreshes.
// Manage pinned Chonk IVC inputs and the Chonk/rollup UltraHonk proving checks. Use when updating, testing, benchmarking, or reviewing the CI flow for Chonk input refreshes.
Run realistic Chonk (client IVC) benchmarks using pinned protocol inputs. Covers native and WASM proving, per-circuit breakdowns, BB_BENCH instrumentation, and profiling code augmentation. Use when asked to benchmark, profile, or measure Chonk proving performance.
Run the Chonk (client-IVC) prover on the remote EC2 and collect Perfetto-compatible JSON traces. Supports both native and WASM runtimes. Generates a one-click Perfetto UI link for visual analysis. Use when asked to profile, trace, or visualize Chonk proving performance.
Run benchmarks on the dedicated remote EC2 benchmarking machine for noise-free, single-run results. Handles env var validation, lock management, binary transfer, and result collection. Use with /benchmark-chonk or any BB benchmark target.
Analyze source-file changes referenced by documentation, update affected docs when needed, and report documentation reference updates for a PR.
Build and update the developer documentation site for a new release
Reference for merge-train automation internals -- workflows, scripts, CI integration, and configuration. Use when modifying or debugging merge-train infrastructure.
| name | chonk-inputs |
| description | Manage pinned Chonk IVC inputs and the Chonk/rollup UltraHonk proving checks. Use when updating, testing, benchmarking, or reviewing the CI flow for Chonk input refreshes. |
| argument-hint | <action> e.g. "download", "check", "refresh-pr", "benchmark", "ultrahonk" |
Pinned Chonk IVC inputs live in an S3 tarball keyed by barretenberg/cpp/scripts/chonk-inputs.hash. The owner scripts are:
barretenberg/cpp/scripts/pinned_chonk_inputs.sh for shared shell helpers.barretenberg/cpp/scripts/chonk_inputs.sh for download, check, and update.barretenberg/cpp/scripts/ci_update_chonk_inputs.sh for the PR push-back step.Use the scripts instead of open-coding URLs, hashes, temp paths, or bucket listings.
Download or repair the local fixture directory:
barretenberg/cpp/scripts/chonk_inputs.sh download
Check pinned VK compatibility without updating:
barretenberg/cpp/scripts/chonk_inputs.sh check
Refresh the pin locally:
barretenberg/cpp/scripts/chonk_inputs.sh update
In PR CI, refresh via the ci-refresh-chonk label or a --ci-refresh-chonk head-commit marker. The follow-up refresh commit includes --ci-skip.
Proving is handled by the pinned-input tests; the CI push-back step runs one small pinned flow before committing a refreshed hash.
Barretenberg owns the Chonk and rollup UltraHonk benchmark commands. Use barretenberg/cpp/bootstrap.sh bench_cmds to inspect the CI command list, or bench_ivc for a focused Chonk run.
The benchmark scripts restore or regenerate their inputs when missing:
barretenberg/cpp/scripts/chonk_inputs.sh download
barretenberg/cpp/scripts/ci_benchmark_ivc_flows.sh native
barretenberg/cpp/scripts/ci_benchmark_ultrahonk_circuits.sh parity_base \
../../yarn-project/end-to-end/ultrahonk-bench-inputs 8
Keep Chonk benchmark command enumeration in barretenberg; yarn-project/end-to-end/bootstrap.sh build_bench_capture is only for live input capture during pin refresh.
aws s3 ls or depend on bucket listing. Verify exact object URLs..cache/ for scratch state and clean job-specific subdirectories.barretenberg/cpp/scripts/chonk-inputs.hash.bash -n on edited shell scripts and yq e . .github/workflows/ci3.yml after workflow edits..cache/chonk-ux-harness/run.sh when available.