{"type":"rich","version":"1.0","author_name":"npub18gjvug29c4yg46lmplq38e75gg6wn5mn8taytckcsr4jt8p74h3s5knkzl","author_url":"https://nostr.ae/npub18gjvug29c4yg46lmplq38e75gg6wn5mn8taytckcsr4jt8p74h3s5knkzl","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-06-15\n📝 Original message:Wasn't the XT hard fork proposed as a last resort, should the bitcoin-core\nmaintainers simply refuse to lift the 1Mb limit? No one wants to go that\nroute. An alternate hard-fork proposal like BIP100 that gets consensus, or\na modified version of gavin's that ups the limit to 8Mb instead of 20Mb, or\nhell even some major changes to the non-consunsus code to make it\nadequately handle the situation when blocks fill up, and allow wallet\nsoftware to continue working with a send-and-forget use pattern, any of\nthese would be enough to avoid the need for an XT only hard-fork.\n\nSo far BIP100 is the only one that seems to actually be getting any sort of\nmomentum toward consensus, and it was proposed... 2 days ago? When the XT\nfork was proposed as a last resort, it was when the opponents were (to my\nunderstanding) suggesting we just let blocks fill up, and hopefully things\nwould just work out on their own.\n\n\n\nAaron Voisine\nco-founder and CEO\nbreadwallet.com\n\nOn Mon, Jun 15, 2015 at 3:56 PM, Brian Hoffman \u003cbrianchoffman at gmail.com\u003e\nwrote:\n\n\u003e Who is actually planning to move to Bitcoin-XT if this happens?\n\u003e\n\u003e Just Gavin and Mike?\n\u003e\n\u003e [image: image1.JPG]\n\u003e\n\u003e On Jun 15, 2015, at 6:17 PM, Faiz Khan \u003cfaizkhan00 at gmail.com\u003e wrote:\n\u003e\n\u003e I'm quite puzzled by the response myself, it doesn't seem to address some\n\u003e of the (more serious) concerns that Adam put out, the most important\n\u003e question that was asked being the one regarding personal ownership of the\n\u003e proposed fork:\n\u003e\n\u003e \"How do you plan to deal with security \u0026 incident response for the\n\u003e duration you describe where you will have control while you are deploying\n\u003e the unilateral hard-fork and being in sole maintainership control?\"\n\u003e\n\u003e I do genuinely hope that whomever (now and future) wishes to fork the\n\u003e protocol reconsider first whether they are truly ready to test/flex their\n\u003e reputation/skills/resources in this way... Intuitively, to me it seems\n\u003e counterproductive, and I don't fully believe it is within a single\n\u003e developer's talents to manage the process start-to-finish (as it is\n\u003e non-trivial to hard-fork successfully, others have rehashed this in other\n\u003e threads)...\n\u003e\n\u003e That being said I think it appropriate if Adam's questions were responded\n\u003e in-line when Mike is feeling up to it. I think that the answers are\n\u003e important for the community to hear when such a drastic change is being\n\u003e espoused.\n\u003e\n\u003e Faiz\n\u003e\n\u003e On Mon, Jun 15, 2015 at 4:56 PM, Bryan Bishop \u003ckanzure at gmail.com\u003e wrote:\n\u003e\n\u003e\u003e On Mon, Jun 15, 2015 at 3:55 PM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\u003e\u003e\n\u003e\u003e\u003e Re: anyone who agrees with noted non-programmers Mike\u0026Gavin must be\n\u003e\u003e\u003e non-technical, stupid, uninformed, etc .... OK, go ahead and show them the\n\u003e\u003e\u003e error of their ways. Anyone can write blogs.\n\u003e\u003e\u003e\n\u003e\u003e\n\u003e\u003e I worry that if this is the level of care you take with reading and\n\u003e\u003e (mis)interpreting Adam's messages, that you might not be taking extreme\n\u003e\u003e care with evaluating consensus changes, even while tired or sleeping. I\n\u003e\u003e encourage you to evaluate both messages and source code more carefully,\n\u003e\u003e especially in the world of bitcoin. However, this goes for everyone and not\n\u003e\u003e just you. Specifically, when Adam mentioned your conversations with\n\u003e\u003e non-technical people, he did not mean \"Mike has talked with people who have\n\u003e\u003e possibly not made pull requests to Bitcoin Core, so therefore Mike is a\n\u003e\u003e non-programmer\". Communication is difficult and I can understand that, but\n\u003e\u003e we really have to be more careful when evaluating each other's messages;\n\u003e\u003e technical miscommunication can be catastrophic in this context. On the\n\u003e\u003e topic of whether you are a programmer, I suspect that ever since you built\n\u003e\u003e CIA.vc we have all known you're a programmer, Mike.\n\u003e\u003e\n\u003e\u003e - Bryan\n\u003e\u003e http://heybryan.org/\n\u003e\u003e 1 512 203 0507\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e ------------------------------------------------------------------------------\n\u003e\u003e\n\u003e\u003e _______________________________________________\n\u003e\u003e Bitcoin-development mailing list\n\u003e\u003e Bitcoin-development at lists.sourceforge.net\n\u003e\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\u003e\n\u003e\u003e --\n\u003e\u003e\n\u003e\u003e My regards,\n\u003e\u003e\n\u003e\u003e Faiz Khan\n\u003e\u003e\n\u003e\u003e  \u003chttps://lists.sourceforge.net/lists/listinfo/bitcoin-development\u003e\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150615/8b369aeb/attachment.html\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: image1.JPG\nType: image/jpeg\nSize: 22107 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150615/8b369aeb/attachment.jpe\u003e"}