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

feat(identity): allow importing and exporting secp256k1 keys #3887

Merged
merged 2 commits into from
May 5, 2023

Conversation

drHuangMHT
Copy link
Contributor

Description

Related: #3681

Notes & open questions

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • A changelog entry has been made in the appropriate crates

@drHuangMHT drHuangMHT changed the title allow importing and exporting secp256k1 keys feat(identity): allow importing and exporting secp256k1 keys May 5, 2023
@drHuangMHT
Copy link
Contributor Author

Getting the public key of the test key is a real pain in the A.

@thomaseizinger thomaseizinger marked this pull request as ready for review May 5, 2023 13:15
Copy link
Contributor

@thomaseizinger thomaseizinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

I've verified that the test vector is the same the nim-libp2p uses here: https://github.com/status-im/nim-libp2p/blob/a1eb53b1813df5d4fa1b343ef003ad9fb5ebb1d8/tests/testpeerid.nim#LL162C6-L162C6

They generated it using go-libp2ps tools so I am quite confident that this works as expected. I added the test vector we are using to the open libp2p/specs PR: libp2p/specs@0e0ced7

@mergify mergify bot merged commit b8411d1 into libp2p:master May 5, 2023
@drHuangMHT drHuangMHT deleted the secp256k1-impl branch May 5, 2023 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants