To all the devs wondering about Musig2. The issue is not so much the crypto/signing here, that base is covered by libsecp256k1. The issue obviously is the coordination. I (well, the robot), made a general musig2 NIP for the general parts irt Nostr tags, verification and how signing/ceremonies go in general. That nip does NOT specify the specific coordination method, those are separate NIPs. I went the route of building out a reference coordination method using plain Nostr events because its the most straightforward, easy, stable and transparent process. It is not private, so not ideal, but that is a separate concern and has no influence on the integrity of the musig2 ceremony (assuming your client picks its nonces right). To try stuff out I initially asked the robot to implement ceremonies using FIPS and one using Marmot. NIP17, Marmot, NIP29 groups, all are reasonable candidates to do this sort of stuff. Who knows, maybe some 'super' implementation is able to manage all of them at the same time, especially if you do the ceremony via a coordinator. Will publish documentation soon and we can have a chat about this. View quoted note →

Here is a little article about what was broken with NIP-03 and how i fixed it. Unfortunately the blossom server gods seem to hate me, so the beefy android APK and zapstore release will have to wait. But you can always build it yourself from the repository. Links to the repository and the two NIPs are in the article. Devs please have a look, especially @utxo the webmaster 🧑‍💻 because i abused wisp to make the client :). And @Vitor Pamplona because i think amethyst is the only client that uses NIP-03 anyway i think. Im going for a walk View article →