{"type":"rich","version":"1.0","author_name":"npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu","author_url":"https://nostr.ae/npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2017-03-28\n📝 Original message:Not sure what \"last week's meeting\" is in reference to?\n\nAgreed that the hard fork should be well-prepared, but I think its\ndangerous to think that a hard fork as agreed upon would be a simple\nrelaxation of the block size. For example, Johnson Lau's previous\nproposal, Spoonnet, which I think is probably one of the better ones,\nwould be incompatible with these rules.\n\nI, of course, worry about what happens if we cannot come to consensus on\na number to soft fork down to, potentially significantly risking miner\nprofits (and, thus, the security of Bitcoin) if a group is able to keep\nthings \"at the status quo\". That said, for that to be alleviated we\ncould simply do something based on historical transaction growth (which\nis somewhat linear, with a few inflection points), but that number ends\nup being super low (eg somewhere around 2MB at the next halving, which\nSegWit itself already provides :/.\n\nWe could, of course, focus on designing a hard fork's activation and\ntechnical details, with a very large block size increase in it (ie\ncloser to 4/6MB at the next halving or so, something we at least could\nbe confident we could develop software for), with intention to soft fork\nit back down if miner profits are suffering.\n\nMatt\n\nOn 03/28/17 16:59, Wang Chun via bitcoin-dev wrote:\n\u003e I've proposed this hard fork approach last year in Hong Kong Consensus\n\u003e but immediately rejected by coredevs at that meeting, after more than\n\u003e one year it seems that lots of people haven't heard of it. So I would\n\u003e post this here again for comment.\n\u003e \n\u003e The basic idea is, as many of us agree, hard fork is risky and should\n\u003e be well prepared. We need a long time to deploy it.\n\u003e \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\u003e \n\u003e With this patch in core's next release, Bitcoin works just as before,\n\u003e no fork will ever occur, until spring 2020. But everyone knows there\n\u003e will be a fork scheduled. Third party services, libraries, wallets and\n\u003e exchanges will have enough time to prepare for it over the next three\n\u003e years.\n\u003e \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. We'll have enough time to discuss\n\u003e all these proposals and decide which one to go. Take an example, if we\n\u003e choose to fork to only 2MB, since 32MiB already scheduled, reduce it\n\u003e from 32MiB to 2MB will be a soft fork.\n\u003e \n\u003e Anyway, we must code something right now, before it becomes too late.\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e"}