1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
|
Delivery-date: Mon, 03 Mar 2025 13:55:26 -0800
Received: from mail-yw1-f186.google.com ([209.85.128.186])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBD3YNWFH7IHBBQ6KTC7AMGQE5OMBZNQ@googlegroups.com>)
id 1tpDkz-00088p-Jl
for bitcoindev@gnusha.org; Mon, 03 Mar 2025 13:55:26 -0800
Received: by mail-yw1-f186.google.com with SMTP id 00721157ae682-6f2a2ab50f6sf71336377b3.3
for <bitcoindev@gnusha.org>; Mon, 03 Mar 2025 13:55:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1741038919; x=1741643719; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:references:in-reply-to:message-id:to:from:date:sender:from
:to:cc:subject:date:message-id:reply-to;
bh=6xfqjzL+fR4FXoaY9ZhsLc+vBG5UK14M4t9dVuaQ4RQ=;
b=uUQabSjSOaCvt9ETGW3rxUBrglNUlRJmV28QlQt3zmvu8jzLyQvAtol+p1AT3Etmle
4BIfeiHU0DoUVPgUP0UOAULlyGrG5vkMgfcQfHsn2IUKH0vIyCQn9gjq5E4/ld6MnE4/
bDbNQ9nIfiwWzxEyz17gU6JibRtpAL6saJEYfcMb1L18ydWIuhNlfSLSkJlMrWeKul1K
rjYTL7tHEsY4MTYsZUdKrti2VCKiHxtD4SzbU9exjwd1Grhcqthh/LI8pyRf5R4G5ci5
d5H6WAPQzydxY4G6kvoQCna62dmsBWaRkEtcPoinLdainkNJUvaWNrIxJK2/Z3N3g+A+
7mqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1741038919; x=1741643719;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:references:in-reply-to:message-id:to:from:date:x-beenthere
:x-gm-message-state:sender:from:to:cc:subject:date:message-id
:reply-to;
bh=6xfqjzL+fR4FXoaY9ZhsLc+vBG5UK14M4t9dVuaQ4RQ=;
b=txX6w+2Zs5vaBknmHs5AfIz0FyIktvi+t3UajLFS1L8d85CZtj3KHkxeFkZyzrMRQ1
7IwolnaD3s2M2q1xqsuJ7WhJ5zSCoB26pQ0vtIV7CSnmJK3CeGDh2QKf8HPjdVdKDay/
DG5eUl1bizcjso+YJCCLySClb/S2yOTGagA3tSPOauf9JdgGWvCPfEwhFJL35dgIyOEV
ITJi2IZKJW+DgmLeQTpOSGdzckmOjhzLAwRp6LCna8nGPMpMoV7NieDPder6+8kOZyVf
jCvISLCFNDocOll5FemB9D7hXPYOxBexlU72fS664mu4Jcyln87ctWdYVTrWpxyS5j0e
0Dsg==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCVEb56OlzcCM7s00l+q7O6O7NuvlbF54ngrreFcSqbjkpMmKQ3zfmft2HfV5ZjzfcbSAB3DZ8BKjah9@gnusha.org
X-Gm-Message-State: AOJu0YzIwIl4ntkmGQJYRL3brBasTp3qlgkZcKdW8U1jgUCpP3MRbqJe
ncclG5o6EIjLSjGEx8Zhd9NTFsBqJaOqtORLzl0jqmHQoFWh16oo
X-Google-Smtp-Source: AGHT+IEK1eE9aB4vT3wYjVHpKkchFLELHME88Y6ID1Wmjhiy7CD+NgaYn/VPLu2RT934h7oZsulw7A==
X-Received: by 2002:a05:6902:725:b0:e5d:bcc5:c33a with SMTP id 3f1490d57ef6-e60b2f55540mr17401674276.43.1741038918914;
Mon, 03 Mar 2025 13:55:18 -0800 (PST)
X-BeenThere: bitcoindev@googlegroups.com; h=Adn5yVF9nnrmhUrPg9/EIUZBM0TWhPW28QI1OSn1y0IQEfxAfA==
Received: by 2002:a25:d3d4:0:b0:e60:9cfa:4134 with SMTP id 3f1490d57ef6-e609f05eb55ls1965305276.2.-pod-prod-06-us;
Mon, 03 Mar 2025 13:55:15 -0800 (PST)
X-Received: by 2002:a05:690c:6c01:b0:6f9:441e:6cf0 with SMTP id 00721157ae682-6fd4a03da91mr200844277b3.5.1741038914771;
Mon, 03 Mar 2025 13:55:14 -0800 (PST)
Received: by 2002:a81:c703:0:b0:6fd:27d2:c7f1 with SMTP id 00721157ae682-6fd4d0922efms7b3;
Mon, 3 Mar 2025 13:00:25 -0800 (PST)
X-Received: by 2002:a05:690c:3686:b0:6ef:6a71:aa55 with SMTP id 00721157ae682-6fd49ead0dbmr212073327b3.0.1741035624106;
Mon, 03 Mar 2025 13:00:24 -0800 (PST)
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"
X-Original-Sender: hunter@surmount.systems
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
<https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.7 (/)
------=_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;"> > it would require an extraordina=
ry amount of computation to wind up with enough
<br> > 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" 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--
|
