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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YJjPG-0002YR-5c
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Feb 2015 13:57:14 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.42 as permitted sender)
client-ip=74.125.82.42; envelope-from=mh.in.england@gmail.com;
helo=mail-wg0-f42.google.com;
Received: from mail-wg0-f42.google.com ([74.125.82.42])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YJjPE-0000l6-9y
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Feb 2015 13:57:14 +0000
Received: by mail-wg0-f42.google.com with SMTP id x13so13747845wgg.1
for <bitcoin-development@lists.sourceforge.net>;
Fri, 06 Feb 2015 05:57:06 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.61.145 with SMTP id p17mr7671986wjr.35.1423231026224;
Fri, 06 Feb 2015 05:57:06 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Fri, 6 Feb 2015 05:57:06 -0800 (PST)
In-Reply-To: <54D41B90.2010208@AndySchroder.com>
References: <544174F8.1050208@AndySchroder.com>
<54D3FEE9.70502@AndySchroder.com> <54D40C7D.8090804@voskuil.org>
<54D41B90.2010208@AndySchroder.com>
Date: Fri, 6 Feb 2015 14:57:06 +0100
X-Google-Sender-Auth: OVlX_wPPB9aVrEaPQbmO0nw8Tuw
Message-ID: <CANEZrP1jch5ivvTLqEV-y4JKa-p6RJXCQb9bM+vtJJ3dPuONMQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andy Schroder <info@andyschroder.com>
Content-Type: multipart/alternative; boundary=047d7bacc0f2c066c9050e6bcbe8
X-Spam-Score: -0.5 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YJjPE-0000l6-9y
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Two Proposed BIPs - Bluetooth
Communication and bitcoin: URI Scheme Improvements
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 13:57:14 -0000
--047d7bacc0f2c066c9050e6bcbe8
Content-Type: text/plain; charset=UTF-8
>
> verification using breadwallet on apple is much faster (<1s) than HTTPS
> payment request on bitcoin wallet on android (apparently apple has a
> significantly more optimized signature verification algorithm).
Probably on Android it's being verified in Java instead of C++. Some
Android APIs are backed by OpenSSL but I don't know off hand if the way
we're verifying cert chains on Android is. It's eminently fixable, at any
rate.
X.509 cert chains are pretty bloated, but even so, shouldn't take several
seconds to transfer even over Bluetooth.
Bottom line is that there may be ~1s time transferring the data with this
> current bluetooth connection. Not sure how slow it will be with the BLE
> connection.
>
BLE isn't really connection oriented, as far as I know.
--047d7bacc0f2c066c9050e6bcbe8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">verification using breadwallet on apple is much =
faster (<1s) than HTTPS payment request on bitcoin wallet on android (ap=
parently apple has a significantly more optimized signature verification al=
gorithm). </blockquote><div><br></div><div>Probably on Android it's bei=
ng verified in Java instead of C++. Some Android APIs are backed by OpenSSL=
but I don't know off hand if the way we're verifying cert chains o=
n Android is. It's eminently fixable, at any rate.</div><div><br></div>=
<div>X.509 cert chains are pretty bloated, but even so, shouldn't take =
several seconds to transfer even over Bluetooth.</div><div><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
solid;padding-left:1ex">Bottom line is that there may be ~1s time transfer=
ring the data with this current bluetooth connection. Not sure how slow it =
will be with the BLE connection.<br></blockquote><div><br></div><div>BLE is=
n't really connection oriented, as far as I know.</div></div></div></di=
v>
--047d7bacc0f2c066c9050e6bcbe8--
|
