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
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
|
Delivery-date: Mon, 02 Jun 2025 09:02:08 -0700
Received: from mail-yw1-f192.google.com ([209.85.128.192])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBDHJDC5244MRB5MV67AQMGQE3UARCUA@googlegroups.com>)
id 1uM7bz-0006CS-PO
for bitcoindev@gnusha.org; Mon, 02 Jun 2025 09:02:08 -0700
Received: by mail-yw1-f192.google.com with SMTP id 00721157ae682-70e5ae5c517sf61681367b3.1
for <bitcoindev@gnusha.org>; Mon, 02 Jun 2025 09:02:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1748880122; x=1749484922; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:references:in-reply-to:message-id:to:from:date:sender:from
:to:cc:subject:date:message-id:reply-to;
bh=ExC1ALPlCifDjqh1T530ucXXjBUxPttiwSkeYLopDqo=;
b=twjYr8lCv39odvlvf6DjrkZYWXIGVi5BCpvF6nvlMKI67Os6R6EBcfKS/+Cf0zdwCv
MtrCTGYWzI4uvuxAzCpWKpfbN73m92oTKHqKjAjoTpJBDIuYyBGUJDxlpoAyjoSaXq0o
K7ShYp0mz2JEcREzzI7uz/npHVAxvBmQiDDNnVunHXoMD2BlGd7eIQyaToPm7cw0uY/S
fI/ZFb0tfM1wkfloCn7pS1bPRYxgOUaBc0of5ncR9XxLZB/PNjO+v5yiW3mm889J1i5r
wEBuI0tFErgiYmsS7xDhLwlP8w6/UbH6Zl9yf8RTK8RvDyIS6c1kaajl0n0T5kl9AuYw
2aGA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1748880122; x=1749484922; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:references:in-reply-to:message-id:to:from:date:from:to:cc
:subject:date:message-id:reply-to;
bh=ExC1ALPlCifDjqh1T530ucXXjBUxPttiwSkeYLopDqo=;
b=ToIDapBc1UNWA4A9mqQMSCvXIWEJf4nIKT4KU+588DMf2peM0C+NsjJke7kzHhmiPp
qlE7JaCu43Ruho82PgBuWeL4K5c4CnTC/aa6jWOXUBQ78D1gnm5vZ++pvGyBjWqmKIRW
io9LWzYPF1Nn8Y+b6OqR4D5G7DcVFhPMS/vWSN/Jw/yGDBBRaWKeHu6vw8HJw93FzQaK
s4uE5/157ZnwhD58RwyFFFXDYqAtE+DY0KRcBCxy+ej4GibcDAkvoy40ewzA1P3YJKb+
ABmdmni/q+xqKDkV78FtO0nJhFt9gIZa6eNalMbU2BRZkPwffFJ5Nx6i52YZNyTR+d0E
jpmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1748880122; x=1749484922;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:references:in-reply-to:message-id:to:from:date:x-beenthere
:x-gm-message-state:sender:from:to:cc:subject:date:message-id
:reply-to;
bh=ExC1ALPlCifDjqh1T530ucXXjBUxPttiwSkeYLopDqo=;
b=fCa/DIZ1Q2rDPodsp6/sJ7AsdpYe826NqdiE79xjuYV47FLoYzb5z2eW72zVMd3OJ9
bBfKqG9zLzzI/De/rnVTC97G7UGxRvl4WOqXF9Ec/GMlKp0rHSwG3Tzfb5Zej5yzE8B4
8RUIId9yK3cs4XsUGKYTX3CCMhgko1FuvUfnKitMjX0SzfO7RIF7DGUpu6LRP5MmcZ7H
PFBIGBVAzTwyJ/rVEOp5/NiLJ1l4rBrh+RZQuHJ7E4uBoY6++uwrPsrEQsaVZcLj2V9t
eRIgzzbphNMS3yI25DYBGLSdBz33X9fyPRJW7WK7oxWn9rriNEJKuyR7oo5tyvYFnLcK
99zQ==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCWLZTrWXaL66S7BGIeDAArwCcCN6UT9ix4ailktHrFam5kPbme31eDcO0vwZOrZP4j++cNZVH0+1POJ@gnusha.org
X-Gm-Message-State: AOJu0YyxMnOEOUSFj4BaYtToQlUnmDPrtbqHkH/giQG2c6Z786+iKWTF
vV0xvr50tthGTuR1qDccrkBwv8wPTjo42U9/0z2EYSpekIylszn8bX22
X-Google-Smtp-Source: AGHT+IHSC5si5qUgppKVr5YtNGi1/HOsNgHcdfA1QeZf8akZt8oxBqN3NdzQ4M2LVbphDdgwxiZflQ==
X-Received: by 2002:a05:6902:2013:b0:e7d:b5bc:aa81 with SMTP id 3f1490d57ef6-e8128dc86c5mr10371040276.27.1748880121817;
Mon, 02 Jun 2025 09:02:01 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=AZMbMZf1NEj/ygpPivImlPXL80tKQ+x5QGjRKgSuto1sv45yOg==
Received: by 2002:a25:dc91:0:b0:e7d:7490:4a2b with SMTP id 3f1490d57ef6-e7f6f7d969fls4998804276.1.-pod-prod-02-us;
Mon, 02 Jun 2025 09:01:56 -0700 (PDT)
X-Received: by 2002:a05:690c:6705:b0:70e:195:e924 with SMTP id 00721157ae682-70f97f3212fmr177897517b3.36.1748880116700;
Mon, 02 Jun 2025 09:01:56 -0700 (PDT)
Received: by 2002:a05:690c:6083:b0:70e:2cf8:9db8 with SMTP id 00721157ae682-70f980e43fams7b3;
Mon, 2 Jun 2025 08:50:30 -0700 (PDT)
X-Received: by 2002:a05:690c:6f06:b0:6f9:7920:e813 with SMTP id 00721157ae682-70f97e2e318mr191520667b3.4.1748879428894;
Mon, 02 Jun 2025 08:50:28 -0700 (PDT)
Date: Mon, 2 Jun 2025 08:50:28 -0700 (PDT)
From: Q C <dogeprotocol1@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <77c90109-6f21-4f92-b122-0a7034fb1a87n@googlegroups.com>
In-Reply-To: <aD2J9HNJUqaod0n2@petertodd.org>
References: <cc2f8908-f6fa-45aa-93d7-6f926f9ba627n@googlegroups.com>
<CAFC_Vt6gqV-8aoTKt2it1p9LAnvaADueHnC1cM6LQojZf6fjCw@mail.gmail.com>
<c8bbcbbb-036b-4e72-9bb5-4490e43dda21n@googlegroups.com>
<aD2J9HNJUqaod0n2@petertodd.org>
Subject: Re: [bitcoindev] Post-Quantum commit / reveal Fawkescoin variant as a
soft fork
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_322516_1630944952.1748879428552"
X-Original-Sender: dogeprotocol1@gmail.com
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
<https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.5 (/)
------=_Part_322516_1630944952.1748879428552
Content-Type: multipart/alternative;
boundary="----=_Part_322517_897132115.1748879428552"
------=_Part_322517_897132115.1748879428552
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
*>>> You can always purchase new BTC to perform the commitment.*Jonathan's=
=20
was probably referring to the public-key being exposed when performing the=
=20
commitment (since this would defeat the purpose).
From first post from Tadge in this thread, the payment needs to be made out=
=20
of band, so the public key isn't exposed during the commitment phase:
>>> get that txid into an OP_RETURN output somehow (paying a miner out of=
=20
band, etc)
On Monday, June 2, 2025 at 6:53:55=E2=80=AFAM UTC-7 Peter Todd wrote:
> On Fri, May 30, 2025 at 03:00:41PM -0700, Jonathan Voss wrote:
> > As far as I can tell, the main flaw in commit/reveal protocols is in th=
e=20
> > commit phase: if revealing a commitment with N confirmations is require=
d=20
> to=20
> > spend bitcoins, then, without spending any bitcoins, how do you get the=
=20
> > commitment into the blockchain in the first place? Maybe I am just=20
> > misunderstanding this. If so, then a commit/reveal scheme may be a=20
> workable=20
> > solution.
>
> You can always purchase new BTC to perform the commitment.
>
> Indeed, this problem is often seen in alt-coins where fees must be paid i=
n=20
> a
> native asset, while users are trying to send some kind of tokenized asset=
=20
> like
> a USD token. You can have funds that you can't move because you don't hav=
e=20
> the
> correct asset. While annoying, this isn't a fatal problem.
>
> --=20
> https://petertodd.org 'peter'[:-1]@petertodd.org
>
--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
77c90109-6f21-4f92-b122-0a7034fb1a87n%40googlegroups.com.
------=_Part_322517_897132115.1748879428552
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div><i>>>>
You can always purchase new BTC to perform the commitment.<br /><br /></i>J=
onathan's was probably referring to the public-key being exposed when perfo=
rming the commitment (since this would defeat the purpose).<br /><br />From=
first post from Tadge in this thread, the payment needs to be made out of =
band, so the public key isn't exposed during the commitment phase:</div><di=
v>>>>
get that txid into an OP_RETURN output somehow (paying a miner out of band,=
etc)<br /><br /></div><br /><div class=3D"gmail_quote"><div dir=3D"auto" c=
lass=3D"gmail_attr">On Monday, June 2, 2025 at 6:53:55=E2=80=AFAM UTC-7 Pet=
er Todd wrote:<br/></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;=
">On Fri, May 30, 2025 at 03:00:41PM -0700, Jonathan Voss wrote:
<br>> As far as I can tell, the main flaw in commit/reveal protocols is =
in the=20
<br>> commit phase: if revealing a commitment with N confirmations is re=
quired to=20
<br>> spend bitcoins, then, without spending any bitcoins, how do you ge=
t the=20
<br>> commitment into the blockchain in the first place? Maybe I am just=
=20
<br>> misunderstanding this. If so, then a commit/reveal scheme may be a=
workable=20
<br>> solution.
<br>
<br>You can always purchase new BTC to perform the commitment.
<br>
<br>Indeed, this problem is often seen in alt-coins where fees must be paid=
in a
<br>native asset, while users are trying to send some kind of tokenized ass=
et like
<br>a USD token. You can have funds that you can't move because you don=
't have the
<br>correct asset. While annoying, this isn't a fatal problem.
<br>
<br>--=20
<br><a href=3D"https://petertodd.org" target=3D"_blank" rel=3D"nofollow" da=
ta-saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://pe=
tertodd.org&source=3Dgmail&ust=3D1748964386849000&usg=3DAOvVaw0=
KR8uNFJVVpVuK9rkfpmml">https://petertodd.org</a> 'peter'[:-1]@<a hr=
ef=3D"http://petertodd.org" target=3D"_blank" rel=3D"nofollow" data-safered=
irecturl=3D"https://www.google.com/url?hl=3Den&q=3Dhttp://petertodd.org=
&source=3Dgmail&ust=3D1748964386849000&usg=3DAOvVaw1x4lf-hsoLGV=
FeP1yG2iuC">petertodd.org</a>
<br></blockquote></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/77c90109-6f21-4f92-b122-0a7034fb1a87n%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/77c90109-6f21-4f92-b122-0a7034fb1a87n%40googlegroups.com</a>.<br />
------=_Part_322517_897132115.1748879428552--
------=_Part_322516_1630944952.1748879428552--
|
