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
|
Return-Path: <aymeric@peersm.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 60DF0C002B
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 5 Feb 2023 12:47:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id 2749A4160D
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 5 Feb 2023 12:47:41 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 2749A4160D
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, 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 smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id AFdGeUrs_xgg
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 5 Feb 2023 12:47:39 +0000 (UTC)
X-Greylist: delayed 19:46:14 by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 5A1F14160B
Received: from 4.mo552.mail-out.ovh.net (4.mo552.mail-out.ovh.net
[178.33.43.201])
by smtp4.osuosl.org (Postfix) with ESMTPS id 5A1F14160B
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 5 Feb 2023 12:47:39 +0000 (UTC)
Received: from mxplan6.mail.ovh.net (unknown [10.109.138.7])
by mo552.mail-out.ovh.net (Postfix) with ESMTPS id 0778E29121;
Sun, 5 Feb 2023 12:47:37 +0000 (UTC)
Received: from peersm.com (37.59.142.108) 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 13:47:36 +0100
Authentication-Results: garm.ovh; auth=pass
(GARM-108S0025a606c24-b342-4cce-afe3-1a47f558f2e4,
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>
<0267d5bb-a54b-894b-3d45-e6cb89eb86a5@peersm.com>
<B7A37621-AC21-43FE-A60D-7516FFD69FCF@petertodd.org>
From: Aymeric Vitte <aymeric@peersm.com>
Message-ID: <92f7a26f-293c-b1e6-d9b2-8de44af5e31c@peersm.com>
Date: Sun, 5 Feb 2023 13:47: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: <B7A37621-AC21-43FE-A60D-7516FFD69FCF@petertodd.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [37.59.142.108]
X-ClientProxiedBy: DAG3EX1.mxp6.local (172.16.2.21) To DAG6EX2.mxp6.local
(172.16.2.52)
X-Ovh-Tracer-GUID: 6dcd2721-1ecc-44a9-bb43-00a45cfd5ae7
X-Ovh-Tracer-Id: 11918776417655481309
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: -100
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvhedrudeggedggeegucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhfhkffffgggjggtgfhisehtkeertddtfeejnecuhfhrohhmpeethihmvghrihgtucggihhtthgvuceorgihmhgvrhhitgesphgvvghrshhmrdgtohhmqeenucggtffrrghtthgvrhhnpeektedvhffgffefgefgleelgfduteehfeefieffieekueevgeeivdffvedvgfelvdenucffohhmrghinhepghhithhhuhgsrdgtohhmpdhpvggvrhhsmhdrtghomhdplhhinhhkvgguihhnrdgtohhmnecukfhppeduvdejrddtrddtrddupdefjedrheelrddugedvrddutdeknecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepuddvjedrtddrtddruddpmhgrihhlfhhrohhmpeeorgihmhgvrhhitgesphgvvghrshhmrdgtohhmqedpnhgspghrtghpthhtohepuddprhgtphhtthhopeevhhhrihhsthhophhhvghrteeslhhifhgvfihithhhrghlrggtrhhithihrdgtohhmpdgsihhttghoihhnqdguvghvsehlihhsthhsrdhlihhnuhigfhhouhhnuggrthhiohhnrdhorhhgpdhpvghtvgesphgvthgvrhhtohguugdrohhrghdpoffvtefjohhsthepmhhoheehvddpmhhouggvpehsmhhtphhouhht
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 12:47:41 -0000
Yes I agree, let people decide and since taproot has no limits then it
sould be the same for OP_RETURN
I posted https://github.com/bitcoin/bitcoin/issues/27043
Le 05/02/2023 à 13:06, Peter Todd a écrit :
>
> On February 5, 2023 12:40:38 PM GMT+01:00, Aymeric Vitte <aymeric@peersm.com> wrote:
>> 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?
> Because what matters is the impact on other users. OpReturn isn't in UTXO space and doesn't even take advantage of the witness discount, so it clearly has minimal impact.
>
> Since it has minimal impact, there's no reason to micromanage exactly how people use it. Let them decide for themselves with the fee market. This is exactly the same as how we didn't put artificial limits on Taproot.
--
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/Ayms/029125db2583e1cf9c3209769eb2cdd7
A bitcoin NFT system: https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7
Move your coins by yourself (browser version): https://peersm.com/wallet
Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions
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.peersm.com
Peersm : http://www.peersm.com
|
