From: Ariel Luaces <arielluaces@gmail•com>
To: Michael Folkson <michaelfolkson@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Yesterday’s UASF (LOT=true) kick off meeting
Date: Wed, 3 Mar 2021 18:18:29 -0800 [thread overview]
Message-ID: <CAOv1TnhbQZ2mfT3Hi75bCuPQ2TOM54iC+rHAV6HDbw7pPYvdzQ@mail.gmail.com> (raw)
In-Reply-To: <CAFvNmHS8_5riG1FvzQvbWS_twxxTq82GFnT2gLGXirz23Q=pcw@mail.gmail.com>
On Wed, Mar 3, 2021 at 12:25 PM Michael Folkson via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> At this point in time it also appears the greatest risk to Taproot
> dying a slow death is a small group of developers who think talking in
> conservative tones and talking about endless philosophy makes Bitcoin
> a conservative system. (It doesn’t, it just makes it a dying, decaying
> one).
The current risk to taproot and all future activations is a loud
minority of users who are threatening to co-opt a LOT=false activation
by switching the parameter and organizing a marketing blitz that could
end in a fork if things don't go well.
As long as that threat persists consensus won't be reached. Then an
activation client probably won't be released because I don't expect
many devs will have an appetite for writing code that either doesn't
have consensus or code that will be manipulated into creating
consensus conflicts.
I think Bitcoin is fine staying as is until that minority forks off
with their own alt-node. If the UASF minority is dead set on creating
the alt-node then I only hope it's released quickly so the deadlock
can break. A quick UASF fork allows for an early LOT=false activation.
Cheers
Ariel Lorenzo-Luaces
> --
> Michael Folkson
> Email: michaelfolkson@gmail•com
> Keybase: michaelfolkson
> PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2021-03-04 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 12:15 Michael Folkson
2021-03-04 2:18 ` Ariel Luaces [this message]
2021-03-04 10:54 ` Michael Folkson
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=CAOv1TnhbQZ2mfT3Hi75bCuPQ2TOM54iC+rHAV6HDbw7pPYvdzQ@mail.gmail.com \
--to=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