<oembed><type>rich</type><version>1.0</version><author_name>npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8</author_name><author_url>https://nostr.ae/npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-04-08&#xA;📝 Original message:To be more specific, why &#34;being higher will secure the Bitcoin network&#xA;better against newer optimizations&#34;?&#xA;Or, to be more clear, let&#39;s forget about future &#34;optimizations&#34;, let&#39;s&#xA;just think of an attacker. Does asicboost being used by all miners&#xA;make the system more secure against an attacker? No, for the attacker&#xA;can use asicboost too.&#xA;What about the case when not all the miners are using asicboost? Then&#xA;the attacker can actually get an advantage by suing asicboost.&#xA;&#xA;Sometimes people compare asicboost with the use of asics in general as&#xA;both providing more security for the network and users. But I don&#39;t&#xA;think this is accurate. The existence of sha256d asics makes an attack&#xA;with general purpose computing hardware (or even more specialized&#xA;architectures like gpgpu) much more expensive and unlikely. As an&#xA;alternative the attacker can spend additional resources investing in&#xA;asics himself (again, making many attacks more expensive and&#xA;unlikely).&#xA;&#xA;But as far as I know, asicboost can be implemented with software&#xA;running on general purpose hardware that integrates with regular&#xA;sha256d asics. There is probably an advantage on having the asicboost&#xA;implementation &#34;in the same box&#34; as the sha256d, yet again the&#xA;attacker can invest in hardware with the competitive advantage from&#xA;having asicboost more intergrated with the sha256d asics too.&#xA;&#xA;To reiterate, whether all miners use asicboost or only a subset of&#xA;them, I remain unconvinced that provides any additional security to&#xA;the network (to be more precise whether that makes &#34;tx history harder&#xA;to rewrite&#34;), even if it results on the hashrate charts looking &#34;more&#xA;secure&#34;.&#xA;&#xA;&#xA;On Sat, Apr 8, 2017 at 6:27 PM, Jorge Timón &lt;jtimon at jtimon.cc&gt; wrote:&#xA;&gt;&#xA;&gt;&#xA;&gt; On 8 Apr 2017 5:06 am, &#34;Jimmy Song via bitcoin-dev&#34;&#xA;&gt; &lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt;&#xA;&gt; Praxeology Guy,&#xA;&gt;&#xA;&gt;&gt; Why would the actual end users of Bitcoin (the long term and short term&#xA;&gt;&gt; owners of bitcoins) who run fully verifying nodes want to change Bitcoin&#xA;&gt;&gt; policy in order to make their money more vulnerable to 51% attack?&#xA;&gt;&#xA;&gt;&#xA;&gt; Certainly, if only one company made use of the extra nonce space, they would&#xA;&gt; have an advantage. But think of it this way, if some newer ASIC optimization&#xA;&gt; comes up, would you rather have a non-ASICBoosted hash rate to defend with&#xA;&gt; or an ASICBoosted hash rate? Certainly, the latter, being higher will secure&#xA;&gt; the Bitcoin network better against newer optimizations.&#xA;&gt;&#xA;&gt;&#xA;&gt; Why?</html></oembed>