summaryrefslogtreecommitdiff
path: root/b2/32246324e03178e481138494f40fdd6e4c1b44
blob: cfa1c68262ddd73cdf476b76c6064f4e24da8fa8 (plain)
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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <paul@airbitz.co>) id 1YJYMr-0002IU-Ah
	for bitcoin-development@lists.sourceforge.net;
	Fri, 06 Feb 2015 02:10:01 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of airbitz.co
	designates 209.85.220.46 as permitted sender)
	client-ip=209.85.220.46; envelope-from=paul@airbitz.co;
	helo=mail-pa0-f46.google.com; 
Received: from mail-pa0-f46.google.com ([209.85.220.46])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YJYMo-0006OU-SZ
	for bitcoin-development@lists.sourceforge.net;
	Fri, 06 Feb 2015 02:10:01 +0000
Received: by mail-pa0-f46.google.com with SMTP id lj1so13897121pab.5
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 05 Feb 2015 18:09:53 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:content-type:mime-version:subject:from
	:in-reply-to:date:cc:content-transfer-encoding:message-id:references
	:to; bh=dyDKhDhLeKrfX1Jl+KfJgNmbzjfE+OuDoDWJtm535r8=;
	b=gPDfHRbr4599PsVrCfpL07reem/JI1JjnPFcDByn02QN0qx40ZZIV+E7iDr+D2Fw/A
	vP6K+qlrNDBK8ZaXvYWiCU9OJ6z6boPiU/DZILgoll2uKmuqOfuy/V/UsvGtuVsngsy5
	0bsup87z6vyzXgJVPuVk6BtX1G1xGtg5SJ+08iHQNjpW+0JSazKI01gyZpRy2HhDV1eE
	hZpos6FMRt/XsxBIMwEqZlwxEatkHnhGvj711HjceI9iF2S3Qnj8tuxzTuoFHX/VI6Qt
	P6CCrinVO3G2N7d4Yzy1VRfW4hheoUaTqAuq4N36kAhxPNzP+fb4046t+9gfsZuf5gYa
	wG8g==
X-Gm-Message-State: ALoCoQnBXFXSWIbkr1/N1gyG/kUx9swFcypcOIh86kGVnSU7DCY9Wy50rvv2jKW/309AxcasrRAK
X-Received: by 10.66.186.110 with SMTP id fj14mr1843551pac.98.1423188593032;
	Thu, 05 Feb 2015 18:09:53 -0800 (PST)
Received: from [10.204.163.123] (mobile-166-171-251-007.mycingular.net.
	[166.171.251.7])
	by mx.google.com with ESMTPSA id b6sm6278973pdk.94.2015.02.05.18.09.50
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 05 Feb 2015 18:09:51 -0800 (PST)
Content-Type: multipart/alternative;
	boundary=Apple-Mail-038E74F9-897D-4D6F-A5B8-F02F6010E1CF
Mime-Version: 1.0 (1.0)
From: Paul Puey <paul@airbitz.co>
X-Mailer: iPhone Mail (12B411)
In-Reply-To: <54D41353.5050205@voskuil.org>
Date: Thu, 5 Feb 2015 18:09:48 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <D0D537F5-201E-43D4-8BE7-ED34902EEF55@airbitz.co>
References: <CABdy8DKS4arkkCLGC=66SUJm5Ugib1EWP7B6MkQRX1k-yd3WBw@mail.gmail.com>
	<CANEZrP3v=ySS4gragaWuBMWi_swocRRRq_kw2edo6+9kifgrFQ@mail.gmail.com>
	<54D3D636.1030308@voskuil.org>
	<CANEZrP3ekWQWeV=Yw_E=n0grORBLHaXLUh3w0EFQdz=HsjWvZw@mail.gmail.com>
	<279489A5-1E46-48A2-8F58-1A25821D4D96@gmail.com>
	<CANEZrP3VAWajxE=mNxb6sLSQbhaQHD=2TgRKvYrEax2PAzCi2A@mail.gmail.com>
	<6AEDF3C4-DEE0-4E31-83D0-4FD92B125452@voskuil.org>
	<CABdy8DLRGyy5dvmVb_B3vao7Qwz-zdAC3-+2nJkg9rSsU6FLbw@mail.gmail.com>
	<C28CD881-DAB8-4EDB-B239-7D45A825EAF0@voskuil.org>
	<54D3FB4A.9010105@voskuil.org>
	<CALkkCJammCvVd6_1SYRvnxsMVj_x1AvS1VsSa6_76d0NWMDs=Q@mail.gmail.com>
	<54D400F0.9090406@voskuil.org>
	<CEB250A3-9014-4AF3-AEB7-E78BE19BF2F5@airbitz.co>
	<54D41353.5050205@voskuil.org>
To: Eric Voskuil <eric@voskuil.org>
X-Spam-Score: -0.3 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.3 HTML_FONT_FACE_BAD     BODY: HTML font face is not a word
	0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	0.0 T_REMOTE_IMAGE         Message contains an external image
X-Headers-End: 1YJYMo-0006OU-SZ
Cc: William Swanson <william@airbitz.co>,
	Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal for P2P Wireless (Bluetooth LE)
	transfer of Payment URI
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2015 02:10:01 -0000


--Apple-Mail-038E74F9-897D-4D6F-A5B8-F02F6010E1CF
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Thanks for all the feedback Eric. You know we value all that you have to say=
. That's what this forum is for. We're looking for great ideas to harden thi=
s protocol and we're not closed to better ideas and we'll improve it as sugg=
estions come up.



  =20
Paul Puey CEO / Co-Founder, Airbitz Inc
619.850.8624 | http://airbitz.co | San Diego
    =20



On Feb 5, 2015, at 5:05 PM, Eric Voskuil <eric@voskuil.org> wrote:

> On 02/05/2015 04:49 PM, Paul Puey wrote:
> The trust can be considered bootstrapped by visual verification of the
> address prefix.

Another (unspendable) address can trivially match the prefix. Imagine
someone walking around in a mall with a phone in the pocket with a
malicious app, just disrupting business by causing money to be burned.
Manual verification doesn't fix this attack.

> If we are really concerned about someone jamming a Bluetooth signal
> in a coffeeshop then the UI can encourage verification of the prefix.

I don't think it would be great to constrain a standard implementation
to low cost purchases or the need for manual verification, but again
manual prefix verification isn't actually a solution.

> Much like how regular Bluetooth requires 'pairing' via entering a 4-6
> digit code.

An appeal to the security of BT bootstrapping isn't exactly flattering.

You know I love Airbitz, and I know you guys are extremely privacy
conscious. I personally would have no problem using this feature under
certain circumstances. My question is only whether it would be wise to
standardize on the proposal as-is.

e

> On Feb 5, 2015, at 3:46 PM, Eric Voskuil <eric@voskuil.org
> <mailto:eric@voskuil.org>> wrote:
>=20
> On 02/05/2015 03:36 PM, M=E2=92=B6rtin H=E2=92=B6bo=E2=93=8B=C5=A1tiak wro=
te:
>>> A BIP-70 signed payment request in the initial broadcast can resolve the=

>>> integrity issues, but because of the public nature of the broadcast
>>> coupled with strong public identity, the privacy compromise is much
>>> worse. Now transactions are cryptographically tainted.
>>>=20
>>> This is also the problem with BIP-70 over the web. TLS and other
>>> security precautions aside, an interloper on the communication, desktop,=

>>> datacenter, etc., can capture payment requests and strongly correlate
>>> transactions to identities in an automated manner. The payment request
>>> must be kept private between the parties, and that's hard to do.
>>=20
>> What about using encryption with forward secrecy? Merchant would
>> generate signed request containing public ECDH part, buyer would send
>> back transaction encrypted with ECDH and his public ECDH part. If
>> receiving address/amount is meant to be private, use commit protocol
>> (see ZRTP/RedPhone) and short authentication phrase (which is hard to
>> spoof thanks to commit protocol - see RedPhone)?
>=20
> Hi Martin,
>=20
> The problem is that you need to verify the ownership of the public key.
> A MITM can substitute the key. If you don't have verifiable identity
> associated with the public key (PKI/WoT), you need a shared secret (such
> as a secret phrase). But the problem is then establishing that secret
> over a public channel.
>=20
> You can bootstrap a private session over the untrusted network using a
> trusted public key (PKI/WoT). But the presumption is that you are
> already doing this over the web (using TLS). That process is subject to
> attack at the CA. WoT is not subject to a CA attack, because it's
> decentralized. But it's also not sufficiently deployed for some scenarios.=

>=20
> e


--Apple-Mail-038E74F9-897D-4D6F-A5B8-F02F6010E1CF
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Thanks for all the feedback Eric. You k=
now we value all that you have to say. That's what this forum is for. We're l=
ooking for great ideas to harden this protocol and we're not closed to bette=
r ideas and we'll improve it as suggestions come up.<br><br><br><span style=3D=
"background-color: rgba(255, 255, 255, 0);"><br></span><table border=3D"0" s=
tyle=3D"-webkit-text-size-adjust: auto; font-size: medium; font-family: Helv=
etica, Arial, sans-serif;"><tbody><tr valign=3D"top"><td style=3D"width: aut=
o; vertical-align: top;"><font face=3D".HelveticaNeueInterface-M3"><span sty=
le=3D"font-size: 17px; -webkit-text-size-adjust: none; background-color: rgb=
a(255, 255, 255, 0);"><img src=3D"https://s3.amazonaws.com/webapp.wisestamp.=
com/v7Zg7GfIQ9mF5xlHZrZA_airbitzlogo.png" alt=3D"logo" style=3D"border: none=
; border-top-left-radius: 4px; border-top-right-radius: 4px; border-bottom-r=
ight-radius: 4px; border-bottom-left-radius: 4px;">&nbsp;&nbsp;&nbsp;<br></s=
pan></font></td><td><font face=3D".HelveticaNeueInterface-M3"><span style=3D=
"font-size: 17px; -webkit-text-size-adjust: none; background-color: rgba(255=
, 255, 255, 0);"><b>Paul Puey</b>&nbsp;CEO / Co-Founder, Airbitz Inc<br></sp=
an></font><div style=3D"margin-top: 0px; margin-bottom: 0px;"><font face=3D"=
.HelveticaNeueInterface-M3"><span style=3D"font-size: 17px; -webkit-text-siz=
e-adjust: none; background-color: rgba(255, 255, 255, 0);"><a style=3D"outli=
ne: none;"></a><a href=3D"tel:619.850.8624" x-apple-data-detectors=3D"true" x=
-apple-data-detectors-type=3D"telephone" x-apple-data-detectors-result=3D"0"=
>6</a><a href=3D"tel:619.850.8624" x-apple-data-detectors=3D"true" x-apple-d=
ata-detectors-type=3D"telephone" x-apple-data-detectors-result=3D"0">19.850.=
8624</a>&nbsp;|&nbsp;<a href=3D"http://airbitz.co/" target=3D"_blank" style=3D=
"outline: none;">http://airbitz.co</a>&nbsp;|&nbsp;San Diego</span></font></=
div><div style=3D"margin-top: 5px;"><font color=3D"#000000" face=3D".Helveti=
caNeueInterface-M3"><span style=3D"font-size: 17px; -webkit-text-size-adjust=
: none; background-color: rgba(255, 255, 255, 0);"><a href=3D"http://faceboo=
k.com/airbitz" target=3D"_blank" style=3D"outline: none;"><img src=3D"http:/=
/images.wisestamp.com/facebook.png" width=3D"16" style=3D"border: none;"></a=
>&nbsp;<a href=3D"http://twitter.com/airbitz" target=3D"_blank" style=3D"out=
line: none;"><img src=3D"http://images.wisestamp.com/twitter.png" width=3D"1=
6" alt=3D"" style=3D"border: none;"></a>&nbsp;<a href=3D"https://plus.google=
.com/118173667510609425617" target=3D"_blank" style=3D"outline: none;"><img s=
rc=3D"http://images.wisestamp.com/googleplus.png" width=3D"16" style=3D"bord=
er: none;"></a>&nbsp;<a href=3D"https://go.airbitz.co/comments/feed/" target=
=3D"_blank" style=3D"outline: none;"><img src=3D"http://images.wisestamp.com=
/blogRSS.png" width=3D"16" style=3D"border: none;"></a>&nbsp;<a href=3D"http=
://linkedin.com/in/paulpuey" target=3D"_blank" style=3D"outline: none;"><img=
 src=3D"http://images.wisestamp.com/linkedin.png" width=3D"16" alt=3D"" styl=
e=3D"border: none;"></a>&nbsp;<a href=3D"https://angel.co/paul-puey" target=3D=
"_blank" style=3D"outline: none;"><img src=3D"http://images.wisestamp.com/an=
gelList.png" width=3D"16" alt=3D"" style=3D"border: none;"></a></span></font=
></div></td></tr></tbody></table><table border=3D"0" style=3D"-webkit-text-s=
ize-adjust: auto; font-size: medium; font-family: Helvetica, Arial, sans-ser=
if;"><tbody><tr valign=3D"top"><td style=3D"width: auto; vertical-align: top=
;"><br></td><td><br></td></tr></tbody></table></div><div><br>On Feb 5, 2015,=
 at 5:05 PM, Eric Voskuil &lt;<a href=3D"mailto:eric@voskuil.org">eric@vosku=
il.org</a>&gt; wrote:<br><br></div><div><span>On 02/05/2015 04:49 PM, Paul P=
uey wrote:</span><br><blockquote type=3D"cite"><span>The trust can be consid=
ered bootstrapped by visual verification of the</span><br></blockquote><bloc=
kquote type=3D"cite"><span>address prefix.</span><br></blockquote><span></sp=
an><br><span>Another (unspendable) address can trivially match the prefix. I=
magine</span><br><span>someone walking around in a mall with a phone in the p=
ocket with a</span><br><span>malicious app, just disrupting business by caus=
ing money to be burned.</span><br><span>Manual verification doesn't fix this=
 attack.</span><br><span></span><br><blockquote type=3D"cite"><span>If we ar=
e really concerned about someone jamming a Bluetooth signal</span><br></bloc=
kquote><blockquote type=3D"cite"><span>in a coffeeshop then the UI can encou=
rage verification of the prefix.</span><br></blockquote><span></span><br><sp=
an>I don't think it would be great to constrain a standard implementation</s=
pan><br><span>to low cost purchases or the need for manual verification, but=
 again</span><br><span>manual prefix verification isn't actually a solution.=
</span><br><span></span><br><blockquote type=3D"cite"><span>Much like how re=
gular Bluetooth requires 'pairing' via entering a 4-6</span><br></blockquote=
><blockquote type=3D"cite"><span>digit code.</span><br></blockquote><span></=
span><br><span>An appeal to the security of BT bootstrapping isn't exactly f=
lattering.</span><br><span></span><br><span>You know I love Airbitz, and I k=
now you guys are extremely privacy</span><br><span>conscious. I personally w=
ould have no problem using this feature under</span><br><span>certain circum=
stances. My question is only whether it would be wise to</span><br><span>sta=
ndardize on the proposal as-is.</span><br><span></span><br><span>e</span><br=
><span></span><br><blockquote type=3D"cite"><span>On Feb 5, 2015, at 3:46 PM=
, Eric Voskuil &lt;<a href=3D"mailto:eric@voskuil.org">eric@voskuil.org</a><=
/span><br></blockquote><blockquote type=3D"cite"><span>&lt;<a href=3D"mailto=
:eric@voskuil.org">mailto:eric@voskuil.org</a>&gt;&gt; wrote:</span><br></bl=
ockquote><blockquote type=3D"cite"><span></span><br></blockquote><blockquote=
 type=3D"cite"><span>On 02/05/2015 03:36 PM, M=E2=92=B6rtin H=E2=92=B6bo=E2=93=
=8B=C5=A1tiak wrote:</span><br></blockquote><blockquote type=3D"cite"><block=
quote type=3D"cite"><blockquote type=3D"cite"><span>A BIP-70 signed payment r=
equest in the initial broadcast can resolve the</span><br></blockquote></blo=
ckquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><bl=
ockquote type=3D"cite"><span>integrity issues, but because of the public nat=
ure of the broadcast</span><br></blockquote></blockquote></blockquote><block=
quote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><spa=
n>coupled with strong public identity, the privacy compromise is much</span>=
<br></blockquote></blockquote></blockquote><blockquote type=3D"cite"><blockq=
uote type=3D"cite"><blockquote type=3D"cite"><span>worse. Now transactions a=
re cryptographically tainted.</span><br></blockquote></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"c=
ite"><span></span><br></blockquote></blockquote></blockquote><blockquote typ=
e=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><span>This is=
 also the problem with BIP-70 over the web. TLS and other</span><br></blockq=
uote></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D=
"cite"><blockquote type=3D"cite"><span>security precautions aside, an interl=
oper on the communication, desktop,</span><br></blockquote></blockquote></bl=
ockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote typ=
e=3D"cite"><span>datacenter, etc., can capture payment requests and strongly=
 correlate</span><br></blockquote></blockquote></blockquote><blockquote type=
=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><span>transact=
ions to identities in an automated manner. The payment request</span><br></b=
lockquote></blockquote></blockquote><blockquote type=3D"cite"><blockquote ty=
pe=3D"cite"><blockquote type=3D"cite"><span>must be kept private between the=
 parties, and that's hard to do.</span><br></blockquote></blockquote></block=
quote><blockquote type=3D"cite"><blockquote type=3D"cite"><span></span><br><=
/blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"=
><span>What about using encryption with forward secrecy? Merchant would</spa=
n><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D=
"cite"><span>generate signed request containing public ECDH part, buyer woul=
d send</span><br></blockquote></blockquote><blockquote type=3D"cite"><blockq=
uote type=3D"cite"><span>back transaction encrypted with ECDH and his public=
 ECDH part. If</span><br></blockquote></blockquote><blockquote type=3D"cite"=
><blockquote type=3D"cite"><span>receiving address/amount is meant to be pri=
vate, use commit protocol</span><br></blockquote></blockquote><blockquote ty=
pe=3D"cite"><blockquote type=3D"cite"><span>(see ZRTP/RedPhone) and short au=
thentication phrase (which is hard to</span><br></blockquote></blockquote><b=
lockquote type=3D"cite"><blockquote type=3D"cite"><span>spoof thanks to comm=
it protocol - see RedPhone)?</span><br></blockquote></blockquote><blockquote=
 type=3D"cite"><span></span><br></blockquote><blockquote type=3D"cite"><span=
>Hi Martin,</span><br></blockquote><blockquote type=3D"cite"><span></span><b=
r></blockquote><blockquote type=3D"cite"><span>The problem is that you need t=
o verify the ownership of the public key.</span><br></blockquote><blockquote=
 type=3D"cite"><span>A MITM can substitute the key. If you don't have verifi=
able identity</span><br></blockquote><blockquote type=3D"cite"><span>associa=
ted with the public key (PKI/WoT), you need a shared secret (such</span><br>=
</blockquote><blockquote type=3D"cite"><span>as a secret phrase). But the pr=
oblem is then establishing that secret</span><br></blockquote><blockquote ty=
pe=3D"cite"><span>over a public channel.</span><br></blockquote><blockquote t=
ype=3D"cite"><span></span><br></blockquote><blockquote type=3D"cite"><span>Y=
ou can bootstrap a private session over the untrusted network using a</span>=
<br></blockquote><blockquote type=3D"cite"><span>trusted public key (PKI/WoT=
). But the presumption is that you are</span><br></blockquote><blockquote ty=
pe=3D"cite"><span>already doing this over the web (using TLS). That process i=
s subject to</span><br></blockquote><blockquote type=3D"cite"><span>attack a=
t the CA. WoT is not subject to a CA attack, because it's</span><br></blockq=
uote><blockquote type=3D"cite"><span>decentralized. But it's also not suffic=
iently deployed for some scenarios.</span><br></blockquote><blockquote type=3D=
"cite"><span></span><br></blockquote><blockquote type=3D"cite"><span>e</span=
><br></blockquote><blockquote type=3D"cite"><span></span><br></blockquote><s=
pan></span><br></div></body></html>=

--Apple-Mail-038E74F9-897D-4D6F-A5B8-F02F6010E1CF--