fix: prevent oracle failure on tag computation for invalid recipient#22163
Open
nventuro wants to merge 1 commit intomerge-train/fairiesfrom
Open
fix: prevent oracle failure on tag computation for invalid recipient#22163nventuro wants to merge 1 commit intomerge-train/fairiesfrom
nventuro wants to merge 1 commit intomerge-train/fairiesfrom
Conversation
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.
From https://github.com/AztecProtocol/barretenberg-claude/issues/1903.
This fixes a king-of-the-hill vector in which an attempt to deliver to an invalid address resulted in a simulation crash. The contract correctly handles this already during encryption, but the PXE tagging code did not. Future versions of PXE will not be vulnerable to this.