fix: Avoid a redundant check containing curve point multiplication #840
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.
Motivation
The function try_output_recovery_with_ock calls parse_note_plaintext_without_memo_ovk from here. The second function validates the ephemeral keys. The first function then calls check_note_validity, which also contains the same check of the same ephemeral keys. These checks both contain a curve point multiplication, and since the second check is redundant, removing it increases performance.
Closes #802.
Solution
check_note_validity
, but still check the commitment bytes.As mentioned in ZcashFoundation/zebra#6392 (comment), I initially thought of refactoring
check_note_validity
directly, which wouldn't be worth it since it's called in other places. Only then I thought of not callingcheck_note_validity
at all, which is a much simpler solution that avoids the redundant check.