Skip to content
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

Eth1 secp256k1 remote signing using AWS KMS #501

Closed
3 tasks done
jframe opened this issue Jan 27, 2022 · 0 comments · Fixed by #837
Closed
3 tasks done

Eth1 secp256k1 remote signing using AWS KMS #501

jframe opened this issue Jan 27, 2022 · 0 comments · Fixed by #837
Assignees
Labels
TeamCerberus Under active development by TeamCerberus @Consensys

Comments

@jframe
Copy link
Contributor

jframe commented Jan 27, 2022

Implement Eth1 secp256k1 signing using the AWS KMS so that Ethereum secp private keys can be used to sign transactions without the key leaving the AWS KMS.

Tasks

  • Add a new key metadata format. The AzureKeySigningMetadata can be used as a guide
  • Create an AWS signer to sign secp256k1 keys using KMS with the AWS SDK
  • Acceptance tests
@jframe jframe added the TeamCerberus Under active development by TeamCerberus @Consensys label Jan 27, 2022
@usmansaleem usmansaleem self-assigned this Jul 4, 2023
@jframe jframe changed the title Eth1 secp256k1 signing AWS HSM Eth1 secp256k1 signing AWS KMS Jul 4, 2023
@usmansaleem usmansaleem changed the title Eth1 secp256k1 signing AWS KMS Eth1 secp256k1 remote signing using AWS KMS Jul 4, 2023
@usmansaleem usmansaleem added the doc-change-required Indicates an issue or PR that requires doc to be updated label Jul 23, 2023
@usmansaleem usmansaleem linked a pull request Jul 23, 2023 that will close this issue
3 tasks
@alexandratran alexandratran removed the doc-change-required Indicates an issue or PR that requires doc to be updated label Aug 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TeamCerberus Under active development by TeamCerberus @Consensys
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants