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
|
Return-Path: <aymeric@peersm.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 84D2EC002A
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 9 May 2023 17:53:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 5958361676
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 9 May 2023 17:53:43 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 5958361676
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001,
RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id x18DmAKFne8y
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 9 May 2023 17:53:41 +0000 (UTC)
X-Greylist: delayed 00:08:30 by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 9D60F60F7F
Received: from 8.mo548.mail-out.ovh.net (8.mo548.mail-out.ovh.net
[46.105.45.231])
by smtp3.osuosl.org (Postfix) with ESMTPS id 9D60F60F7F
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 9 May 2023 17:53:41 +0000 (UTC)
Received: from mxplan6.mail.ovh.net (unknown [10.108.1.72])
by mo548.mail-out.ovh.net (Postfix) with ESMTPS id 2952A2039E;
Tue, 9 May 2023 17:45:08 +0000 (UTC)
Received: from peersm.com (37.59.142.110) by DAG6EX2.mxp6.local (172.16.2.52)
with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Tue, 9 May
2023 19:45:07 +0200
Authentication-Results: garm.ovh; auth=pass
(GARM-110S004a2e53332-06b1-42b7-961b-7bb38aea592e,
0D11D2E5C77D93C48ECA98F9824AD0C1D0204CA6) smtp.auth=aymeric@peersm.com
X-OVh-ClientIp: 92.184.102.227
To: Christopher Allen <ChristopherA@lifewithalacrity.com>, Bitcoin Protocol
Discussion <bitcoin-dev@lists.linuxfoundation.org>, Moth
<moth_oshi@proton.me>
References: <SzOndBJmU5RPVdT2IhiWUmw925vgy-KCwrbWC4_e8tHVj5VWUn-Tr50TjxTczUUDcaVjUJEiuLVmFjfmtZwwvLyuUSkrGVg9uNje2oARArc=@proton.me>
<CACrqygCN-LLttNks-MpBKErZauZyx8hpV=MCgvACRoOcRxETOQ@mail.gmail.com>
From: Aymeric Vitte <aymeric@peersm.com>
Message-ID: <39514580-3d3e-d633-8270-952caab73b1e@peersm.com>
Date: Tue, 9 May 2023 19:45:11 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CACrqygCN-LLttNks-MpBKErZauZyx8hpV=MCgvACRoOcRxETOQ@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------A84AEE2529320B177E0DB6BB"
X-Originating-IP: [37.59.142.110]
X-ClientProxiedBy: DAG6EX2.mxp6.local (172.16.2.52) To DAG6EX2.mxp6.local
(172.16.2.52)
X-Ovh-Tracer-GUID: 82b6975d-6ec6-4425-884f-156815544509
X-Ovh-Tracer-Id: 9701879501270180829
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: -100
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvhedrfeeguddggedvucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhfhkffffgggjggtihesrgdtreertdefheenucfhrhhomhepteihmhgvrhhitgcugghithhtvgcuoegrhihmvghrihgtsehpvggvrhhsmhdrtghomheqnecuggftrfgrthhtvghrnhepueegleekleetteefffeuhfeiueehkeeukedvteeifeegudelgeetveeuleeujedvnecuffhomhgrihhnpehgihhthhhusgdrtghomhenucfkphepuddvjedrtddrtddruddpfeejrdehledrudegvddruddutddpledvrddukeegrddutddvrddvvdejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepuddvjedrtddrtddruddpmhgrihhlfhhrohhmpeeorgihmhgvrhhitgesphgvvghrshhmrdgtohhmqedpnhgspghrtghpthhtohepuddprhgtphhtthhopehmohhthhgpohhshhhisehprhhothhonhdrmhgvpdgsihhttghoihhnqdguvghvsehlihhsthhsrdhlihhnuhigfhhouhhnuggrthhiohhnrdhorhhgpdevhhhrihhsthhophhhvghrteeslhhifhgvfihithhhrghlrggtrhhithihrdgtohhmpdfovfetjfhoshhtpehmohehgeekpdhmohguvgepshhmthhpohhuth
X-Mailman-Approved-At: Tue, 09 May 2023 17:54:38 +0000
Subject: Re: [bitcoin-dev] Witness script validation to reject arbitrary data
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 09 May 2023 17:53:43 -0000
--------------A84AEE2529320B177E0DB6BB
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Le 08/05/2023 =E0 23:43, Christopher Allen via bitcoin-dev a =E9crit :
> There was a recent thread discussing raising the limit on
> OP_RETURN https://github.com/bitcoin/bitcoin/issues/27043
Indeed we already discussed all of this, and the conclusion was: there
are no reasons to impose limits, because people will find some deviant
(or not) workarounds (like Stamps), and fees will regulate this
And how to control the value of what is stored? If I store e=3Dmc2, the
way I like since as many said it's super easy to find plenty of ways to
store in bitcoin, this one is short and supposed to have more value than
bitcoin, no?
Personnally I think of course that you should store a reference to
something and not the something, so a few hashes and/or signatures which
you cannot do with OP_RETURN today (80B Moth, not 80kB)
I don't see very well what can be done against the freeriders, except
avoiding that they impact the whole network (a bit =E0 la bittorrent),
maybe the issue is more about decentralization rather than trying to
impose limitations, so the decentralized miners can't have the whole
image of the whole txs and hold low fees txs, which is not the case at
all today, but it seems a bit utopic right now
Or maybe when the ordinal meme stuff/BRC20 will be proven to have
finally zero value the market will self regulate
--------------A84AEE2529320B177E0DB6BB
Content-Type: text/html; charset="windows-1252"
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Le 08/05/2023 à 23:43, Christopher
Allen via bitcoin-dev a écrit :<br>
</div>
<blockquote
cite="mid:CACrqygCN-LLttNks-MpBKErZauZyx8hpV=MCgvACRoOcRxETOQ@mail.gmail.com"
type="cite">There was a recent thread discussing raising the limit
on OP_RETURN <font color="#419cff"><font color="#419cff"><font
color="#419cff"><font color="#419cff"><font color="#419cff"><font
color="#419cff"><a moz-do-not-send="true"
href="https://github.com/bitcoin/bitcoin/issues/27043">https://github.com/bitcoin/bitcoin/issues/27043</a></font></font></font></font></font></font></blockquote>
Indeed we already discussed all of this, and the conclusion was:
there are no reasons to impose limits, because people will find some
deviant (or not) workarounds (like Stamps), and fees will regulate
this<br>
<br>
And how to control the value of what is stored? If I store e=mc2,
the way I like since as many said it's super easy to find plenty of
ways to store in bitcoin, this one is short and supposed to have
more value than bitcoin, no?<br>
<br>
Personnally I think of course that you should store a reference to
something and not the something, so a few hashes and/or signatures
which you cannot do with OP_RETURN today (80B Moth, not 80kB)<br>
<br>
I don't see very well what can be done against the freeriders,
except avoiding that they impact the whole network (a bit à la
bittorrent), maybe the issue is more about decentralization rather
than trying to impose limitations, so the decentralized miners can't
have the whole image of the whole txs and hold low fees txs, which
is not the case at all today, but it seems a bit utopic right now<br>
<br>
Or maybe when the ordinal meme stuff/BRC20 will be proven to have
finally zero value the market will self regulate<br>
<br>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>
--------------A84AEE2529320B177E0DB6BB--
|
