[zk-sdk] Allow all-zero ciphertext for ciphertext-ciphertext equality proof #202
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.
Problem
Terribly sorry, this is a quick follow-up to solana-program/token-2022#915. I went through all the token-2022 instructions to double check that we don't use all-zero (identity points) public keys or ciphertexts in any of the token-2022 application. But since solana-program/token-2022#913 was not merged, I missed that we would need to allow all-zero ciphertexts for the ciphertext-ciphertext validity proof.
Summary of Changes