-
Notifications
You must be signed in to change notification settings - Fork 2.6k
ed25519-zebra #8055
Comments
Related lib https://github.com/hdevalence/ed25519consensus for the Go implementation |
We never use the prehashed variant in substrate or polkadiot according to We should go ahead and switch to ed25519-zebra whenever convenient. |
If I understand correctly, |
It's less strict and thus better. :) |
Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. |
It's being worked on.. |
Is this something the other polkadot implementations will also want to switch over to? (i.e. should there be some linked issues?) |
We still need this, which requires updating #8764. We now need to understand the difference between ed25519-zebra and ed25519-consensus, which forked after 3 Dec 2020 --- commit ZcashFoundation/ed25519-zebra@0e7a96a https://github.com/penumbra-zone/ed25519-consensus/commits/main I'm personally inclined to stick with zebra because zcash is a more established player. Also, we switched schnorrkel back off curve25519-dalek-ng recently, non-ng has many open issues & pulls https://github.com/dalek-cryptography/curve25519-dalek/issues but at least it has them so everyone knows the status of things. |
Are we using the prehashed variant of ed25519 anyplace? If not, then we should replace ed25519-dalek with ed25519-zebra, which better supports batch verification.
Ain't clear if ed25519-zebra ever wants features not required by zcash, so maybe we should do something else if we use the prehashed variant of ed25519 somewhere. I once pointed @tomaka to its existence
The text was updated successfully, but these errors were encountered: