From: "/dev /fd0" <alicexbtong@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Workshops and Activation for CHECKTEMPLATEVERIFY and CHECKSIGFROMSTACK
Date: Mon, 18 Aug 2025 01:37:54 +0530 [thread overview]
Message-ID: <CALiT-Zr7ZyPi655GsXbsNZMnQpz2RDAwhFqFhkLQ=1JD-1c60A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2166 bytes --]
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_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/CALiT-Zr7ZyPi655GsXbsNZMnQpz2RDAwhFqFhkLQ%3D1JD-1c60A%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 3084 bytes --]
next reply other threads:[~2025-08-18 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 20:07 /dev /fd0 [this message]
2025-08-20 18:23 ` [bitcoindev] " Antoine Riard
2025-08-22 3:28 ` /dev /fd0
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-Zr7ZyPi655GsXbsNZMnQpz2RDAwhFqFhkLQ=1JD-1c60A@mail.gmail.com' \
--to=alicexbtong@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.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