<oembed><type>rich</type><version>1.0</version><author_name>npub1a9hemj8hf6exprh5q6w8y70n9mm36h6pt5vlp2wtl9gjwfzaqjrqeuvwuq</author_name><author_url>https://nostr.ae/npub1a9hemj8hf6exprh5q6w8y70n9mm36h6pt5vlp2wtl9gjwfzaqjrqeuvwuq</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-04-08&#xA;📝 Original message:&gt; Second, we can make this change relatively quickly. Most of the Segwit testing stays valid and this change can be deployed relatively quickly.&#xA;&#xA;It is true only for nodes software. Most of the world&#39;s mining&#xA;infrastructure (at least for pool mining) is not ready for such&#xA;change. Current version of Stratum protocol doesn&#39;t support block&#xA;version changing. A broad adoption would require:&#xA;&#xA;- A new standard extension to the mining protocol (generally, we want&#xA;the hash rate to be free to change the used pool without efficiency&#xA;loss)&#xA;- Pool operators must change their software.&#xA;- All miners must update their firmware IF they have compatible&#xA;hardware (we know there is compatible hardware out there but&#xA;definitely not all of the currently used). The firmware can be changed&#xA;after the mining protocol extension is settled.&#xA;&#xA;Until all miners update (firmware or hardware), the change encourages&#xA;large difference in mining efficiency. And IMO it gives another&#xA;advantage to large mining operations in general.&#xA;&#xA;&gt; But think of it this way, if some newer ASIC optimization comes up, would you rather have a non-ASICBoosted hash rate to defend with or an ASICBoosted hash rate? Certainly, the latter, being higher will secure the Bitcoin network better against newer optimizations.&#xA;&#xA;You make a strong assumption that the new optimization is not&#xA;compatible with overt ASICBoost. If it is compatible, ASICBoost&#xA;doesn&#39;t help you with &#34;defending against&#34; the new optimization at all.&#xA;And it can be the case that the new optimization is based on ASICBoost&#xA;so you can make the situation &#34;worse&#34; by allowing it.&#xA;&#xA;&gt; Certainly, if only one company made use of the extra nonce space, they would have an advantage.&#xA;&#xA;Can you explain why the reality should be significantly different? In&#xA;sufficiently near future.&#xA;&#xA;&gt; Is that patented in any jurisdiction, all jurisdictions or only certain jurisdictions? Would a patent granted for SHA256 in Swaziland be sufficient for Bitcoin to change the Proof of Work algorithm?&#xA;&#xA;We don&#39;t have to deal with any such theoretical situation now. You&#xA;proposal goes in opposite direction, by adding support for patented&#xA;algorithm. I don&#39;t know myself what the possible legal implications&#xA;are (maybe only for a subset of miners) so I consider it as an&#xA;unnecessary risk. At least before some conclusive legal analysis says&#xA;differently.</html></oembed>