Enable ClientIVC proof generation for devnet#244
Merged
critesjosh merged 2 commits intonextfrom Feb 25, 2026
Merged
Conversation
The devnet node validates client-side transaction proofs even when realProofs is false. Without enabling the prover, the PXE generates empty/fake proofs that are rejected with "Invalid tx: Invalid proof". This conditionally enables proverEnabled in the PXE config when targeting devnet, keeping it disabled for local network (faster iteration). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Runs deploy-account::devnet on pushes and PRs to next/dev branches. No local network or Aztec CLI needed since it targets the remote devnet. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
proverEnabledin the PXE config when targeting devnet, fixing "Invalid tx: Invalid proof" errors on account and contract deploymentsrealProofs: false, so the PXE must generate real ClientIVC proofsChanges
src/utils/setup_wallet.ts— conditionally setproverEnabled: configManager.isDevnet()scripts/multiple_wallet.ts— use the same conditional prover config (was creating wallets directly)src/utils/deploy_account.ts— clean up deploy options formattingTest plan
yarn deploy-account::devnetsucceeds (was failing with "Invalid proof")yarn deploy::devnetworks🤖 Generated with Claude Code