1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
Return-Path: <AdamISZ@protonmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id A6C08C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 23 May 2022 22:10:03 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 8B381401A4
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 23 May 2022 22:10:03 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=protonmail.com
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id BBjS6Mjugmcn
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 23 May 2022 22:10:02 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-4316.protonmail.ch (mail-4316.protonmail.ch [185.70.43.16])
by smtp2.osuosl.org (Postfix) with ESMTPS id 526C7400BF
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 23 May 2022 22:10:02 +0000 (UTC)
Date: Mon, 23 May 2022 22:09:52 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail3; t=1653343800; x=1653603000;
bh=pdBKxyjqkkCukmRYL6Xb9VofEHxSgyehzjsDRSth9hk=;
h=Date:To:From:Reply-To:Subject:Message-ID:In-Reply-To:References:
Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
Message-ID;
b=us6jnlN0NF8b720gC/rID1ufEh4Ba62QcSTcbaLoPe65MWdSS3vRujRb86pOe+x2f
qljiLZ89Z1V297y+zYQYDGVmc925pKTLw9CYzpNMrZWrRsUPGCL4xZd4pHd487oxS4
E7a+cDAxuTbgoc41fPs230S+/Qi8U7Z98iETR3GxOcsYVwsvp4F8enQ1mO87TEiJj+
2SsaRk+zeUgHr7H8wXTLcPnErAB90jpG7MbhJpaRoHxdjEpaOuhr4Y97YiE2t7clOM
N/SjoZlT9dN+XqqsZnkPRaIGxIv7DeTRpMhqo6WeQa0rjK3acwWIB7NvJ6nHaktFaL
woD3ggCK2xNOA==
To: Jonas Nick <jonasdnick@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: AdamISZ <AdamISZ@protonmail.com>
Reply-To: AdamISZ <AdamISZ@protonmail.com>
Message-ID: <HPRdBVSvEmkPyHkS-175ZYEYyL-ULZAgmhSPh3uwVtfryFOKZUFKUM5QXnSXjwZy3b10sV55f9lhOkZ-ILShaWSWJ7GMN0JmKNweKY6kfLg=@protonmail.com>
In-Reply-To: <c2a9b488-8d29-d1c6-b2c3-bc17d12b7d65@gmail.com>
References: <46175970-d2ab-a58e-7010-f29820849604@gmail.com>
<yitwgERAsaofLM5dheUZUYyFp0ncU8xyN98xTym3MkCxTch83DkweZN5JYyovVcfxA2Mo7DjTbv1Iku3wBApYiPG_cMwznTytKFpcjYa1O0=@protonmail.com>
<c2a9b488-8d29-d1c6-b2c3-bc17d12b7d65@gmail.com>
Feedback-ID: 11565511:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 23 May 2022 22:27:42 +0000
Subject: Re: [bitcoin-dev] MuSig2 BIP
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2022 22:10:03 -0000
Jonas, all,:
So I do want to ask a couple further clarifying questions on this point, bu=
t I got rather majorly sidetracked :)
I wonder can you (and other list readers!) take a look at my attempt here t=
o summarize what is described in Footnote 2 of the draft BIP (as it's relat=
ed 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=
@lists.linuxfoundation.org> wrote:
> Thank you for taking the time to look at the BIP and reference code, waxw=
ing. 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 si=
mply
> copying the public key of some other signer. Therefore, the BIP is much m=
ore
> useful if it can deal with identical public keys.
>
> The MuSig2 BIP draft requires some added complexity to handle identical p=
ublic
> keys (because of the MuSig2* optimization). But this solution naturally a=
llows
> identifying and removing disruptive signers, which ultimately reduces the
> complexity for MuSig2 users.
>
> [0] https://github.com/jonasnick/bips/blob/musig2/bip-musig2.mediawiki#pu=
blic-key-aggregation
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
