From: alicexbt <alicexbt@protonmail•com>
To: "lf-lists@mattcorallo•com" <lf-lists@mattcorallo•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Automatically reverting ("transitory") soft forks, e.g. for CTV
Date: Fri, 22 Apr 2022 19:05:31 +0000 [thread overview]
Message-ID: <6MmFuR8zLjds01q3blgKd9Kh512Pc_Vxuf2CyOl6uXacihgkP1ItB5EigQBGamGMHBysu11Lel8qMj7T92gYaLS3jQROG4g7HrCJKUOgnZM=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Hi TheBlueMatt,
>> There are at least three or four separate covenants designs that have
>>> been posted to this list, and I don't see why we're even remotely
>>> talking about a specific one as something to move forward with at
>>> this point.
>>
>>> To my knowledge none of these other proposals (drafts, really) have
>>> actual implementations let alone the many sample usages that exist for
>> CTV.
> You can fix this! Don't point to something you can easily remedy in the > short-term as an argument
> for or against something in the long-term.
How can we fix this? If a proposal already fixed it, does it have some consensus or it was fixed in a different way?
/dev/fd0
Sent with [ProtonMail](https://protonmail.com/) secure email.
[-- Attachment #2: Type: text/html, Size: 1378 bytes --]
next reply other threads:[~2022-04-22 19:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 19:05 alicexbt [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-21 1:04 David A. Harding
2022-04-21 2:05 ` Luke Dashjr
2022-04-21 3:10 ` alicexbt
2022-04-21 5:56 ` Luke Dashjr
2022-04-21 6:20 ` Jeremy Rubin
2022-04-21 6:37 ` Luke Dashjr
2022-04-21 13:10 ` Jeremy Rubin
2022-04-24 15:22 ` Peter Todd
2022-04-21 14:58 ` Matt Corallo
2022-04-21 18:06 ` David A. Harding
2022-04-21 18:39 ` Matt Corallo
2022-04-21 22:28 ` David A. Harding
2022-04-21 23:02 ` Matt Corallo
2022-04-22 1:20 ` David A. Harding
2022-04-22 18:40 ` Matt Corallo
2022-04-22 18:49 ` Corey Haddad
2022-04-22 16:48 ` James O'Beirne
2022-04-22 17:06 ` James O'Beirne
2022-04-22 16:28 ` James O'Beirne
2022-04-22 18:35 ` Matt Corallo
2022-04-21 19:08 ` Jeremy Rubin
2022-04-22 0:28 ` Anthony Towns
2022-04-22 1:44 ` David A. Harding
2022-04-22 19:57 ` Antoine Riard
2022-04-25 5:12 ` ZmnSCPxj
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='6MmFuR8zLjds01q3blgKd9Kh512Pc_Vxuf2CyOl6uXacihgkP1ItB5EigQBGamGMHBysu11Lel8qMj7T92gYaLS3jQROG4g7HrCJKUOgnZM=@protonmail.com' \
--to=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lf-lists@mattcorallo$(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