From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org,
Sergio Demian Lerner <sergio.d.lerner@gmail•com>
Subject: Re: [bitcoin-dev] A Segwit2x BIP
Date: Wed, 12 Jul 2017 01:06:14 +0000 [thread overview]
Message-ID: <201707120106.16951.luke@dashjr.org> (raw)
In-Reply-To: <CAKzdR-oRdX-fXyc6womZOyYyfHUJZdgh92FUMM8pR_QDNiJfkQ@mail.gmail.com>
On Monday 10 July 2017 11:50:33 AM Sergio Demian Lerner via bitcoin-dev wrote:
> Regarding the timeline, its certainly rather short, but also is the UASF
> BIP 148 ultimatum.
BIP148 began with 8 months lead time, reduced to 5 months from popular request
and technical considerations. There is nothing about BIP148 that compels an
attempted hardfork 90 days later - that could just as well have been 18
months.
> More than 80% of the miners and many users are willing to go in the
> Segwit2x direction. With the support and great talent of the Bitcoin Core
> developers, Segwit2x activation will not cause any major disruptions.
That's not true at all. Based on my observations, only approximately 20% of
the community follow Core's technical lead without significant consideration
of their own - and who knows if that would change if Core were to suggest
clearly-unsafe block size increases, or attempted to force a hardfork against
consensus. Even with Core's support, many people would oppose the hardfork
attempt, and it would fail.
> Without Core, there will be a temporary split. Both sides will have to
> hard-fork.
Segwit2x's hardfork does not compel the remaining Bitcoin users to also
hardfork.
> I want a Bitcoin united. But maybe a split of Bitcoin, each side with its
> own vision, is not so bad.
I concur, but I disagree your approach has any possibility of a united
Bitcoin. The only way to get that today, would be to do Segwit+Drivechain, not
Segwit+Hardfork.
Luke
next prev parent reply other threads:[~2017-07-12 1:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 22:25 Sergio Demian Lerner
2017-07-07 22:44 ` Matt Corallo
2017-07-07 23:25 ` Gregory Maxwell
2017-07-07 23:22 ` Gregory Maxwell
2017-07-13 3:10 ` Sergio Demian Lerner
2017-07-13 3:19 ` Sergio Demian Lerner
2017-07-07 23:27 ` Luke Dashjr
2017-07-07 23:38 ` Gregory Maxwell
2017-07-08 6:30 ` Erik Aronesty
2017-07-08 13:28 ` Btc Drak
[not found] ` <A7FFF8F7-9806-44F1-B68F-F83C44893365@ob1.io>
2017-07-10 11:50 ` Sergio Demian Lerner
2017-07-10 18:38 ` Jorge Timón
2017-07-12 8:15 ` Tom Zander
2017-07-12 12:38 ` Jonas Schnelli
2017-07-12 17:38 ` Jorge Timón
2017-07-13 19:19 ` Sergio Demian Lerner
2017-07-13 19:48 ` Andrew Chow
2017-07-13 21:18 ` Charlie 'Charles' Shrem
2017-07-14 13:50 ` Erik Aronesty
2017-07-12 1:06 ` Luke Dashjr [this message]
2017-07-12 15:41 ` Aymeric Vitte
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=201707120106.16951.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=sergio.d.lerner@gmail$(echo .)com \
/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