Skip to content
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 ED25519 seeding #648

Open
jasny opened this issue May 7, 2018 · 3 comments
Open

Support ED25519 seeding #648

jasny opened this issue May 7, 2018 · 3 comments

Comments

@jasny
Copy link

jasny commented May 7, 2018

Waves platform uses a custom way of seeding a key pair.

There is a standard way of seeding ED25519 keys implemented in NaCl compatible libraries (including tweetnacl.js, pynacl and libsodium). The ED25519 can be converted to Curve25519 / X25519 keys. Some libraries (like libsodium) even support generating Curve25519 directly.

Using these (converted) keys work for Waves transactions 🎉. Unfortunately, it's impossible to import them in the WavesGUI, since they can't be generated from seed using the Waves algorithm 😞.

Supporting to seed via ED25519 using the NaCL standard means inoperability with platforms that use ED25519 (like our project @legalthings).

@xenohunter
Copy link
Contributor

Hello! Thanks for the proposal, we'll consider it and most probably will implement along with that issue: #57. Maybe I don't fully understand the matter but could that be the same thing you are writing about?

@jasny
Copy link
Author

jasny commented May 13, 2018

It's a different issue. It is similar as described here in using ED25519 keys to generate Curve25519: https://github.com/wavesplatform/nanos-app-waves/blob/master/README.md#original-description-of-burst-wallet

@xenohunter
Copy link
Contributor

Thanks! We'll use it as a reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants