-
Notifications
You must be signed in to change notification settings - Fork 2
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
Support for parsing key files #81
Comments
Copied from #83 (mostly for the code rather than the explanation around it): it generates valid keys, but they just differ from how the cli would interpret things.
Here's the implementation that ended up working; from the skey bytes (5820xyz), we grab the juicy bits (strip off the 5820), and then pass that to ed25519.NewKeyFromSeed to get the actual payment key. This is what then works with the ed25519.Sign / ed25519.Verify method. However in bursa, https://github.com/blinklabs-io/bursa/blob/main/bursa.go#L134-L144, it looks like you're just taking the key (not the seed), and serializing it. Here's the code that produces results consistent with cardano-cli for both extended and non-extended keys:
And here's the unit tests written to track this down:
|
We should have functions which can parse the key file data.
The text was updated successfully, but these errors were encountered: