From: alicexbt <alicexbt@protonmail•com>
To: Michael Folkson <michaelfolkson@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] What to do when contentious soft fork activations are attempted
Date: Sun, 01 May 2022 01:20:22 +0000 [thread overview]
Message-ID: <WtHCNGNhHAWBer9QnaWajdbJ341jMHQJa23WAPgNaRldKhopPIN7ry8wNAnmfnlAK6j0m7p3NEgckA6kIjWV5_rFla63Bh6HCfAlLHFODsE=@protonmail.com> (raw)
In-Reply-To: <EpwH6R7Ol7S4DZ4r_UcSSMU9RysZiRHFKZ2WkWZatUIeU9YE9avRZ-YIiafnf6I6U4tBbEu5xHa4JwcGh0fxMuyY-fGMwpaesfo5XK6SzLc=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 4990 bytes --]
Hi Michael,
> Maybe the whole thing worked as designed. Some users identified what was going on, well known Bitcoin educators such as Andreas Antonopoulos, Jimmy Song etc brought additional attention to the dangers, a URSF movement started to gain momentum and those attempting a contentious soft fork activation backed off. (Disappointingly Bitcoin Optech didn't cover my previous posts to this mailing list [1](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-October/019535.html), [2](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019728.html), [3](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020235.html) highlighting the dangers many months ago or recent posts. Normally Optech is very high signal.)
Some users have been misled and there is nothing great being achieved by doing this on social media. Andreas is clueless about BIP 119 and other covenant proposals. He is spreading misinformation and some of the URSF enthusiasts do not understand what are they even opposing or going to run with risks involved.
Answering the subject of this email: "What to do when contentious soft forks activations are attempted?"
- Do not consider something contentious because someone said it on mailing list
- Do not spread misinformation
- Read all posts in detail with different opinions
- Avoid personal attacks
- Look at the technical details, code etc. and comment on things that could be improved
/dev/fd0
Sent with [ProtonMail](https://protonmail.com/) secure email.
------- Original Message -------
On Saturday, April 30th, 2022 at 3:23 PM, Michael Folkson via bitcoin-dev bitcoin-dev@lists•linuxfoundation.org wrote:
> I’ve been in two minds on whether to completely move on to other topics or to formulate some thoughts on the recent attempt to activate a contentious soft fork. In the interests of those of us who have wasted days/weeks/months of our time on this (with no personal upside) and who don’t want to repeat this exercise again I thought I should at least raise the issue for discussion of what should be done differently if this is tried again in future.
>
> This could be Jeremy with OP_CTV at a later point (assuming it is still contentious) or anyone who wants to pick up a single opcode that is not yet activated on Bitcoin and try to get miners to signal for it bypassing technical concerns from many developers, bypassing Bitcoin Core and bypassing users.
>
> Maybe the whole thing worked as designed. Some users identified what was going on, well known Bitcoin educators such as Andreas Antonopoulos, Jimmy Song etc brought additional attention to the dangers, a URSF movement started to gain momentum and those attempting a contentious soft fork activation backed off. (Disappointingly Bitcoin Optech didn't cover my previous posts to this mailing list [1](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-October/019535.html), [2](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019728.html), [3](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020235.html) highlighting the dangers many months ago or recent posts. Normally Optech is very high signal.)
>
> Alternatively this was the first time a contentious soft fork activation was attempted, we were all woefully unprepared for it and none of us knew what we were doing.
>
> I’m unsure on the above. I’d be interested to hear thoughts. What I am sure of is that it is totally unacceptable for one individual to bring the entire Bitcoin network to the brink of a chain split. There has to be a personal cost to that individual dissuading them from trying it again otherwise they’re motivated to try it again every week/month. Perhaps the personal cost that the community is now prepared if that individual tries it again is sufficient. I’m not sure. Obviously Bitcoin is a permissionless network, Bitcoin Core and other open source projects are easily forked and no authority (I’m certainly no authority) can stop things like this happening again.
>
> I’ll follow the responses if people have thoughts (I won't be responding to the instigators of this contentious soft fork activation attempt) but other than that I’d like to move on to other things than contentious soft fork activations. Thanks to those who have expressed concerns publicly (too many to name, Bob McElrath was often wording arguments better than I could) and who were willing to engage with the URSF conversation. If an individual can go directly to miners to get soft forks activated bypassing technical concerns from many developers, bypassing Bitcoin Core and bypassing users Bitcoin is fundamentally broken. The reason I still have hope that it isn't is that during a period of general apathy some people were willing to stand up and actively resist it.
>
> --
> Michael Folkson
> Email: michaelfolkson at protonmail.com
> Keybase: michaelfolkson
> PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
[-- Attachment #2: Type: text/html, Size: 5790 bytes --]
next prev parent reply other threads:[~2022-05-01 1:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 9:53 Michael Folkson
2022-05-01 1:20 ` alicexbt [this message]
2022-05-01 12:47 ` Jorge Timón
2022-05-03 14:36 ` Ryan Grant
2022-05-06 17:17 ` Jorge Timón
2022-05-06 18:23 ` Russell O'Connor
2022-05-06 22:44 ` Jorge Timón
2022-05-01 19:14 ` Billy Tetrud
[not found] <mailman.53264.1651860071.8511.bitcoin-dev@lists.linuxfoundation.org>
2022-05-06 19:58 ` John Tromp
2022-05-07 1:57 ` Jorge Timón
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='WtHCNGNhHAWBer9QnaWajdbJ341jMHQJa23WAPgNaRldKhopPIN7ry8wNAnmfnlAK6j0m7p3NEgckA6kIjWV5_rFla63Bh6HCfAlLHFODsE=@protonmail.com' \
--to=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=michaelfolkson@protonmail$(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