From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W7qAV-0002kh-0d for bitcoin-development@lists.sourceforge.net; Mon, 27 Jan 2014 17:40:19 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of m.gmane.org designates 80.91.229.3 as permitted sender) client-ip=80.91.229.3; envelope-from=gcbd-bitcoin-development@m.gmane.org; helo=plane.gmane.org; Received: from plane.gmane.org ([80.91.229.3]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1W7qAT-00059r-Uj for bitcoin-development@lists.sourceforge.net; Mon, 27 Jan 2014 17:40:18 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1W7qAI-00012I-Tm for bitcoin-development@lists.sourceforge.net; Mon, 27 Jan 2014 18:40:06 +0100 Received: from f053014231.adsl.alicedsl.de ([78.53.14.231]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 Jan 2014 18:40:06 +0100 Received: from andreas by f053014231.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 27 Jan 2014 18:40:06 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Andreas Schildbach Date: Mon, 27 Jan 2014 18:39:53 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: f053014231.adsl.alicedsl.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: X-Spam-Score: -0.9 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.91.229.3 listed in list.dnswl.org] -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 1.1 DKIM_ADSP_ALL No valid author signature, domain signs all mail -0.0 SPF_PASS SPF: sender matches SPF record -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1W7qAT-00059r-Uj Subject: Re: [Bitcoin-development] Payment Protocol for Face-to-face 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: Mon, 27 Jan 2014 17:40:19 -0000 On 01/27/2014 06:11 PM, Jeremy Spilman wrote: >> SCAN TO PAY >> For scan-to-pay, the current landscape looks different. I assume at >> least 50% of Bitcoin transactions are initiated by a BIP21 URL encoded >> into a QR-code. Nevertheless, I tried to encode a payment request into >> the bitcoin URL. I used my existing work on encoding transactions into >> QR-codes. Steps to encode: > > Really interesting work. When using scan-to-pay, after the payer scans the > QR code with the protobuf PaymentRequest (not a URL to download the > PaymentRequest) are they using their own connectivity to submit the > Payment response? > > How about putting a Bluetooth address in the payment_url inside the > PaymentDetails message for the smartphone to send back the Payment > response and get PaymentAck? That's exactly what I have prototyped. I am putting a Bluetooth MAC address into the payment_url. Have a look at the TAP TO PAY paragraph for details, its mostly the same mechanism.