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
Subject: Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE
 OP_IF OP_PUSH
Precedence: list

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