Delivery-date: Wed, 24 Apr 2024 08:35:39 -0700
Sender: bitcoindev@googlegroups.com
Date: Mon, 22 Apr 2024 09:09:46 -0700 (PDT)
From: Ali Sherief <ali@notatether.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <c32da32a-e950-4f76-b8b3-8206894cc836n@googlegroups.com>
In-Reply-To: <CAEM=y+X-a3VoJ1urjBFhxGpaRzN9dgPr-z6u+YottNsMBT03Sg@mail.gmail.com>
References: <CAEM=y+X-a3VoJ1urjBFhxGpaRzN9dgPr-z6u+YottNsMBT03Sg@mail.gmail.com>
Subject: [bitcoindev] Re: Updated BIP for OP_CAT
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_435270_187652630.1713802186499"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_435270_187652630.1713802186499
Content-Type: multipart/alternative; 
	boundary="----=_Part_435271_89912851.1713802186499"

------=_Part_435271_89912851.1713802186499
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=20
can "support tree signatures with a thousand public keys." I think it would=
=20
be more useful to put the theoretical limit there, as it is buried along=20
with the rest of the data on tree signatures inside the reference link to=
=20
Blockstream's web page, which could go stale for whatever reason.

On a further note, if there are enough practical uses for tree signatures,=
=20
we could make it into a fully fledged BIP too, instead of just something=20
cool that would make the Stacker News front page.

- Ali

On Tuesday, April 16, 2024 at 7:21:22=E2=80=AFPM UTC Ethan Heilman wrote:

Hi everyone,

We've recently made a number of updates to the OP_CAT BIP proposal=20
including adding a rationale section, an expanded backwards compatibility=
=20
section and an updated reference implementation.

It can be found as a PR to the bitcoin/bips repo here:=20
https://github.com/bitcoin/bips/pull/1525
or as BINANA BIN-2024-0001:=20
https://github.com/bitcoin-inquisition/binana/blob/master/2024/BIN-2024-000=
1.md

Thanks,
Ethan

--=20
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 e=
mail 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.

------=_Part_435271_89912851.1713802186499
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Ethan,<br /><br />Very good to see your OP_CAT design is now on the mail=
ing list.<br /><br />Inside the BIP text, you mention that a sufficiently l=
arge 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 i=
t is buried along with the rest of the data on tree signatures inside the r=
eference link to Blockstream's web page, which could go stale for whatever =
reason.<br /><br />On a further note, if there are enough practical uses fo=
r tree signatures, we could make it into a fully fledged BIP too, instead o=
f just something cool that would make the Stacker News front page.<br /><br=
 />- Ali<br /><br /><div><div dir=3D"auto">On Tuesday, April 16, 2024 at 7:=
21:22=E2=80=AFPM UTC Ethan Heilman wrote:<br /></div><blockquote style=3D"m=
argin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); paddin=
g-left: 1ex;"><div dir=3D"ltr">Hi everyone,<br /><br />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 refere=
nce implementation.<br /><br />It can be found as a PR to the bitcoin/bips =
repo here:=C2=A0<br /><a href=3D"https://github.com/bitcoin/bips/pull/1525"=
 target=3D"_blank" rel=3D"nofollow">https://github.com/bitcoin/bips/pull/15=
25</a><br />or as BINANA BIN-2024-0001: <br /><a href=3D"https://github.com=
/bitcoin-inquisition/binana/blob/master/2024/BIN-2024-0001.md" target=3D"_b=
lank" rel=3D"nofollow">https://github.com/bitcoin-inquisition/binana/blob/m=
aster/2024/BIN-2024-0001.md</a><br /><br />Thanks,<br />Ethan<br /><br /></=
div>
</blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/c32da32a-e950-4f76-b8b3-8206894cc836n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/c32da32a-e950-4f76-b8b3-8206894cc836n%40googlegroups.com</a>.=
<br />

------=_Part_435271_89912851.1713802186499--

------=_Part_435270_187652630.1713802186499--