<oembed><type>rich</type><version>1.0</version><author_name>npub1mju50kqcm07heu967fkq6h4kq666xgekc4yrldf7q52xx9vr8jnsrdxnq7</author_name><author_url>https://nostr.ae/npub1mju50kqcm07heu967fkq6h4kq666xgekc4yrldf7q52xx9vr8jnsrdxnq7</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-03-28&#xA;📝 Original message:On Tuesday, 28 March 2017 18:59:32 CEST Wang Chun via bitcoin-dev wrote:&#xA;&gt; Despite spam tx on the network, the block capacity is approaching its&#xA;&gt; limit, and we must think ahead. Shall we code a patch right now, to&#xA;&gt; remove the block size limit of 1MB, but not activate it until far in&#xA;&gt; the future. I would propose to remove the 1MB limit at the next block&#xA;&gt; halving in spring 2020, only limit the block size to 32MiB which is&#xA;&gt; the maximum size the current p2p protocol allows. This patch must be&#xA;&gt; in the immediate next release of Bitcoin Core.&#xA;...&#xA;&gt; We don&#39;t yet have an agreement on how to increase the block size&#xA;&gt; limit. There have been many proposals over the past years, like&#xA;&gt; BIP100, 101, 102, 103, 104, 105, 106, 107, 109, 148, 248, BU, and so&#xA;&gt; on. These hard fork proposals, with this patch already in Core&#39;s&#xA;&gt; release, they all become soft fork.&#xA;&#xA;I think that is a very smart idea, thank you for making it.&#xA;-- &#xA;Tom Zander&#xA;Blog: https://zander.github.io&#xA;Vlog: https://vimeo.com/channels/tomscryptochannel</html></oembed>