summaryrefslogtreecommitdiff
path: root/5b/9e05e0020aaa71190c54c3e0b1a3837270dafb
blob: 6a3052d79f65efbd24fdd27816b3688d71a52be1 (plain)
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
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
Delivery-date: Fri, 02 May 2025 08:28:43 -0700
Received: from mail-qv1-f60.google.com ([209.85.219.60])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBC7YL44NVYFRBIOJ2PAAMGQEMB2GPQQ@googlegroups.com>)
	id 1uAsJe-0006kh-SY
	for bitcoindev@gnusha.org; Fri, 02 May 2025 08:28:43 -0700
Received: by mail-qv1-f60.google.com with SMTP id 6a1803df08f44-6ecfbdaaee3sf39936536d6.3
        for <bitcoindev@gnusha.org>; Fri, 02 May 2025 08:28:43 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1746199717; cv=pass;
        d=google.com; s=arc-20240605;
        b=EtRsd9Bs0Q0FT7UcMz6s7oXuE0lWDDlpYfRGr0QC+Mq59PhYp1KLYMg8l6CI92X0Mi
         11q5C4LzQ+6VpSRdWzrztFyoCBt5AJvjBeLK5iz+0bvlEvISxkDVDYapnptwe/mLTMBn
         y6chO0lIfDaZhYtGNpAZz6D8T9N0mYPiHG2VPhZquYZ8u2SSp/kJxZKnHK2emJwa+nVb
         i7K2Q9+eR6jUpFn3cTerkFP4qEkR6D6d27R33cotKjzV8Xf2hX0qdJbEMSGv+FV/mYeW
         vX6cfIkmBSLo5Nwcp40UrNmnsRrW4HuPBV/BSYeZ9OiO9zW2AimF5P6k6OHv1m/xfgA/
         uGDA==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:cc:to:subject:message-id:date:from
         :in-reply-to:references:mime-version:sender:dkim-signature
         :dkim-signature;
        bh=P9hUJ5NN14AwmifR86AZE2x2HXbqQGhR/Id3aQaRoTM=;
        fh=X2y2sN0ctlYXwAuvcO8MLXpFezNhmbpK4SdfBXMKsUQ=;
        b=W7zXgwbZxahcveQWiwtekMDBUl36QorSQ6VwSucSvzQW6UWbFdZxroyYETRIZxqeNL
         SqQCluw9lrm2d/7g6lvr8Lj/J9qdoKZc8QZDjlwoJ7053n8r+e8Z/RLEKKir8lno0svD
         agC1KneOnjRl4uSalRTbrvEx3tNw69jHLO75hqntCVC6U1HDze+mNlrt/r5fX78yL2I9
         t/uu/L5tdfjHUxJUdeNvshV4iupoyAWbuBBlS8BXNOtosPBhX/gbLHg6xBmGcuPz8M04
         NivYpSF2Y8Fhhr+I2orV0L8H8hscbUfzBmfQUSdyjgb2wGY2HEV9GMF6zRQKoupPmTvG
         Zx6g==;
        darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
       dkim=pass header.i=@gmail.com header.s=20230601 header.b=DMlsgUNp;
       spf=pass (google.com: domain of saintwenhao@gmail.com designates 2a00:1450:4864:20::642 as permitted sender) smtp.mailfrom=saintwenhao@gmail.com;
       dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com;
       dara=pass header.i=@googlegroups.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1746199717; x=1746804517; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:sender:from:to:cc:subject:date:message-id
         :reply-to;
        bh=P9hUJ5NN14AwmifR86AZE2x2HXbqQGhR/Id3aQaRoTM=;
        b=WL74ot9WDdzqHa0k1wHRlGF/MT4sOcpB49P4ujVcWlonriS1QilncDLt/9yU6cRi4/
         AKQMNtwvdhViysnkAZ16H+23QCr4z+/plSmRneRUio7YR+wYTLxqgmSuBTJDc85G1LUo
         pboAS3Bg99dausv2LqMx1/5UZyDcOjC13yDHBwYDqoTS6BLbvJmfjFiZQs5czqhBUpMV
         uOirheBVJ4ud6N+Jown5bw182+lXXgv4sCUDKNenF8zK6GJZcrxwCxRBnlRRl/G5ijzZ
         vfXp8ynzRVnfP+8v9HrhByQ0VrUw+n9OfFKk95tl5FqqT/FmMqNIcyaQy6RkU0MofsWh
         cs9A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1746199717; x=1746804517; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:from:to:cc:subject:date:message-id:reply-to;
        bh=P9hUJ5NN14AwmifR86AZE2x2HXbqQGhR/Id3aQaRoTM=;
        b=gYmXUo9lHbb7pIcyDSBPT8yi7Dot8Ge2OqL+WUaPoJRTM+jBxF+1ZWRvOlMFiN6c2M
         wq5eV4cgL+jlfMNlmpkwcIunc5s/4qog21qpHjf3GLweP9Rcy3Rk+l1BPw4DpeWrT0yi
         mX8KaNcHmXpqnM9/wzu6TV9vgml3OJVrEEVPPnVNkNovLaL3GrsZOmsrFMOfrbzUcz8X
         xc/n+we0SD3mEubCLV7Ft7KCIlNeM1x5f2i2SjNVZcVGxM5oulJMQ2RTyxBMXv9da+iL
         1LFjn8btwn1/+QKT3zCJccOPwGk/uqz8SuCN+D+prsLR0In8Tlj+BI9bFE60Yx05lSYo
         dSzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1746199717; x=1746804517;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:x-beenthere:x-gm-message-state:sender:from
         :to:cc:subject:date:message-id:reply-to;
        bh=P9hUJ5NN14AwmifR86AZE2x2HXbqQGhR/Id3aQaRoTM=;
        b=LtrMHI4LTfITa7wKn5ZtIt0FeVwddDKtjG5k3zuPtbOX3RM5ClOaBm/CL+YpS9bNwN
         ermyddfIpCM1UIHjHdL/OXi9nUdB/7zXPRHbmCDrjnqIEgM1AMWfPaVfVp1guxRhk30a
         3FkQ15DE4a17L43Ks+Vr5rlidR3bEGxjIIBoJq0Cf2GXbMxZfdW257gEdfd2jVkT53pb
         SSz8cL8siGOvDMrOn34UchY9mRTbg3v303X4QRBFE+4Q0onzF9CTrBCFQYOQfP1cLRMe
         glxs0p33GdF455u6ZY6T1oAqw+ShpFhaaQQH1+4r7c0X/HSqgE0uXWTqkpFEfwYWLvYh
         Z0UA==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCWFfk9VhYe4JtiF0lze1vfxI9wd8rzhNbXavOcq0ssrlP45qwW0L/dz88Z9c9ofVIqQuL7OdnvzKfXM@gnusha.org
X-Gm-Message-State: AOJu0YxtpLwAY8XhJLgrPmQ2aLkzB4LsBEbNMIcnccn6DPW6hHCofwie
	giC/wXkIyJU86e+TOebTcwNGH9EDxf76hAF2NPKzms0Z8dO3rnTx
X-Google-Smtp-Source: AGHT+IHZAt/GdN145J5c7krTfrIm835xo/TPT5IIE6uIFkuYy1WKrm/hjywDJVjfqnz1jwMiG2gNbQ==
X-Received: by 2002:a05:6214:d0e:b0:6e8:fbb7:6764 with SMTP id 6a1803df08f44-6f51564fcd3mr48246086d6.45.1746199716468;
        Fri, 02 May 2025 08:28:36 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=AVT/gBEtjdpPStwYxShynR/SdfzJn5s8PvpxQaiH4HcQzEUf6A==
Received: by 2002:a05:6214:5018:b0:6d8:b1cf:a07d with SMTP id
 6a1803df08f44-6f5084f5448ls34816386d6.2.-pod-prod-02-us; Fri, 02 May 2025
 08:28:33 -0700 (PDT)
X-Forwarded-Encrypted: i=2; AJvYcCXDzDNNoD5M5pG51WNyfp3+hWYl36HcVPmpfm05OdWqc+2gO4ncIFM24Vw0WRcrKq2EhGZ9n0X6QDAL@googlegroups.com
X-Received: by 2002:a05:620a:318c:b0:7c7:a5b7:b288 with SMTP id af79cd13be357-7cad5b3fe4amr407885485a.19.1746199713280;
        Fri, 02 May 2025 08:28:33 -0700 (PDT)
Received: by 2002:a05:600c:5903:b0:43c:fe31:d01d with SMTP id 5b1f17b1804b1-441bbdf626dms5e9;
        Fri, 2 May 2025 06:58:16 -0700 (PDT)
X-Forwarded-Encrypted: i=2; AJvYcCVW5eFJEt+dnX67OIUknHMSEPGFXT1nAUztLK4S2mFQKKJ9yqxN4nlHL7TNI0rz/vuJxJ9QfpJGRn33@googlegroups.com
X-Received: by 2002:a05:600c:cc8:b0:43c:f6c6:578c with SMTP id 5b1f17b1804b1-441bbec6527mr31910085e9.15.1746194294539;
        Fri, 02 May 2025 06:58:14 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1746194294; cv=none;
        d=google.com; s=arc-20240605;
        b=JNKv3mNTPXW/33WQyKmSoJQntdvA+dusFeX7x+8X4jJpY5yXrkOzkWAeHnRqcmDQN8
         A/Bh3qmqUza9Qvo1bn1IKgjFvuz/blxiTwyUulCgL3auz4Qgvwlwjr2quSUnPAaTB2I7
         4rahso6uyTBrYJqsfpYZ3+M6KLaqw7sODRMdc6Nqo5AAq5tQ/GunAbLOahIbBS0DGXMD
         6O5HG+iCri/4evcW5Ani/LeICNftsOvtmekNNqvXWa4u5e7IEmHkJkG5/0JcupQGVmUS
         tvTq1cv1UgHojO/lNWj7SigZN1za/Nb0GLGdT8AsaTdF5/nTmR5ilPQEN5iRs9uecqyt
         V15g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:dkim-signature;
        bh=oJavvNknjs50206AzQGTZF85wFXIIb7y3+WStwT78wE=;
        fh=6SoNPnXK7Xt8npCazC2LjQO6KFhFUtRgm4RZtEzftkM=;
        b=j6u021lxWch77ll+wb2DXWUzXRgsQWPOnLOht2kcbqdRGW5vk8x8k7r0yQclF2gacS
         KM3oH3xRI2fMxjhLT3hBoBNyDGAC/RQtZ3Ub/cjJZvRqOD7chcnG0DXY9MfZ1J8ZNIZq
         /qd++dn8wYT+D5VbXQe5M4JYN8ap4sXKWpoaBxXidvNWp3iCTH4g1rOokJnuQc9JhLsz
         dxAsN7HWXb/x66ymwvMGNeB+gubrYQ3m6haKNBtuDtzWwti3YiGAwno3Hvo6GOIX2e0n
         BBKXLcXk+ROo+TXJRhPuxWgoyUT2gTrDOG9El3JMzaGdhuUyuLbd5ZzDD1byhDxD1rDO
         2jdA==;
        dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
       dkim=pass header.i=@gmail.com header.s=20230601 header.b=DMlsgUNp;
       spf=pass (google.com: domain of saintwenhao@gmail.com designates 2a00:1450:4864:20::642 as permitted sender) smtp.mailfrom=saintwenhao@gmail.com;
       dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com;
       dara=pass header.i=@googlegroups.com
Received: from mail-ej1-x642.google.com (mail-ej1-x642.google.com. [2a00:1450:4864:20::642])
        by gmr-mx.google.com with ESMTPS id 5b1f17b1804b1-441ae3fa9e2si1830545e9.1.2025.05.02.06.58.14
        for <bitcoindev@googlegroups.com>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Fri, 02 May 2025 06:58:14 -0700 (PDT)
Received-SPF: pass (google.com: domain of saintwenhao@gmail.com designates 2a00:1450:4864:20::642 as permitted sender) client-ip=2a00:1450:4864:20::642;
Received: by mail-ej1-x642.google.com with SMTP id a640c23a62f3a-ac2dfdf3c38so374309066b.3
        for <bitcoindev@googlegroups.com>; Fri, 02 May 2025 06:58:14 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCWViVsMTOB+bv5wEZJ3h8ks39Qfq0u1ULUe8n2terojgGnsjCOU2QYNa6vPRyUdQSfwichGYIJyTVQA@googlegroups.com
X-Gm-Gg: ASbGncv13BhX+hMUNgKHFSzGr/loG8wDqoxF/khNCvKV5xH4hbdf6OFlSgDs9jPJjt1
	Iiv4yMhwu4KR85Lch/49yeODcD4xdu9jDnqubrBlwkg1HAnrz3UMImIVdoi/GB4+hF6VeWbJqg1
	06HH8v49ZVAYHF9DT6bhfjAg==
X-Received: by 2002:a17:906:9c8c:b0:ac2:d0e6:2b99 with SMTP id
 a640c23a62f3a-ad17adc78d2mr274860566b.36.1746194293866; Fri, 02 May 2025
 06:58:13 -0700 (PDT)
MIME-Version: 1.0
References: <db3d0ec4-90b8-44a4-b912-b98ec9083b10n@googlegroups.com>
 <c3b9617f-b419-4fc0-9a00-5d1866f80920n@googlegroups.com> <CAFC_Vt6c_DwmpCzNVCRWzz9E2AGn0PpkZzLeYeGNE1tYbUzyOA@mail.gmail.com>
 <CAJDmzYyAb4GT+rdpF8ndAcFrFziQyO=QpA36m1T8gw0LTLLg-g@mail.gmail.com>
In-Reply-To: <CAJDmzYyAb4GT+rdpF8ndAcFrFziQyO=QpA36m1T8gw0LTLLg-g@mail.gmail.com>
From: Saint Wenhao <saintwenhao@gmail.com>
Date: Fri, 2 May 2025 15:58:02 +0200
X-Gm-Features: ATxdqUE9sKfDlmLsrbaSiu7cMFeZE37fYzrj4YGyp-DIHI0hGBYEXhMu-c_AaFY
Message-ID: <CACgYNOKXtmN7dwCX63UBhc4GhMAUOuaYKMfyj4Aa8-qv3v8c_Q@mail.gmail.com>
Subject: Re: [bitcoindev] Re: Introducing Hourglass
To: Agustin Cruz <agustin.cruz@gmail.com>
Cc: Nagaev Boris <bnagaev@gmail.com>, Michael Tidwell <michael@tidwell.io>, 
	Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Content-Type: multipart/alternative; boundary="0000000000009847db0634278a13"
X-Original-Sender: saintwenhao@gmail.com
X-Original-Authentication-Results: gmr-mx.google.com;       dkim=pass
 header.i=@gmail.com header.s=20230601 header.b=DMlsgUNp;       spf=pass
 (google.com: domain of saintwenhao@gmail.com designates 2a00:1450:4864:20::642
 as permitted sender) smtp.mailfrom=saintwenhao@gmail.com;       dmarc=pass
 (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com;       dara=pass header.i=@googlegroups.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 (/)

--0000000000009847db0634278a13
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> coins that don=E2=80=99t make the jump are effectively burned or otherwis=
e
invalidated by consensus, so there=E2=80=99s nothing left for an attacker t=
o sign

If you require the classical ECDSA signature, and a quantum-resistant one,
then it will make coins "trapped", instead of "burned". And I think it is
better, because then, if some quantum-resistant algorithm will be broken
for any reason (some of them were broken classically), then it will be
possible to go back to ECDSA, and soft-fork-out of the upgraded version by
doing a downgrade, and switching to a different quantum-resistant scheme.

Also, as long as ECDSA is not fully broken, the implementation of all of
that will still be needed, to validate all historical blocks.

And of course in some cases, it may be still possible to prove, that you
are the original owner of the coin, for example if some key is a part of
some HD wallet. By making funds unspendable, instead of trapped, you break
all ways of accepting such proofs in the future.

pt., 2 maj 2025 o 13:06 Agustin Cruz <agustin.cruz@gmail.com> napisa=C5=82(=
a):

> Hi everyone,
> Boris=E2=80=99 point about a quantum capable attacker simply broadcasting=
 and self
> mining at the same time is exactly the scenario that pushed me toward the
> QRAMP idea in the first place. Rather than trying to chase a well funded
> adversary around the mempool, QRAMP proposal says: let=E2=80=99s set a fi=
rm
> deadline and make every unspent P2PK output move to a quantum safe addres=
s
> before it arrives. Once the block height or a date passes, anything that
> stayed behind just stops being spendable. Holders who migrate on time kee=
p
> full control; coins that don=E2=80=99t make the jump are effectively burn=
ed or
> otherwise invalidated by consensus, so there=E2=80=99s nothing left for a=
n attacker
> to sign.
>
> Regards,
> Agust=C3=ADn
>
> On Thu, May 1, 2025 at 2:07=E2=80=AFPM Nagaev Boris <bnagaev@gmail.com> w=
rote:
>
>> On Wed, Apr 30, 2025 at 12:26=E2=80=AFAM Michael Tidwell <michael@tidwel=
l.io>
>> wrote:
>> > - 2. Single Entity rush spends:
>> > A single entity generates QC signatures and tries to rapidly flip the
>> UTXOs while having their first mover competitive edge. They either
>> broadcast to the mempool, partner with miners, or mine directly. This
>> creates potential miner collusion if P2PK fees remain low, pressuring th=
e
>> QC entity to raise fees and incentivize miners before their competitive
>> advantage expires and others catch up.
>> >
>> [...]
>> >
>> > - 4. Patient Miner:
>> > A single QC capable entity, also operating as a miner or partners with
>> a miner, chooses to be patient, including P2PK transactions only in thei=
r
>> own blocks to maximize long-term profits.
>>
>> IMHO for a single QC capable entity even if it mines itself or
>> partners with a miner, it would make sense to broadcast the
>> transaction publicly. If it doesn't broadcast, then it can only
>> capture one UTXO when it mines a block - rarely, depending on their
>> hashrate share. If it mines itself and broadcasts at the same time,
>> there is a possibility that another miner includes the transaction
>> into a block. So a rational QC capable entity would broadcast in
>> addition to mine themselves.
>>
>> Also it would make sense to use different UTXOs for broadcasting and
>> for self mining: if another miner mines one UTXO, the QC entity can
>> continue mining another UTXO trying to mine the next block with it. If
>> they use the same UTXO, they would have to quickly make a signature
>> for a fresh UTXO for their own block. Or just have a pool of attacked
>> UTXOs and take them one by one...
>>
>> --
>> Best regards,
>> Boris Nagaev
>>
>> --
>> You received this message because you are subscribed to the Google Group=
s
>> "Bitcoin Development Mailing List" group.
>> To unsubscribe from this group and stop receiving emails from it, send a=
n
>> email to bitcoindev+unsubscribe@googlegroups.com.
>> To view this discussion visit
>> https://groups.google.com/d/msgid/bitcoindev/CAFC_Vt6c_DwmpCzNVCRWzz9E2A=
Gn0PpkZzLeYeGNE1tYbUzyOA%40mail.gmail.com
>> .
>>
> --
> 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
> email to bitcoindev+unsubscribe@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/CAJDmzYyAb4GT%2BrdpF8ndAcFrF=
ziQyO%3DQpA36m1T8gw0LTLLg-g%40mail.gmail.com
> <https://groups.google.com/d/msgid/bitcoindev/CAJDmzYyAb4GT%2BrdpF8ndAcFr=
FziQyO%3DQpA36m1T8gw0LTLLg-g%40mail.gmail.com?utm_medium=3Demail&utm_source=
=3Dfooter>
> .
>

--=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/=
CACgYNOKXtmN7dwCX63UBhc4GhMAUOuaYKMfyj4Aa8-qv3v8c_Q%40mail.gmail.com.

--0000000000009847db0634278a13
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt; coins that don=E2=80=99t make the jump are effectivel=
y burned or otherwise invalidated by consensus, so there=E2=80=99s nothing =
left for an attacker to sign<br><br>If you require the classical ECDSA sign=
ature, and a quantum-resistant one, then it will make coins &quot;trapped&q=
uot;, instead of &quot;burned&quot;. And I think it is better, because then=
, if some quantum-resistant algorithm will be broken for any reason (some o=
f them were broken classically), then it will be possible to go back to ECD=
SA, and soft-fork-out of the upgraded version by doing a downgrade, and swi=
tching to a different quantum-resistant scheme.<br><br>Also, as long as ECD=
SA is not fully broken, the implementation of all of that will still be nee=
ded, to validate all historical blocks.<br><br>And of course in some cases,=
 it may be still possible to prove, that you are the original owner of the =
coin, for example if some key is a part of some HD wallet. By making funds =
unspendable, instead of trapped, you break all ways of accepting such proof=
s in the future.</div><br><div class=3D"gmail_quote gmail_quote_container">=
<div dir=3D"ltr" class=3D"gmail_attr">pt., 2 maj 2025 o 13:06=C2=A0Agustin =
Cruz &lt;<a href=3D"mailto:agustin.cruz@gmail.com">agustin.cruz@gmail.com</=
a>&gt; napisa=C5=82(a):<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div dir=3D"ltr"><div dir=3D"ltr">Hi everyone,<br>Boris=E2=80=99 po=
int about a quantum capable attacker simply broadcasting and self mining at=
 the same time is exactly the scenario that pushed me toward the QRAMP idea=
 in the first place. Rather than trying to chase a well funded adversary ar=
ound the mempool, QRAMP proposal says: let=E2=80=99s set a firm deadline an=
d make every unspent P2PK output move to a quantum safe address before it a=
rrives. Once the block height or a date passes, anything that stayed behind=
 just stops being spendable. Holders who migrate on time keep full control;=
 coins that don=E2=80=99t make the jump are effectively burned or otherwise=
 invalidated by consensus, so there=E2=80=99s nothing left for an attacker =
to sign.<br><br>Regards,<br>Agust=C3=ADn</div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 1, 2025 at 2:07=E2=80=
=AFPM Nagaev Boris &lt;<a href=3D"mailto:bnagaev@gmail.com" target=3D"_blan=
k">bnagaev@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex">On Wed, Apr 30, 2025 at 12:26=E2=80=AFAM Michael Tidwel=
l &lt;<a href=3D"mailto:michael@tidwell.io" target=3D"_blank">michael@tidwe=
ll.io</a>&gt; wrote:<br>
&gt; - 2. Single Entity rush spends:<br>
&gt; A single entity generates QC signatures and tries to rapidly flip the =
UTXOs while having their first mover competitive edge. They either broadcas=
t to the mempool, partner with miners, or mine directly. This creates poten=
tial miner collusion if P2PK fees remain low, pressuring the QC entity to r=
aise fees and incentivize miners before their competitive advantage expires=
 and others catch up.<br>
&gt;<br>
[...]<br>
&gt;<br>
&gt; - 4. Patient Miner:<br>
&gt; A single QC capable entity, also operating as a miner or partners with=
 a miner, chooses to be patient, including P2PK transactions only in their =
own blocks to maximize long-term profits.<br>
<br>
IMHO for a single QC capable entity even if it mines itself or<br>
partners with a miner, it would make sense to broadcast the<br>
transaction publicly. If it doesn&#39;t broadcast, then it can only<br>
capture one UTXO when it mines a block - rarely, depending on their<br>
hashrate share. If it mines itself and broadcasts at the same time,<br>
there is a possibility that another miner includes the transaction<br>
into a block. So a rational QC capable entity would broadcast in<br>
addition to mine themselves.<br>
<br>
Also it would make sense to use different UTXOs for broadcasting and<br>
for self mining: if another miner mines one UTXO, the QC entity can<br>
continue mining another UTXO trying to mine the next block with it. If<br>
they use the same UTXO, they would have to quickly make a signature<br>
for a fresh UTXO for their own block. Or just have a pool of attacked<br>
UTXOs and take them one by one...<br>
<br>
-- <br>
Best regards,<br>
Boris Nagaev<br>
<br>
-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev%2Bunsubscribe@googlegroups.com" target=
=3D"_blank">bitcoindev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/CAFC_Vt6c_DwmpCzNVCRWzz9E2AGn0PpkZzLeYeGNE1tYbUzyOA%40mail.gmail=
.com" rel=3D"noreferrer" target=3D"_blank">https://groups.google.com/d/msgi=
d/bitcoindev/CAFC_Vt6c_DwmpCzNVCRWzz9E2AGn0PpkZzLeYeGNE1tYbUzyOA%40mail.gma=
il.com</a>.<br>
</blockquote></div></div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; 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" target=
=3D"_blank">bitcoindev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/CAJDmzYyAb4GT%2BrdpF8ndAcFrFziQyO%3DQpA36m1T8gw0LTLLg-g%40mail.g=
mail.com?utm_medium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">http=
s://groups.google.com/d/msgid/bitcoindev/CAJDmzYyAb4GT%2BrdpF8ndAcFrFziQyO%=
3DQpA36m1T8gw0LTLLg-g%40mail.gmail.com</a>.<br>
</blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; 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/CACgYNOKXtmN7dwCX63UBhc4GhMAUOuaYKMfyj4Aa8-qv3v8c_Q%40mail.gmail=
.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/ms=
gid/bitcoindev/CACgYNOKXtmN7dwCX63UBhc4GhMAUOuaYKMfyj4Aa8-qv3v8c_Q%40mail.g=
mail.com</a>.<br />

--0000000000009847db0634278a13--