From: Ethan Heilman <eth3rs@gmail•com>
To: Ali Sherief <ali@notatether•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: Updated BIP for OP_CAT
Date: Thu, 25 Apr 2024 20:34:31 -0400 [thread overview]
Message-ID: <CAEM=y+W5EfKAXDad-ByLt1x9mWu4QAx_hEt_SYq_Lj6DArpVBw@mail.gmail.com> (raw)
In-Reply-To: <c32da32a-e950-4f76-b8b3-8206894cc836n@googlegroups.com>
Excellent point, I've updated the BIP to specify the theoretical
maximum of public keys. See commit
https://github.com/EthanHeilman/bips/commit/852502b9cf0568dc4c75d93aaaaee3d102002ec7
> On a further note, if there are enough practical uses for tree signatures, we could make it into a fully fledged BIP too
I'd love to see a tree signature BIP. You should make one.
On Wed, Apr 24, 2024 at 11:35 AM Ali Sherief <ali@notatether•com> wrote:
>
> Hi Ethan,
>
> Very good to see your OP_CAT design is now on the mailing list.
>
> Inside the BIP text, you mention that a sufficiently large OP_CAT script can "support tree signatures with a thousand public keys." I think it would be more useful to put the theoretical limit there, as it is buried along with the rest of the data on tree signatures inside the reference link to Blockstream's web page, which could go stale for whatever reason.
>
> On a further note, if there are enough practical uses for tree signatures, we could make it into a fully fledged BIP too, instead of just something cool that would make the Stacker News front page.
>
> - Ali
>
> On Tuesday, April 16, 2024 at 7:21:22 PM UTC Ethan Heilman wrote:
>
> Hi everyone,
>
> We've recently made a number of updates to the OP_CAT BIP proposal including adding a rationale section, an expanded backwards compatibility section and an updated reference implementation.
>
> It can be found as a PR to the bitcoin/bips repo here:
> https://github.com/bitcoin/bips/pull/1525
> or as BINANA BIN-2024-0001:
> https://github.com/bitcoin-inquisition/binana/blob/master/2024/BIN-2024-0001.md
>
> Thanks,
> Ethan
>
> --
> 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 on the web visit https://groups.google.com/d/msgid/bitcoindev/c32da32a-e950-4f76-b8b3-8206894cc836n%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 on the web visit https://groups.google.com/d/msgid/bitcoindev/CAEM%3Dy%2BW5EfKAXDad-ByLt1x9mWu4QAx_hEt_SYq_Lj6DArpVBw%40mail.gmail.com.
next prev parent reply other threads:[~2024-04-26 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 19:03 [bitcoindev] " Ethan Heilman
2024-04-22 16:09 ` [bitcoindev] " Ali Sherief
2024-04-26 0:34 ` Ethan Heilman [this message]
2024-04-22 21:51 ` Ethan Heilman
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='CAEM=y+W5EfKAXDad-ByLt1x9mWu4QAx_hEt_SYq_Lj6DArpVBw@mail.gmail.com' \
--to=eth3rs@gmail$(echo .)com \
--cc=ali@notatether$(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