Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 84D2EC002A for ; 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 ; 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 ; 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 ; 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 , Bitcoin Protocol Discussion , Moth References: From: Aymeric Vitte 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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



Le 08/05/2023 à 23:43, Christopher Allen via bitcoin-dev a écrit :
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=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?

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 à 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--