From: "'Antoine Poinsot' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.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 14:11:32 +0000 [thread overview]
Message-ID: <tTFTcI1mOB8uc9VsOtAzYOSa7wLkrC50Sy7sWwCffVtkwFNiS_74c97w3AxUzw62f8bQ66gPoU1iIu_cfqJlLJL7gds8Vr7DLdoAKE9Q-GI=@protonmail.com> (raw)
In-Reply-To: <2584bf15-8e7f-4d89-8987-f41dd06b2824n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]
I wouldn't go as far as saying it received "a lot" of support, but it did receive some and i agree it would be nice to have both opcodes being discussed on Signet.
The PR adding it to inquisition last year as part of LNHANCE was abandoned and closed a few months ago. Greg Sanders recently opened a WIP pull request to add CSFS on its own: https://github.com/bitcoin-inquisition/bitcoin/pull/72.
> This also allows applications relying on CTV + CSFS to develop further.
Looking forward to see some of that.
On Sunday, March 16th, 2025 at 11:38 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.
--
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/tTFTcI1mOB8uc9VsOtAzYOSa7wLkrC50Sy7sWwCffVtkwFNiS_74c97w3AxUzw62f8bQ66gPoU1iIu_cfqJlLJL7gds8Vr7DLdoAKE9Q-GI%3D%40protonmail.com.
[-- Attachment #2: Type: text/html, Size: 3531 bytes --]
next prev parent reply other threads:[~2025-03-17 14:17 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 [this message]
2025-03-17 14:43 ` /dev /fd0
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='tTFTcI1mOB8uc9VsOtAzYOSa7wLkrC50Sy7sWwCffVtkwFNiS_74c97w3AxUzw62f8bQ66gPoU1iIu_cfqJlLJL7gds8Vr7DLdoAKE9Q-GI=@protonmail.com' \
--to=bitcoindev@googlegroups.com \
--cc=darosior@protonmail$(echo .)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