📅 Original date posted:2022-05-23
📝 Original message:Thank you for taking the time to look at the BIP and reference code, waxwing. I
don't know if you're overlooking anything, so let me try to restate the
paragraph in the BIP draft that attempts to cover this topic [0].
Suppose signers would just abort in the presence of identical public keys. In
that case, a disruptive signer can permanently DoS-attack a session by simply
copying the public key of some other signer. Therefore, the BIP is much more
useful if it can deal with identical public keys.
The MuSig2 BIP draft requires some added complexity to handle identical public
keys (because of the MuSig2* optimization). But this solution naturally allows
identifying and removing disruptive signers, which ultimately reduces the
complexity for MuSig2 users.
[0] https://github.com/jonasnick/bips/blob/musig2/bip-musig2.mediawiki#public-key-aggregation
Jonas Nick [ARCHIVE] /
npub1at…y3z5a
2023-06-07 23:09:57
in reply to nevent1q…c5ve
Author Public Key
npub1at3pav59gkeqz9kegzqhk2v4j4r435x42ytf23pxs8crt74tuc8s2y3z5aPublished at
2023-06-07 23:09:57Event JSON
{
"id": "69df9a62bf3ac8ae327c643f955563143837ce29a0ad9afeb5122621cf99239a",
"pubkey": "eae21eb28545b20116d940817b2995954758d0d5511695442681f035faabe60f",
"created_at": 1686179397,
"kind": 1,
"tags": [
[
"e",
"fbc301a8701a363e71bd586f5c5625ea83d991fcb7c25f51abb36ba7ede688cb",
"",
"root"
],
[
"e",
"18590d0f81c43af446321d83b1a9198fe1dd39fbba06fee51b172aa941cd4b59",
"",
"reply"
],
[
"p",
"9b3cb9066a41d6c59c090531827defe6138e14f8b94a7802a8a183aa309a4e2b"
]
],
"content": "📅 Original date posted:2022-05-23\n📝 Original message:Thank you for taking the time to look at the BIP and reference code, waxwing. I\ndon't know if you're overlooking anything, so let me try to restate the\nparagraph in the BIP draft that attempts to cover this topic [0].\n\nSuppose signers would just abort in the presence of identical public keys. In\nthat case, a disruptive signer can permanently DoS-attack a session by simply\ncopying the public key of some other signer. Therefore, the BIP is much more\nuseful if it can deal with identical public keys.\n\nThe MuSig2 BIP draft requires some added complexity to handle identical public\nkeys (because of the MuSig2* optimization). But this solution naturally allows\nidentifying and removing disruptive signers, which ultimately reduces the\ncomplexity for MuSig2 users.\n\n[0] https://github.com/jonasnick/bips/blob/musig2/bip-musig2.mediawiki#public-key-aggregation",
"sig": "8bbd5b2f4ff7370870bfab58110614767e010fe9c8492eb3ef196043f8952c1274b08512eba05da5a6db32cd6135e882db17afc48591a1e84c9a64a46b86c31e"
}