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