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

Switch keys to secp256k1 #3

Open
jandrieu opened this issue Mar 15, 2022 · 2 comments
Open

Switch keys to secp256k1 #3

jandrieu opened this issue Mar 15, 2022 · 2 comments

Comments

@jandrieu
Copy link

@wip-abramson Can we generate a bunch of key pairs for secp256k1 instead of the ed25519 curve? Just replace all the existing keys with secp versions.

@wip-abramson
Copy link
Member

Sure, this is easy enough. Are JSON Web Keys (.jwk) files okay?

@wip-abramson
Copy link
Member

So I created a branch feature/secp-keys which contains a new folder keys in it.

This folder has keys for each of the actors in .jwk format. Which looks like this:

{"kty":"EC","crv":"secp256k1","x":"5lqgcTPez3h4xtPtDN-H6-IDlrk8Ea4zPebgdBIKH1g","y":"BWBKVbVwCQLM4FAVgO4V-azr6AZojBpG4JQ9tALisYk","d":"XdnnfcT-U7iR_KvCq3FHqi-a87ErzvH4cIg3XieFcns"}

The (x,y) values define a point on a curve (public key). The d value is the private key.

I also used the didkit to generate DIDDocs for each of these keys. These are currently under the keys folder too.

Take a look. Let me know what you think. We can always refactor the structure later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants