<oembed><type>rich</type><version>1.0</version><author_name>npub1ldcq03p2qe58u0xnlwa35wchjuhz49y6ueu5ghmtjetez9xstnvsmt8ur6</author_name><author_url>https://nostr.ae/npub1ldcq03p2qe58u0xnlwa35wchjuhz49y6ueu5ghmtjetez9xstnvsmt8ur6</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-04-05&#xA;📝 Original message:On Wed, Apr 5, 2017 at 7:31 PM, Peter Todd via bitcoin-dev &lt;&#xA;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt;&#xA;&gt; While I&#39;m in favour of blocking covert usage of ASICBOOST, there&#39;s every&#xA;&gt; reason&#xA;&gt; to block non-covert usage of it as well. In a low margin business like&#xA;&gt; mining,&#xA;&gt; the advatange it gives is enormous - quite possibly 10x your profit margin&#xA;&gt; -&#xA;&gt; and given that barrier free access to being able to purchase ASICs is&#xA;&gt; already&#xA;&gt; an archilles heal for Bitcoin there is every reason to eliminate this legal&#xA;&gt; vulnerability. Additionally, it&#39;s a technical vulnerability as well: we&#xA;&gt; want&#xA;&gt; getting into the ASIC manufacturing and design business to have as low&#xA;&gt; barriers&#xA;&gt; to entry as is feasible, and the ASICBOOST exploit significantly increases&#xA;&gt; the&#xA;&gt; minimum capital requirements to do so.&#xA;&gt;&#xA;&#xA;Asicboost also has the problem that it isn&#39;t treating the hashing as a&#xA;black box, and thus has impacts on what gets mined. In particular it&#xA;creates an incentive to make blocks smaller. That&#39;s a very unwanted effect,&#xA;and anything like it should be engineered out on principle.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170405/bd9a7d92/attachment.html&gt;</html></oembed>