From: /dev /fd0 <alicexbtong@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Covenants Support - Bitcoin Wiki
Date: Fri, 29 Nov 2024 06:08:57 -0800 (PST) [thread overview]
Message-ID: <028c0197-5c45-4929-83a9-cfe7c87d17f4n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1292 bytes --]
Hi Bitcoin Developers,
I have created the first draft of a bitcoin wiki page to update opinions of
bitcoin developers on different covenant proposals. It uses the same
template as segwit support page. Feel free to add more opcodes as I only
added the ones that looked relevant.
Wiki link: https://en.bitcoin.it/wiki/Covenants_support
I am aware of the opinions of some developers; however, I did not want to
write on their behalf. Please add your GitHub username and share your
opinions on the proposed opcodes. This would help in reaching a consensus
on the next soft fork and make things easier.
Rationale for supporting OP_CTV:
https://notes.dunst.be/slide/#/2/slide/view/Ekky-cAegV9dSOaNOjH9TStNOmAnrhDDc9hxHlmRs5M/embed/present/
I like a few other use cases however mainly interested in pools with
covenants. This would help improve joinstr (coinjoin implementation).
/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/028c0197-5c45-4929-83a9-cfe7c87d17f4n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1859 bytes --]
next reply other threads:[~2024-11-29 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 14:08 /dev /fd0 [this message]
2024-12-06 21:45 ` Jonas Nick
2024-12-07 0:29 ` /dev /fd0
2024-12-07 1:42 ` Yuval Kogman
2024-12-09 20:13 ` Anthony Towns
2024-12-09 20:45 ` Brandon Black
2024-12-11 13:28 ` Anthony Towns
2024-12-11 15:11 ` Brandon Black
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=028c0197-5c45-4929-83a9-cfe7c87d17f4n@googlegroups.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