Closed delaneyj closed 2 years ago
Also confirmed on go playground
Looks like it stems from golang.org/x/crypto/ed25519
now being in stdlib as crypto/ed25519
You are right. crypto/ed25519 is added to stdlib in the resent version of go. As a temporary solution you can just import golang.org/x/crypto/ed25519 instead of crypto/ed25519.
how can i parse data for this v2
@shahriar350 check out the docs
thank you so much.
Symmetric/local keys work great, however...
Gives a err of
incorrect private key type
. What am I doing wrong here?