This repository has been archived by the owner on Feb 19, 2024. It is now read-only.
Use uncompressed representation for ECPublicKey equality #178
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.
Pull Request Template
Title
Use uncompressed representation for ECPublicKey equality
Description
Previously, if we initiated two instances of a public key of the same EC point with compressed and uncompressed byte representation (using
ECPublicKey.fromBytes
) we would end up with two unequal objects. This PR changes it so that they're equal. Precisely: two public keys are equal if their uncompressed byte representation is equal. It also adds a validation that the bytes passed actually represent a valid point. This change also revealed that some classes were implicitly relying and being given a key with compressed bytes representation (RadixAddress for example).