<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-08&#xA;📝 Original message:Pavel,&#xA;&#xA;&#xA;&gt; I agree. I only wanted to make clear, that the impact would be&#xA;&gt; significant. Lot of parties would be involved with nonequivalent&#xA;&gt; starting positions.&#xA;&gt;&#xA;&gt;&#xA;I agree with you. I believe nonequivalent starting positions are the norm&#xA;in mining, not the exception and hence don&#39;t believe this to be a problem.&#xA;&#xA;&#xA;&gt;&#xA;&gt; I think the ASICBoost can and should be prevented completely.&#xA;&gt;&#xA;&#xA;It certainly can be and from the responses I&#39;m getting, I believe there&#xA;would be at least a few people that would enthusiastically support a BIP to&#xA;do that. That is, however, a separate issue than my proposal. My proposal&#xA;aims to bring ASICBoost out into the open *while it is still possible*. A&#xA;BIP to prevent ASICBoost completely is in that sense compatible.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170408/06fbf04c/attachment.html&gt;</html></oembed>