From: Mike Hearn <mike@plan99•net>
To: Andy Schroder <info@andyschroder•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Two Proposed BIPs - Bluetooth Communication and bitcoin: URI Scheme Improvements
Date: Fri, 6 Feb 2015 14:57:06 +0100 [thread overview]
Message-ID: <CANEZrP1jch5ivvTLqEV-y4JKa-p6RJXCQb9bM+vtJJ3dPuONMQ@mail.gmail.com> (raw)
In-Reply-To: <54D41B90.2010208@AndySchroder.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
>
> 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.
[-- Attachment #2: Type: text/html, Size: 1190 bytes --]
next prev parent reply other threads:[~2015-02-06 13:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 19:58 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 [this message]
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
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=CANEZrP1jch5ivvTLqEV-y4JKa-p6RJXCQb9bM+vtJJ3dPuONMQ@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=info@andyschroder$(echo .)com \
/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