From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 6EC49C002B for ; Thu, 2 Feb 2023 12:24:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 4976440C46 for ; Thu, 2 Feb 2023 12:24:24 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 4976440C46 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HV_gjcXSt-g8 for ; Thu, 2 Feb 2023 12:24:23 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 0C92F40A09 Received: from smtpout3.mo529.mail-out.ovh.net (smtpout3.mo529.mail-out.ovh.net [46.105.54.81]) by smtp2.osuosl.org (Postfix) with ESMTPS id 0C92F40A09 for ; Thu, 2 Feb 2023 12:24:23 +0000 (UTC) Received: from mxplan6.mail.ovh.net (unknown [10.109.146.41]) by mo529.mail-out.ovh.net (Postfix) with ESMTPS id 2BE3E215B1; Thu, 2 Feb 2023 12:24:20 +0000 (UTC) Received: from peersm.com (37.59.142.107) 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; Thu, 2 Feb 2023 13:24:20 +0100 Authentication-Results: garm.ovh; auth=pass (GARM-107S0010851967f-c80c-4851-8a3a-42fa0f27b640, 6AA1D679F834A14CBEAA49266E816969C7C1CEBF) smtp.auth=aymeric@peersm.com X-OVh-ClientIp: 92.184.100.16 To: Peter Todd References: <764E460B-C0C6-47B8-A97E-F7CBC81FD645@petertodd.org> <16446c77-c9de-7b11-8e66-7f8e20421cba@peersm.com> From: Aymeric Vitte Message-ID: <67fd09e8-f70b-c1be-78c3-f3ec936dfee8@peersm.com> Date: Thu, 2 Feb 2023 13:24:12 +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: Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit X-Originating-IP: [37.59.142.107] X-ClientProxiedBy: DAG7EX1.mxp6.local (172.16.2.61) To DAG6EX2.mxp6.local (172.16.2.52) X-Ovh-Tracer-GUID: dda415aa-4edd-4a03-be5f-edaf82167439 X-Ovh-Tracer-Id: 12354499678104806365 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvhedrudefkedgfeejucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhevhffkffgfgggjtgfgihesthekredttdefheenucfhrhhomhepteihmhgvrhhitgcugghithhtvgcuoegrhihmvghrihgtsehpvggvrhhsmhdrtghomheqnecuggftrfgrthhtvghrnhepuefgvdeuudeuvdeguddtteeihedttdejudeuffelfedutdejteduvedtheffgeeunecuffhomhgrihhnpehpvggvrhhsmhdrtghomhdplhhinhhkvgguihhnrdgtohhmpdhgihhthhhusgdrtghomhenucfkphepuddvjedrtddrtddruddpfeejrdehledrudegvddruddtjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeduvdejrddtrddtrddupdhmrghilhhfrhhomhepoegrhihmvghrihgtsehpvggvrhhsmhdrtghomheqpdhnsggprhgtphhtthhopedupdhrtghpthhtoheprghpohgvlhhsthhrrgesfihpshhofhhtfigrrhgvrdhnvghtpdgsihhttghoihhnqdguvghvsehlihhsthhsrdhlihhnuhigfhhouhhnuggrthhiohhnrdhorhhgpdhpvghtvgesphgvthgvrhhtohguugdrohhrghdpoffvtefjohhsthepmhhohedvledpmhhouggvpehsmhhtphhouhht X-Mailman-Approved-At: Thu, 02 Feb 2023 13:02:30 +0000 Cc: Bitcoin Protocol Discussion 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2023 12:24:24 -0000 Thanks, then this limitation should be rethought I think (see the email I just sent replying to the coloured thread) Because it forces people to store in witness (less easy to track/show I believe) or adopt some deviant behavior (like storing in addresses where the utxo will remain unspendable forever) Le 02/02/2023 à 12:49, Peter Todd a écrit : > On Thu, Feb 02, 2023 at 12:45:42PM +0100, Aymeric Vitte wrote: >> As far as I can read nobody replied to the initial question: what is >> considered as good/best practice to store in Bitcoin? > Your answer is beyond not putting unspendable data in the UTXO set, the exact > details don't really matter. Do what makes sense for your specific application. > >> Reiterating my question: what are the current rules for OP_RETURN, max >> size and number of OP_RETURN per tx > Max 80 bytes, one OpReturn output per tx. > > This of course is the standardness rule. With a miner willing to mine non-std > transactions anything goes. > -- 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