1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WLbX1-0005xG-W9
for bitcoin-development@lists.sourceforge.net;
Thu, 06 Mar 2014 16:52:28 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.169 as permitted sender)
client-ip=209.85.220.169; envelope-from=mh.in.england@gmail.com;
helo=mail-vc0-f169.google.com;
Received: from mail-vc0-f169.google.com ([209.85.220.169])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WLbX0-0003mT-8k
for bitcoin-development@lists.sourceforge.net;
Thu, 06 Mar 2014 16:52:27 +0000
Received: by mail-vc0-f169.google.com with SMTP id hq11so2950854vcb.0
for <bitcoin-development@lists.sourceforge.net>;
Thu, 06 Mar 2014 08:52:20 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.52.135.65 with SMTP id pq1mr8590589vdb.13.1394124740683;
Thu, 06 Mar 2014 08:52:20 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.52.24.38 with HTTP; Thu, 6 Mar 2014 08:52:20 -0800 (PST)
In-Reply-To: <lfa8pf$ckc$1@ger.gmane.org>
References: <CANEZrP3w9c_UX3dd+7LdWNXCEwjnAG+bYWxqKYo_fzakWQu=Bg@mail.gmail.com>
<CALDj+BZE1KtMGpMH3UHtxjN2vXxu39o_hAWPdg==KLsWpe1zqA@mail.gmail.com>
<lfa8pf$ckc$1@ger.gmane.org>
Date: Thu, 6 Mar 2014 17:52:20 +0100
X-Google-Sender-Auth: WqIU_oR_NPfq3voJXcSHBVOYrR8
Message-ID: <CANEZrP0HXEOMg3Q_eaTz05T82JwH39sGq3Gu2gkc7A+PPUh=4w@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=bcaec52d5729f0efe604f3f2f529
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WLbX0-0003mT-8k
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Instant / contactless payments
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 16:52:28 -0000
--bcaec52d5729f0efe604f3f2f529
Content-Type: text/plain; charset=UTF-8
>
> I wonder about the receipt step -- are you generating a PDF on device
> and sending it via NFC? This is something that could be supported by the
> BIP70 payment protocol. We should try to avoid the second tap, its not
> intuitive.
>
Together, the signed PaymentRequest and the transactions in the block chain
should act like a receipt: it's proof you requested payment in a certain
way, and I satisfied that payment. So it's proof of payment and the memo
field can describe what I bought.
> Contactless cards? Last I was to London, the Oyster card was already
> contactless. Have there ever been magnet-strip-based Oyster cards?
>
He means, contactless credit cards can be used too. No need to enroll for
Oyster specifically. I guess in the long run Oyster and its equivalents in
other cities (octopus etc) will be phased out.
--bcaec52d5729f0efe604f3f2f529
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">I wonder about the receipt step -- are you gener=
ating a PDF on device<br>
and sending it via NFC? This is something that could be supported by the<br=
>
BIP70 payment protocol. We should try to avoid the second tap, its not<br>
intuitive.<br></blockquote><div><br></div><div>Together, the signed Payment=
Request and the transactions in the block chain should act like a receipt: =
it's proof you requested payment in a certain way, and I satisfied that=
payment. So it's proof of payment and the memo field can describe what=
I bought.</div>
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"">Contactless cards? Last I was to London, the Oyster card wa=
s already<br></div>
contactless. Have there ever been magnet-strip-based Oyster cards?<br></blo=
ckquote><div><br></div><div>He means, contactless credit cards can be used =
too. No need to enroll for Oyster specifically. I guess in the long run Oys=
ter and its equivalents in other cities (octopus etc) will be phased out.</=
div>
</div></div></div>
--bcaec52d5729f0efe604f3f2f529--
|
