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 ) 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 ; 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: References: Date: Thu, 6 Mar 2014 17:52:20 +0100 X-Google-Sender-Auth: WqIU_oR_NPfq3voJXcSHBVOYrR8 Message-ID: From: Mike Hearn To: Andreas Schildbach 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 Subject: Re: [Bitcoin-development] Instant / contactless payments X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
I wonder about the receipt step -- are you gener= ating 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 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.
=C2=A0
Contactless cards? Last I was to London, the Oyster card wa= s 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 Oys= ter and its equivalents in other cities (octopus etc) will be phased out.
--bcaec52d5729f0efe604f3f2f529--