<oembed><type>rich</type><version>1.0</version><author_name>npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_name><author_url>https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-05-29&#xA;📝 Original message:&gt;&#xA;&gt; By the time a hard fork can happen, I expect average block size will be&#xA;&gt; above 500K.&#xA;&gt;&#xA;&#xA;Yes, possibly.&#xA;&#xA;&#xA;&gt; Would you support a rule that was &#34;larger of 1MB or 2x average size&#34; ?&#xA;&gt; That is strictly better than the situation we&#39;re in today.&#xA;&gt;&#xA;&#xA;It is, but only by a trivial amount - hitting the limit is still very&#xA;likely. I don&#39;t want to see this issue come up over and over again. Ideally&#xA;never. We shouldn&#39;t be artificially throttling organic growth of the&#xA;network, especially not by accident.&#xA;&#xA;IMO it&#39;s not even clear there needs to be a size limit at all. Currently&#xA;the 32mb message cap imposes one anyway, but if miners can always just&#xA;discourage blocks over some particular size if they want to.&#xA;&#xA;But I can get behind a 20mb limit (or 20mb+N) as it represents a reasonable&#xA;compromise: the limit still exists, it&#39;s far below VISA capacity etc, but&#xA;it should also free up enough space that everyone can get back to what we&#xA;*should* be focusing on, which is user growth!&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150529/9ca670f1/attachment.html&gt;</html></oembed>