public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Peter D. Gray" <peter@coinkite.com>
To: Eric Voskuil <eric@voskuil.org>
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
Date: Fri, 6 Feb 2015 14:06:07 -0500	[thread overview]
Message-ID: <20150206190607.GB40004@coinkite.com> (raw)
In-Reply-To: <CANEZrP23tfTzCfk2eXUOPX=CFCg6GKn4HO5Rb3ZxeOJQtEQCHw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]

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


[-- Attachment #2: Type: application/pgp-signature, Size: 514 bytes --]

      reply	other threads:[~2015-02-06 19:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 19:58 [Bitcoin-development] Two Proposed BIPs - Bluetooth Communication and bitcoin: URI Scheme Improvements Andy Schroder
2014-10-20 12:50 ` Mike Hearn
2014-10-20 15:12   ` Andy Schroder
2014-10-20 16:29     ` Mike Hearn
2014-10-22 16:01   ` Justus Ranvier
2015-02-05 23:38 ` Andy Schroder
2015-02-06  0:36   ` Eric Voskuil
2015-02-06  1:40     ` Andy Schroder
2015-02-06  2:14       ` Eric Voskuil
2015-02-06  8:53       ` Andreas Schildbach
2015-02-06 13:57       ` Mike Hearn
2015-02-06  8:40     ` Andreas Schildbach
2015-02-06  9:00       ` Eric Voskuil
2015-02-06 13:54         ` Mike Hearn
2015-02-06 19:06           ` Peter D. Gray [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150206190607.GB40004@coinkite.com \
    --to=peter@coinkite.com \
    --cc=andreas@schildbach.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=eric@voskuil.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox