<oembed><type>rich</type><version>1.0</version><author_name>npub1ldcq03p2qe58u0xnlwa35wchjuhz49y6ueu5ghmtjetez9xstnvsmt8ur6</author_name><author_url>https://nostr.ae/npub1ldcq03p2qe58u0xnlwa35wchjuhz49y6ueu5ghmtjetez9xstnvsmt8ur6</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-03-29&#xA;📝 Original message:On Tue, Mar 28, 2017 at 9:59 AM, Wang Chun via bitcoin-dev &lt;&#xA;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt;&#xA;&gt; The basic idea is, as many of us agree, hard fork is risky and should&#xA;&gt; be well prepared. We need a long time to deploy it.&#xA;&gt;&#xA;&#xA;Much as it may be appealing to repeal the block size limit now with a grace&#xA;period until a replacement is needed in a repeal and replace strategy, it&#39;s&#xA;dubious to assume that an idea can be agreed upon later when it can&#39;t be&#xA;agreed upon now. Trying to put a time limit on it runs into the possibility&#xA;that you&#39;ll find that whatever reasons there were for not having general&#xA;agreement on a new setup before still apply, and running into the&#xA;embarrassing situation of winding up sticking with the status quo after&#xA;much sturm and drang.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170328/e04b8d19/attachment.html&gt;</html></oembed>