Add new serialized pubkey type#2156
Merged
Roasbeef merged 2 commits intobtcsuite:masterfrom Apr 10, 2024
Merged
Conversation
Pull Request Test Coverage Report for Build 8528940528Details
💛 - Coveralls |
ffranr
force-pushed
the
add-pubkey-serialized-type
branch
from
02c8bf7 to
373e335
Compare
Roasbeef
requested changes
Apr 2, 2024
This commit adds a new type called `SerializedKey`. A serialized type is useful when using public keys as map keys. This is because functionally identical public keys can have different internal representations. These differences would cause the map to treat them as different keys.
ffranr
force-pushed
the
add-pubkey-serialized-type
branch
from
373e335 to
665eeb5
Compare
Member
|
Will tag a new |
Member
|
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
4 participants
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.
This commit adds a new type called
SerializedKey.A serialized type is useful when using public keys as map keys. This is because functionally identical public keys can have different internal representations. These differences would cause the map to treat them as different keys.