📅 Original date posted:2022-05-23
📝 Original message:Jonas, all,:
So I do want to ask a couple further clarifying questions on this point, but I got rather majorly sidetracked :)
I wonder can you (and other list readers!) take a look at my attempt here to summarize what is described in Footnote 2 of the draft BIP (as it's related to this discussion and also .. it's pretty interesting generally!):
https://gist.github.com/AdamISZ/ca974ed67889cedc738c4a1f65ff620b
(btw github gists have equation rendering now which is nice!)
Thanks,
waxwing/AdamISZ
Sent with ProtonMail secure email.
------- Original Message -------
On Monday, May 23rd, 2022 at 10:56, Jonas Nick via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
> 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
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
AdamISZ [ARCHIVE] /
npub1nv…kqw2t
2023-06-07 23:09:57
in reply to nevent1q…d3lf
Author Public Key
npub1nv7tjpn2g8tvt8qfq5ccyl00ucfcu98ch998sq4g5xp65vy6fc4sykqw2tPublished at
2023-06-07 23:09:57Event JSON
{
"id": "358c1aacbd575525ed9f6513f4991d85119bb731e93513a82c31401cdf147928",
"pubkey": "9b3cb9066a41d6c59c090531827defe6138e14f8b94a7802a8a183aa309a4e2b",
"created_at": 1686179397,
"kind": 1,
"tags": [
[
"e",
"fbc301a8701a363e71bd586f5c5625ea83d991fcb7c25f51abb36ba7ede688cb",
"",
"root"
],
[
"e",
"69df9a62bf3ac8ae327c643f955563143837ce29a0ad9afeb5122621cf99239a",
"",
"reply"
],
[
"p",
"eae21eb28545b20116d940817b2995954758d0d5511695442681f035faabe60f"
]
],
"content": "📅 Original date posted:2022-05-23\n📝 Original message:Jonas, all,:\n\nSo I do want to ask a couple further clarifying questions on this point, but I got rather majorly sidetracked :)\nI wonder can you (and other list readers!) take a look at my attempt here to summarize what is described in Footnote 2 of the draft BIP (as it's related to this discussion and also .. it's pretty interesting generally!):\n\nhttps://gist.github.com/AdamISZ/ca974ed67889cedc738c4a1f65ff620b\n\n(btw github gists have equation rendering now which is nice!)\n\nThanks,\nwaxwing/AdamISZ\n\n\n\nSent with ProtonMail secure email.\n------- Original Message -------\nOn Monday, May 23rd, 2022 at 10:56, Jonas Nick via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\n\u003e Thank you for taking the time to look at the BIP and reference code, waxwing. I\n\u003e don't know if you're overlooking anything, so let me try to restate the\n\u003e paragraph in the BIP draft that attempts to cover this topic [0].\n\u003e\n\u003e Suppose signers would just abort in the presence of identical public keys. In\n\u003e that case, a disruptive signer can permanently DoS-attack a session by simply\n\u003e copying the public key of some other signer. Therefore, the BIP is much more\n\u003e useful if it can deal with identical public keys.\n\u003e\n\u003e The MuSig2 BIP draft requires some added complexity to handle identical public\n\u003e keys (because of the MuSig2* optimization). But this solution naturally allows\n\u003e identifying and removing disruptive signers, which ultimately reduces the\n\u003e complexity for MuSig2 users.\n\u003e\n\u003e [0] https://github.com/jonasnick/bips/blob/musig2/bip-musig2.mediawiki#public-key-aggregation\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev",
"sig": "8b38ef8d918697e77601a30bceae0a1cd89ed524e6a06a043e6da478dd77dd892344c44159714a509925efb1e6fd8a91b23a4c7a0138a7b7c09522aa5866c2b0"
}