From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Two Proposed BIPs - Bluetooth Communication and bitcoin: URI Scheme Improvements
Date: Fri, 06 Feb 2015 09:40:35 +0100 [thread overview]
Message-ID: <mb1um3$ee3$1@ger.gmane.org> (raw)
In-Reply-To: <54D40C7D.8090804@voskuil.org>
On 02/06/2015 01:36 AM, Eric Voskuil wrote:
> The main advantage of BLE over BT is that it uses much less power, with
> a trade-off in lower bandwidth (100 kbps vs. 2 mbps). The BLE range can
> be even greater and connection latency lower than BT. For payment
> purposes the lower bandwidth isn't much of a hit.
I'm all for extending the BT:<mac> scheme to Bluetooth LE. If you have
ideas how this can be done please let us know. I haven't had a chance to
play around with LE because none of my devices support it.
I suspect the way how Bluetooth LE transfers files (like payment
requests) is opening a plain old Bluetooth socket. If this is true, I'm
afraid Bluetooth LE would not add anything for sending the BIP70
messages back and forth. Note signed payment requests can easily be 4 kB
in size, so speed *does* matter.
next prev parent reply other threads:[~2015-02-06 8:40 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 [this message]
2015-02-06 9:00 ` Eric Voskuil
2015-02-06 13:54 ` Mike Hearn
2015-02-06 19:06 ` Peter D. Gray
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='mb1um3$ee3$1@ger.gmane.org' \
--to=andreas@schildbach.de \
--cc=bitcoin-development@lists.sourceforge.net \
/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