[PrivateKey] Add support for AIP80 to Ed25519 and Secp256k1 #38
Conversation
This file contains 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
GhostWalker562
requested review from
davidiw,
gregnazario and
a team
as code owners
GhostWalker562
force-pushed
the
support-aip-80
branch
from
21e7441
to
d6fc463
Compare
gregnazario
approved these changes
Oct 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Added support for formatting and parsing private keys with prefixes.
Main Changes:
PrivateKeyfor formatting and parsing AIP-80 private keysfrom_hexfunction that accepts bothbytes, hex strings, and AIP-80 compliant stringsTest Plan
from_hexbytes, hex string, and AIP-80 compliant stringsRelated Links