From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 623A2C000B for ; Tue, 20 Apr 2021 01:23:17 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 4385460758 for ; Tue, 20 Apr 2021 01:23:17 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: 1.391 X-Spam-Level: * X-Spam-Status: No, score=1.391 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: smtp3.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=cock.li 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 514-TsMqt8T8 for ; Tue, 20 Apr 2021 01:23:15 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from mail.cock.li (unknown [37.120.193.123]) by smtp3.osuosl.org (Postfix) with ESMTPS id A25E060731 for ; Tue, 20 Apr 2021 01:23:15 +0000 (UTC) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cock.li; s=mail; t=1618881793; bh=2ysf8sO/yCim8RArEzTc/GtQ/hhAhbyhXNOCnWKytho=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=N+fSVmICq43Mhjg1FVt1bGTCHqy7KQjQ/xE3YSAObpEkjERm+G6fZXo+I2YWieA5m 6uIkhJqBdtcezlki5wUlTYOcxjYd0IVRz8Q6s1SFTWoKZaftpg50PZm5kGNvQri0jT imnY7twt8B2TdUBJkdyU50EjN47LOBE7EzbEySjMAVPCqiJuVK3TGlVKdUwlK20aVj 7LquXEihYzsTChqG/I0VjCCBZNw2+kS5hAVm2K/0Txqb375SbtXSGPuoHRRNIJx5cV VDV1Y2whENnafvkbLxg/6fry9m/wNRI1xEkJB64wVnMXU3MfhLvxYJXn8pxafwsSfu /m6pyBvLM8LOQ== Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 20 Apr 2021 01:23:12 +0000 From: yanmaani@cock.li To: Ruben Somsen , Bitcoin Protocol Discussion In-Reply-To: References: Message-ID: <050674b8bc51cff11e0a6e105880b647@cock.li> X-Sender: yanmaani@cock.li User-Agent: Roundcube Webmail/1.3.15 X-Mailman-Approved-At: Tue, 20 Apr 2021 02:28:44 +0000 Cc: christopher.gilliard@gmail.com Subject: Re: [bitcoin-dev] BIP - limiting OP_RETURN / HF 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, 20 Apr 2021 01:23:17 -0000 > If only one hash is allowed per block, then those who wish to utilize > the hash will have to out-bid each other ("fee-bidding"). This hash can > then be used to create another chain ("merged-mining") Merged mining at present only needs one hash for a merkle root, and that's stored in the coinbase. It would be even simpler to add the following rules: 1) No OP_RETURN transactions allowed at all 2) If you want to commit data, do so in that one transaction in the coinbase Also curious about how you'd handle the payment - do I need to put in a transaction that burns bitcoins for the tx fee? That isn't free in terms of storage either.