fix: removing reduntant decode in prove #19611
Open
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
Eliminates redundant encode/decode cycle during internal proof verification in
AztecClientBackend.prove().Before: When
prove()generated a proof, it would:verify()which immediately decodes those bytes backchonkVerify()which encodes againAfter:
prove()now calls a privateverifyNative()method that accepts the nativeChonkProofdirectly, skipping the unnecessary encode/decode round-trip.This reduces conversions from 4 to 2 for internal verification with no impact on the public API.