[bitcoin-dev] hard-fork "X+Y" compromise discussion re-run
adam.back at gmail.com
Sat Apr 1 13:18:18 UTC 2017
I agree with everything Matt said. This "X+Y" "compromise" is not a
new proposal and has been hashed over multiple times in the past
dating back to at least fall 2015, ignores basically all design
considerations and research over the last years, doesn't understand
the real-politic of the delays, and so doesn't even help in the
I have taken the liberty of making a reddit thread with some of the
previous explainers about why this doesn't work in practice (even
ignoring all politics and hypothetically assuming it was a great
all-new idea), let the discussion commence!
UASF is a more logical step, than these "X+Y" politically motivated
hard-forks, though UASF has risks vs SegWit BIPs in flight, the delay
and risk is far lower than political hard-forks.
I have set the reply-to to bitcoin-discuss.
More information about the bitcoin-dev