Open chrisalmeida opened 8 months ago
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.
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.
Hey any plans to support Ed25519?