-
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
Add secp256r1 Signing Keys #7718
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Add support for singing tranactions with the secp256r1/NIST P-256 algorithm (used in macOS/iOS/watchOS & Android secure enclaves). Already discussed in #4789 and #7074 but there was no standalone issue.
Problem Definition
Supporting the signing algorithm for the secure enclave in macOS/iOS/watchOS and Android Hardware-backed Keystore will allow these devices to basically function as hardware wallets. There has been speculation that the secp256r1/NIST P-256 algorithm was backdoored by the NSA, but this is unproven and users should be able to choose their desired level of security. For many users, having a smartphone-backed key for low security operations (as enabled by the other key management modules #7074) may be the best options.
Proposal
PubKey
implementation with addresses based on ADR 028For Admin Use
The text was updated successfully, but these errors were encountered: