From: Adam Back <adam.back@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Cc: bitcoin-discuss@lists•linuxfoundation.org
Subject: [bitcoin-dev] hard-fork "X+Y" compromise discussion re-run
Date: Sat, 1 Apr 2017 15:18:18 +0200 [thread overview]
Message-ID: <CALqxMTHjsCeyy+y-ViouHP7DBNrBGp4QxgpP2nq0uStBC10BfQ@mail.gmail.com> (raw)
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
political domain.
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!
https://www.reddit.com/r/Bitcoin/comments/62rrlv/how_about_a_new_compromise_activate_the_existing/
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.
Adam
reply other threads:[~2017-04-01 13:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALqxMTHjsCeyy+y-ViouHP7DBNrBGp4QxgpP2nq0uStBC10BfQ@mail.gmail.com \
--to=adam.back@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoin-discuss@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox