-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[cli] Allow for AIP-80 compliant strings while importing #15039
Conversation
⏱️ 20m total CI duration on this PR
|
1b37337
to
22d2c9c
Compare
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.
Looks fine, we'll have to of course put saving to the new format in a future release. Probably will need eventually to have a proper feature flag system.
Let's add an optional prefix to check for, when stripping, and set it by default on the CLI to ed25519
d93e7cd
to
e0380d3
Compare
5943a9e
to
5fcb1cc
Compare
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.
Looks good to me!
a1b1a41
to
ad2ab71
Compare
ad2ab71
to
fe89305
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
✅ Forge suite
|
Description
Add support for AIP-80 formatted private keys. With this formatting, also restrict secp256k1 private keys.
https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-80.md
How Has This Been Tested?
Built locally and imported private keys starting with
ed25519-priv
using the CLI argument--private-key
, manual input, and configs.Key Areas to Review
Should cover all of the private key import cases in the CLI.
--private-key
Private key variants
Type of Change
Which Components or Systems Does This Change Impact?
Checklist