-
Notifications
You must be signed in to change notification settings - Fork 49
feat(dpp): add a convenience method to get the public key data for a private key depending on the key type #2214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
QuantumExplorer
merged 5 commits into
v1.4-dev
from
feat/addKeyTypePrivateKeyToPublicKey
Oct 6, 2024
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ff64350
feat: add a convenience method to get the public key data for a priva…
QuantumExplorer c285445
fix features
QuantumExplorer 14d5409
fix features
QuantumExplorer a0e5e0d
fix features
QuantumExplorer 4d838f0
fix features
QuantumExplorer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Improve error handling in BLS12_381 implementation
The BLS12_381 implementation is generally correct, but there's room for improvement in error handling:
The use of
expect()when callingg1_element()could lead to a panic. Consider usingmap_err()to convert any error to aProtocolErrorinstead.The error handling for the
not(feature = "bls-signatures")case is good, returning aNotSupportederror.Consider replacing the
expect()call with proper error handling:This change will propagate any errors from
g1_element()as aProtocolErrorinstead of panicking.📝 Committable suggestion