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
|
Delivery-date: Wed, 30 Apr 2025 20:15:51 -0700
Received: from mail-qt1-f186.google.com ([209.85.160.186])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBAABBU6OZPAAMGQE23AC5CY@googlegroups.com>)
id 1uAKOs-0003NF-DT
for bitcoindev@gnusha.org; Wed, 30 Apr 2025 20:15:51 -0700
Received: by mail-qt1-f186.google.com with SMTP id d75a77b69052e-476900d10casf13697691cf.0
for <bitcoindev@gnusha.org>; Wed, 30 Apr 2025 20:15:50 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1746069344; cv=pass;
d=google.com; s=arc-20240605;
b=bs43xBzPWSZ3McSb9wiknn/eaFmk97aSQwU+iqwPHi3rVKlk2O0klc9ai5t5Ckl5oQ
uFfelJG1ZvR5L9S+WoTcL93rMZ1f8oWHDdYH/pNkoOc0CODE0EmvpeCH+98N8V9yHi2S
0wKAJGir0ogApeLNyoiG6hhLg+pnlgqclq9lCwedNl/yfs4I49Up0lyx9k+LbWg5CPHQ
65rjMLA3NPgxlHnw2BCf18pb1cXELpZ6jhFiFwqWkeoB++pK0rVDOeLL4LNt6V2HdtdL
BUUG2oG7NVNrkn0mqO9cBbbza3Yr9TY0YxBSpDFF99Iw6sf9/ZX9YPJsx4KcRiHHn0aP
JqrQ==
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:to:references:message-id
:content-transfer-encoding:cc:date:in-reply-to:from:subject
:mime-version:feedback-id:sender:dkim-signature;
bh=6kjuNznLqkiSlD4KbFXLVDdKN5M6w9NzNjBiBaSmYqo=;
fh=9l7ResO8ynieaMr60NIJASuVD+BPUwLc5h+GG9YpUhw=;
b=csI3FEFhAj3Bse/5YADN4tKDlj0ddT1rOhW7QykV1RqjUEuxChZv786DgWJSfeDtXD
CmrGTOX5DMXHUnVOLXBQLX+jTz+7LXYviv31Jy8d0tgyNtlTsC+SVH6UUd2+1AAtoEY7
N16juieg4q2oM0MjO/Du5FLlZELZmg5K4gpUJ/VSbJDsPdH/UBWapNocaUM5kqM1FbNC
JRws13T4g84/DeO3uOLyEHvfr8lAlLYKgFDgbor8NKZz9HnOaEIuOBneX+Q6znlsu8pB
SeOZ4x8ohVDnAbdBKVnN1rtjTL/I1snai//0XX15T3p4hUQbsFs4rU7CngH7oSagoIIs
qTvw==;
darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
dkim=pass header.i=@sprovoost.nl header.s=fm1 header.b=sipgNghb;
dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=uRyzzECV;
spf=pass (google.com: domain of sjors@sprovoost.nl designates 202.12.124.153 as permitted sender) smtp.mailfrom=sjors@sprovoost.nl;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=sprovoost.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1746069344; x=1746674144; 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:to:references:message-id
:content-transfer-encoding:cc:date:in-reply-to:from:subject
:mime-version:feedback-id:sender:from:to:cc:subject:date:message-id
:reply-to;
bh=6kjuNznLqkiSlD4KbFXLVDdKN5M6w9NzNjBiBaSmYqo=;
b=iLRTDJGhb+6vowg55fsVaTsrHB64hxORJH4HYF5MqpXzHtDEzQOpjzzaxbd7m/RMCA
QGYZ6E9mL/uhsqdc+d8/NRUBzmkysXNMCEQ5/SOFqIvv0CAZDtWSZgGGLmQ/7rGl3yQ2
KUdtOl2lwzvsFgukKQ1qSM0Q/tN3E37lGTM9AIUjBBOPsW1l9GAI6qq+Q0G/PFLOgtmY
iQsqQXvI6XQfl3HrrSwBhTc/6kUDOLLOzy5rMABKfe7yxDq36TAEM2eHpb5u5DSzxxWZ
zty6zXPGhwkVHuc5G6CIKGETAx1pl164V5dM7pKKs8bu6YncUQC0lalEp/7cbes4xTYo
sqpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1746069344; x=1746674144;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:to:references:message-id
:content-transfer-encoding:cc:date:in-reply-to:from:subject
:mime-version:feedback-id:x-beenthere:x-gm-message-state:sender:from
:to:cc:subject:date:message-id:reply-to;
bh=6kjuNznLqkiSlD4KbFXLVDdKN5M6w9NzNjBiBaSmYqo=;
b=BqJecdRdoP1zW5xJS60JBKQoxB2U0nJ86tlT3g2kRgG4MUc4f9QokkUNAEy78DGU11
QnvBkMitbI7oYlRBPMG8RWZzs8O0tTM2HrGElf0sSiqfwRP7lurQeM+sVNQ9VC7vRMF6
s+MZXWH+5ovUsxlh5WwczC8u4ILKqHocQrPoa9hR7I96KA3MnpvlKOcFzsLsaQvHqQsn
H6AMor0VVcGynMZC4ZfwjVr7ksp1oIBiJkpLGPeMdnDtCHwlG181PQ2xjmQFzPmykcqv
YcY1mxOiGOUKuOM0+SaRrD+ehf5wwFnQhj7ewsUPwAc0dhfON0Gzs76+9UDDoX9OCKcg
zpSA==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCUVBkvHLSGEl13yYSVhQenzIYeRN7BdZozl48zJQtBQ+oX3OzTOv1ZH+zqTrP1IYLwpCyof/7jsNynl@gnusha.org
X-Gm-Message-State: AOJu0YzrjrgOFfIuy0cCF6L9dV0kLkac29kMYsl4ddJKn6a0JVS51pb8
yDsxA0lgH2f3gsEs3JrnIDCrGDSlfrkI24vsVFXwrBhYgHbmWOek
X-Google-Smtp-Source: AGHT+IGm8Rt8S8PHjDHnoC5JEDBcrm6L4ulqrX96ZZsfIOASlptfOJxfyk73JuyiSiDLgC9cDKL8sg==
X-Received: by 2002:a05:6808:8381:b0:403:37dd:e26f with SMTP id 5614622812f47-40337de0ba8mr173980b6e.33.1746069333948;
Wed, 30 Apr 2025 20:15:33 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=AVT/gBG13YmWguJkcFyJrP26Jdkh3DZQL1KfIXGC987oaussVA==
Received: by 2002:a4a:a646:0:b0:606:1fcd:dd8f with SMTP id 006d021491bc7-607def3e4fcls131107eaf.2.-pod-prod-06-us;
Wed, 30 Apr 2025 20:15:31 -0700 (PDT)
X-Received: by 2002:a05:6808:3988:b0:400:fa6a:d9f6 with SMTP id 5614622812f47-402d1971945mr3198472b6e.25.1746069331170;
Wed, 30 Apr 2025 20:15:31 -0700 (PDT)
Received: by 2002:a05:6808:1912:b0:3f9:f009:458e with SMTP id 5614622812f47-40220c290e9msb6e;
Wed, 30 Apr 2025 09:30:58 -0700 (PDT)
X-Received: by 2002:a05:6602:3810:b0:85b:505a:7e01 with SMTP id ca18e2360f4ac-86497f745b9mr343344839f.5.1746030658052;
Wed, 30 Apr 2025 09:30:58 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1746030658; cv=none;
d=google.com; s=arc-20240605;
b=W7ZWgxboNQhr4DQjevfTzBV8en7L7pGss2R14dxuVJHhl0Jdvx3JIxuJmDkKeTcX9G
cfOJnRFNDA+ps7ACFFb+pJ8AMt81qb5H4sji5qBQaFE9p+DnROu8acbfIflANH02zfm5
plmK3AE4VGmEcOd5LpVAkn/+V1QVucbSCy6Jh0sQRwXfsLfkhEmi/g4HQswc5YL4iC81
BaulJjTYm4AUahueoQMSb28t48nuruD1t2QhL1l2gvRt4lXByCP1+6VYCGARcDaKNVQY
+0bczr7qJxXKcGC1WSvZEz7c46p8xEnDdMXZW11VH/bmhyJf8P+RcykrmVJQLSSJioL1
MiYA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=to:references:message-id:content-transfer-encoding:cc:date
:in-reply-to:from:subject:mime-version:feedback-id:dkim-signature
:dkim-signature;
bh=pilagUFR8FigOGBmzXuWfPxaBtoObyvRsxyJroSuw3I=;
fh=2tnLtRTU76qOXoC8xcvwpnm9gVpwwX1WLjjYroiHIUE=;
b=ewRUMV7BbwlvZEg1/ByPFy2NlRmBWnZ3K9iPJY7SeqQM4hoSxWzxuj+oJ4mkEghtQ7
OHwsWQrGUCxcQbNw+jbz4tUTqpM9nf8WnlRDr0x0bSJOwJJnzbOyEMqscL5ZOF1fA2wJ
uVP2d9M7cAOoVdC3SxhrnNPpdK2lP0G2f/Yxa+EamLGEJVztCYb73nNRhYuYVk159OKM
LnvJzV3sa5ctg6q2mgGztvljHXR7nkSbMrF5VxRjzak9roO4FEKPEogJyQj1v7xrTlOG
s8wXJlAErgHwlpFyCoDngRTmzY/xnjc6ToupDsYJqs1IeopHpsanIpWDmeRq/7JIr7uC
3Fgg==;
dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
dkim=pass header.i=@sprovoost.nl header.s=fm1 header.b=sipgNghb;
dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=uRyzzECV;
spf=pass (google.com: domain of sjors@sprovoost.nl designates 202.12.124.153 as permitted sender) smtp.mailfrom=sjors@sprovoost.nl;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=sprovoost.nl
Received: from fhigh-b2-smtp.messagingengine.com (fhigh-b2-smtp.messagingengine.com. [202.12.124.153])
by gmr-mx.google.com with ESMTPS id ca18e2360f4ac-8648c087b3esi17144839f.4.2025.04.30.09.30.57
for <bitcoindev@googlegroups.com>
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Wed, 30 Apr 2025 09:30:57 -0700 (PDT)
Received-SPF: pass (google.com: domain of sjors@sprovoost.nl designates 202.12.124.153 as permitted sender) client-ip=202.12.124.153;
Received: from phl-compute-01.internal (phl-compute-01.phl.internal [10.202.2.41])
by mailfhigh.stl.internal (Postfix) with ESMTP id 28ABE25401CF;
Wed, 30 Apr 2025 12:30:57 -0400 (EDT)
Received: from phl-mailfrontend-02 ([10.202.2.163])
by phl-compute-01.internal (MEProxy); Wed, 30 Apr 2025 12:30:57 -0400
X-ME-Sender: <xms:QFASaJSbNqFEIAqgpHNrA9TjZeC6aHdxMGCWo_VkOZHvn6BxXtiI6w>
<xme:QFASaCxSbcDXlhfoa4ikWRmMIuXzpjb_mRnD3zwPlyZqZkgwRtkJCX1euk3u0R_pK
eAPbCOaWs8mv5lJlg>
X-ME-Received: <xmr:QFASaO3cTwYbURQyAX3mwaisprXzws_UjSDMzrFmxZTYmOEuhqvyxUekBvc--LTCWjaI>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvieejudekucetufdoteggodetrf
dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggv
pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpih
gvnhhtshculddquddttddmnecujfgurheptggguffhjgffvefgkfhfvffosehtqhhmtdhh
tdejnecuhfhrohhmpefujhhorhhsucfrrhhovhhoohhsthcuoehsjhhorhhssehsphhroh
hvohhoshhtrdhnlheqnecuggftrfgrthhtvghrnhepleehudefgeeuieetgffhhfeviedt
vefhudekffeuvdejjeethffhtdelveeigeelnecuffhomhgrihhnpehsthgrtghkvgigtg
hhrghnghgvrdgtohhmpdhgihhthhhusgdrtghomhenucevlhhushhtvghrufhiiigvpedt
necurfgrrhgrmhepmhgrihhlfhhrohhmpehsjhhorhhssehsphhrohhvohhoshhtrdhnlh
dpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepsghi
thgtohhinhguvghvsehgohhoghhlvghgrhhouhhpshdrtghomhdprhgtphhtthhopegsnh
grghgrvghvsehgmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:QFASaBBr3eVqeQdOHTQdPTBNU5ZWuObrJyONZjFlvlx3zOPnDlpShA>
<xmx:QFASaCi6epx-SGD1uPnfeb7mxAqV7YRJk4SQ9gHjtPq-YFh4p6J0Eg>
<xmx:QFASaFrPR7GzJBYiChSmaFn12tegwYEYYfS6xD3QVxPbxbOUl-OFnQ>
<xmx:QFASaNi2c6XhmdkphuXL1BuLOAS9CNIVyqvce9t1g0ahjLxrpXy0lA>
<xmx:QFASaB32XhAHIr0aPAyn99sYSTLM83hNTCR7auVzn6aEsnodK4cX_Khu>
Feedback-ID: ie5e042df:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed,
30 Apr 2025 12:30:56 -0400 (EDT)
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.500.181.1.5\))
Subject: Re: [bitcoindev] Relax OP_RETURN standardness restrictions
From: Sjors Provoost <sjors@sprovoost.nl>
In-Reply-To: <CAFC_Vt7TP3YKcnQzZaAkJMQ8zHTVoLwgByx9bU8pt7e2fMT9Cw@mail.gmail.com>
Date: Wed, 30 Apr 2025 18:30:45 +0200
Cc: Nagaev Boris <bnagaev@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <613DAEA9-4911-4C32-8300-C6D8C87DD92E@sprovoost.nl>
References: <rhfyCHr4RfaEalbfGejVdolYCVWIyf84PT2062DQbs5-eU8BPYty5sGyvI3hKeRZQtVC7rn_ugjUWFnWCymz9e9Chbn7FjWJePllFhZRKYk=@protonmail.com>
<03be4934-f0ff-4b58-880d-861d63a4f970@dashjr.org>
<CEB83B34-6C5B-469E-9914-20940F27EEC0@sprovoost.nl>
<d18b4149-5523-44bd-8332-2b7962f4b674@dashjr.org>
<QMywWcEgJgWmiQzASR17Dt42oLGgG-t3bkf0vzGemDVNVnvVaD64eM34nOQHlBLv8nDmeBEyTXvBUkM2hZEfjwMTrzzoLl1_62MYPz8ZThs=@wuille.net>
<f4f6831a-d6b8-4f32-8a4e-c0669cc0a7b8n@googlegroups.com>
<4DAF69CE-2AA6-4429-9F3C-91030C88A88B@sprovoost.nl>
<CAFC_Vt7TP3YKcnQzZaAkJMQ8zHTVoLwgByx9bU8pt7e2fMT9Cw@mail.gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
X-Mailer: Apple Mail (2.3826.500.181.1.5)
X-Original-Sender: sjors@sprovoost.nl
X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass
header.i=@sprovoost.nl header.s=fm1 header.b=sipgNghb; dkim=pass
header.i=@messagingengine.com header.s=fm3 header.b=uRyzzECV; spf=pass
(google.com: domain of sjors@sprovoost.nl designates 202.12.124.153 as
permitted sender) smtp.mailfrom=sjors@sprovoost.nl; dmarc=pass (p=NONE
sp=NONE dis=NONE) header.from=sprovoost.nl
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.8 (/)
> Op 30 apr 2025, om 17:37 heeft Nagaev Boris <bnagaev@gmail.com> het volge=
nde geschreven:
>=20
> On Tue, Apr 29, 2025 at 12:13=E2=80=AFPM Sjors Provoost <sjors@sprovoost.=
nl> wrote:
>>> If that wasn't bad enough, exploiters get a 75% discount on transaction=
fees.
>>=20
>> At the time SegWit was proposed it was clear that the worst case block s=
ize would increase to 4 MB. It took a few years for people to figure out ho=
w to take advantage of that. Somewhere between 2015 and early 2017 would ha=
ve been good time to object to the SegWit discount, but removing it now wou=
ld be a hard fork. Fwiw I think the discount was a good idea.
>=20
> Can you elaborate on why removing the SegWit discount now would be a
> hard fork, please? This would be a tightening of consensus rules -
> blocks that are valid under the current rules become invalid under new
> rules, but not vice versa.
>=20
> (I'm not proposing this, just a technical question.)
Good point. It might indeed be a soft fork: https://bitcoin.stackexchange.c=
om/a/121185/4948
It just has to be combined with a block size decrease.
I think it would boil down to reducing MAX_BLOCK_WEIGHT from 4 million to 1=
million, while at the same time reducing WITNESS_SCALE_FACTOR from 4 to 1.
So it undoes the block size increase created by SegWit. From the perspectiv=
e of pre-segwit nodes, they would see that typical blocks got smaller, beca=
use they don't see the witness data.
I also can't think of a vice-versa example. One could start by adjusting al=
l the tests in Bitcoin Core to verify if there really isn't one.
It would however be a confiscatory soft fork. E.g. if you have a pre-signed=
1.1 MB transaction, it won't fit in a block. Similarly, though less severe=
, a 101 KB pre-signed transaction would no longer be standard, so you'd hav=
e to find a miner or accelerator.
Those transactions may sound silly, but soft fork proposals have been criti=
cised for far less likely confiscatory surface. See e.g. the original Great=
Consensus Cleanup thread from 2010.
Note that a similar, albeit temporary, block size decrease has been propose=
d before, see [0].
> The initial size limit upon activation depends on when it is activated: f=
or example, if in 2018 January, it would begin at ~356k; or if in 2024 June=
, it would begin at just over 1 MB.
It kept the SegWit discount intact, though it added a byte based ceiling:
> The weight of a block may not exceed double the size limit in bytes.
It was never assigned a BIP number, so I'm not sure how serious this propos=
al was. In any case, it got no traction, nor did any other block size decre=
ase proposal.
So even if there was support for removing the witness discount, since you c=
an't do that without also decreasing the block size, I don't think this ave=
nue is worth exploring.
- Sjors
[0] https://github.com/luke-jr/bips/blob/bip-blksize/bip-blksize.mediawiki
--=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/=
613DAEA9-4911-4C32-8300-C6D8C87DD92E%40sprovoost.nl.
|
