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
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
|
Delivery-date: Wed, 16 Oct 2024 17:55:27 -0700
Received: from mail-yb1-f184.google.com ([209.85.219.184])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBCM7BC7H6ENRB5WAYG4AMGQEOR72B4Y@googlegroups.com>)
id 1t1EnW-0003ES-NB
for bitcoindev@gnusha.org; Wed, 16 Oct 2024 17:55:27 -0700
Received: by mail-yb1-f184.google.com with SMTP id 3f1490d57ef6-e29135d1d0csf784108276.1
for <bitcoindev@gnusha.org>; Wed, 16 Oct 2024 17:55:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1729126520; x=1729731320; 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:message-id:to:from:date:sender:from:to:cc:subject:date
:message-id:reply-to;
bh=aAEQr2RbN4iP5pKnubWlD8ukpsmPjT9FdmL/ggPhHUg=;
b=jBHffL5MNPhf/KSXXlMuZsn+pIF9aqtucKWFAEqensU+TPBKH35Ooi5IpvPQhQmwxG
sy1njyrbgEYGIq5SSA/ioXDW/cSKorP2TGMt+V10x6pgnASk+9CD0CFRELBlYGv6oxI5
j7TvXedmhNcoFJ6Eoh1xJ/FLVeSpwY2wxfSivh9r+ZkUGTpTGtBj2yOO8wJS5VLxGCqA
HKif2CtddbtImejwxzUEveGwGlIVgNAIS8QKw4f6phkY5Zq1YjJ/oZ9NRvzLJE5tLSMF
4JOBXA+GunaSCngFjrGUClflgETN5I8QCaarJ/7iLOzBGbJ0xSNcREsYQ8azoKxpIkFf
UfcA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1729126520; x=1729731320; 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:message-id:to:from:date:from:to:cc:subject:date:message-id
:reply-to;
bh=aAEQr2RbN4iP5pKnubWlD8ukpsmPjT9FdmL/ggPhHUg=;
b=fKdradQ1zrMele6SOzQl1oR5iGRyl2rzD3Gt6oXgkuTtPoZD+DcNed80mTxidfHdPM
Pe1pA7unbsEJLj3UioEs92UD08KyXWtDFQoNsXuCYK06pgogVcQXTwsd92e5rzW/zV+6
22NB8PHSwpSRLEmZcyQVlaJxi/bcNJmY/9X36StQBBqVxD/Px3cUATdVfWEJgOOo4juD
gmPUwSv+/GCqpafk4K+HHRvD+JUkYuGpnAm3QlwzwUdgUJoZ0LwTu3SmF39eF8PPqCTA
tRw0s2k0tpJkYled8sOkRJFIoBTYglHW1gNTT9K5VTth1gLDdfaPpA+BeJIPk1IUNVXe
FsMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1729126520; x=1729731320;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:message-id:to:from:date:x-beenthere:x-gm-message-state
:sender:from:to:cc:subject:date:message-id:reply-to;
bh=aAEQr2RbN4iP5pKnubWlD8ukpsmPjT9FdmL/ggPhHUg=;
b=OHkTXSlaBfeqed3PuiJ+0KvAxJnKuFRLyCv+bjcj3ZQl4tPQrDrlONHFWptrZ9Yy8a
89H6S897KcgfVDuAi0S/Ds7iry+S/pXoUilt7a7K4K8aesH7Vomjvj0i/guPJIw/waIa
Wzdb7ceuf/sQ9nSLaKh1drlyU/v6c7ctkygmFIwbRCtB7d3LnF6kUOShK5Z37lU+Ql3o
r5zxHeGwC7RDe+ttPjkpHH4bLJ85lQGN454QBJJPeBU841OOX5EQ4Y2LtkvOrgKsSCan
J/SMTqOPJ8mm0DiCFIM8EjNlm5iJv72hzUxFGi/aAJ9tO5j59IpqzmWpK2FcCRPrJAG1
Pz/A==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCUyPedqeZ/ZJINUb5PlT/X0E5C30+NLlH8l7LRHRU6Av+1KsAiXBBQDVh/XSCbkzUIqo8keSB9gF88o@gnusha.org
X-Gm-Message-State: AOJu0YyfyFQZzGla+Zoiw+1zmu1Ggzon09h0bjP7LtpL5L9KaKy7DYOZ
/ikfygVxcYhZ1Yg/yX8e8FJsK6FT5ghLtHDUJoiXoSxeE8e2KnMl
X-Google-Smtp-Source: AGHT+IEqTzsV56+aCU69Tx/Nb5RoLEAEEIuLB6LlTiryU+FgyzWSdF9V0in7sy1PrWftc7JmQ8RJcQ==
X-Received: by 2002:a05:6902:1611:b0:e29:948:55fc with SMTP id 3f1490d57ef6-e2919d61598mr19010823276.10.1729126520111;
Wed, 16 Oct 2024 17:55:20 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a05:6902:726:b0:e28:e985:da9 with SMTP id
3f1490d57ef6-e2b9ce33831ls534781276.2.-pod-prod-07-us; Wed, 16 Oct 2024
17:55:17 -0700 (PDT)
X-Received: by 2002:a05:690c:d8f:b0:6e0:5d7:8432 with SMTP id 00721157ae682-6e3d407c534mr62311027b3.5.1729126517835;
Wed, 16 Oct 2024 17:55:17 -0700 (PDT)
Received: by 2002:a05:690c:dd0:b0:6dd:f386:13dc with SMTP id 00721157ae682-6e3d73b63d0ms7b3;
Wed, 16 Oct 2024 17:45:30 -0700 (PDT)
X-Received: by 2002:a05:6902:2003:b0:e29:20a5:8b26 with SMTP id 3f1490d57ef6-e2931bca88amr12862365276.43.1729125929997;
Wed, 16 Oct 2024 17:45:29 -0700 (PDT)
Date: Wed, 16 Oct 2024 17:45:29 -0700 (PDT)
From: scott beeker <devbythebay2@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <0e40068e-6840-49a2-a800-a1f34a0ad9ccn@googlegroups.com>
Subject: [bitcoindev] Hardforking Bitcoin to SLH-DSA (Future Proofing)
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_114668_576186209.1729125929768"
X-Original-Sender: devbythebay2@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_114668_576186209.1729125929768
Content-Type: multipart/alternative;
boundary="----=_Part_114669_1085048807.1729125929768"
------=_Part_114669_1085048807.1729125929768
Content-Type: text/plain; charset="UTF-8"
Hardforking Bitcoin to SLH-DSA
Bitcoin's transition to a post-quantum cryptographic algorithm like SLH-DSA
(Stateless Hash-Based Digital Signature Algorithm) would be a significant
and complex undertaking. Here's an analysis of the potential process and
implications:
Motivation for the Transition
The primary reason for considering a transition to SLH-DSA would be to
protect Bitcoin against potential threats from quantum computers. While
quantum computers capable of breaking Bitcoin's current elliptic curve
cryptography are not yet a reality, the cryptocurrency community is
increasingly aware of the need to prepare for this eventuality.
Technical Aspects of the Transition
Signature Scheme Replacement
The current Bitcoin protocol uses the Elliptic Curve Digital Signature
Algorithm (ECDSA) for transaction signatures. Replacing this with SLH-DSA
would require substantial changes to the core protocol[1].
Key and Signature Sizes
One of the main challenges in implementing SLH-DSA for Bitcoin would be
dealing with the increased key and signature sizes:
Algorithm
Public Key Size
Signature Size
ECDSA
33 bytes
71-73 bytes
SLH-DSA
32-64 bytes
7,856-49,216 bytes
The significantly larger signature sizes of SLH-DSA would have implications
for block size, transaction throughput, and network bandwidth
requirements[1].
Performance Considerations
SLH-DSA is known for its strong security properties but comes with
performance costs. It has longer signing times compared to ECDSA, which
could affect transaction processing speeds[1].
Implementation ChallengesConsensus Changes
Implementing SLH-DSA would require a hard fork of the Bitcoin network, as
it involves fundamental changes to the consensus rules. This would need
widespread agreement among miners, node operators, and users.
Backward Compatibility
The transition would need to address backward compatibility issues,
potentially requiring a period where both ECDSA and SLH-DSA signatures are
supported to allow users time to migrate their funds to new addresses.
Wallet Software Updates
All Bitcoin wallet software would need to be updated to support the new
signature scheme, including key generation, signing, and verification
processes.
Potential BenefitsQuantum Resistance
The primary benefit would be Bitcoin's resistance to attacks from quantum
computers, ensuring the long-term security of the network[1].
Conservative Security Approach
SLH-DSA is considered a conservative choice for post-quantum cryptography,
as it relies on the well-studied security of hash functions rather than
newer mathematical problems like lattices[1].
Potential DrawbacksIncreased Resource Requirements
The larger signature sizes would increase the storage and bandwidth
requirements for running Bitcoin nodes, potentially leading to increased
centralization.
Transaction Costs
Larger signatures could result in higher transaction fees, as more
blockchain space would be required for each transaction.
Complexity
The transition process itself would be complex and risky, potentially
introducing vulnerabilities if not executed correctly.
Conclusion
While transitioning Bitcoin to SLH-DSA is technically possible, it would be
a monumental undertaking requiring extensive planning, testing, and
community consensus. The cryptocurrency community would need to carefully
weigh the long-term security benefits against the short-term disruption and
increased resource requirements. As quantum computing advances, this topic
is likely to become increasingly relevant in discussions about Bitcoin's
future.
Citations:
[1] We wrote the code, and the code won | Trail of Bits Blog
https://blog.trailofbits.com/2024/08/15/we-wrote-the-code-and-the-code-won/
[2] SLotH -- An SLH-DSA/SPHINCS+ Hash-Based Signature Accelerator
https://github.com/slh-dsa/sloth
[3] Cryptographic Right Answers: Post Quantum Edition - Latacora
https://www.latacora.com/blog/2024/07/29/crypto-right-answers-pq/
Is your feature related to a problem, if so please describe it.
https://www.csoonline.com/article/3562701/chinese-researchers-break-rsa-encryption-with-a-quantum-computer.html/amp/
--
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 on the web visit https://groups.google.com/d/msgid/bitcoindev/0e40068e-6840-49a2-a800-a1f34a0ad9ccn%40googlegroups.com.
------=_Part_114669_1085048807.1729125929768
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<span dir=3D"auto" style=3D"box-sizing: border-box; font-size: 2em; margin-=
right: 0px; margin-left: 0px; line-height: 1.25; padding-bottom: 0.3em; col=
or: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemFont, "=
Segoe UI", "Noto Sans", Helvetica, Arial, sans-serif, "=
Apple Color Emoji", "Segoe UI Emoji";">Hardforking Bitcoin t=
o SLH-DSA</span><p dir=3D"auto" style=3D"box-sizing: border-box; margin-top=
: 0px; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemFo=
nt, "Segoe UI", "Noto Sans", Helvetica, Arial, sans-ser=
if, "Apple Color Emoji", "Segoe UI Emoji";">Bitcoin's t=
ransition to a post-quantum cryptographic algorithm like SLH-DSA (Stateless=
Hash-Based Digital Signature Algorithm) would be a significant and complex=
undertaking. Here's an analysis of the potential process and implications:=
</p><span dir=3D"auto" style=3D"box-sizing: border-box; font-size: 1.5em; l=
ine-height: 1.25; padding-bottom: 0.3em; color: rgb(31, 35, 40); font-famil=
y: -apple-system, BlinkMacSystemFont, "Segoe UI", "Noto Sans=
", Helvetica, Arial, sans-serif, "Apple Color Emoji", "=
Segoe UI Emoji";">Motivation for the Transition</span><p dir=3D"auto" =
style=3D"box-sizing: border-box; margin-top: 0px; color: rgb(31, 35, 40); f=
ont-family: -apple-system, BlinkMacSystemFont, "Segoe UI", "=
Noto Sans", Helvetica, Arial, sans-serif, "Apple Color Emoji"=
;, "Segoe UI Emoji";">The primary reason for considering a transi=
tion to SLH-DSA would be to protect Bitcoin against potential threats from =
quantum computers. While quantum computers capable of breaking Bitcoin's cu=
rrent elliptic curve cryptography are not yet a reality, the cryptocurrency=
community is increasingly aware of the need to prepare for this eventualit=
y.</p><span dir=3D"auto" style=3D"box-sizing: border-box; font-size: 1.5em;=
line-height: 1.25; padding-bottom: 0.3em; color: rgb(31, 35, 40); font-fam=
ily: -apple-system, BlinkMacSystemFont, "Segoe UI", "Noto Sa=
ns", Helvetica, Arial, sans-serif, "Apple Color Emoji", &quo=
t;Segoe UI Emoji";">Technical Aspects of the Transition=C2=A0<br /></s=
pan><span dir=3D"auto" style=3D"box-sizing: border-box; font-size: 1.25em; =
line-height: 1.25; color: rgb(31, 35, 40); font-family: -apple-system, Blin=
kMacSystemFont, "Segoe UI", "Noto Sans", Helvetica, Ari=
al, sans-serif, "Apple Color Emoji", "Segoe UI Emoji";"=
>Signature Scheme Replacement</span><p dir=3D"auto" style=3D"box-sizing: bo=
rder-box; margin-top: 0px; color: rgb(31, 35, 40); font-family: -apple-syst=
em, BlinkMacSystemFont, "Segoe UI", "Noto Sans", Helvet=
ica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji=
";">The current Bitcoin protocol uses the Elliptic Curve Digital Signa=
ture Algorithm (ECDSA) for transaction signatures. Replacing this with SLH-=
DSA would require substantial changes to the core protocol[1].</p><span dir=
=3D"auto" style=3D"box-sizing: border-box; font-size: 1.25em; line-height: =
1.25; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemFon=
t, "Segoe UI", "Noto Sans", Helvetica, Arial, sans-seri=
f, "Apple Color Emoji", "Segoe UI Emoji";">Key and Sign=
ature Sizes</span><p dir=3D"auto" style=3D"box-sizing: border-box; margin-t=
op: 0px; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystem=
Font, "Segoe UI", "Noto Sans", Helvetica, Arial, sans-s=
erif, "Apple Color Emoji", "Segoe UI Emoji";">One of th=
e main challenges in implementing SLH-DSA for Bitcoin would be dealing with=
the increased key and signature sizes:</p><span style=3D"box-sizing: borde=
r-box; display: block; color: rgb(31, 35, 40); font-family: -apple-system, =
BlinkMacSystemFont, "Segoe UI", "Noto Sans", Helvetica,=
Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji&quo=
t;;"><span role=3D"table" style=3D"box-sizing: border-box; border-spacing: =
0px; border-collapse: collapse; margin-top: 0px; display: block; width: max=
-content; max-width: 100%; overflow: auto;"><span style=3D"box-sizing: bord=
er-box;"><span style=3D"box-sizing: border-box;"><span style=3D"box-sizing:=
border-box; padding: 6px 13px;"><br />Algorithm</span><span style=3D"box-s=
izing: border-box; padding: 6px 13px;"><br />Public Key Size</span><span st=
yle=3D"box-sizing: border-box; padding: 6px 13px;"><br />Signature Size</sp=
an></span></span><span style=3D"box-sizing: border-box;"><span style=3D"box=
-sizing: border-box;"><span style=3D"box-sizing: border-box; padding: 6px 1=
3px;"><br />ECDSA</span><span style=3D"box-sizing: border-box; padding: 6px=
13px;"><br />33 bytes</span><span style=3D"box-sizing: border-box; padding=
: 6px 13px;"><br />71-73 bytes</span></span><span style=3D"box-sizing: bord=
er-box;"><span style=3D"box-sizing: border-box; padding: 6px 13px;"><br />S=
LH-DSA</span><span style=3D"box-sizing: border-box; padding: 6px 13px;"><br=
/>32-64 bytes</span><span style=3D"box-sizing: border-box; padding: 6px 13=
px;"><br />7,856-49,216 bytes</span></span></span></span></span><p dir=3D"a=
uto" style=3D"box-sizing: border-box; margin-top: 0px; color: rgb(31, 35, 4=
0); font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", &=
quot;Noto Sans", Helvetica, Arial, sans-serif, "Apple Color Emoji=
", "Segoe UI Emoji";">The significantly larger signature siz=
es of SLH-DSA would have implications for block size, transaction throughpu=
t, and network bandwidth requirements[1].</p><span dir=3D"auto" style=3D"bo=
x-sizing: border-box; font-size: 1.25em; line-height: 1.25; color: rgb(31, =
35, 40); font-family: -apple-system, BlinkMacSystemFont, "Segoe UI&quo=
t;, "Noto Sans", Helvetica, Arial, sans-serif, "Apple Color =
Emoji", "Segoe UI Emoji";">Performance Considerations</span>=
<p dir=3D"auto" style=3D"box-sizing: border-box; margin-top: 0px; color: rg=
b(31, 35, 40); font-family: -apple-system, BlinkMacSystemFont, "Segoe =
UI", "Noto Sans", Helvetica, Arial, sans-serif, "Apple =
Color Emoji", "Segoe UI Emoji";">SLH-DSA is known for its st=
rong security properties but comes with performance costs. It has longer si=
gning times compared to ECDSA, which could affect transaction processing sp=
eeds[1].</p><span dir=3D"auto" style=3D"box-sizing: border-box; font-size: =
1.5em; line-height: 1.25; padding-bottom: 0.3em; color: rgb(31, 35, 40); fo=
nt-family: -apple-system, BlinkMacSystemFont, "Segoe UI", "N=
oto Sans", Helvetica, Arial, sans-serif, "Apple Color Emoji"=
, "Segoe UI Emoji";">Implementation Challenges</span><span dir=3D=
"auto" style=3D"box-sizing: border-box; font-size: 1.25em; line-height: 1.2=
5; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemFont, =
"Segoe UI", "Noto Sans", Helvetica, Arial, sans-serif, =
"Apple Color Emoji", "Segoe UI Emoji";">Consensus Chang=
es</span><p dir=3D"auto" style=3D"box-sizing: border-box; margin-top: 0px; =
color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemFont, &qu=
ot;Segoe UI", "Noto Sans", Helvetica, Arial, sans-serif, &qu=
ot;Apple Color Emoji", "Segoe UI Emoji";">Implementing SLH-D=
SA would require a hard fork of the Bitcoin network, as it involves fundame=
ntal changes to the consensus rules. This would need widespread agreement a=
mong miners, node operators, and users.</p><span dir=3D"auto" style=3D"box-=
sizing: border-box; font-size: 1.25em; line-height: 1.25; color: rgb(31, 35=
, 40); font-family: -apple-system, BlinkMacSystemFont, "Segoe UI"=
, "Noto Sans", Helvetica, Arial, sans-serif, "Apple Color Em=
oji", "Segoe UI Emoji";">Backward Compatibility</span><p dir=
=3D"auto" style=3D"box-sizing: border-box; margin-top: 0px; color: rgb(31, =
35, 40); font-family: -apple-system, BlinkMacSystemFont, "Segoe UI&quo=
t;, "Noto Sans", Helvetica, Arial, sans-serif, "Apple Color =
Emoji", "Segoe UI Emoji";">The transition would need to addr=
ess backward compatibility issues, potentially requiring a period where bot=
h ECDSA and SLH-DSA signatures are supported to allow users time to migrate=
their funds to new addresses.</p><span dir=3D"auto" style=3D"box-sizing: b=
order-box; font-size: 1.25em; line-height: 1.25; color: rgb(31, 35, 40); fo=
nt-family: -apple-system, BlinkMacSystemFont, "Segoe UI", "N=
oto Sans", Helvetica, Arial, sans-serif, "Apple Color Emoji"=
, "Segoe UI Emoji";">Wallet Software Updates</span><p dir=3D"auto=
" style=3D"box-sizing: border-box; margin-top: 0px; color: rgb(31, 35, 40);=
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", &quo=
t;Noto Sans", Helvetica, Arial, sans-serif, "Apple Color Emoji&qu=
ot;, "Segoe UI Emoji";">All Bitcoin wallet software would need to=
be updated to support the new signature scheme, including key generation, =
signing, and verification processes.</p><span dir=3D"auto" style=3D"box-siz=
ing: border-box; font-size: 1.5em; line-height: 1.25; padding-bottom: 0.3em=
; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemFont, &=
quot;Segoe UI", "Noto Sans", Helvetica, Arial, sans-serif, &=
quot;Apple Color Emoji", "Segoe UI Emoji";">Potential Benefi=
ts</span><span dir=3D"auto" style=3D"box-sizing: border-box; font-size: 1.2=
5em; line-height: 1.25; color: rgb(31, 35, 40); font-family: -apple-system,=
BlinkMacSystemFont, "Segoe UI", "Noto Sans", Helvetica=
, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji&qu=
ot;;">Quantum Resistance</span><p dir=3D"auto" style=3D"box-sizing: border-=
box; margin-top: 0px; color: rgb(31, 35, 40); font-family: -apple-system, B=
linkMacSystemFont, "Segoe UI", "Noto Sans", Helvetica, =
Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji"=
;;">The primary benefit would be Bitcoin's resistance to attacks from quant=
um computers, ensuring the long-term security of the network[1].</p><span d=
ir=3D"auto" style=3D"box-sizing: border-box; font-size: 1.25em; line-height=
: 1.25; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemF=
ont, "Segoe UI", "Noto Sans", Helvetica, Arial, sans-se=
rif, "Apple Color Emoji", "Segoe UI Emoji";">Conservati=
ve Security Approach</span><p dir=3D"auto" style=3D"box-sizing: border-box;=
margin-top: 0px; color: rgb(31, 35, 40); font-family: -apple-system, Blink=
MacSystemFont, "Segoe UI", "Noto Sans", Helvetica, Aria=
l, sans-serif, "Apple Color Emoji", "Segoe UI Emoji";">=
SLH-DSA is considered a conservative choice for post-quantum cryptography, =
as it relies on the well-studied security of hash functions rather than new=
er mathematical problems like lattices[1].</p><span dir=3D"auto" style=3D"b=
ox-sizing: border-box; font-size: 1.5em; line-height: 1.25; padding-bottom:=
0.3em; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemF=
ont, "Segoe UI", "Noto Sans", Helvetica, Arial, sans-se=
rif, "Apple Color Emoji", "Segoe UI Emoji";">Potential =
Drawbacks</span><span dir=3D"auto" style=3D"box-sizing: border-box; font-si=
ze: 1.25em; line-height: 1.25; color: rgb(31, 35, 40); font-family: -apple-=
system, BlinkMacSystemFont, "Segoe UI", "Noto Sans", He=
lvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI E=
moji";">Increased Resource Requirements</span><p dir=3D"auto" style=3D=
"box-sizing: border-box; margin-top: 0px; color: rgb(31, 35, 40); font-fami=
ly: -apple-system, BlinkMacSystemFont, "Segoe UI", "Noto San=
s", Helvetica, Arial, sans-serif, "Apple Color Emoji", "=
;Segoe UI Emoji";">The larger signature sizes would increase the stora=
ge and bandwidth requirements for running Bitcoin nodes, potentially leadin=
g to increased centralization.</p><span dir=3D"auto" style=3D"box-sizing: b=
order-box; font-size: 1.25em; line-height: 1.25; color: rgb(31, 35, 40); fo=
nt-family: -apple-system, BlinkMacSystemFont, "Segoe UI", "N=
oto Sans", Helvetica, Arial, sans-serif, "Apple Color Emoji"=
, "Segoe UI Emoji";">Transaction Costs</span><p dir=3D"auto" styl=
e=3D"box-sizing: border-box; margin-top: 0px; color: rgb(31, 35, 40); font-=
family: -apple-system, BlinkMacSystemFont, "Segoe UI", "Noto=
Sans", Helvetica, Arial, sans-serif, "Apple Color Emoji", &=
quot;Segoe UI Emoji";">Larger signatures could result in higher transa=
ction fees, as more blockchain space would be required for each transaction=
.</p><span dir=3D"auto" style=3D"box-sizing: border-box; font-size: 1.25em;=
line-height: 1.25; color: rgb(31, 35, 40); font-family: -apple-system, Bli=
nkMacSystemFont, "Segoe UI", "Noto Sans", Helvetica, Ar=
ial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji";=
">Complexity</span><p dir=3D"auto" style=3D"box-sizing: border-box; margin-=
top: 0px; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSyste=
mFont, "Segoe UI", "Noto Sans", Helvetica, Arial, sans-=
serif, "Apple Color Emoji", "Segoe UI Emoji";">The tran=
sition process itself would be complex and risky, potentially introducing v=
ulnerabilities if not executed correctly.</p><span dir=3D"auto" style=3D"bo=
x-sizing: border-box; font-size: 1.5em; line-height: 1.25; padding-bottom: =
0.3em; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemFo=
nt, "Segoe UI", "Noto Sans", Helvetica, Arial, sans-ser=
if, "Apple Color Emoji", "Segoe UI Emoji";">Conclusion<=
/span><p dir=3D"auto" style=3D"box-sizing: border-box; margin-top: 0px; col=
or: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemFont, "=
Segoe UI", "Noto Sans", Helvetica, Arial, sans-serif, "=
Apple Color Emoji", "Segoe UI Emoji";">While transitioning B=
itcoin to SLH-DSA is technically possible, it would be a monumental underta=
king requiring extensive planning, testing, and community consensus. The cr=
yptocurrency community would need to carefully weigh the long-term security=
benefits against the short-term disruption and increased resource requirem=
ents. As quantum computing advances, this topic is likely to become increas=
ingly relevant in discussions about Bitcoin's future.</p><p dir=3D"auto" st=
yle=3D"box-sizing: border-box; margin-top: 0px; color: rgb(31, 35, 40); fon=
t-family: -apple-system, BlinkMacSystemFont, "Segoe UI", "No=
to Sans", Helvetica, Arial, sans-serif, "Apple Color Emoji",=
"Segoe UI Emoji";">Citations:<br style=3D"box-sizing: border-box=
;" />[1] We wrote the code, and the code won | Trail of Bits Blog=C2=A0<a h=
ref=3D"https://blog.trailofbits.com/2024/08/15/we-wrote-the-code-and-the-co=
de-won/" rel=3D"nofollow" style=3D"box-sizing: border-box; background-color=
: transparent; text-decoration-line: underline; text-underline-offset: 0.2r=
em;">https://blog.trailofbits.com/2024/08/15/we-wrote-the-code-and-the-code=
-won/</a><br style=3D"box-sizing: border-box;" />[2] SLotH -- An SLH-DSA/SP=
HINCS+ Hash-Based Signature Accelerator=C2=A0<a href=3D"https://github.com/=
slh-dsa/sloth" style=3D"box-sizing: border-box; background-color: transpare=
nt; text-decoration-line: underline; text-underline-offset: 0.2rem;">https:=
//github.com/slh-dsa/sloth</a><br style=3D"box-sizing: border-box;" />[3] C=
ryptographic Right Answers: Post Quantum Edition - Latacora=C2=A0<a href=3D=
"https://www.latacora.com/blog/2024/07/29/crypto-right-answers-pq/" rel=3D"=
nofollow" style=3D"box-sizing: border-box; background-color: transparent; t=
ext-decoration-line: underline; text-underline-offset: 0.2rem;">https://www=
.latacora.com/blog/2024/07/29/crypto-right-answers-pq/</a></p><span dir=3D"=
auto" style=3D"box-sizing: border-box; font-size: 1.25em; line-height: 1.25=
; color: rgb(31, 35, 40); font-family: -apple-system, BlinkMacSystemFont, &=
quot;Segoe UI", "Noto Sans", Helvetica, Arial, sans-serif, &=
quot;Apple Color Emoji", "Segoe UI Emoji";">Is your feature =
related to a problem, if so please describe it.</span><p dir=3D"auto" style=
=3D"box-sizing: border-box; margin-top: 0px; color: rgb(31, 35, 40); font-f=
amily: -apple-system, BlinkMacSystemFont, "Segoe UI", "Noto =
Sans", Helvetica, Arial, sans-serif, "Apple Color Emoji", &q=
uot;Segoe UI Emoji";"><a href=3D"https://www.csoonline.com/article/356=
2701/chinese-researchers-break-rsa-encryption-with-a-quantum-computer.html/=
amp/" rel=3D"nofollow" style=3D"box-sizing: border-box; background-color: t=
ransparent; text-decoration-line: underline; text-underline-offset: 0.2rem;=
">https://www.csoonline.com/article/3562701/chinese-researchers-break-rsa-e=
ncryption-with-a-quantum-computer.html/amp/</a></p>
<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 on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/0e40068e-6840-49a2-a800-a1f34a0ad9ccn%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/0e40068e-6840-49a2-a800-a1f34a0ad9ccn%40googlegroups.com</a>.=
<br />
------=_Part_114669_1085048807.1729125929768--
------=_Part_114668_576186209.1729125929768--
|
