From: "/dev /fd0" <alicexbtong@gmail•com>
To: Weikeng Chen <weikeng.chen@l2iterative•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Time to add CSFS to Signet?
Date: Mon, 17 Mar 2025 20:13:55 +0530 [thread overview]
Message-ID: <CALiT-Zo3JcUjyQ3=--oecm6Nq2CM20AzZbpLQsZhSXKJfxm7rQ@mail.gmail.com> (raw)
In-Reply-To: <2584bf15-8e7f-4d89-8987-f41dd06b2824n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
Hi Weikeng,
I agree that it has a lot of support among bitcoin developers. No
objections for CSFS on [wiki][0]with evaluations from more than 50 bitcoin
developers.
Co-author of APO, Christian Decker has also expressed his support for it on
[twitter][1]. Even Greg Maxwell considers it [useful][2].
[0]: https://en.bitcoin.it/wiki/Covenants_support
[1]: https://x.com/Snyke/status/1895880013796556818
[2]: https://freenode.irclog.whitequark.org/bitcoin-wizards/2019-11-28
/dev/fd0
floppy disk guy
On Mon, Mar 17, 2025, 7:03 PM Weikeng Chen <weikeng.chen@l2iterative•com>
wrote:
> I am writing just to solicit people's opinions on whether CSFS should be
> added to signet given that CTV + CSFS combination has recently received a
> lot of support. Although CTV has already been on signet for a few years,
> CSFS isn't.
>
> With CTV and CSFS being on the signet also allows part of the LNHANCE to
> start experimenting, and it has been discussed that CSFS helps with BitVM
> by replacing Winternitz signatures completely with a much lower potential
> on-chain data availability overhead. This also allows applications relying
> on CTV + CSFS to develop further.
>
> Thanks,
> Weikeng
>
> --
> 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/2584bf15-8e7f-4d89-8987-f41dd06b2824n%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/2584bf15-8e7f-4d89-8987-f41dd06b2824n%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-Zo3JcUjyQ3%3D--oecm6Nq2CM20AzZbpLQsZhSXKJfxm7rQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 3340 bytes --]
next prev parent reply other threads:[~2025-03-17 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 3:38 Weikeng Chen
2025-03-17 14:11 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-17 14:43 ` /dev /fd0 [this message]
2025-03-17 22:52 ` 'moonsettler' via Bitcoin Development Mailing List
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-Zo3JcUjyQ3=--oecm6Nq2CM20AzZbpLQsZhSXKJfxm7rQ@mail.gmail.com' \
--to=alicexbtong@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=weikeng.chen@l2iterative$(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