From: Ariel Lorenzo-Luaces <arielluaces@gmail•com>
To: Luke Dashjr <luke@dashjr•org>
Cc: Michael Folkson <michaelfolkson@gmail•com>,
bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] UASF (LOT=true) kick off meeting - Tuesday March 2nd 19:00 UTC on ##uasf IRC channel
Date: Tue, 02 Mar 2021 11:36:54 -0800 [thread overview]
Message-ID: <99431100-cf4a-48f7-afd1-37ab7fa92c0a@gmail.com> (raw)
In-Reply-To: <202103021857.39275.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]
You can try to redefine all you want but it doesn't make what you're saying true.
A soft fork is a constriction of rules
A 51% attack is a soft fork with majority mining power.
I didn't say that LOT=true does it I said that it must achieve 51% miner support to pose reorg risks to force apathetic users into paying attention. Please read my message again.
Your definition of invalid has no power here. We are all painfully aware of your semantic mental gymnastics.
Cheers
Ariel Lorenzo-Luaces
On Mar 2, 2021, 10:58 AM, at 10:58 AM, Luke Dashjr <luke@dashjr•org> wrote:
>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
[-- Attachment #2: Type: text/html, Size: 2405 bytes --]
next prev parent reply other threads:[~2021-03-02 19:36 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
2021-03-02 19:36 ` Ariel Lorenzo-Luaces [this message]
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=99431100-cf4a-48f7-afd1-37ab7fa92c0a@gmail.com \
--to=arielluaces@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)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