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
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
|
Delivery-date: Tue, 27 May 2025 16:15:13 -0700
Received: from mail-oo1-f62.google.com ([209.85.161.62])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBDJ6TUHA44ARB54O3HAQMGQE6IJTOSQ@googlegroups.com>)
id 1uK3Vo-0000y1-BO
for bitcoindev@gnusha.org; Tue, 27 May 2025 16:15:13 -0700
Received: by mail-oo1-f62.google.com with SMTP id 006d021491bc7-605f8bca0e3sf3273907eaf.3
for <bitcoindev@gnusha.org>; Tue, 27 May 2025 16:15:12 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1748387706; cv=pass;
d=google.com; s=arc-20240605;
b=MoU9v6NUtfWK0TVTJDJ9ABiF9zD4VqJo6X5lT4PJKORubsEZ0UL1SoxXsnwOD6il8H
99nlMCYgJ2OZIq7Ww5Bq42oEf+avqOL5mUNvqEcJsN7kG/ewW0pBc1wrTvE4vX+ddebp
NOkmOGCGDTdRt+tnUCB+pTfcOdUctf0r9gKlXg/+K1ax+KW0L10VstiKCubkHPbFsj53
HHnOAwf9JcYl2IMaezvgj1SNQBqVUV8oL4abkWM0jI5AxMFdRffQBnjdJhh55uxRGy9i
CxEplys4BkAu6IJBRZ3ZIu2pw58b4m8RJ01S42qGr4poaSYZ5FegpbFBzuTGa6c53gr7
uxCw==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:to:subject:message-id:date:from
:in-reply-to:references:mime-version:sender:dkim-signature;
bh=2h9M6fk4JdxStx4y7TWETE+7fH32fSN4KAgfz27RviE=;
fh=LQsAnBzPZnWwuxugEw2tveNh/odr5B4hQ6UD7y6y8X8=;
b=Fta36NpRUOrbJ3ZXxbBk2wjBB7gaRqQkzJcJd2iGUlgDezATAYWHPq2BkzeDi82/T1
QdQaOtdUqJjfCM42V0Z3/InDU90D4Ji8PPVj9BjC9qakMySM0Ry73kqQFHHdoLNx9iZX
GEJVU4rpzvqme5QaOF/UZ54AHH6AJzcNXDPueIV9xkAov6AB4RZCEkYLACl7y//2d/iL
wwIFPhCm9UWqIMGWLXckkE8v/pVxEDUlDStlZybn4S6DK8h3C+eivXDtoA+gV5Cf5CNM
YLOhCdDes0YYzUDPMxGL5oyh8fM2wDS+ucRS3fmz7w+IJtCTB0c/quAgzlYQgb9E5iSD
BG4A==;
darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
spf=pass (google.com: domain of dscotese@gmail.com designates 209.85.128.54 as permitted sender) smtp.mailfrom=dscotese@gmail.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1748387706; x=1748992506; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:to:subject:message-id:date:from:in-reply-to
:references:mime-version:sender:from:to:cc:subject:date:message-id
:reply-to;
bh=2h9M6fk4JdxStx4y7TWETE+7fH32fSN4KAgfz27RviE=;
b=N9hU86BNneyIuECpWtpOI/OtDLZvoEerI3vuDYX0z24dbd1glBSG2T5E0o5GJ9epi+
SrQ1wqFeHsn+EooCeNNyc8JBf9usE3ZQWWlPy/1xSwHMWztR22hY2hkwDoxiKogJn1nQ
Ak0zpBGuWXM3gDgacEHcwNOLTXRTE2IpztqrHJ9iIv3aKGEb98Cmzhw2CXVAb5lqL59f
5ngU6Z3gtfXsnRSEJErroAyyhbw0yR0Ql2KL0mi4qcbHx17uuoYkiMH7Sp1giw+UXy0f
uAr2kV8gP2mkXbWgBsMx+TR7cNy2DXBBJQGORlOQRhz3Rzcpu6P0LlrsaGB8bYbVbLRK
sx5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1748387706; x=1748992506;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:to:subject:message-id:date:from:in-reply-to
:references:mime-version:x-beenthere:x-gm-message-state:sender:from
:to:cc:subject:date:message-id:reply-to;
bh=2h9M6fk4JdxStx4y7TWETE+7fH32fSN4KAgfz27RviE=;
b=meDuAYVEGS52TmgCYUpbcjSO8MelgoZBYN2eKQQjgN9gvIERIgtV9qzJ8BaaOiwpZT
26LhFKdF0lOqei5+aVpseZrJ6N/x763z4RY8lcBZ19Ug0Ftkye8ws+/1W1v6p8nZlWCz
1YGXD03zDCHndfNfMg29hE6xQCLADh3aFaT8aV1Zl12oR3aZ9y/oqly2NQwy7AhJw+Iq
2HnxlBKfMHrDMRqYQVD+4WArK8vo2vRhk6ne/x9uiE5c0tFzUGaTwN5YSXeER/SvfRP2
0AKE/U5IiuukjI7QFtqv2O+U1peYlIRJLfOaj4xuzU+N3iJ7qexgUrI0wRKc3nQP7mbI
mMXw==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCVdc075YoJgTwnYFfASyq1GLXG9/HOtyA1xohjS8wctlP49ORJfPyGt5cKFUh5k1s2QcZZXvx6N9/n+@gnusha.org
X-Gm-Message-State: AOJu0Yw4OXmXhZ4zwEuBto5iHlyfNF4XiU6D4pam1s7X/py5oCrqENLy
108hbBUlScmxhtvJnAtPy70BJVClAZaNy9+XmfXI3d3Rw8rr795+/h/G
X-Google-Smtp-Source: AGHT+IFWn8PfJgWE9NlQj+QsQSOddmr2+DbSHRsuVndbsPxIE2Y6+JAEZ3xR1L3iXn0nJ0MXlM48Wg==
X-Received: by 2002:a05:6871:d186:b0:2e8:7471:6350 with SMTP id 586e51a60fabf-2e874716454mr5053500fac.1.1748387706051;
Tue, 27 May 2025 16:15:06 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=AZMbMZfzAMoO0Txg6HGFMjmD7pPo2v42m8h/uS782WJCJHfY0A==
Received: by 2002:a4a:e5c8:0:b0:609:1093:ed15 with SMTP id 006d021491bc7-60b9f4a580els336881eaf.0.-pod-prod-09-us;
Tue, 27 May 2025 16:15:02 -0700 (PDT)
X-Received: by 2002:a05:6808:7005:b0:404:78f9:771a with SMTP id 5614622812f47-40646843adbmr9334381b6e.26.1748387702829;
Tue, 27 May 2025 16:15:02 -0700 (PDT)
Received: by 2002:a05:600c:2206:b0:43c:fd8b:faa8 with SMTP id 5b1f17b1804b1-442fe8b8c82ms5e9;
Tue, 27 May 2025 16:10:22 -0700 (PDT)
X-Received: by 2002:a05:600c:4f52:b0:43d:42b:e186 with SMTP id 5b1f17b1804b1-44c919e1860mr127418985e9.8.1748387419769;
Tue, 27 May 2025 16:10:19 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1748387419; cv=none;
d=google.com; s=arc-20240605;
b=IX4pDV9xAVlTGE8I4drthHkkupjTNXOXb7XUSrsrKebir168orV6QnGWCO5V9Y1+OR
lsgtLj+e+oozXQ8hHKI1PeIxCHQY0oGrqE5tNc1kYoBltCh102Zbcviw1LMDRjs30DdF
48s2TEDQJqjv1HUIFFd6ZMwrVkIOAwjWpDdgXTWV3TiVv4HphE+si3J79gSx6xnYxcUX
wl9m0G696z7EUCx5ploOMqA+k4H7D5Uk3z0ob7CW2lO7PeSrMdAdMFhaw7Cg34HMmecS
QSW0zOWeHUI4MY7HLr/eY2TJKZ9yqDWSPvD3fu58ZZDYUEAjajpGObWWwQi+YQTgNuVe
XNhA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version;
bh=OmV2YqCQHyv7akJn3LzpBkzhg2J2RKF3ELvVU868gQA=;
fh=DMP0F9ULS1guKiqimntQRCN8ZraraesEgQuVcn7F0Z0=;
b=N5ktZj3ZB8tRzorQWIwXX0Apw6386w5Uz6JHR0KeQREY30SNQlgt2T+spLyNlYV7CL
sUB1AB4opx2Wc309jAcM1Y5BbfATGc15BDUAl8IBW23Xio4gvBgpmONuv3pCsWQzbA2W
gpFInP3i2zDuY2CsRMebcmUvuRctXSoPcpQjrCsekxNIo2w0qiVgpzSmb38p8BKeoqQH
OFBFHZwFQRtnnqFf44J8aUgwzwnrG1LmWpSxqc3N7pNgY9++Yme1V/JrNhYop5qU6Ni/
2+OC3UH1w48lrojP8SWnajQqSyl2Mhiwu2eEOzqLTTJbU9POISiConslM9l+8kbWgW18
SYGg==;
dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
spf=pass (google.com: domain of dscotese@gmail.com designates 209.85.128.54 as permitted sender) smtp.mailfrom=dscotese@gmail.com
Received: from mail-wm1-f54.google.com (mail-wm1-f54.google.com. [209.85.128.54])
by gmr-mx.google.com with ESMTPS id 5b1f17b1804b1-44ffc0dee5csi51835e9.0.2025.05.27.16.10.19
for <bitcoindev@googlegroups.com>
(version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
Tue, 27 May 2025 16:10:19 -0700 (PDT)
Received-SPF: pass (google.com: domain of dscotese@gmail.com designates 209.85.128.54 as permitted sender) client-ip=209.85.128.54;
Received: by mail-wm1-f54.google.com with SMTP id 5b1f17b1804b1-43edb40f357so33617635e9.0
for <bitcoindev@googlegroups.com>; Tue, 27 May 2025 16:10:19 -0700 (PDT)
X-Gm-Gg: ASbGncsLD3AYH0Eb+aRXovyDydFBajBEj8B+y8zJc2Z44p35IFioFYWDUlTQwFs65Et
mKuJ+R6AQEbd1p2S+RHOOk6fUZtqnczu69bxcbRbM/ls9QdLgUgdTH2yXy2E3hXi3fPcXrT2jwf
znhyDT40Nysweh+cqMujPOekvQcZEbpOLnmow=
X-Received: by 2002:a05:6000:1888:b0:3a4:e8c4:7a78 with SMTP id
ffacd0b85a97d-3a4e8c47cc8mr301587f8f.52.1748387418464; Tue, 27 May 2025
16:10:18 -0700 (PDT)
MIME-Version: 1.0
References: <a2fde16d-5ddd-47ae-8b8f-6ca313d92b66n@googlegroups.com>
<CAMZUoK=mux6u=f_b0yLb6nvJp41H7iPg7G+dLO5xT94kbDybjQ@mail.gmail.com> <a484ae6a-33d6-4704-8356-c0ed1e5ae376n@googlegroups.com>
In-Reply-To: <a484ae6a-33d6-4704-8356-c0ed1e5ae376n@googlegroups.com>
From: Dave Scotese <dscotese@litmocracy.com>
Date: Tue, 27 May 2025 16:10:07 -0700
X-Gm-Features: AX0GCFvP0TUVkM1MQb3RE7Fb-W9_wiVxNYZ1XngR-pmtv9NFK07kU3hXFiSRmTE
Message-ID: <CAGLBAhc6QG5H5BXPg=Ny5dR563YwL+iB22+P=usam5Ev9F0TDg@mail.gmail.com>
Subject: Re: [bitcoindev] Proposal to solve the spam war: configurable data
blob relay policy
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Content-Type: multipart/alternative; boundary="00000000000001e8290636262b0e"
X-Original-Sender: dscotese@litmocracy.com
X-Original-Authentication-Results: gmr-mx.google.com; spf=pass
(google.com: domain of dscotese@gmail.com designates 209.85.128.54 as
permitted sender) smtp.mailfrom=dscotese@gmail.com
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 (/)
--00000000000001e8290636262b0e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
As far as I can tell, the resource being wasted is the bandwidth of those
who are (currently kind enough to be) maintaining the network. They are
giving away that bandwidth for free, and I think they ought to be
compensated for it, but until enough of it is "wasted", the demand for such
compensation will remain too low for that problem to be solved. Everyone
who broadcasts a transaction offers the miners the chance to earn a fee,
and those miners seem to me to be the only ones with the right incentive to
solve the problem (because if it gets bad enough, they don't get valuable
bitcoin transactions to mine quickly enough). I believe that in time,
miners will develop a way of privately compensating transaction relayers
for this reason. I would very much enjoy seeing the propagation of data
grow as a market on its own in which nerds like me could participate simply
by leaving their internet-connected machines on all the time and
maintaining the software that runs it.
Protecting Bitcoin from becoming that market and perhaps crowding out its
financial utility might not be such a good idea, but distributing Bitcoin
technology has vastly lowered the cost of financial transactions for
everyone. If we need two networks, one for stuff like what Citrea is doing
and the other for finance with a technological fence around it, I'm all for
it. Has Citrea heard of nostr?
Dave Scotese
On Tue, May 27, 2025 at 10:18=E2=80=AFAM Jonathan Voss <k98kurz@gmail.com> =
wrote:
> My understanding is that Citrea is using a ZKP proof to recover from an
> invalid protocol state. Whatever data gets into the blockchain, the onus =
is
> on the Citrea-compatible nodes to do the actual validation -- Bitcoin
> itself has no part in this other than distributing the data. Adding a new
> relay service for promulgating data that is provably committed to in an
> OP_RETURN would not be a significant additional burden to the L2 protocol
> if this additional relay service is adopted by a sufficient proportion of
> nodes, and L2 protocol participants would have an incentive to run this n=
ew
> relay service for their own benefit, so they would likely already have th=
e
> data cached by the time the transaction is confirmed. I don't have any ha=
rd
> numbers on this, but my conjecture is that L2 protocols would run enough
> relays themselves for the system to be viable, and the clear segregation
> between arbitrary data ephemerally cached and monetary data permanently
> stored will be enough incentive for many node operators to also adopt it.
>
> On Tuesday, May 27, 2025 at 12:05:51=E2=80=AFPM UTC-4 Russell O'Connor wr=
ote:
>
>> On Sat, May 24, 2025 at 5:33=E2=80=AFPM Jonathan Voss <k98...@gmail.com>=
wrote:
>>
>>> However, the recent discussion premised upon Citrea's Clementine Bridge
>>> evidences primarily that the relaying capabilities of the Bitcoin netwo=
rk
>>> itself are sufficiently useful for L2 designers that there is an incent=
ive
>>> to bypass standardness restrictions for the sake of reliably promulgati=
ng
>>> data -- at least in the case of Citrea, they say they need to quickly a=
nd
>>> widely disseminate 140+ bytes of arbitrary ZKP data to recover from an
>>> invalid protocol state, and the utility of that ZKP data very quickly
>>> decreases after it has been confirmed and processed.
>>
>>
>> Does your proposal actually solve this problem? Posting the 140 bytes o=
f
>> data to the blockchain works as a public bulletin board because the actu=
al
>> data within the block is what is ultimately guaranteed to be disseminate=
d
>> to all participants. With your proposal, a transaction with an OP_RETUR=
N
>> containing a hash of data could end up being mined without the relevant
>> transaction ever even being relayed through the Bitcoin network.
>>
>> --
> 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 visit
> https://groups.google.com/d/msgid/bitcoindev/a484ae6a-33d6-4704-8356-c0ed=
1e5ae376n%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/a484ae6a-33d6-4704-8356-c0e=
d1e5ae376n%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter>
> .
>
--=20
I own Litmocracy <http://www.litmocracy.com> and Meme Racing
<http://www.memeracing.net> (in alpha).
I'm the webmaster for The Voluntaryist <http://www.voluntaryist.com> which
now accepts Bitcoin.
"He ought to find it more profitable to play by the rules" - Satoshi
Nakamoto
--=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/=
CAGLBAhc6QG5H5BXPg%3DNy5dR563YwL%2BiB22%2BP%3Dusam5Ev9F0TDg%40mail.gmail.co=
m.
--00000000000001e8290636262b0e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">As far as I can tell, the resource being wasted is the ban=
dwidth of those who are (currently kind enough=C2=A0to be) maintaining the =
network. They are giving away that bandwidth for free, and I think they oug=
ht to be compensated for it, but until enough of it is "wasted", =
the demand for such compensation will remain too low for that problem to be=
solved. Everyone who broadcasts a transaction offers the miners the chance=
to earn a fee, and those miners seem to me to be the only ones with the ri=
ght incentive to solve the problem (because if it gets bad enough, they don=
't get valuable bitcoin transactions to mine quickly enough). I believe=
that in time, miners will develop=C2=A0a way of privately compensating tra=
nsaction relayers for this reason. I would very much enjoy seeing the propa=
gation of data grow as a market on its own in which nerds like me could par=
ticipate simply by leaving their internet-connected machines on all the tim=
e and maintaining the software that runs it.<div><br></div><div>Protecting =
Bitcoin from becoming that market and perhaps crowding out its financial ut=
ility might not be such a good idea, but distributing Bitcoin technology ha=
s vastly lowered the cost of financial transactions for everyone. If we nee=
d two networks, one for stuff like what Citrea is doing and the other for f=
inance with a technological fence around it, I'm all for it. Has Citrea=
heard of nostr?</div><div><br></div><div>Dave Scotese</div></div><br><div =
class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail=
_attr">On Tue, May 27, 2025 at 10:18=E2=80=AFAM Jonathan Voss <<a href=
=3D"mailto:k98kurz@gmail.com">k98kurz@gmail.com</a>> wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">My understanding is that Cit=
rea is using a ZKP proof to recover from an invalid protocol state. Whateve=
r data gets into the blockchain, the onus is on the Citrea-compatible nodes=
to do the actual validation -- Bitcoin itself has no part in this other th=
an distributing the data. Adding a new relay service for promulgating data =
that is provably committed to in an OP_RETURN would not be a significant ad=
ditional burden to the L2 protocol if this additional relay service is adop=
ted by a sufficient proportion of nodes, and L2 protocol participants would=
have an incentive to run this new relay service for their own benefit, so =
they would likely already have the data cached by the time the transaction =
is confirmed. I don't have any hard numbers on this, but my conjecture =
is that L2 protocols would run enough relays themselves for the system to b=
e viable, and the clear segregation between arbitrary data ephemerally cach=
ed and monetary data permanently stored will be enough incentive for many n=
ode operators to also adopt it.<br><br><div class=3D"gmail_quote"><div dir=
=3D"auto" class=3D"gmail_attr">On Tuesday, May 27, 2025 at 12:05:51=E2=80=
=AFPM UTC-4 Russell O'Connor wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, May 24, 2025 at 5:3=
3=E2=80=AFPM Jonathan Voss <<a rel=3D"nofollow">k98...@gmail.com</a>>=
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">However,=
the recent discussion premised upon Citrea's Clementine Bridge evidenc=
es primarily that the relaying capabilities of the Bitcoin network itself a=
re sufficiently useful for L2 designers that there is an incentive to bypas=
s standardness restrictions for the sake of reliably promulgating data -- a=
t least in the case of Citrea, they say they need to quickly and widely dis=
seminate 140+ bytes of arbitrary ZKP data to recover from an invalid protoc=
ol state, and the utility of that ZKP data very quickly decreases after it =
has been confirmed and processed.</blockquote><div><br></div></div></div></=
div><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote">Does your =
proposal actually solve this problem?=C2=A0 Posting the 140 bytes of data t=
o the blockchain works as a public bulletin board because the actual data w=
ithin the block is what is ultimately guaranteed to be disseminated to all =
participants.=C2=A0 With your proposal, a transaction with an OP_RETURN con=
taining a hash of data could end up being mined without the relevant transa=
ction ever even being relayed through the Bitcoin network.</div><br></div>
</div>
</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" target=
=3D"_blank">bitcoindev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/a484ae6a-33d6-4704-8356-c0ed1e5ae376n%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter" target=3D"_blank">https://groups.googl=
e.com/d/msgid/bitcoindev/a484ae6a-33d6-4704-8356-c0ed1e5ae376n%40googlegrou=
ps.com</a>.<br>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature"><div dir=3D"ltr">I own <a href=3D"http://www.litmocracy.com" targ=
et=3D"_blank">Litmocracy</a> and <a href=3D"http://www.memeracing.net" targ=
et=3D"_blank">Meme Racing</a> (in alpha). <br>I'm the webmaster for <a =
href=3D"http://www.voluntaryist.com" target=3D"_blank">The Voluntaryist</a>=
which now accepts Bitcoin.<br>"He ought to find it more profitable to=
play by the rules" - Satoshi Nakamoto</div></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/CAGLBAhc6QG5H5BXPg%3DNy5dR563YwL%2BiB22%2BP%3Dusam5Ev9F0TDg%40ma=
il.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/d/msgid/bitcoindev/CAGLBAhc6QG5H5BXPg%3DNy5dR563YwL%2BiB22%2BP%3Dusam5E=
v9F0TDg%40mail.gmail.com</a>.<br />
--00000000000001e8290636262b0e--
|