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
|
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 C45E8C002B
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 5 Feb 2023 11:59:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 8AF24606F2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 5 Feb 2023 11:59:36 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 8AF24606F2
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.554
X-Spam-Level:
X-Spam-Status: No, score=-0.554 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001,
RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 C6-p4O4CYL24
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 5 Feb 2023 11:59:35 +0000 (UTC)
X-Greylist: delayed 00:18:50 by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 0B06B606EC
Received: from 1.mo548.mail-out.ovh.net (1.mo548.mail-out.ovh.net
[178.32.121.110])
by smtp3.osuosl.org (Postfix) with ESMTPS id 0B06B606EC
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 5 Feb 2023 11:59:34 +0000 (UTC)
Received: from mxplan6.mail.ovh.net (unknown [10.108.20.173])
by mo548.mail-out.ovh.net (Postfix) with ESMTPS id 8353420C20;
Sun, 5 Feb 2023 11:40:42 +0000 (UTC)
Received: from peersm.com (37.59.142.99) 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, 5 Feb
2023 12:40:36 +0100
Authentication-Results: garm.ovh; auth=pass
(GARM-99G003901c20ff-3a3a-469f-8f6d-0a1b248fd2ab,
0098AF237195B9B300583606E28666A1C7481BE7) smtp.auth=aymeric@peersm.com
X-OVh-ClientIp: 92.184.100.162
To: Peter Todd <pete@petertodd.org>, Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>, 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>
<28C74556-8AB4-4E16-AC7D-7F3FAA0A29AC@petertodd.org>
From: Aymeric Vitte <aymeric@peersm.com>
Message-ID: <0267d5bb-a54b-894b-3d45-e6cb89eb86a5@peersm.com>
Date: Sun, 5 Feb 2023 12:40:38 +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: <28C74556-8AB4-4E16-AC7D-7F3FAA0A29AC@petertodd.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [37.59.142.99]
X-ClientProxiedBy: DAG3EX1.mxp6.local (172.16.2.21) To DAG6EX2.mxp6.local
(172.16.2.52)
X-Ovh-Tracer-GUID: 13c83752-645b-4d15-b325-0e4e8b6c34c7
X-Ovh-Tracer-Id: 10787528484164690909
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: -100
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvhedrudeggedgfeduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhfhkffffgggjggtgfhisehtqhertddtfeejnecuhfhrohhmpeethihmvghrihgtucggihhtthgvuceorgihmhgvrhhitgesphgvvghrshhmrdgtohhmqeenucggtffrrghtthgvrhhnpeegkeefjeefvdehueehhfeghfdtveeihfeggeehleeijeduueelvddufeeufeegueenucffohhmrghinhepphgvvghrshhmrdgtohhmpdhlihhnkhgvughinhdrtghomhdpghhithhhuhgsrdgtohhmnecukfhppeduvdejrddtrddtrddupdefjedrheelrddugedvrdelleenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeduvdejrddtrddtrddupdhmrghilhhfrhhomhepoegrhihmvghrihgtsehpvggvrhhsmhdrtghomheqpdhnsggprhgtphhtthhopedupdhrtghpthhtohepvehhrhhishhtohhphhgvrhetsehlihhfvgifihhthhgrlhgrtghrihhthidrtghomhdpsghithgtohhinhdquggvvheslhhishhtshdrlhhinhhugihfohhunhgurghtihhonhdrohhrghdpphgvthgvsehpvghtvghrthhouggurdhorhhgpdfovfetjfhoshhtpehmohehgeekpdhmohguvgepshhmthhpohhuth
X-Mailman-Approved-At: Sun, 05 Feb 2023 15:47:20 +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, 05 Feb 2023 11:59:36 -0000
I think logically:
- if you want to store something big and can afford several txs in your
design, then you use something like witness
- if you want to store small things like signatures, addresses hashes
and some metadata and your design does not make several txs easy, then
you use OP_RETURN
Then how can we move forward with several OP_RETURN and no size limit?
I can start posting a bug/enhancement proposal in bitcoin repo but can't
write the PR
Le 05/02/2023 =C3=A0 01:04, Peter Todd a =C3=A9crit :
>
> On February 5, 2023 12:09:02 AM GMT+01:00, Aymeric Vitte via bitcoin-de=
v <bitcoin-dev@lists.linuxfoundation.org> wrote:
>> I don't know, what number would you advise? When I made the
>> bitcoin-transactions nodejs module some years ago the limit (from the
>> specs) was 512B
> 1) Allowing only one OpReturn output causes problems trying to compose =
different uses of OpReturn. We should allow any number of OpReturn output=
s.
>
> 2) There's no reason to put a size limit given all the other ways peopl=
e can publish data, including with a 75% discount. Let the fee market dea=
l with it.
--=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
|
