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
|
Return-Path: <aymeric@peersm.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
by lists.linuxfoundation.org (Postfix) with ESMTP id CD670C002B
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 12 Feb 2023 16:24:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 9AAEC60B9A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 12 Feb 2023 16:24:05 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 9AAEC60B9A
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-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 yrNVNGfOW2nG
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 12 Feb 2023 16:24:04 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org BDFB960A69
Received: from smtpout3.mo529.mail-out.ovh.net
(smtpout3.mo529.mail-out.ovh.net [46.105.54.81])
by smtp3.osuosl.org (Postfix) with ESMTPS id BDFB960A69
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 12 Feb 2023 16:24:03 +0000 (UTC)
Received: from mxplan6.mail.ovh.net (unknown [10.108.20.235])
by mo529.mail-out.ovh.net (Postfix) with ESMTPS id DCF69209D5;
Sun, 12 Feb 2023 16:24:00 +0000 (UTC)
Received: from peersm.com (37.59.142.102) 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.17; Sun, 12 Feb
2023 17:24:00 +0100
Authentication-Results: garm.ovh; auth=pass
(GARM-102R0043b340e09-e490-431f-a883-dd441d1a0d61,
B4C7D7AD1F5A4529B5943D5837896D0BF92101CE) smtp.auth=aymeric@peersm.com
X-OVh-ClientIp: 92.184.102.200
To: Russell O'Connor <roconnor@blockstream.com>, Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>, Peter Todd <pete@petertodd.org>,
Andrew Poelstra <apoelstra@wpsoftware.net>, Christopher Allen
<ChristopherA@lifewithalacrity.com>
References: <CACrqygAMsO1giYuxm=DZUqfeRjEqGM7msmEnZ-AHws3oA2=aqw@mail.gmail.com>
<ca8622cb-445e-4258-bbac-b3ee1ce95f4c@protonmail.com>
<57f780b1-f262-9394-036c-70084320e9cf@peersm.com>
<CACrqygCNf3Gv8+VjhyqS4GTb3Epo8qXEKGtQB6sqyR6ib44-fA@mail.gmail.com>
<CABE6yHtM2Dqc63_eURSr7dMirJti5sYnqvHj7vQ_Ab9FC_d04g@mail.gmail.com>
<3d00aacb-585d-f875-784d-34352860d725@peersm.com>
<CACrqygB_FbsRGWYPSUEFTnP15y94Hmo4JtAuv6bH1D3YtbAw9Q@mail.gmail.com>
<b292d887-cbd5-165c-de01-793df2b5e8f3@peersm.com>
<CACrqygAv842ucN7PLYMENXFiSwAZJy2Y+FziJXrWjyCcOXmL3g@mail.gmail.com>
<230265ee-c3f8-dff3-9192-f0c8dc4d913c@peersm.com>
<CAMZUoKkAdQ9TSMm4vPJOrThu_h6VbqwPhOQQR7-Yr+WZ0DMBYw@mail.gmail.com>
<76718304-A8E3-46E6-B2F7-DE86831F15DF@petertodd.org>
<CAMZUoKnrs-uxnTqpa96B4H86=gAtafowDi0D5HdnExvBWqTqPQ@mail.gmail.com>
From: Aymeric Vitte <aymeric@peersm.com>
Message-ID: <f5c0abc5-e52f-6d41-c050-bb3ecbeb3986@peersm.com>
Date: Sun, 12 Feb 2023 17:23:59 +0100
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: <CAMZUoKnrs-uxnTqpa96B4H86=gAtafowDi0D5HdnExvBWqTqPQ@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------9AF7A061FABC2FC78A967B1D"
X-Originating-IP: [37.59.142.102]
X-ClientProxiedBy: DAG5EX1.mxp6.local (172.16.2.41) To DAG6EX2.mxp6.local
(172.16.2.52)
X-Ovh-Tracer-GUID: 4eac7d6e-93a3-4812-84b7-967629ea97ee
X-Ovh-Tracer-Id: 1342072691644785571
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: -100
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvhedrudehledgkeekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhfhkffffgggjggtihesrgdtreertdefheenucfhrhhomhepteihmhgvrhhitgcugghithhtvgcuoegrhihmvghrihgtsehpvggvrhhsmhdrtghomheqnecuggftrfgrthhtvghrnhepteehfedvvdehffdthfejvddtjeejieetudevleeikeduvedvtdelveevfeetgfefnecuffhomhgrihhnpehgihhthhhusgdrtghomhdplhhinhhugihfohhunhgurghtihhonhdrohhrghdpphgvvghrshhmrdgtohhmpdhlihhnkhgvughinhdrtghomhenucfkphepuddvjedrtddrtddruddpfeejrdehledrudegvddruddtvdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeduvdejrddtrddtrddupdhmrghilhhfrhhomhepoegrhihmvghrihgtsehpvggvrhhsmhdrtghomheqpdhnsggprhgtphhtthhopedupdhrtghpthhtohepvehhrhhishhtohhphhgvrhetsehlihhfvgifihhthhgrlhgrtghrihhthidrtghomhdprghpohgvlhhsthhrrgesfihpshhofhhtfigrrhgvrdhnvghtpdhpvghtvgesphgvthgvrhhtohguugdrohhrghdpsghithgtohhinhdquggvvheslhhishhtshdrlhhinhhugihfohhunhgurghtihhonh
drohhrghdprhhotghonhhnohhrsegslhhotghkshhtrhgvrghmrdgtohhmpdfovfetjfhoshhtpehmohehvdelpdhmohguvgepshhmthhpohhuth
X-Mailman-Approved-At: Sun, 12 Feb 2023 16:49:12 +0000
Subject: Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE
OP_IF OP_PUSH
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: Sun, 12 Feb 2023 16:24:05 -0000
--------------9AF7A061FABC2FC78A967B1D
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
https://github.com/bitcoin/bitcoin/issues/27043#issuecomment-1427069403
"What is the process to have someone do the PR for this? Or I do it and
most likely it will be a very shxtty one since I am not a C/C++ expert,
then wasting the time of everybody
It's urgently required, I did consider OP_RETURN as a dart in the past
but changed my mind, it's adapted to the current evolutions, not
flooding bitcoin with 2 txs while only 1 is needed
If not the best 1 tx solution is super simple: store in addresses, and
super bad at the end because burning bitcoins, while still not expensive
if you don't need to store big things"
Le 05/02/2023 =E0 19:12, Russell O'Connor via bitcoin-dev a =E9crit :
>
>
> On Sat., Feb. 4, 2023, 21:01 Peter Todd, <pete@petertodd.org
> <mailto:pete@petertodd.org>> wrote:
>
>
>
> On February 5, 2023 1:11:35 AM GMT+01:00, Russell O'Connor via
> bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org
> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
> >Since bytes in the witness are cheaper than bytes in the script
> pubkey,
> >there is a crossover point in data size where it will simply be
> cheaper to
> >use witness data. Where that crossover point is depends on the fi=
ner
> >details of the overhead of the two methods, but you could make som=
e
> >reasonable assumptions. Such a calculation could form the basis o=
f a
> >reasonable OP_RETURN proposal. I don't know if it would be
> persuasive, but
> >it would at least be coherent.
>
> I don't think it's worth the technical complexity trying to
> carefully argue a specific limit. Let users decide for themselves
> how they want to use OpReturn.
>
>
> Even better.
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--=20
Sophia-Antipolis, France
CV: https://www.peersm.com/CVAV.pdf
LinkedIn: https://fr.linkedin.com/in/aymeric-vitte-05855b26
GitHub : https://www.github.com/Ayms
A Universal Coin Swap system based on Bitcoin: https://gist.github.com/Ay=
ms/029125db2583e1cf9c3209769eb2cdd7
A bitcoin NFT system: https://gist.github.com/Ayms/01dbfebf219965054b4a3b=
eed1bfeba7
Move your coins by yourself (browser version): https://peersm.com/wallet
Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transac=
tions
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.p=
eersm.com
Peersm : http://www.peersm.com
--------------9AF7A061FABC2FC78A967B1D
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><a class="moz-txt-link-freetext" href="https://github.com/bitcoin/bitcoin/issues/27043#issuecomment-1427069403">https://github.com/bitcoin/bitcoin/issues/27043#issuecomment-1427069403</a><br>
<br>
"What is the process to have someone do the PR for this? Or I do
it and most likely it will be a very shxtty one since I am not a
C/C++ expert, then wasting the time of everybody<br>
<br>
It's urgently required, I did consider OP_RETURN as a dart in the
past but changed my mind, it's adapted to the current evolutions,
not flooding bitcoin with 2 txs while only 1 is needed<br>
<br>
If not the best 1 tx solution is super simple: store in addresses,
and super bad at the end because burning bitcoins, while still not
expensive if you don't need to store big things"<br>
</p>
<br>
<div class="moz-cite-prefix">Le 05/02/2023 à 19:12, Russell O'Connor
via bitcoin-dev a écrit :<br>
</div>
<blockquote
cite="mid:CAMZUoKnrs-uxnTqpa96B4H86=gAtafowDi0D5HdnExvBWqTqPQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat., Feb. 4, 2023,
21:01 Peter Todd, <<a moz-do-not-send="true"
href="mailto:pete@petertodd.org">pete@petertodd.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On February 5, 2023 1:11:35 AM GMT+01:00, Russell O'Connor
via bitcoin-dev <<a moz-do-not-send="true"
href="mailto:bitcoin-dev@lists.linuxfoundation.org"
target="_blank" rel="noreferrer">bitcoin-dev@lists.linuxfoundation.org</a>>
wrote:<br>
>Since bytes in the witness are cheaper than bytes in
the script pubkey,<br>
>there is a crossover point in data size where it will
simply be cheaper to<br>
>use witness data. Where that crossover point is
depends on the finer<br>
>details of the overhead of the two methods, but you
could make some<br>
>reasonable assumptions. Such a calculation could form
the basis of a<br>
>reasonable OP_RETURN proposal. I don't know if it
would be persuasive, but<br>
>it would at least be coherent.<br>
<br>
I don't think it's worth the technical complexity trying
to carefully argue a specific limit. Let users decide for
themselves how they want to use OpReturn.<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Even better.</div>
<div dir="auto">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
bitcoin-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Sophia-Antipolis, France
CV: <a class="moz-txt-link-freetext" href="https://www.peersm.com/CVAV.pdf">https://www.peersm.com/CVAV.pdf</a>
LinkedIn: <a class="moz-txt-link-freetext" href="https://fr.linkedin.com/in/aymeric-vitte-05855b26">https://fr.linkedin.com/in/aymeric-vitte-05855b26</a>
GitHub : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms">https://www.github.com/Ayms</a>
A Universal Coin Swap system based on Bitcoin: <a class="moz-txt-link-freetext" href="https://gist.github.com/Ayms/029125db2583e1cf9c3209769eb2cdd7">https://gist.github.com/Ayms/029125db2583e1cf9c3209769eb2cdd7</a>
A bitcoin NFT system: <a class="moz-txt-link-freetext" href="https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7">https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7</a>
Move your coins by yourself (browser version): <a class="moz-txt-link-freetext" href="https://peersm.com/wallet">https://peersm.com/wallet</a>
Bitcoin transactions made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-transactions">https://github.com/Ayms/bitcoin-transactions</a>
torrent-live: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/torrent-live">https://github.com/Ayms/torrent-live</a>
node-Tor : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms/node-Tor">https://www.github.com/Ayms/node-Tor</a>
Anti-spies and private torrents, dynamic blocklist: <a class="moz-txt-link-freetext" href="http://torrent-live.peersm.com">http://torrent-live.peersm.com</a>
Peersm : <a class="moz-txt-link-freetext" href="http://www.peersm.com">http://www.peersm.com</a></pre>
</body>
</html>
--------------9AF7A061FABC2FC78A967B1D--
|
