<oembed><type>rich</type><version>1.0</version><author_name>npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n</author_name><author_url>https://nostr.ae/npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-11-13&#xA;📝 Original message:On Friday, November 13, 2015 2:56:55 AM Chun Wang via bitcoin-dev wrote:&#xA;&gt; * 2 MB, 210000 &lt;= height &lt; 420000;&#xA;&#xA;It&#39;s impossible to have the entire network upgraded in the past.&#xA;&#xA;Furthermore, 1 MB is already too large a block size today. While blocks don&#39;t &#xA;need to be as big as the limit, it&#39;s better to have the limit approximate what &#xA;is reasonably possible without straining the network. So while your proposed &#xA;schedule change might be workable (if miners can be trusted to keep actual &#xA;block size under 50% pending future improvements), I prefer the proposal &#xA;beginning at the next subsidy halving (which we&#39;re well on the way to).&#xA;&#xA;Luke</html></oembed>