feat: generate secp256k1 private key #483
Merged
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
Main feature
Generate an Secp256k1 nodekey from a private key (in hex format).
polycli nodekey --private-key 2a4ae8c4c250917781d38d95dafbb0abe87ae2c9aea02ed7c7524685358e49c2 --key-type secp256k1 | jq
Most of the logic has been copy/pasted from 0xPolygon/cometbft's fork (scep256k1 package). Indeed, it's not possible to import the package yet because
go.mod
declares its path asgithub.com/cometbft/cometbft
instead ofgithub.com/0xpolygon/cometbft
. Unfortunately, the logic will need to be updated to support new versions. For now, we support the latest polygon's cometbft relase.Minor
Allow passing an hex encoded private key from the command line to generate a node key.
polycli nodekey --private-key 2a4ae8c4c250917781d38d95dafbb0abe87ae2c9aea02ed7c7524685358e49c2 | jq
Jira / Linear Tickets
x
Testing
x