<oembed><type>rich</type><version>1.0</version><author_name>npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r</author_name><author_url>https://nostr.ae/npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-12-16&#xA;📝 Original message:On Wed, Dec 16, 2015 at 10:08 PM, Jeff Garzik &lt;jgarzik at gmail.com&gt; wrote:&#xA;&gt;&gt; You present this as if the Bitcoin Core development team is in charge&#xA;&gt;&gt; of deciding the network consensus rules, and is responsible for making&#xA;&gt;&gt; changes to it in order to satisfy economic demand. If that is the&#xA;&gt;&gt; case, Bitcoin has failed, in my opinion.&#xA;&gt;&#xA;&gt;&#xA;&gt; This circles back to Problem #1:   Avoidance of a choice is a still a choice&#xA;&gt; - failing to ACK a MAX_BLOCK_SIZE increase still creates very real Economic&#xA;&gt; Change Event risk.&#xA;&#xA;We are not avoiding a choice. We don&#39;t have the authority to make a choice.&#xA;&#xA;&gt; And #3:  If the likely predicted course is that Bitcoin Core will not accept&#xA;&gt; a protocol change changing MAX_BLOCK_SIZE via hard fork in the short term,&#xA;&gt; the core dev team should communicate that position clearly to users and&#xA;&gt; media.&#xA;&#xA;I indeed think we can communicate much better that deciding consensus&#xA;rules is not within our power.&#xA;&#xA;-- &#xA;Pieter</html></oembed>