public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "/dev /fd0" <alicexbtong@gmail.com>
To: Antoine Riard <antoine.riard@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: Workshops and Activation for CHECKTEMPLATEVERIFY and CHECKSIGFROMSTACK
Date: Fri, 22 Aug 2025 08:58:32 +0530	[thread overview]
Message-ID: <CALiT-ZoNdW=1mdyjpy6zLgTNCJHL8fKt9svM_5GWi96HPsVQmA@mail.gmail.com> (raw)
In-Reply-To: <e0a46b30-e633-4f38-b737-a5f1973da901n@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 5342 bytes --]

Hi Antoine,

>  Why the 58 other names on the letter have not spent _their_ _free_ time
reviewing more CTV code ?

Some of them have reviewed CTV earlier in other pull requests and others
could be application developers who are interested in the use cases.

> https://github.com/ariard/bitcoin-contracting-primitives-wg (can transfer
you the repo ownership if you wish so)

Thanks for sharing the link. I found the [taproot workshops][0] repository
useful as well. I will create a new repository for CTV-CSFS workshops,
meetings etc. to document everything.

Workshop #1

Time: 28 August 2025 15:00 UTC
Channel: #ctv-csfs-activation on libera.chat

- Review and understand [BIP 119][1]
- Create basic CTV transactions on signet

[0]: https://github.com/bitcoinops/taproot-workshop
[1]: https://github.com/bitcoin/bips/blob/master/bip-0119.mediawiki

/dev/fd0
floppy disk guy

On Thu, Aug 21, 2025 at 5:37 AM Antoine Riard <antoine.riard@gmail.com>
wrote:

> Hi Floppy,
>
> The call to review CTV has been published Jun. 9.
>
> On this letter, I can count ~60 names.
>
> Since the time of publication (2 months after), only 5 people have put a
> code review comment on #31989.
>
> Among the 5 people, only 2 were letter signatories (average-gary + stuxto).
>
> Why the 58 other names on the letter have not spent _their_ _free_ time
> reviewing more CTV code ?
>
> ...
>
> Now, of course anyone is free to patch CTV on top of knot and go to try
> the activation run with that.
>
> Personally, I still think we should aim for more neutral consensus
> development process...
>
> This was the intent with the bitcoin contracting primitives WG, done on an
> open IRC chan.
>
> https://github.com/ariard/bitcoin-contracting-primitives-wg (can transfer
> you the repo ownership if you wish so)
>
> Where rather to present a primitive proposal as a "done deal" from a "pow
> wow" of experts,
> the goal was to create a neutral online forum for discussion open to
> anyone in the world
> who self-estimate they qualify as an expert on bitcoin consensus...and
> humbly trying to
> do better than the mess of the 2015 - 2017 period w.r.t consensus changes.
>
> Best,
> Antoine
> OTS hash: 0d3c23682b630c9c85288ece8e1acae2f4a3c76254e16e36ccb6ca0fcef2556b
>
> Le lundi 18 août 2025 à 15:43:54 UTC+1, /dev /fd0 a écrit :
>
>> Hi everyone,
>>
>> IRC channel: #ctv-csfs-activation on libera.chat
>>
>> I [requested][0] the economic nodes to review different soft fork
>> proposals and share their opinion on 5 March 2025. Four entries were added
>> to the [wiki][1] and nobody has any objections to the proposals. Some
>> organizations do not want to publicly participate in this process to avoid
>> politics and drama.
>>
>> A [letter][2] was signed on 9 June 2025 by bitcoin developers to get more
>> core contributors involved in the review process. It was followed by a
>> [proposal][3] that makes a few changes to CHECKTEMPLATEVERIFY and combines
>> it with CHECKSIGFROMSTACK. Personally, I don't like that TEMPLATEHASH is
>> restricted to taproot and don't see anything wrong with
>> CHECKTEMPLATEVERIFY. However, other developers may disagree with me and
>> have different opinion. I have created an IRC channel for workshops,
>> meetings, activation, etc.
>>
>> We can finalize a meeting schedule so we can use the IRC channel to move
>> closer to covenants activation on bitcoin.
>>
>> I think BIP 8 would be a better option for the next soft fork.
>> [Previously][4], some suggestions were [rejected][5] because knots was not
>> used by a large number of users. However, things have changed since then
>> and [~15%][6] of nodes use knots for bitcoin.
>>
>> [0]: https://groups.google.com/g/bitcoindev/c/kd8g8V1NVOY/m/nE2y5V66AQAJ
>> [1]: https://en.bitcoin.it/wiki/Covenants_support
>> [2]: https://ctv-csfs.com/
>> [3]: https://groups.google.com/g/bitcoindev/c/5wLThgegha4/m/iUWIZPIaCAAJ
>> [4]:
>> https://gnusha.org/pi/bitcoindev/CAFvNmHS4s_MbXP8o3kWmaUZ5...@mail.gmail.com/
>> <https://gnusha.org/pi/bitcoindev/CAFvNmHS4s_MbXP8o3kWmaUZ5Xks1b76jSDymp1Bjr--4R8_v3Q@mail.gmail.com/>
>> [5]:
>> https://diyhpl.us/cgit/pi-bitcoindev/plain/cc/877bbc8de83e7aa4d2252a0473d05d634946b4/dev/fd0
>> [6]: https://bitnodes.io/nodes/?q=knots#network-snapshot
>>
>> /dev/fd0
>> floppy disk guy
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Bitcoin Development Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to bitcoindev+unsubscribe@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/e0a46b30-e633-4f38-b737-a5f1973da901n%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/e0a46b30-e633-4f38-b737-a5f1973da901n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CALiT-ZoNdW%3D1mdyjpy6zLgTNCJHL8fKt9svM_5GWi96HPsVQmA%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 7194 bytes --]

      reply	other threads:[~2025-08-22 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-17 20:07 [bitcoindev] Workshops and Activation for CHECKTEMPLATEVERIFY and CHECKSIGFROMSTACK /dev /fd0
2025-08-20 18:23 ` [bitcoindev] " Antoine Riard
2025-08-22  3:28   ` /dev /fd0 [this message]

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='CALiT-ZoNdW=1mdyjpy6zLgTNCJHL8fKt9svM_5GWi96HPsVQmA@mail.gmail.com' \
    --to=alicexbtong@gmail.com \
    --cc=antoine.riard@gmail.com \
    --cc=bitcoindev@googlegroups.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