-
Notifications
You must be signed in to change notification settings - Fork 4
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
VC issuing tool key encoding problems #19
Comments
from @ChristopherA : One thing to be aware of here is some standardization work around the EcdsaSecp256k1Signature2019 signature suite: digitalbazaar/jsonld-signatures#74 (comment) |
(Happy to help out / answer questions on this) |
Okay I think I got this to work now, with bitcoin private/public keys. I'll reproduce and document my steps within the next hour or two. |
Excellent. I also want to point to the newly updated docs in vc-js, specifically the key generation section, which includes ecdsa keys. I'll be working to reconcile that with the work at w3c-ccg/lds-ecdsa-secp256k1-2019#2, as well. |
Thanks a lot @dmitrizagidulin Looks like I was able to sign (and then verify) using vc-demo from an existing bitcoin wif/private key - documented my steps here - https://gist.github.com/AnthonyRonning/9e83ae7e0e208320b244f727cde545d7 Though noting that this is more so for hacking & testing purposes for this week's btcr hackathon, surely not official recommended steps. |
VC issuing tool key encoding problems
The text was updated successfully, but these errors were encountered: