From: Mike Hearn <mike@plan99•net>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Bluetooth on Android
Date: Fri, 13 Sep 2013 18:21:19 +0200 [thread overview]
Message-ID: <CANEZrP1xWjxcjNYAXKUvsCLgZ8z5CiLkox=aRPDHCJ+Bvn+mHA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
Just a heads up,
Over a year ago Andreas and I prototyped bluetooth tx submission on Android
at a hackfest in Berlin, and it will be with support on-by-default for the
sending side soon. That means, anyone can enable the feature in the
settings page and start receiving payments via Bluetooth as long as both
sides use the Bitcoin Wallet app.
The protocol used is a set of proprietary things. Once the payment protocol
is implemented in bitcoinj, I guess we will recast the bluetooth support to
use that and then submit a BIP for it, but right now it wouldn't make sense
to do so as we know the current protocol has a limited lifespan.
Send via bluetooth resolves one of the most common UX fails we see here in
Europe: people travel to conferences or events and then want to spend their
Bitcoins whilst they're abroad, but they can't reasonably do so because
data roaming is so expensive. By allowing the receiver i.e. merchant to
receive the tx via Bluetooth, this problem is avoided - often the receiver
is local and will be able to broadcast the transaction on your behalf.
Briefly, we use an unauthenticated RFCOMM socket with the adapter MAC
address in a new btcmac parameter in the bitcoin: URI qrcode. No pairing is
required. MITM attacks on the connection are possible, but all that's done
with it is writing raw tx bytes out over the connection so MITM is limited
to DoS.
[-- Attachment #2: Type: text/html, Size: 1533 bytes --]
reply other threads:[~2013-09-13 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CANEZrP1xWjxcjNYAXKUvsCLgZ8z5CiLkox=aRPDHCJ+Bvn+mHA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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