From: "Jorge Timón" <jtimon@jtimon.cc>
To: "Russell O'Connor" <roconnor@blockstream.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] What to do when contentious soft fork activations are attempted
Date: Sat, 7 May 2022 00:44:24 +0200 [thread overview]
Message-ID: <CABm2gDooJ=HHmNdwncrthOn1deoCojhEUusWnNj_0ASsq9wybg@mail.gmail.com> (raw)
In-Reply-To: <CAMZUoKnaj9eOkWcn5NaSJb+NtCe=5Uv_FZR-VAqR0De68G33hA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]
So, to be clear, you didn't design speedy trial "to make everyone unhappy"
as Ryan claims, no?
That's a really strange claim on his part.
When the grace period for slower activation after lock in was added, I
don't think it was added to make me or people like me who dislike that
proposal unhappy. On the contrary, I think the goal was precisely to
address some of our concerns.
But it doesn't address them all, as I've tried to explain other times.
I truly think you wanted to make everyone happy with speedy trial, but you
didn't do it, sorry.
I know it' not a lack of capacity because you did impressive and genius
things like simplicity.
But despite your best intentions and your great capacity, I still think
speedy trial is a very bad proposal because you got the analysis wrong.
Let me reiterate that this is not attack against you, but only against one
of your ideas.
Sorry if I sounded sarcastic, but I was trying to be sarcastic with ryan,
not with you.
On Fri, May 6, 2022 at 8:24 PM Russell O'Connor via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> 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.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 3608 bytes --]
next prev parent reply other threads:[~2022-05-06 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 9:53 [bitcoin-dev] What to do when contentious soft fork activations are attempted 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
2022-05-06 22:44 ` Jorge Timón [this message]
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='CABm2gDooJ=HHmNdwncrthOn1deoCojhEUusWnNj_0ASsq9wybg@mail.gmail.com' \
--to=jtimon@jtimon.cc \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=roconnor@blockstream.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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