From: "Russell O'Connor" <roconnor@blockstream•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] What to do when contentious soft fork activations are attempted
Date: Fri, 6 May 2022 14:23:51 -0400 [thread overview]
Message-ID: <CAMZUoKnaj9eOkWcn5NaSJb+NtCe=5Uv_FZR-VAqR0De68G33hA@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDp6YvV0ZLgW2Mzp8LivMM-KWjAA4ZmV1XO-6R+WuD9zEg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On Fri, May 6, 2022 at 2:01 PM Jorge Timón via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> Russell O'Connor wrote the definitive explanation for how ST arose in
>> the consensus process and how it was designed to make everyone
>> unhappy. It's a great explanation of what we went through last year.
>>
>> https://r6.ca/blog/20210615T191422Z.html
>>
>> "On Building Consensus and Speedy Trial"
>>
>> on | 2021-06-15T19:14:22Z
>> by | Russell O'Connor
>>
>
> That's a lot of text, are you sure he said in there he designed speedy
> trial to make everyone unhappy?
> Well, if we're still talking about it, that proves that it failed at its
> own design criterion of failing fast.
>
Quoting from https://r6.ca/blog/20210615T191422Z.html:
> Speedy Trial’s design is not based on any sort of activation philosophy
about failing fast.
[-- Attachment #2: Type: text/html, Size: 1651 bytes --]
next prev parent reply other threads:[~2022-05-06 18:24 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
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 [this message]
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='CAMZUoKnaj9eOkWcn5NaSJb+NtCe=5Uv_FZR-VAqR0De68G33hA@mail.gmail.com' \
--to=roconnor@blockstream$(echo .)com \
--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