Skip to content

fix: return Chonk prove verification key#24078

Draft
AztecBot wants to merge 1 commit into
nextfrom
cb/fix-chonk-prove-vk
Draft

fix: return Chonk prove verification key#24078
AztecBot wants to merge 1 commit into
nextfrom
cb/fix-chonk-prove-vk

Conversation

@AztecBot

Copy link
Copy Markdown
Collaborator

Summary

  • return the serialized hiding-kernel VK from ChonkProve
  • verify pinned Chonk flows and TS client proofs with the VK used by the proof, instead of recomputing it from hiding bytecode
  • reuse the prove response VK for bb prove --write_vk

Root cause

The nightly debug failure was in ChonkPinnedIvcInputsTest.AllPinnedFlows, not in CMake compilation. ChonkProve generated a proof and verified it successfully with the accumulated hiding-kernel VK. The test then recomputed a VK through ChonkComputeVk from only the hiding-kernel bytecode. That write-VK/mock construction produced different hiding-kernel metadata (pub_inputs_offset 673 instead of 669, different selector commitments), so the verifier parsed the proof public inputs against the wrong VK and hit the debug databus assertion.

Verification

  • cmake --preset debug -DAVM=OFF -DAVM_TRANSPILER_LIB=
  • cmake --build --preset debug --target bbapi_tests -j 16
  • cmake --build --preset debug --target bb -j 16
  • build-debug/bin/bbapi_tests --gtest_filter='BBApiMsgpack/*.DefaultConstructorRoundtrip'
  • build-debug/bin/bbapi_tests --gtest_filter='BBApiInputValidation.*:CBind.*'
  • NATIVE_PRESET=debug CHONK_PINNED_IVC_FLOW='deploy_ecdsar1+sponsored_fpc' scripts/run_test.sh bbapi_tests ChonkPinnedIvcInputsTest.AllPinnedFlows
  • corepack yarn prettier --check src/barretenberg/backend.ts

Notes: clang-format is not installed in this container. Full TS typecheck was blocked by missing ignored aztec-wsdb generated bindings, and ESLint was blocked by an unavailable eslint-plugin-import referenced by the repo config.


Created by claudebox · group: slackbot

@AztecBot AztecBot added ci-draft Run CI on draft PRs. ci-no-fail-fast Sets NO_FAIL_FAST in the CI so the run is not aborted on the first failure claudebox Owned by claudebox. it can push to this PR. labels Jun 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-draft Run CI on draft PRs. ci-no-fail-fast Sets NO_FAIL_FAST in the CI so the run is not aborted on the first failure claudebox Owned by claudebox. it can push to this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant