-
sarangVery interesting preprint on an attack applying to (among other things) two-round MuSig: eprint.iacr.org/2020/945.pdf
-
sarangPreviously it wasn't known if 2-round MuSig was secure in practice, but there was not a proof
-
sarangNow there's an answer!
-
hycand the answer is no?
-
sarangIf correct, it means there's a polynomial-time algorithm against two-round MuSig
-
sarangBut the MuSig authors had already noted you need 3 rounds for provable security
-
sarangThis preprint also claims polynomial complexity attacks on some blind signature schemes too
-
sarangI'm going through it now
-
UkoeHB_Just started preparing for multisig security patches
-
UkoeHB_yesterday
-
sarangHow so UkoeHB_?
-
sarang(bearing in mind that existing keys need to keep working)
-
UkoeHB_Figuring out what needs changing
-
sarangYeah maintaining backwards compatibility seems like the trickiest part =p
-
UkoeHB_Robust key aggregation should be safe and relatively easy
-
sarangSure; the practical issue seems more about ensuring that existing multisig key distributions continue operating
-
sarangSimilar things arise for old-version transaction proofs, wallet signatures, etc.
-
geonicsarang: I know it just came out, but do you know when you'll be able to finish your review of the Atomic Swap paper?
-
geonicplenty of excitement around and I'm not sure if it needs to be tempered a bit until we hear your opinion
-
geonicalso, the author said the paper was written "together with the MRL" while you commented that "it's still being reviewed". wondering about that
-
UkoeHB_I kind of wonder how much backward compatibility is required. If barely anyone is using multisig, then we might be able to get by with 'yo, upgrade and try try again'
-
UkoeHB_We can't allow any loopholes where old formats are still permitted, meaning people can hack the client to exploit the weakness