We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@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.
The text was updated successfully, but these errors were encountered:
Sure, this is easy enough. Are JSON Web Keys (.jwk) files okay?
Sorry, something went wrong.
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.
No branches or pull requests
@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.
The text was updated successfully, but these errors were encountered: