From: Natanael <natanael.l@gmail•com>
To: "MⒶrtin HⒶboⓋštiak" <martin.habovstiak@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Standardizing automatic pre-negotiation of transaction terms with BIP70? (Emulating Amazon one-click purchase at all merchants)
Date: Tue, 10 Feb 2015 12:58:42 +0100 [thread overview]
Message-ID: <CAAt2M182P9BpJ=H1rSGF45qNWii12n1YpKOxnULcPW1L4XLZ+w@mail.gmail.com> (raw)
In-Reply-To: <CALkkCJYDUvtuWGQ5Pq85krGQp=bRYQ1sazg-3T0B8ipr8SGuYA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2212 bytes --]
> In what universe is that simple? Your solution: browser extension +
> wallet + comminucation API + all the wallets need to implement it
> Our solution: just browser extension.
Browser extension would only be required until browsers add native support
for detecting the tag and prompting a wallet client. This probably won't
happen in the near future, though.
Also, the kind of browser extension you're talking about would be limited
to just one device or require manually configured syncing between your
devices, and would also likely be limited to just a few platforms.
The communication is done between the wallet and merchant the same as
always with BIP70, but with some extra BIP70 extensions for this purpose.
It just starts talking earlier.
It supports graceful degradation just fine, if the browser or wallet don't
support it or the wallet isn't linked to that computer's browser, then
nothing out of the ordinary happens. The browser extension really don't do
anything special, it just relays the details in the HTML tag.
> > As one example, your browser could ask your hardware wallet over BLE for
> > this data. This way you barely have to trust the computer you're using
at
> > all, as everything it does is confirmed on the hardware wallet before
> > payment (assuming it has a screen, which it should). Linking your
hardware
> > wallet over BLE to new devices which you then use for browsing and
shopping
> > could be trivial and yet allow secure auto-fill of this kind.
>
> This looks more interesting but is information about your location
> really so secret that you need to hold it in HW wallet? Because if so,
> you probably don't want to use untrusted machine anyway. (Or just use
> Qubes OS.)
It isn't necessarily top secret, but why not be protective by default? Your
hardware wallet is already designed to keep secrets. Lets say you're at a
library computer, or at a friend's house, why not let your hardware wallet
deal with all the security?
In this scenario it is likely already functioning as a central point for
all your Bitcoin related purchases anyway, so it might as well be the
device that remembers all your shopping preferences for you. So let's make
it simple to use!
[-- Attachment #2: Type: text/html, Size: 2529 bytes --]
prev parent reply other threads:[~2015-02-10 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAt2M18H0K99bmD4H_FRSeE+O9nGFDruCmo63GOQt1kxAdVBmQ@mail.gmail.com>
2015-02-10 10:21 ` Natanael
2015-02-10 10:34 ` MⒶrtin HⒶboⓋštiak
2015-02-10 10:41 ` Natanael
2015-02-10 10:48 ` MⒶrtin HⒶboⓋštiak
2015-02-10 11:12 ` Natanael
2015-02-10 11:21 ` MⒶrtin HⒶboⓋštiak
2015-02-10 10:50 ` Oleg Andreev
2015-02-10 10:59 ` Eric Voskuil
2015-02-10 11:08 ` Mike Hearn
2015-02-10 11:19 ` Natanael
2015-02-10 11:33 ` MⒶrtin HⒶboⓋštiak
2015-02-10 11:58 ` Natanael [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='CAAt2M182P9BpJ=H1rSGF45qNWii12n1YpKOxnULcPW1L4XLZ+w@mail.gmail.com' \
--to=natanael.l@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=martin.habovstiak@gmail$(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