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

Ed25519 Support #1

Open
chrisalmeida opened this issue Mar 14, 2024 · 2 comments
Open

Ed25519 Support #1

chrisalmeida opened this issue Mar 14, 2024 · 2 comments

Comments

@chrisalmeida
Copy link

Hey any plans to support Ed25519?

@cmdruid
Copy link
Owner

cmdruid commented Mar 16, 2024

It depends. I have looked into it and I'm not opposed to it. I also don't see any technical issues with it.

The main problem for me is that the landscape for Ed25519 is a big mess. So I would need some formal specification for implementing musig2 over ed25519, or at least a standard for handling the tweaking, aggregation and validation.

There are also some other caveats with ed25519 that may open attack vectors within musig2, so I am wondering if there is any research out there on that subject.

I am interested in mixing starknet proofs with musig2 and frost, so I do have some plans to hack together an implementation in the future, but no set timeframe currently.

@cmdruid
Copy link
Owner

cmdruid commented Aug 1, 2024

Just wanted to update this topic.

The new RFC spec for FROST has a nice way of introducing Ed25519 (plus a bunch of other domains) by defining an proper interface for the cryptography primitives.

You could do something similar with Musig2, and then add your crypto suite of choice. This would be outside the spec of BIP327 though.

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

No branches or pull requests

2 participants