From: Eric Voskuil <eric@voskuil•org>
To: Natanael <natanael.l@gmail•com>,
"MⒶrtin HⒶboⓋštiak" <martin.habovstiak@gmail•com>
Cc: Bitcoin Dev <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 02:59:21 -0800 [thread overview]
Message-ID: <54D9E489.4080207@voskuil.org> (raw)
In-Reply-To: <CAAt2M1_d0hkP4hjeiL-JGXWLGFFnRh8p+AiuVWxg3aOWNfEVZA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
On 02/10/2015 02:41 AM, Natanael wrote:
> Den 10 feb 2015 11:34 skrev "MⒶrtin HⒶboⓋštiak"
> <martin.habovstiak@gmail•com <mailto:martin.habovstiak@gmail•com>>:
>>
>> Why would anyone want to do anything about payment before choosing
>> what he wants to buy and for what price? I've never used Amazon but
>> isn't filling a form with shipping information enough?
>
> That's not what this is about.
>
> BIP70 isn't just payment, it is about communication the terms of the sale.
Hi Natanael,
BIP70 exists for seller non-repudiation (i.e. a cryptographically signed
receipt for payment) and establishing strong seller identity in a
face-to-face or other non-web scenario (since TLS doesn't help).
Anything else is incidental.
> Let's say you're visiting an international webshop. But they don't ship
> to your country. Wouldn't you want to know that before your start
> filling the cart? With this, your wallet / browser extension could tell
> you right away that you can't shop there. No time wasted!
>
> That's just one requirement of many where you would benefit from being
> told right away if it is acceptable for both parties or not.
There's quite a bit that can be done with wallets and web sites, but
personally I'd freak out if my wallet prompted me because I visited a
web site.
e
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-02-10 10:59 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 [this message]
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
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=54D9E489.4080207@voskuil.org \
--to=eric@voskuil$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=martin.habovstiak@gmail$(echo .)com \
--cc=natanael.l@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