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
|
Delivery-date: Fri, 02 May 2025 15:23:52 -0700
Received: from mail-qv1-f62.google.com ([209.85.219.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+bncBDRYHVHZTUGRB3ML2XAAMGQEDBYO6GY@googlegroups.com>)
id 1uAynP-0003Qn-FT
for bitcoindev@gnusha.org; Fri, 02 May 2025 15:23:52 -0700
Received: by mail-qv1-f62.google.com with SMTP id 6a1803df08f44-6e8ec18a29asf28684776d6.2
for <bitcoindev@gnusha.org>; Fri, 02 May 2025 15:23:51 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1746224625; cv=pass;
d=google.com; s=arc-20240605;
b=A6Se+Otwr3S7CFbgE1KMRM3fIvYVFBU0MRzmj+PvykQJitlizw6FU6ieVrGFkFDe2S
xOra6s0Ev/mlQp75Up9Gjs1Z712ZEHwHnxsRYY9o6CYNqh/MOlFMBf1VO16MRa9831W0
sI5BkYh+vPYzusp9cmLhXjHIDo0202ECfKfxjuMGFojmCXFE8i3kjjxeBkIZKtibZJvI
Ac4l60C3bXsEwsFrKADjuOpqhGWUQlXgvC4/EMe3MmOm4g2rZ+4a7eQJJ1TL/cUCi3YF
5VOnAJRskxH7b0Ed250scnPHuyCyyjb2E+wyN3/34bgFu72uJyVeeIX4TejxwhFAIMAe
zdgA==
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:in-reply-to:content-disposition
:mime-version:references:message-id:subject:cc:to:from:date
:feedback-id:sender:dkim-signature;
bh=ctQsSx9ESZPVqe8Wi0iAUkd2F3eIdwHDRczaDrv376Y=;
fh=NrSTYJwV5gb0xKqaHflSLrew3xh/WLepBRUCOpqkgPQ=;
b=WHD/pVV/zbCTDN3TSdsDrY7H3MINGj1T2+RUFeUKJukJhJvCqb3vEuk+wfKgWlL6Kr
2C48KW6LxF7o/GZynarCe0+DciP72l8ImXpYEqjtFTH4Z3G9eecwaOR10C9TMp72HlDk
ARdTeaIyBy4ac2vaEFvtP4U3hIscNAqc7fqA+OHMiIsypp/9H8Hv1h6CcAM6vgLrGSOd
3T51AnW8PdxjfmG3lN/9ywxs5VE1SlBCf3w+8wU39iw//lUFsKGXLNuEMYnSKU3pSkge
HBa90/2PRMaFW2DhiF9u+06+rYq7XI51PFY22yhfvFUts7K1MNPVTfnppGR6run8dXAn
U1HQ==;
darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=vGWjc7od;
spf=pass (google.com: domain of pete@petertodd.org designates 202.12.124.145 as permitted sender) smtp.mailfrom=pete@petertodd.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1746224625; x=1746829425; 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:in-reply-to:content-disposition:mime-version
:references:message-id:subject:cc:to:from:date:feedback-id:sender
:from:to:cc:subject:date:message-id:reply-to;
bh=ctQsSx9ESZPVqe8Wi0iAUkd2F3eIdwHDRczaDrv376Y=;
b=RFNcB78bSrWtFiCUPlSVXCXfRxlaYfqtxcIiGSFYGhlZiBt0z0JaqvUWmPGrPfnw6x
Co0l9ohsHHIGyDjAGLXrOKtKADz+n/k+/g2KMwcceo4fDptUL7qrRzTnnZOSC6qDk6hS
q2/B+XECWg/EPaAWqnd+W5fNEfFX/GWv9SvE7oIzhkpepmBS4TCrhaAwV0bCBZckvcmv
n09ssQsgtkdfRcq+isWqlOdS8VS5A9NtGC6e0FvkHt/W5EDJZJ1zEF99X4FnOl4Rwe9m
BssMYNwObV37UfOJ2Iiei0uHlKGC73svAcEcLpfocGVk0odlC5UPloffweR7fN07NreU
OZjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1746224625; x=1746829425;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:in-reply-to:content-disposition:mime-version
:references:message-id:subject:cc:to:from:date:feedback-id
:x-beenthere:x-gm-message-state:sender:from:to:cc:subject:date
:message-id:reply-to;
bh=ctQsSx9ESZPVqe8Wi0iAUkd2F3eIdwHDRczaDrv376Y=;
b=aCfsEaE6GiVzOX/d/pVKCJgXU6U6raFvXrFSUbHIkiK6t1D2yAaorkIO9YXJl4yO2U
hnkGh3TjDUVeajxX4o4Y9w63R0JD/Co/gWNh7XyG+50A2t+g2bxwPEfkPhSGVD6UWw/M
lOcJ4JeetZO1HF5PvSc3lbYN7+vXFMgc0WeQFNQFDgTfETxaSuI4ClfxP3TyTB8sx9vN
RT/3fqayG6shcnPU/juYuqNnvDaX6IqEVT9mYJB6iY9yyxzq1Gpf6H2KQ1tDiMBsvxTv
ww80BvDMrCuMN6i02W4IUdVn57i1s6Y0/WdwrbWYFMYf7g7fCZYbzxNso3CvoAAXn61D
5Chw==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCXk76tHvhJFTLjDWa9ENXomyyk8s3iBkXLJJVHH2CD+IQ/cUY7/dV7zoWK2fQXiIGfuc3B9c5+fj8pE@gnusha.org
X-Gm-Message-State: AOJu0YwM1wD10szh6/QCI6nIDgwZfuCglljQBdU8ImmcMrvauD/u4fdl
SjT2WIgAk1brnnGIZmrj5DrBD71n9kGlgJJOkRsIibciAiIbJICJ
X-Google-Smtp-Source: AGHT+IGZj7v3C33d5tTsCfP32WQhZZuW8VRPUZYmuGIcS8TuiwGWe00wgrp6KjNBsFALGEiDT3Mwfg==
X-Received: by 2002:a05:6214:20a3:b0:6f4:ffc4:e229 with SMTP id 6a1803df08f44-6f514b7a408mr81431506d6.0.1746224625383;
Fri, 02 May 2025 15:23:45 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=AVT/gBFZzA6L9rWSC9aYOanIf3Px62yYveLGHxG1FEiyYE8B/g==
Received: by 2002:a0c:e5c7:0:b0:6e8:f2bd:66b1 with SMTP id 6a1803df08f44-6f508546980ls2163996d6.2.-pod-prod-08-us;
Fri, 02 May 2025 15:23:41 -0700 (PDT)
X-Received: by 2002:a05:620a:254d:b0:7c5:55f9:4bb2 with SMTP id af79cd13be357-7cad5b36e1cmr594700685a.22.1746224621498;
Fri, 02 May 2025 15:23:41 -0700 (PDT)
Received: by 2002:a05:620a:6221:b0:7c5:495f:5415 with SMTP id af79cd13be357-7cad5c98378ms85a;
Fri, 2 May 2025 13:03:34 -0700 (PDT)
X-Received: by 2002:a05:6214:e69:b0:6e4:2f7f:d0bb with SMTP id 6a1803df08f44-6f5152595c6mr70409286d6.4.1746216212945;
Fri, 02 May 2025 13:03:32 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1746216212; cv=none;
d=google.com; s=arc-20240605;
b=X3em6C8nPVL/PhaFcA4YGOnvGwCr6UaKCjk8CLkoCYLNqwj+9zosH4i3jD0/DNGHvd
V+s3UB8Tpr4wFAZ9xtySpTkuyWsCxaN4B0iD2lNAggPGKUVUfGgZX58ZnUj0yvVSPuza
3deN9eBnxByBiJvaVeRXLdh2Vtb3c6/VusdNbtdBZBxPlM2oejQ6fYpdgTeQR4agfQko
3UWQRXt1X757KOXptexhcQoXCHvJrylJNvsvPcRmG9djn7kT8G/p1lhNAEhWfUSP6U70
lri/AHip02C0L60XbIkZn0BWauen32ow8fJRFxVGTppbHPVQqeu0qibbdlETxbT/mZAh
RSjQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=in-reply-to:content-disposition:mime-version:references:message-id
:subject:cc:to:from:date:feedback-id:dkim-signature;
bh=wOscAKT7TTLaWuWRVt3UK9aYn/XOnnAl7IZEOCRs7Lw=;
fh=m2IwlnuMmP6ceRgqI8U7RCh8Dkd3VeWlWEfxse0Wcvc=;
b=di72sZz1DmDoGjJx8y1tcQyxXeZTZlSaZCwznOr6BCFitK2nPyl6ckzlXxbhhGKVSV
QqSPavpDdpbJZHEYiNDbwC0q7rFAkAiXyGqkoOJtCriG6gjol/ZIlsHL6trrSXOM8jRn
e2cRgdMDKlpqVTlySmpg+r4rDU3RMrRkz80EAyKMfVpXPAMVJ7myy6XdYbuhzQ0QXcy9
PmIXYiOf12Il9NjaZA5t7buc7Nxtheb9I7lFEfKIyTyl6foHSBjS3xpGGELLOl0Vv6wG
9+pKOaO0f4ibQUrSYyuI1mfeSzT6ndcyxCiXSvWToymp4qsYyK/TFrYcGW4znacAO8D5
lJTg==;
dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=vGWjc7od;
spf=pass (google.com: domain of pete@petertodd.org designates 202.12.124.145 as permitted sender) smtp.mailfrom=pete@petertodd.org
Received: from fout-b2-smtp.messagingengine.com (fout-b2-smtp.messagingengine.com. [202.12.124.145])
by gmr-mx.google.com with ESMTPS id d75a77b69052e-48b98a267c1si1605611cf.5.2025.05.02.13.03.32
for <bitcoindev@googlegroups.com>
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Fri, 02 May 2025 13:03:32 -0700 (PDT)
Received-SPF: pass (google.com: domain of pete@petertodd.org designates 202.12.124.145 as permitted sender) client-ip=202.12.124.145;
Received: from phl-compute-11.internal (phl-compute-11.phl.internal [10.202.2.51])
by mailfout.stl.internal (Postfix) with ESMTP id 52ADD11400D6;
Fri, 2 May 2025 16:03:32 -0400 (EDT)
Received: from phl-mailfrontend-02 ([10.202.2.163])
by phl-compute-11.internal (MEProxy); Fri, 02 May 2025 16:03:32 -0400
X-ME-Sender: <xms:EyUVaEDscrPCPRYvDzB6rIdjfTUgys0taAMOgPF931hrtjWowuvQag>
<xme:EyUVaGgzJjumo9nzj3xajx4AXR9UMeg_outF-5yxNqeSmUyM-BTzIEOjr_usY6wNF
ow402Lao_xU3gzdk3E>
X-ME-Received: <xmr:EyUVaHmrswxZ51VU1KPKthD3-F-Ei-AJBdUyf1B13xlssdhMar04GpO_Mai4_vEPOx_80WR6yEAYbaL0pPe6g-gf9So>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvjeeffeeiucetufdoteggodetrf
dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggv
pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpih
gvnhhtshculddquddttddmnecujfgurhepfffhvfevuffkfhggtggujgesghdtroertddt
jeenucfhrhhomheprfgvthgvrhcuvfhougguuceophgvthgvsehpvghtvghrthhouggurd
horhhgqeenucggtffrrghtthgvrhhnpeehteffgedviefhudetffetteevhfffhfdvheef
feevgeektdduudekkedugffhueenucffohhmrghinheprghnthhoihhnvghprdgtohhmpd
hpvghtvghrthhouggurdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm
pehmrghilhhfrhhomhepphgvthgvsehpvghtvghrthhouggurdhorhhgpdhnsggprhgtph
htthhopedvpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopegsihhttghoihhnuggv
vhesghhoohhglhgvghhrohhuphhsrdgtohhmpdhrtghpthhtohepuggrrhhoshhiohhrse
hprhhothhonhhmrghilhdrtghomh
X-ME-Proxy: <xmx:EyUVaKwk_hosSYIE1It1QVXfWPd78vd04mgsF8OOI9oE56y9XHaNTw>
<xmx:FCUVaJTp-wXMdaHE7HNhRoGt81fX_fcLJ7oLl2-iGQ6wLfSAIWLWzQ>
<xmx:FCUVaFYIdA0KrY8SRsumDn2opdyZzgViPjxteAH3l7L6VT6nD42OwQ>
<xmx:FCUVaCRiyq_gxCE1G05ct88xtMa1LjUN7ukle6ItbJ0Vn4zNpjLiug>
<xmx:FCUVaANnkeVbYtdHJqRYzkCxTgKzATLqk825A1z_hiZq6cu9wqzhmIee>
Feedback-ID: i525146e8:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri,
2 May 2025 16:03:31 -0400 (EDT)
Received: by localhost (Postfix, from userid 1000)
id 0EDB79FBD9; Fri, 2 May 2025 20:03:28 +0000 (UTC)
Date: Fri, 2 May 2025 20:03:28 +0000
From: Peter Todd <pete@petertodd.org>
To: Antoine Poinsot <darosior@protonmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Removing OP_Return restrictions: Devil's Advocate Position
Message-ID: <aBUlEOBqqrOIGHWC@petertodd.org>
References: <rhfyCHr4RfaEalbfGejVdolYCVWIyf84PT2062DQbs5-eU8BPYty5sGyvI3hKeRZQtVC7rn_ugjUWFnWCymz9e9Chbn7FjWJePllFhZRKYk=@protonmail.com>
<IpyzvdqFhM_40OKYdilNrHU9u_cIx7BKlYKBUgTGPW6idPAItRiza5tq8B1jEs141ypieLGkR2UMRIxg0qdxBMl6DQ3UKaQsID0gBjWLXtY=@protonmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature"; boundary="c3ES558w6cJYFS6M"
Content-Disposition: inline
In-Reply-To: <IpyzvdqFhM_40OKYdilNrHU9u_cIx7BKlYKBUgTGPW6idPAItRiza5tq8B1jEs141ypieLGkR2UMRIxg0qdxBMl6DQ3UKaQsID0gBjWLXtY=@protonmail.com>
X-Original-Sender: pete@petertodd.org
X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass
header.i=@messagingengine.com header.s=fm3 header.b=vGWjc7od; spf=pass
(google.com: domain of pete@petertodd.org designates 202.12.124.145 as
permitted sender) smtp.mailfrom=pete@petertodd.org
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.8 (/)
--c3ES558w6cJYFS6M
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, May 01, 2025 at 10:40:19PM +0000, 'Antoine Poinsot' via Bitcoin Dev=
elopment Mailing List wrote:
> As i have repeatedly asked people to take conceptual discussions to the m=
ailing list, i am circling back to this thread to answer objections. I have=
also written my point of view and reasons for proposing this change in a b=
log post which goes into more details: https://antoinep.com/posts/relay_pol=
icy_drama.
I agree with the linked write-up: the quality of debate has been
atrocious. We've had a bunch of people who should know better, making
points that don't make technical sense, and a bunch of passerby's
repeating that nonsense (as well as even more nonsensical arguments).
With that in mind, I thought it'd be worthwhile to Devil's Advocate the
change, and go through some technically valid arguments against it:
# _Uninterrupted_ Illicit Data
Credit where credit is due, this was the only reasonable argument
against that was actually brought up on GitHub. In short, OP_Return,
unlike other standard ways of embedding data in Bitcoin transactions,
allows for long uninterrupted, arbitrary, messages to be embedded
verbatim.
The claimed risk is that this data could then end up peoples' hard
drives, complicating forensics analysis in the future and potentially
falsely incriminating people. (if you can encode your illicit data such
that the right bytes happen to match Bitcoin opcodes, you can already
embed it verbatim, uninterrupted, as seen by how inscriptions embed data
in witnesses; Martin Habov=C5=A1tiak already brought this up on this very
list).
We already have this issue with dumb virus detection software. Which is
why a few years ago code was added to XOR "encrypt" the block*.dat files
by default (chainstate is also XOR "encrypted").
The only remaining argument here is if we should go to the trouble of
adding code to Bitcoin Core to convert existing block*.dat files to the
XOR scheme, without re-downloading.
# Setting Policy Expectations For a Consensus Change
While it is clearly infeasible to prevent people from publishing data
with Bitcoin's existing consensus rules, it _is_ hypothetically possible
to make data publication somewhat more expensive with consensus changes.
Gregory Maxwell outlined how to do so on this mailing list years ago
(I'm not going to dig up the reference). Basically his approach works as
follows:
1) Limit all data in the chain to be either hash digests, signatures,
pubkeys, or trivial values like true and false.
2) Require transactions to *prove* that every item of data is what it
claims to be with, e.g. a hash digest pre-image, a valid signature (for
a pubkey), or the fact that a signature was valid. I may be wrong. But I
*believe* that with protocol changes it is possible for Lightning and
Ark to work in this model.
3) Phase out non-compliant transactions, e.g. applying a block-weight
multiplier that increases over time to eventually make them entirely
unaffordable.
Note that such a scheme *will* require massive ecosystem wide change:
even existing address standards will need to be modified (and made
larger) to prove that you are paying to a real address rather than
something encoding data.
Also note that *even this* consensus change *still* won't entirely
prevent people from publishing data! No-matter what we do you can always
grind pubkeys and hashes to set the first 4-6 bytes of them to the value
that you want. Thus if you're pushing 32 bytes of data, encoded as 33
bytes including the serialized length, and get 5 bytes per push, you
have an overhead of about 6.6x. Existing data encoders have been happy
to pay even more money than that in terms of increased fees during fee
spikes; the difference in cost between witness space and txout space is
already 4x, and some are happy to publish data that way anyway.
A tricky thing here is upgrade paths. If we make these rules apply to
all transactions, with any version number, we've radically limited our
ability to upgrade the Bitcoin protocol in the future. We probably can
make this *not* apply to transactions and taproot script types with
unknown version numbers. However we'd have to do something like ensure
it only applies to insecure transactions without signatures. And even
then some miners will bypass this by mining that stuff anyway for a fee.
That's pretty ugly. _Maybe_ we can make a mechanism where miners signal
support to allow new version numbers first, prior to an upgrade. But
that also adds plenty of complexity.
That said, if the Luke's of the world want to make a reasonable
technical argument, come up with a reasonable scheme like the above and
show that it has a chance of actually getting implemented.
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--=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/=
aBUlEOBqqrOIGHWC%40petertodd.org.
--c3ES558w6cJYFS6M
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmgVJQ0ACgkQLly11TVR
Lzey5A//fhANNPypRTASii1KN6dsmGkgX8epI80EneLEmlCwa2YXG6dh7wyp7Bgb
J+mTdOil0V8v35E2Pr4U0TkppUd4HBY5HEN3rmahg++YUGLWZu11FacmIBjqMwdi
BAoIiA8FCO23FIiruW8MCoXge3zLTkZtq60B+hSBltym/bwyJmWdP+f0bJ65w0jG
nYwxR3cYMrFKEK6iAfLf2Vf0CQbfxXIBk3EHTR37UXhpZK4TrOQFns9ElAFf8Ara
1oI9jrHsvVHVM+BI+OHg8ltrKAqfTHJeQwlWpF0fJIqmW/CFQmBa2G19zfyk0zAb
GgNhR7NjLva83ubMpUvg1F9ya0MGz2I20a6lkKhqBXxcW678tEV3Kf5B2njECmm/
fTIYmGBncrdtUg8OZPvlGTBcWk6FLFIM8pzev1OKUQxeSnconEYAIZTmC3QTTo5I
UaPETzJFm12liq3weOC1wmWBF0cDQkhL+jPAkuvYNZ/G72Qa1puyRaG3CnptCmMF
W9IzJ9RWgTlUOLBiZJ8lDXr/JzVuWkiXFa8U/YDAM7N01cfyi33vBKWopwTkWHiw
POFhgHFAyRjFcUJ6YrhlfijZRmG6KHunsnDbj4OuOiit6BXv219jo4cE2fEDTBu6
i6bbFW/nDTCDb3fKATJY0DzUGg/4kaiR9zJFMAN+25UZ1CSZ2/w=
=eKjy
-----END PGP SIGNATURE-----
--c3ES558w6cJYFS6M--
|
