From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org,
"Ariel Lorenzo-Luaces" <arielluaces@gmail•com>
Cc: Michael Folkson <michaelfolkson@gmail•com>
Subject: Re: [bitcoin-dev] UASF (LOT=true) kick off meeting - Tuesday March 2nd 19:00 UTC on ##uasf IRC channel
Date: Tue, 2 Mar 2021 18:57:38 +0000 [thread overview]
Message-ID: <202103021857.39275.luke@dashjr.org> (raw)
In-Reply-To: <b56bd582-e605-4389-96ce-c1cb0c58f1ad@gmail.com>
On Tuesday 02 March 2021 18:22:35 Ariel Lorenzo-Luaces via bitcoin-dev wrote:
> I'm realizing that a clear advantage of LOT=false is that it can happen
> without the need for a social movement. All that is really needed is the
> convincing of 95% miners. Apathetic users will never notice any kind of
> service disruption no matter the success or failure of the activation. This
> is obviously why it naturally became the default activation method.
No. Miners enforcing rules without the social support is a 51% attack, not a
softfork.
> While LOT=true, on the other hand, must be able to 51% the blockchain to
> win the apathetic users. But then the reorgs will not be pretty. Or if it
> ever clearly gets over the 51% hurdle then all apathetic users now need to
> scramble to use the rogue client to be safe from reorgs. Either way it's
> disruptive.
No, LOT=True doesn't do this. It only happens if miners choose to create an
invalid chain, which they could do at any time with or without a softfork
involved.
Luke
next prev parent reply other threads:[~2021-03-02 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 17:47 Michael Folkson
2021-03-02 18:22 ` Ariel Lorenzo-Luaces
2021-03-02 18:57 ` Luke Dashjr [this message]
2021-03-02 19:36 ` Ariel Lorenzo-Luaces
2021-03-02 20:19 ` Eric Voskuil
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=202103021857.39275.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=arielluaces@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=michaelfolkson@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