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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <peter@coinkite.com>) id 1YJoEJ-0003pA-R6
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Feb 2015 19:06:15 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of coinkite.com
designates 108.166.43.68 as permitted sender)
client-ip=108.166.43.68; envelope-from=peter@coinkite.com;
helo=smtp68.ord1c.emailsrvr.com;
Received: from smtp68.ord1c.emailsrvr.com ([108.166.43.68])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1YJoEI-0000Jw-S8
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Feb 2015 19:06:15 +0000
Received: from smtp1.relay.ord1c.emailsrvr.com (localhost.localdomain
[127.0.0.1])
by smtp1.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id
8EC043800F9; Fri, 6 Feb 2015 14:06:09 -0500 (EST)
Received: by smtp1.relay.ord1c.emailsrvr.com (Authenticated sender:
peter-AT-coinkite.com) with ESMTPSA id 4694538010C;
Fri, 6 Feb 2015 14:06:09 -0500 (EST)
X-Sender-Id: peter@coinkite.com
Received: from coinkite.com ([UNAVAILABLE]. [216.223.137.93])
(using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384)
by 0.0.0.0:465 (trex/5.4.2); Fri, 06 Feb 2015 19:06:09 GMT
Date: Fri, 6 Feb 2015 14:06:07 -0500
From: "Peter D. Gray" <peter@coinkite.com>
To: Eric Voskuil <eric@voskuil.org>
Message-ID: <20150206190607.GB40004@coinkite.com>
References: <544174F8.1050208@AndySchroder.com>
<54D3FEE9.70502@AndySchroder.com> <54D40C7D.8090804@voskuil.org>
<mb1um3$ee3$1@ger.gmane.org> <54D482B8.9070108@voskuil.org>
<CANEZrP23tfTzCfk2eXUOPX=CFCg6GKn4HO5Rb3ZxeOJQtEQCHw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature"; boundary="Ruyc9IU5x/hZJuxv"
Content-Disposition: inline
In-Reply-To: <CANEZrP23tfTzCfk2eXUOPX=CFCg6GKn4HO5Rb3ZxeOJQtEQCHw@mail.gmail.com>
Organization: Coinkite Cryptobank (www.coinkite.com)
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Score: -1.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 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [108.166.43.68 listed in list.dnswl.org]
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1YJoEI-0000Jw-S8
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
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
Reply-To: Peter Gray <peter@coinkite.com>
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 19:06:15 -0000
--Ruyc9IU5x/hZJuxv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
I think the Bitcoin community needs a good person-to-person payment
protocol for BLE simply because Bluetooth LE is effectively
peer-to-peer. Unlike NFC or conventional Bluetooth, a $5 micro can
be either the master or slave and talk directly to other $5 micros
nearby.
[ASIDE... BLE is also the first wireless tech that Apple has allowed us free
access to. They have claimed all NFC/RFID connections for their own
"Pay" junk, and Bluetooth accessories are all locked down into their
"make for iphone" program which literally requires a letter from
your lawyer to enter. Of course Apple is just one vendor.]
Surely, as a community, we can make a rock-solid P2P protocol that
is resistant to spoofing and vandalism. I'm a big fan of putting
crypto to good use, and doing a slightly more complex protocol
involving EC signing of nonces sounds great.
My only change to the RedPhone based "commit protocol" proposed
previously, is I'd like the confirmation code to be a 6-digit decimal
number rather than words. Wordlists are good for Red phone's audio
application, but it's a lot easier to display a 6-digit code on
vending machines, small mobile screens, and printed receipts.
Just my two cents.
---
Peter D. Gray || Founder, Coinkite || Twitter: @dochex || GPG: A3A31BAD 5A2A5B10
--Ruyc9IU5x/hZJuxv
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - https://gpgtools.org
iQEcBAEBCgAGBQJU1RCfAAoJEKOjG61aKlsQPMkH/iOlCDyuPX7xHErJuG0RePgK
caiBQvi/Vv+SD7GeWHPbP/K08zQGr0cQxbW3Kyksc2HuLjEVX5X5qkDmf3gHi1d0
GJTLPz72vjs/VROh67hPX3S2xpoXzJ+8M1MVqvw4hp+CImfJgnjLiIE7t065NP+s
TcGS9+7aK41st0fPzbq9/8xr0rfldGhLMrohAHyhzcMiFFmlmi7YB6XYSRC7eaJb
n3wFSkFk9fRP3diwCDh3wBpzEMhj4fVA/9HpvhetmqtGYauXY7cVeu3WDhmOO4S6
q/yNNL6LlA19egGjXTubjRiCZ6vtfdrFxnQ35l8lbtDLp+LqdYpJv4fWTZteweU=
=N5a9
-----END PGP SIGNATURE-----
--Ruyc9IU5x/hZJuxv--
|
