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
|
Delivery-date: Wed, 14 May 2025 02:37:29 -0700
Received: from mail-oo1-f64.google.com ([209.85.161.64])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBDS45GVMVEJBBT6ISHAQMGQETJCRW2Q@googlegroups.com>)
id 1uF8YJ-0004e1-Tz
for bitcoindev@gnusha.org; Wed, 14 May 2025 02:37:29 -0700
Received: by mail-oo1-f64.google.com with SMTP id 006d021491bc7-60221ba69d1sf1807950eaf.3
for <bitcoindev@gnusha.org>; Wed, 14 May 2025 02:37:27 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1747215442; cv=pass;
d=google.com; s=arc-20240605;
b=f/v7W4eO/x0XWy1NiUzqUNd8wq2hhmF7x149jHbVlY9jdisKqfq1TDPeIHAoyNqTeb
X3xrt2ToAO55/2bG4AvSw9rYnsIR3OUPZHjUkbccEPPU2o9mk/7T/JlcK0n4vMjgyBYl
aexFNQ+Pql/+HqaVXBWTsuri7illuyh1w5uTRiZG/urNzEdJ0wecc6gziXWdeILWNCPY
X6DH+w4i+1CLzdObiylN04HeVuTBplzXqFzuDkTEfv8AiDNc/wl2/k0DQq1NErL5sJal
cPZLyuDyQWdPu2pbJ2cuikZNwGOi59+K75W32Mva/4hbLX/FIxks90HvBtZhawwS8h81
kWhg==
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:content-transfer-encoding:cc:to
:subject:message-id:date:from:in-reply-to:references:mime-version
:sender:dkim-signature:dkim-signature;
bh=PU3WV/7LufrnKb606l8aDq6Ta8Run//SHnqIMJIc0jk=;
fh=1AQsP/sisP1gHJrrGdYMLixGxpH+B16Sck3eNDUcxrM=;
b=XDf0sD3qQ3dj6ODCC/ILP8pCKqHOjUksVWpRtQpqGNrpdkqVolfwpjH5fTk8bLBYTZ
zm615DW11CrJMTa8dR3OmnEv/z4UbtOWWl1/dS0dyCe9H228kLVqrc14aUmuHe1WyQjf
cX3ykLusd6BNkezvVCjA9OVK0IL3Pc0ZkeeSPeiNfJjbQs0TZDSAI5Xq4NRTM1EPnDGr
nzEG3DowRM7/te5KElEWDWSlB/oN0/jOfCbq0aU/8gVt0D6eKG8RuhriSHfbiE/09M7m
K4rPAdbXPkeFUHivbm6d5s8i1W0i4rtAW5/idxdyN8su+kEAY8twJ4eeikwWBSjaea5f
rN4g==;
darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
dkim=pass header.i=@gmail.com header.s=20230601 header.b=lnmasf4N;
spf=pass (google.com: domain of decker.christian@gmail.com designates 2607:f8b0:4864:20::12b as permitted sender) smtp.mailfrom=decker.christian@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=1747215442; x=1747820242; 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:content-transfer-encoding:cc:to:subject
:message-id:date:from:in-reply-to:references:mime-version:sender
:from:to:cc:subject:date:message-id:reply-to;
bh=PU3WV/7LufrnKb606l8aDq6Ta8Run//SHnqIMJIc0jk=;
b=AZbi4rv6IysubzakPzU4F3DiLgOCfEhoVfBBBFbkQ9Ejc+vCit97GGmcDQKrssoNfq
zPsvXSBPVBkNBzQZskhpBictmTL+D1Zt+Q/JxBzcafLLfBB/OhAWLQ+FmSL63THFLgOm
szgFujfRDnzLX/9gr8mwFpACG49IHxjpxBDh0hynKkndUNgymWTJYzPqjOBwHyCo2Cwb
H104ODBpajManGyzq9D/ys1sQpv7Z6IPzyiiH8Tl4cCh2Va9LZqq6xqZ9xr9RRd788oE
9NxKwzz+ojxtB55VnnOKJeTu1BPYQvmZ6JNevvbPfpe6/I0nNOa5+fZhd9YKlyhaXZj2
/0Dw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1747215442; x=1747820242; 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:content-transfer-encoding:cc:to:subject
:message-id:date:from:in-reply-to:references:mime-version:from:to:cc
:subject:date:message-id:reply-to;
bh=PU3WV/7LufrnKb606l8aDq6Ta8Run//SHnqIMJIc0jk=;
b=k41f9euOyKpSo5giwVejanc9Nir+IQxeCliFgTqsA9Mh1MncoY5sMYba6yLvr7UUo8
ybw2TTz+Ik9Ci59idXrFUqVyAmWrQmY9mekURQv53G0E8yhDJVNN8VJEP+qn+EopaH+6
fVEjLDdTYXJmchDpriXcr/xeeoyfkW8pjAe4gUZB1otgMmOUVe6neyQIK6CQp8+1DHJA
LmRUFSfqnGgq/UCe16ol+bmKLkaEm1NZkk8n8ahPsc4LpfLd0JLVftTaII0vEVJIEXp4
9n2TEpxHNg+YKtXSU9yWhCcRpxkMvyaBsCoFa9PUUQbkYhFs2Azrq9yoV8tqM3b7hAcC
Z6Kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1747215442; x=1747820242;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:content-transfer-encoding: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=PU3WV/7LufrnKb606l8aDq6Ta8Run//SHnqIMJIc0jk=;
b=g9GsjrTh1CAa4g66l7UmyW+I10r3imSqxL3pCFWwwFqP7VAMKBgQh3YW0Ae1xbYxbG
MgXXd8MnUJKQAAsBXZ/FM4075JvpTWYPkAkq/V/mHpnxCrhllNw3FT9X/BKmeyqkzQUf
wQUkRORk6i0+oAz2F0D+OnfCzvGrm/SHp+L7VZ9R7SBO/WHo74EfEqZ82VGDFm0LH92j
NIFgm7v7diHdxX/eFSLKJHrUXHzVWC9q+UMuwhzsrd3e9V8koiLWfuLv8RFT5/L+UVy/
MESbpIj2wXwhwT61c9gakFNHKDKi/fC37F7p51DG+colOWSNDno6fJi2l53w/pR8vv8R
jK/Q==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCWxWVV/Ciz/7uTK0nzFOZc1/w7eLO/VCLRmCCgDR2Ax4rxQAAIL0gcnteBaqKROyu8Z1RxS2Zpkyepf@gnusha.org
X-Gm-Message-State: AOJu0Yyi08s3ZKakubX9JF11xLqnPdknhcxFm6SFeZWVlBHUpk2k6xem
WasLJenZu75GIDJs7SiRM6Dsuwwy/eSVaglTSd0zkzPHeNYRsXNt
X-Google-Smtp-Source: AGHT+IF+/ZmKahNW5eKsKnohsJTulgU5m0z8I9D8tFo9Q4KO6XEDHBj52AA7/6eNUtDiqfIP6yILlQ==
X-Received: by 2002:a05:6871:7c17:b0:2c2:542b:bce4 with SMTP id 586e51a60fabf-2e32b070a80mr1380508fac.8.1747215441931;
Wed, 14 May 2025 02:37:21 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=AVT/gBGr7uMCmQ8hUFsPdxDy/WO6s4BZoCmlF+7/zAj9XWHbaw==
Received: by 2002:a05:6871:6106:b0:2a9:5c2a:c3b8 with SMTP id
586e51a60fabf-2db7fe512e6ls2550888fac.0.-pod-prod-02-us; Wed, 14 May 2025
02:37:19 -0700 (PDT)
X-Forwarded-Encrypted: i=2; AJvYcCXCxI/HcO4WAZ2s76I2zrpGX2CjdS/tKyXK48mte/OLc9P/ptggU5NcEoisVCKtK0ViXQNwVmFKx4rG@googlegroups.com
X-Received: by 2002:a05:6808:2d1a:b0:3f8:8977:7294 with SMTP id 5614622812f47-404c20fa3c2mr1471141b6e.31.1747215438910;
Wed, 14 May 2025 02:37:18 -0700 (PDT)
Received: by 2002:a05:6808:1aa9:b0:403:484c:9068 with SMTP id 5614622812f47-40380031a02msb6e;
Wed, 14 May 2025 01:28:32 -0700 (PDT)
X-Forwarded-Encrypted: i=2; AJvYcCWHSMmticK4sN90+F2kpRCnzUOv9boETt2H8MBXTnaWSOzOPjFmdcGITGISZzVUdcsNMB1jbX4Fbu83@googlegroups.com
X-Received: by 2002:a17:90b:2f48:b0:2fe:861b:1ae3 with SMTP id 98e67ed59e1d1-30e2e5e5a83mr3889201a91.8.1747211311025;
Wed, 14 May 2025 01:28:31 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1747211311; cv=none;
d=google.com; s=arc-20240605;
b=LNiqk5zxeMlJX4d9LzuAyaqn5idEMXPR2o5fxMsLHZLSu9V72jQcZy9CY0lgJVlqcu
hobT/nuSE82J67TH2pXk3hT5vTqmCawFEBGGRAG1uGzxcZIankTPgQLAAyLaFd6f0ejc
b25BqOoTSgVyqWVPefM19rDUlQRoRSSEvU5+75ZNkl9Y0a1c1YchRuIhm9dxUAGMZ99h
1/E6ybMGXFKnOuxQCyNUM7vFcnf6J95Q46wbwEQykXAJgKvDFTpROVwRQRVJtu8JP5vk
+sPt8b1gFXyzSHLzBgGJO5G02c8Vy7ZV0drMXY+cf6OIOdSVy0OufH5eY0SDWTwIuedN
MhRg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=content-transfer-encoding:cc:to:subject:message-id:date:from
:in-reply-to:references:mime-version:dkim-signature;
bh=BYxV1DfJcPAu6vOAASp7llP560hSvcia2GOPQ8+TFdg=;
fh=Tn4c6XEIaHxEnmaQd3r01zzpyFfuWQnZ2e8soBYdXqI=;
b=e6GR4BaueH0SYl74Ie0+SL40+2KT/hsANZrRqk+GnmuxENyrJ+zIsOlZ9ExhXQXP5L
N0xkHSdNypLbookpq7jGB7FTbr7B9WTES1JhqfW/1LLkEve21ncWf98oAroKb6jX6qna
dUVOaXHCr2hop3lkc7TrnLUYYIFVxr1pykkSZZtB49VirQPvujSYYXuqQrRMH3Q0zCze
DnJwAxWWTiTwS79erFBf3fUN/x9KlaFiCvNz/Je7Nzh7127u0fTv0KjqHsg5ptI4l3Ah
B9oVhRTSxnsmvb2oaD/g0nz2DfrK/ScLR2dY8IeoAv4OKsUlbyupOQVKXib5E4kzDULY
kFDQ==;
dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
dkim=pass header.i=@gmail.com header.s=20230601 header.b=lnmasf4N;
spf=pass (google.com: domain of decker.christian@gmail.com designates 2607:f8b0:4864:20::12b as permitted sender) smtp.mailfrom=decker.christian@gmail.com;
dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com;
dara=pass header.i=@googlegroups.com
Received: from mail-il1-x12b.google.com (mail-il1-x12b.google.com. [2607:f8b0:4864:20::12b])
by gmr-mx.google.com with ESMTPS id 98e67ed59e1d1-30e33401c53si41449a91.1.2025.05.14.01.28.31
for <bitcoindev@googlegroups.com>
(version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
Wed, 14 May 2025 01:28:31 -0700 (PDT)
Received-SPF: pass (google.com: domain of decker.christian@gmail.com designates 2607:f8b0:4864:20::12b as permitted sender) client-ip=2607:f8b0:4864:20::12b;
Received: by mail-il1-x12b.google.com with SMTP id e9e14a558f8ab-3d96d16b369so60103085ab.0
for <bitcoindev@googlegroups.com>; Wed, 14 May 2025 01:28:30 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCVMA0y0I9IMXG9fXisjCYvZqhjDCKHRlRL1rwqI99CnYpEU9IdRhsf2ve4gliOK9BxA4FgiDj0bfcjM@googlegroups.com
X-Gm-Gg: ASbGncsH4GSor05GW0h57sLVEqH1ppU0ajfC6tyEiOSNlpdUfzvhwf53RiSjkGqsE4+
TSJ5sH1fOuqPRaETaYG+rTVVOAXFf43lJHL1k+6ZvFO9YACeW2GPc88NmiyCA+MN2qSSlU4ZDYw
l60R04nrzPiuZfq2qEXQtx/9NhI+JidD36
X-Received: by 2002:a05:6e02:4509:20b0:3db:754c:63b with SMTP id
e9e14a558f8ab-3db754c0b07mr707675ab.12.1747211310048; Wed, 14 May 2025
01:28:30 -0700 (PDT)
MIME-Version: 1.0
References: <CAGL6+mH+9iq5_SR-Fa5zVZRoTpHasX7xoprYeJZRd5D80J1GqA@mail.gmail.com>
<CALkkCJbeAYA2X8jv8iWthKBB8GqxA49DCFm+UMnhmXYpexTNtw@mail.gmail.com>
<CAGL6+mHv+kn6SU9pf0Rz3FmM5OfcsmEtqGBRJ7Upb-b0MofS5A@mail.gmail.com>
<CALxbBHW8YD-F2N9PYcAii5wXfEAPratQ6i6ke-i59pdoFczSoA@mail.gmail.com> <CAGL6+mFF8noQxXWy8PXBT9vSBQv0Hx3jn7cFtQMkv4PcnhyGyw@mail.gmail.com>
In-Reply-To: <CAGL6+mFF8noQxXWy8PXBT9vSBQv0Hx3jn7cFtQMkv4PcnhyGyw@mail.gmail.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Wed, 14 May 2025 10:27:54 +0200
X-Gm-Features: AX0GCFvIrDd-SXO4CF0ujtJlu8I1cngtUSityvH61FkNhOMoIEJ4y_9e_yxItc8
Message-ID: <CALxbBHWP=zOfT0+YM=4MgR6SEuT9CCFHQEuH_mkgtDKiRxpfog@mail.gmail.com>
Subject: Re: [bitcoindev] [Proposal] 64-bit arithmetic in Script
To: Chris Stewart <stewart.chris1234@gmail.com>
Cc: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= <martin.habovstiak@gmail.com>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Original-Sender: Decker.Christian@gmail.com
X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass
header.i=@gmail.com header.s=20230601 header.b=lnmasf4N; spf=pass
(google.com: domain of decker.christian@gmail.com designates
2607:f8b0:4864:20::12b as permitted sender) smtp.mailfrom=decker.christian@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 (/)
Hi Chris,
I was contacted by other ML members pointing out that the GSR may not
have announced on the ML. I was not aware, and would not have brought
it up as a competing effort in such a case.
Apologies for the noise, and I hope that an update on the idea and
current status of the GSR will be published eventually :-)
Regards,
Christian
On Wed, May 14, 2025 at 10:24=E2=80=AFAM Chris Stewart
<stewart.chris1234@gmail.com> wrote:
>
> Hi Christian,
>
> Thank you for the interest in this proposal!
>
> I=E2=80=99d like to invite you, Rusty, or any other contributors to provi=
de an update to the list on the status of GSR. The most recent public writi=
ng I=E2=80=99m aware of is Rusty=E2=80=99s blog post, which is now around 1=
8 months old. Are there any newer materials =E2=80=94 such as additional po=
sts, WIP BIPs, or code =E2=80=94 that we could review or experiment with? E=
ven rough drafts would be helpful for prototyping and discussion.
>
> I=E2=80=99m not opposed to the broader goals of GSR, but I do think it=E2=
=80=99s a bit ambitious. That=E2=80=99s partly why I=E2=80=99ve focused my =
efforts on isolating what I believe is the most requested feature: 64-bit p=
recision to enable amount locks.
>
> >arbitrary sized integers
>
> It would be helpful to see some concrete examples of opcodes that would r=
equire arbitrary precision, but wouldn=E2=80=99t be achievable with 64-bit =
arithmetic. Looking at the Elements project, there are a couple of examples=
=E2=80=94 ECMULSCALARVERIFY and TWEAKVERIFY =E2=80=94 which operate on 256=
-bit stack arguments. Notably, these opcodes don=E2=80=99t support composit=
ion with existing arithmetic opcodes like OP_ADD or OP_SUB; they simply ver=
ify cryptographic conditions. I would argue they do not actually require su=
pporting more precision in Script as the stack arguments aren't parsed into=
CScriptNum.
>
> It could be useful to have a list of these potential opcodes that could b=
e enabled in a single place to give other protocol developers an idea of wh=
at is enabled by arbitrary precision.
>
> >maybe you could join that effort for your use-cases too?
>
> Where can one go to join the effort?
>
> -Chris
>
>
> On Tue, May 13, 2025 at 6:45=E2=80=AFAM Christian Decker <decker.christia=
n@gmail.com> wrote:
>>
>> Hi Chris,
>>
>> quite an interesting proposal, but much like Martin I wonder if we
>> shouldn't go beyond. For comparison Rusty's GSR comprises arbitrary
>> sized integers and their associated operations, with fine-grained
>> accounting of operations based on the operands size, so scripts stay
>> performant and manageable.
>>
>> That proposal is much further along in both design and analysis, so
>> maybe you could join that effort for your use-cases too?
>>
>> Cheers,
>> Christian
>>
>> On Tue, May 13, 2025 at 11:06=E2=80=AFAM Chris Stewart
>> <stewart.chris1234@gmail.com> wrote:
>> >
>> > Hi Martin
>> >
>> > Thanks for your interest in the topic.
>> >
>> > >It mentions upgrading existing opcodes, which is a hardfork, not soft=
fork, at least without using a different leaf version. But it also mention=
s OP_SUCCESSX which are different opcodes
>> >
>> > I view 64-bit arithmetic as a feature of a wider set of consensus chan=
ges. Here is what I think the most likely deployment story is
>> >
>> > >This proposal could be deployed in conjunction with any of the new op=
code proposals in the Motivation section using Tapscript's OP_SUCCESSx sema=
ntics.[18]
>> >
>> > The opcodes mentioned in the motivation section are OP_{IN,OUT}_AMOUNT=
, OP_VAULT, OP_CHECKCONTRACTVERIFY, OP_CTV
>> >
>> > As an example, this proposal could (hypothetically) be deployed in con=
junction with OP_CCV. OP_CCV would take advantage of the OP_SUCCESSx semant=
ics allowing us to redefine existing opcode's (OP_ADD,OP_SUB, etc) semantic=
s.
>> >
>> > There=E2=80=99s been some discussion around deploying OP_CTV via a NOP=
opcode instead of OP_SUCCESSx. I think that would be a poor choice, as it =
wouldn=E2=80=99t allow new Script features to be shipped in parallel with t=
he new opcode.
>> >
>> > I found this StackExchange post helpful in thinking through various de=
ployment strategies for new Tapscript-based consensus upgrades.
>> >
>> > >I'd also love to see analysis why stop at 64 bits and not go all the =
way to 256 which could be useful for cryptography.
>> >
>> > In my view, there=E2=80=99s still a lot of uncertainty about cryptogra=
phic features being added to Script. There's increasing discussion around q=
uantum computing, which raises the question of how much numerical precision=
we may eventually need. I'm not opposed to extending precision further=E2=
=80=94but if we go beyond 64 bits, why stop at 256? With OP_SUCCESSx, arbit=
rary precision becomes a real option.
>> >
>> > I chose 64 bits because it covers what=E2=80=99s needed for amount loc=
ks. If someone strongly believes that 64 bits isn't enough, I=E2=80=99d wel=
come a competing BIP and would be happy to review and discuss it with the a=
uthor.
>> >
>> > >Anyway, pushing amounts on the stack would be great. Though I'm surpr=
ised you're only proposing the sum, not individual outputs. Why?
>> >
>> > Good question=E2=80=94and slightly out of scope for this BIP. Script d=
oesn=E2=80=99t support looping, so it=E2=80=99s not straightforward to iter=
ate over and sum all elements unless the transaction structure (i.e., numbe=
r of inputs or outputs) is known in advance.
>> > You can measure the number of stack elements with OP_DEPTH, but there=
=E2=80=99s no way to write something like OP_ADD [num-stack-elements-from-O=
P_DEPTH] to sum them all. I=E2=80=99m definitely open to hearing other appr=
oaches, though.
>> >
>> > -Chris
>> >
>> >
>> >
>> > On Mon, May 12, 2025 at 2:32=E2=80=AFPM Martin Habov=C5=A1tiak <martin=
.habovstiak@gmail.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> the proposal seems to be quite confused about how it's going to do th=
at. It mentions upgrading existing opcodes, which is a hardfork, not soft f=
ork, at least without using a different leaf version. But it also mentions =
OP_SUCCESSX which are different opcodes. I think it needs some analysis. (l=
eaf version seems better intuitively)
>> >>
>> >> I'd also love to see analysis why stop at 64 bits and not go all the =
way to 256 which could be useful for cryptography.
>> >>
>> >> Anyway, pushing amounts on the stack would be great. Though I'm surpr=
ised you're only proposing the sum, not individual outputs. Why?
>> >>
>> >> Good luck!
>> >>
>> >> Martin
>> >>
>> >> D=C5=88a po 12. 5. 2025, 14:21 Chris Stewart <stewart.chris1234@gmail=
.com> nap=C3=ADsal(a):
>> >>>
>> >>> This soft fork proposal extends the range of numeric operands in Scr=
ipt from -2^31+1 to 2^31-1, to -2^63+1 to 2^63-1. It further expands the re=
sult range for arithmetic operations from -2^63 to 2^63-1, to -2^127 to 2^1=
27- 1.
>> >>>
>> >>> All existing opcodes[1] that interpret stack elements as numbers are=
upgraded to support 64-bit parameters.
>> >>>
>> >>> The existing number encoding format[2] and arithmetic semantics[3] f=
rom the original Bitcoin implementation are preserved, while enhancing the =
supported precision.
>> >>>
>> >>> https://github.com/Christewart/bips/blob/2025-03-17-64bit-pt2/bip-XX=
XX.mediawiki
>> >>>
>> >>> The purpose for this BIP is to lay the groundwork for introducing am=
ounts into Script. This document takes no opinion on how this is done.
>> >>>
>> >>> I've prototyped a few different proposals now introducing amount loc=
ks into Script[0][1] and feel like this proposal is stable enough for serio=
us review.
>> >>>
>> >>> -Chris
>> >>>
>> >>> [0] - https://delvingbitcoin.org/t/op-inout-amount/549/4?u=3Dchris_s=
tewart_5
>> >>>
>> >>> [1] - https://delvingbitcoin.org/t/op-inout-amount/549/5?u=3Dchris_s=
tewart_5
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> You received this message because you are subscribed to the Google G=
roups "Bitcoin Development Mailing List" group.
>> >>> To unsubscribe from this group and stop receiving emails from it, se=
nd an email to bitcoindev+unsubscribe@googlegroups.com.
>> >>> To view this discussion visit https://groups.google.com/d/msgid/bitc=
oindev/CAGL6%2BmH%2B9iq5_SR-Fa5zVZRoTpHasX7xoprYeJZRd5D80J1GqA%40mail.gmail=
.com.
>> >
>> > --
>> > You received this message because you are subscribed to the Google Gro=
ups "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/bitcoi=
ndev/CAGL6%2BmHv%2Bkn6SU9pf0Rz3FmM5OfcsmEtqGBRJ7Upb-b0MofS5A%40mail.gmail.c=
om.
--=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/=
CALxbBHWP%3DzOfT0%2BYM%3D4MgR6SEuT9CCFHQEuH_mkgtDKiRxpfog%40mail.gmail.com.
|