MIME-Version: 1.0
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 <rsomsen@gmail.com>, Bitcoin Protocol Discussion
 <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <CAPv7Tja=4ZFm5+gHw+wMcZyPEqeQiVx-AjyXsRn0T8a+tXHb1A@mail.gmail.com>
References: <CAK=nyAxOa8fsVfxucH7WTTMn25BCzgQ28h_sNsunedpCoRXjjQ@mail.gmail.com>
 <CABE6yHscUPAcyK58DvqhOnxSOoPMBAy9aMUmReJYSkBit-Mekg@mail.gmail.com>
 <CAPv7Tja=4ZFm5+gHw+wMcZyPEqeQiVx-AjyXsRn0T8a+tXHb1A@mail.gmail.com>
Message-ID: <050674b8bc51cff11e0a6e105880b647@cock.li>
User-Agent: Roundcube Webmail/1.3.15
Cc: christopher.gilliard@gmail.com
Subject: Re: [bitcoin-dev] BIP - limiting OP_RETURN / HF
Precedence: list

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