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
|
Delivery-date: Thu, 02 Oct 2025 14:59:31 -0700
Received: from mail-oo1-f55.google.com ([209.85.161.55])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBCLKJO6NVAIRBN7L7PDAMGQELCP2CIQ@googlegroups.com>)
id 1v4RKk-0005dB-Us
for bitcoindev@gnusha.org; Thu, 02 Oct 2025 14:59:31 -0700
Received: by mail-oo1-f55.google.com with SMTP id 006d021491bc7-645bb9d1518sf1669627eaf.3
for <bitcoindev@gnusha.org>; Thu, 02 Oct 2025 14:59:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1759442364; x=1760047164; 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=WZdsHre/KY56a05FeTa9orZUFiCc2ESfvzq1XojkiPY=;
b=a7x9m64BtR5WpkykqJLcusJ3o5a/B69WYNkkAkJ/5LdBS+MPIkaBBaCJWrXAeH3hA/
WM7fn2PrK/6FWIaWG83LNJN8XVTBYFqKqNXlIWaPo638TEMQYa6zB+4CxS5jRi2NtN2M
NZKkS5+o4nRyA/cGiJLfevmFL2gOofxGXOMRnY/y+bOcQwwMJc2hj2Bzci8bVpbreEPj
XjploGWZDK8BKC+b7HBGt9+4IcmJvUav7TWRoQ9ZYBQmKbbiamHLBAqu36OLYKVxvXf+
8kZjCmmueaK5nmq+aYohI7qBH4jgCzCeae6IBiWWU9PB/4hQwcgJyixyUo4b2SXkpU+q
MX8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1759442364; x=1760047164;
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=WZdsHre/KY56a05FeTa9orZUFiCc2ESfvzq1XojkiPY=;
b=QH+/0Ejs5hdTxOiAxaiaXkyupJFtHFSBRDsJIoF1I51/hiwWhUEO/nkN81F9upZtfn
yFPONcZDa8QudyMrK++mF8bfb3h8e2lYMM8TKqYdJrmYuVx/ehg0IAA79FuMx8RDRRiA
ARsc1D+dKHMddAjeXXwxS5v3UPJfhKSpMMmcMOkORj6AGZ+egOe7zUYbgMk9L+b1fgl3
YjHJ942wKN4Zq6bzrm15uKqjpq45ue8dcSW7JgIuRbJM0AdnGNf4Vm0SLyhRROY8eAmk
rftTVH2MSNy//h5tZKt5bMIhYsex1k1yTFAHAF3XfKyMzgVq6xhCRGN2AhBAnAl7GPhY
UL3g==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCWYL1RojHu5citbOJmQqs/GlOZ/H1GeD797g47ACxzfjFve5ZfbawnZ8SQ6daodN4aUPBYZ1diN8PKp@gnusha.org
X-Gm-Message-State: AOJu0Yzf19RRUjmb3Ds3sQEDkEaT6OVnEGqay2pYQN2XCmC5zSxgfpV/
1V/kpD3fgVjaLqlfQN9eEXGY+6w6tWeO4PLdZvjC1AyRajGhoVKnpI3Z
X-Google-Smtp-Source: AGHT+IH2HjicLEJLK9M6+RdUh5sjIW7xBcLPHH/Mn2Xku1yv70YsCR6QfTSMHm5RWjeIdCoFW+jrsw==
X-Received: by 2002:a05:6870:961d:b0:365:7ea4:28a1 with SMTP id 586e51a60fabf-3b104764a2bmr629808fac.48.1759442364377;
Thu, 02 Oct 2025 14:59:24 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h="ARHlJd5m2oYJmBFCxfVBUG7QtuJ+V6Yacn6eaNk34P22aQdujQ=="
Received: by 2002:a05:6871:d810:20b0:336:1449:b8ad with SMTP id
586e51a60fabf-3abfd9e2e0dls539038fac.1.-pod-prod-03-us; Thu, 02 Oct 2025
14:59:19 -0700 (PDT)
X-Received: by 2002:a05:6808:50a6:b0:43d:1edb:779f with SMTP id 5614622812f47-43fc188b285mr315562b6e.42.1759442359111;
Thu, 02 Oct 2025 14:59:19 -0700 (PDT)
Received: by 2002:a05:690c:ed6:b0:725:2535:e36 with SMTP id 00721157ae682-77f93fd870bms7b3;
Thu, 2 Oct 2025 13:42:08 -0700 (PDT)
X-Received: by 2002:a05:690c:6b02:b0:721:c0d:9dd9 with SMTP id 00721157ae682-77f946d9ae7mr12554147b3.52.1759437727254;
Thu, 02 Oct 2025 13:42:07 -0700 (PDT)
Date: Thu, 2 Oct 2025 13:42:06 -0700 (PDT)
From: PortlandHODL <admin@qrsnap.io>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <6f6b570f-7f9d-40c0-a771-378eb2c0c701n@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Limit ScriptPubkey Size >= 520 Bytes Consensus.
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_540_1866751492.1759437726892"
X-Original-Sender: admin@qrsnap.io
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.7 (/)
------=_Part_540_1866751492.1759437726892
Content-Type: multipart/alternative;
boundary="----=_Part_541_616318533.1759437726892"
------=_Part_541_616318533.1759437726892
Content-Type: text/plain; charset="UTF-8"
Proposing: Softfork to after (n) block height; the creation of outpoints
with greater than 520 bytes in the ScriptPubkey would be consensus invalid.
This is my gathering of information per BIP 0002
After doing some research into the number of outpoints that would have
violated the proposed rule there are exactly 169 outpoints. With only 8
being non OP_RETURN. I think after 15 years and not having discovered use
for 'large' ScriptPubkeys; the reward for not invalidating them at the
consensus level is lower than the risk of their abuse.
-
*Reasons for *
- Makes DoS blocks likely impossible to create that would have any
sufficient negative impact on the network.
- Leaves enough room for hooks long term
- Would substantially reduce the divergence between consensus and
relay policy
- Incredibly little use onchain as evidenced above.
- Could possibly reduce codebase complexity. Legacy Script is largely
considered a mess though this isn't a complete disablement it should reduce
the total surface that is problematic.
- Would make it harder to use the ScriptPubkey as a 'large'
datacarrier.
- Possible UTXO set size bloat reduction.
- *Reasons Against *
- Bitcoin could need it in the future? Quantum?
- Users could just create more outpoints.
Thoughts?
source of onchain data
<https://github.com/portlandhodl/portlandhodl/blob/main/greater_520_pubkeys.csv>
PortlandHODL
--
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/6f6b570f-7f9d-40c0-a771-378eb2c0c701n%40googlegroups.com.
------=_Part_541_616318533.1759437726892
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Proposing: Softfork to after (n) block height; the creation of outpoints wi=
th greater than 520 bytes in the ScriptPubkey would be consensus invalid. <=
br /><br />This is my gathering of information per BIP 0002<br /><br />Afte=
r doing some research into the number of outpoints that would have violated=
the proposed rule there are exactly 169 outpoints. With only 8 being non O=
P_RETURN. I think after 15 years and not having discovered use for 'large' =
ScriptPubkeys; the reward for not invalidating them at the consensus level =
is lower than the risk of their abuse.=C2=A0<br /><ul><li><b>Reasons for<br=
/></b><ul><li>Makes DoS blocks likely impossible to create that would have=
any sufficient negative impact on the network.</li><li>Leaves enough room =
for hooks long term<br /></li><li>Would substantially reduce the divergence=
between consensus=C2=A0 and relay policy</li><li>Incredibly little use onc=
hain as evidenced above.</li><li>Could possibly reduce codebase complexity.=
Legacy Script is largely considered a mess though this isn't a complete di=
sablement it should reduce the total surface that is problematic.</li><li>W=
ould make it harder to use the ScriptPubkey as a 'large' datacarrier.</li><=
li>Possible UTXO set size bloat reduction.<br /><br /></li></ul></li><li><b=
>Reasons Against=C2=A0</b><ul><li>Bitcoin could need it in the future? Quan=
tum?<br /></li><li>Users could just create more outpoints.</li></ul></li></=
ul>Thoughts?<br /><br /><a href=3D"https://github.com/portlandhodl/portland=
hodl/blob/main/greater_520_pubkeys.csv">source of onchain data=C2=A0</a><br=
/><br />PortlandHODL<br /><br />
<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/6f6b570f-7f9d-40c0-a771-378eb2c0c701n%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/6f6b570f-7f9d-40c0-a771-378eb2c0c701n%40googlegroups.com</a>.<br />
------=_Part_541_616318533.1759437726892--
------=_Part_540_1866751492.1759437726892--
|
