{"type":"rich","version":"1.0","author_name":"npub1ac86vemj7ce5z8jyxt39rna3tvwql6xd30ha3vxcd6esysp23d9qrlswfj","author_url":"https://nostr.ae/npub1ac86vemj7ce5z8jyxt39rna3tvwql6xd30ha3vxcd6esysp23d9qrlswfj","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-09-28\n📝 Original message:I wonder what Gavin's views are, he's usually constructive, and see if\nhe'll include it in XT - I think he may have said he was supportive.\n\nThe rationale for soft vs hard-forks is well known, so I wont go over them.\n\nAdam\n\n\nOn 28 September 2015 at 06:48, Mike Hearn via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e There is no consensus on using a soft fork to deploy this feature. It will\n\u003e result in the same problems as all the other soft forks - SPV wallets will\n\u003e become less reliable during the rollout period. I am against that, as it's\n\u003e entirely avoidable.\n\u003e\n\u003e Make it a hard fork and my objection will be dropped.\n\u003e\n\u003e Until then, as there is no consensus, you need to do one of two things:\n\u003e\n\u003e 1) Drop the \"everyone must agree to make changes\" idea that people here like\n\u003e to peddle, and do it loudly, so everyone in the community is correctly\n\u003e informed\n\u003e\n\u003e 2) Do nothing\n\u003e\n\u003e\n\u003e\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"}