You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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?
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).
The text was updated successfully, but these errors were encountered: