<oembed><type>rich</type><version>1.0</version><author_name>npub17w8rw3wtcr03zdsdjhmcj37w0g6l79gsspleltsznexdktv0qw0qd3nc05</author_name><author_url>https://nostr.ae/npub17w8rw3wtcr03zdsdjhmcj37w0g6l79gsspleltsznexdktv0qw0qd3nc05</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-04-07&#xA;📝 Original message:I&#39;ve gotten feedback from Adam Back that you actually don&#39;t need all 32&#xA;bits in the header for overt ASICBoost, so I&#39;m modifying my proposal. Of&#xA;the 32-bit version field, bits 16 to 23 are reserved for miners, the&#xA;witness commitment stays as defined in BIP-141 except that it&#39;s now&#xA;required. BIP9 then is modified so that bits 16 to 23 are now no longer&#xA;usable.&#xA;&#xA;On Fri, Apr 7, 2017 at 3:06 PM, Jimmy Song &lt;jaejoon at gmail.com&gt; wrote:&#xA;&#xA;&gt; Hey everyone, This is an idea that I had about Segwit and Gregory&#39;s&#xA;&gt; proposal from yesterday that I wanted to run by everyone on this list. I&#39;m&#xA;&gt; not at all sure what this would mean for non-upgraded nodes on the network&#xA;&gt; and would like feedback on that. This is not a formal BIP as it&#39;s a&#xA;&gt; modification to a previously submitted one, but I&#39;m happy to formalize it&#xA;&gt; if it would help.&#xA;&gt; ----------------------------------------&#xA;&gt; MotivationOne of the interesting aspects of Gregory Maxwell’s proposal is&#xA;&gt; that it only precludes the covert version of ASICBoost. He specifically&#xA;&gt; left the overt version alone.&#xA;&gt;&#xA;&gt; Overt ASICBoost requires grinding on the version bits of the Block header&#xA;&gt; instead of the Merkle Root. This is likely more efficient than the Merkle&#xA;&gt; Root grinding (aka covert ASICBoost) and requires way less resources&#xA;&gt; (much less RAM, SHA256 calculations, no tx shuffling, etc).&#xA;&gt;&#xA;&gt; If we combine Gregory Maxwell’s proposal with BIP-141 (Segwit) and add a&#xA;&gt; slight modification, this should, in theory, make ASICBoost a lot more&#xA;&gt; useful to miners and appeal to their financial interests.&#xA;&gt; The Modification&#xA;&gt;&#xA;&gt; Currently, the version bits (currently 4 bytes, or 32 bits) in the header&#xA;&gt; are used for BIP9 signaling. We change the version bits to a nonce-space so&#xA;&gt; the miners can use it for overt ASICBoost. The 32-bits are now moved over&#xA;&gt; to the Coinbase transaction as part of the witness commitment. The witness&#xA;&gt; commitment goes from 38 bytes to 42 bytes, with the last 4 bytes being used&#xA;&gt; as the version bits in the block header previously. The witness commitment&#xA;&gt; becomes required as per Gregory Maxwell’s proposal.&#xA;&gt; Reasoning&#xA;&gt;&#xA;&gt; First, this brings ASICBoost out into the open. Covert ASICBoost becomes&#xA;&gt; much more costly and overt ASICBoost is now encouraged.&#xA;&gt;&#xA;&gt; Second, we can make this change relatively quickly. Most of the Segwit&#xA;&gt; testing stays valid and this change can be deployed relatively quickly.&#xA;&gt;&#xA;&gt; Note on SPV clients&#xA;&gt;&#xA;&gt; Currently Segwit stores the witness commitment in the Coinbase tx, so&#xA;&gt; lightweight clients will need to get the Coinbase tx + Merkle proof to&#xA;&gt; validate segwit transactions anyway. Putting block version information in&#xA;&gt; the Coinbase tx will not impose an extra burden on upgraded light clients.&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170407/8f71b5b3/attachment.html&gt;</html></oembed>