From: Luke Dashjr <luke@dashjr•org>
To: Anthony Towns <aj@erisian•com.au>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Modern Soft Fork Activation
Date: Sun, 12 Jan 2020 05:58:33 +0000 [thread overview]
Message-ID: <202001120558.34256.luke@dashjr.org> (raw)
In-Reply-To: <20200111144207.5xzspeptstspsbsf@erisian.com.au>
On Saturday 11 January 2020 14:42:07 Anthony Towns wrote:
> the UASF approach had significant potential technical problems
> (potential for long reorgs, p2p network splits) that weren't
> resolved by the time it became active.
Long reorgs, only for old nodes, were a possibility, but not a problem.
The p2p network split issues WERE resolved well before activation.
(In fact, Bitcoin Knots still ships with the general p2p fixes.)
> neither
> BIP-148 or BIP-91 gained enough consensus to be supported in
> bitcoin core though
There was no measurable difference in community support between BIP148 and
Segwit itself, months before BIP148's activation. (There was about 20% that
indicated they would support BIP148 "only if Bitcoin Core releases it", which
IMO "counts" in this context.)
The only difference was in the opinions of developers. Basing the decision to
exclude BIP148 as even an *option* on this basis was IMO improper and
shouldn't be repeated. The community's readiness to switch to another
fork/build for UASFs is also valuable, but shouldn't be necessary.
Luke
next prev parent reply other threads:[~2020-01-12 5:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 21:30 Matt Corallo
2020-01-10 22:21 ` Jorge Timón
2020-01-10 22:43 ` Matt Corallo
2020-01-10 23:07 ` Jorge Timón
2020-01-10 23:37 ` Luke Dashjr
2020-01-11 0:54 ` Jeremy
2020-01-14 19:22 ` Matt Corallo
2020-01-11 14:42 ` Anthony Towns
2020-01-12 5:58 ` Luke Dashjr [this message]
2020-01-14 19:42 ` Matt Corallo
2020-01-16 3:46 ` Anthony Towns
2020-01-13 8:34 Yosef
2020-01-14 3:20 ` Anthony Towns
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=202001120558.34256.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=aj@erisian$(echo .)com.au \
--cc=bitcoin-dev@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