Delivery-date: Mon, 03 Mar 2025 13:55:26 -0800
Sender: bitcoindev@googlegroups.com
Date: Mon, 3 Mar 2025 13:00:23 -0800 (PST)
From: Hunter Beast <hunter@surmount.systems>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <fac67bec-cbf3-4e49-b73d-f8057adca0aan@googlegroups.com>
In-Reply-To: <69ab395f-acba-4d11-87ee-9da6327509c6@gmail.com>
References: <8797807d-e017-44e2-b419-803291779007n@googlegroups.com>
 <5667eb21-cd56-411d-a29f-81604752b7c4@gmail.com>
 <16d7adca-a01e-40c5-9570-31967ee339ecn@googlegroups.com>
 <5550807e-0655-4895-bc66-1b67bfde8c3e@gmail.com>
 <8e1cf1b5-27d1-4510-afec-52fb28959189n@googlegroups.com>
 <69ab395f-acba-4d11-87ee-9da6327509c6@gmail.com>
Subject: Re: [bitcoindev] P2QRH / BIP-360 Update
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_21714_53943040.1741035623622"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_21714_53943040.1741035623622
Content-Type: multipart/alternative; 
	boundary="----=_Part_21715_755010069.1741035623622"

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

Hi, Jonas

In order to spend the coins, a valid signature will need to be present in=
=20
the attestation. Even if it's a 1/1024 multisig, a valid public key=20
signature pair will need to be provided. The merkle path would then be how=
=20
the arbitrary data could be encoded. In my mind this is a highly=20
impractical scenario that gets exponentially more complex, and only works=
=20
32 bytes at a time.

Does that make sense?

Hunter

On Wednesday, February 26, 2025 at 3:00:36=E2=80=AFAM UTC-7 Jonas Nick wrot=
e:

> > it would require an extraordinary amount of computation to wind up with=
=20
> enough
> > to store arbitrary data.
>
> I have no idea why this would require extraordinary amount of computation=
.=20
> In
> the example I provided, arbitrary data can be included in the attestation
> structure with zero additional computational cost, no elliptic curve=20
> grinding or
> hash collisions required.
>

--=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 visit https://groups.google.com/d/msgid/bitcoindev/=
fac67bec-cbf3-4e49-b73d-f8057adca0aan%40googlegroups.com.

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

Hi, Jonas<div><br /></div><div>In order to spend the coins, a valid signatu=
re will need to be present in the attestation. Even if it's a 1/1024 multis=
ig, a valid public key signature pair will need to be provided. The merkle =
path would then be how the arbitrary data could be encoded. In my mind this=
 is a highly impractical scenario that gets exponentially more complex, and=
 only works 32 bytes at a time.</div><div><br /></div><div>Does that make s=
ense?</div><div><br /></div><div>Hunter<br /><br /></div><div class=3D"gmai=
l_quote"><div dir=3D"auto" class=3D"gmail_attr">On Wednesday, February 26, =
2025 at 3:00:36=E2=80=AFAM UTC-7 Jonas Nick wrote:<br/></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin: 0 0 0 0.8ex; border-left: 1px solid rg=
b(204, 204, 204); padding-left: 1ex;"> &gt; it would require an extraordina=
ry amount of computation to wind up with enough
<br> &gt; to store arbitrary data.
<br>
<br>I have no idea why this would require extraordinary amount of computati=
on. In
<br>the example I provided, arbitrary data can be included in the attestati=
on
<br>structure with zero additional computational cost, no elliptic curve gr=
inding or
<br>hash collisions required.
<br></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 visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/fac67bec-cbf3-4e49-b73d-f8057adca0aan%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/fac67bec-cbf3-4e49-b73d-f8057adca0aan%40googlegroups.com</a>.<br />

------=_Part_21715_755010069.1741035623622--

------=_Part_21714_53943040.1741035623622--