-
Notifications
You must be signed in to change notification settings - Fork 73
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
EdDSASigner- The privatekeyBytes is 64? #238
Comments
how did you generate the private key? This library [currently] uses In this convention, Ed25519 secret keys are represented on 64 bytes which I believe is actually the full keypair, not just the secret part, adding up to a total of 64 bytes. I think after we manage to modularize this library (see #170) the EdDSASigner will likely lose that 64 byte check logic, or be replaced entirely by something new, depending on the underlying crypto package being used. |
about the full keypair, does that means "privatekey+publickey" or "publickey + privatekey"? |
Hello, Any question is that: Do you have any idea about it? Thanks. |
It seems to be private+public. See the code
I have no idea without more details. What parameters are you sending to the function? |
Hi, I think I have found the issue, it is all caused by my misuse of the full keypair. Really thanks a lot. |
I'm happy to hear that you solved it. I'm closing this then. |
Hello,
I generated a private key by ED25519, and the private key is 32 bytes.
I want to use EdDSASigner to sign it, but it seems like the EdDSASigner will check the private key bytes.
From my understanding, the ED25519 private key should be 32 bytes, right? I'm not sure if it is a bug or my misunderstanding.
Expecting your reply!
Thanks.
The text was updated successfully, but these errors were encountered: