Hi, Jonas<div><br /></div><div>In order to spend the coins, a valid signature will need to be present in the attestation. Even if it's a 1/1024 multisig, 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 sense?</div><div><br /></div><div>Hunter<br /><br /></div><div class="gmail_quote"><div dir="auto" class="gmail_attr">On Wednesday, February 26, 2025 at 3:00:36 AM UTC-7 Jonas Nick wrote:<br/></div><blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> &gt; it would require an extraordinary 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 computation. In
<br>the example I provided, arbitrary data can be included in the attestation
<br>structure with zero additional computational cost, no elliptic curve grinding 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 email to <a href="mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoindev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href="https://groups.google.com/d/msgid/bitcoindev/fac67bec-cbf3-4e49-b73d-f8057adca0aan%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/bitcoindev/fac67bec-cbf3-4e49-b73d-f8057adca0aan%40googlegroups.com</a>.<br />