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; 
To: bitcoin-development@lists.sourceforge.net
From: Andreas Schildbach <andreas@schildbach.de>
Date: Thu, 20 Mar 2014 09:09:39 +0100
Message-ID: <lge7nk$3mf$2@ger.gmane.org>
References: <lc5hmg$1jh$1@ger.gmane.org>
	<leuunm$tjk$1@ger.gmane.org>	<CANEZrP3nQfvDArKTRgje0Cus4G2JD_zpxSjA3fXfxM2TNAP80Q@mail.gmail.com>	<CALDj+BafD+6KTNcYDBEu5gNPzYozSkiC-JCxrY-PzXL2DYBRsw@mail.gmail.com>
	<CAJHLa0N4J_Z907+D0ENSNKfNAW2N=7Jf4JzSCO=SU558GtGTzA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
In-Reply-To: <CAJHLa0N4J_Z907+D0ENSNKfNAW2N=7Jf4JzSCO=SU558GtGTzA@mail.gmail.com>
Subject: Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments
Precedence: list

Afaik, BIP73 needs an external server (the web server).


On 03/20/2014 04:31 AM, Jeff Garzik wrote:
> Take a look at BIP 73:
> https://github.com/bitcoin/bips/blob/master/bip-0073.mediawiki
> 
> 
> 
> 
> On Wed, Mar 19, 2014 at 10:22 PM, Alex Kotenko <alexykot@gmail.com
> <mailto:alexykot@gmail.com>> wrote:
> 
>     Hi Andreas
> 
> 
>     I'm implementing support for BIP70 in my POS at the moment, and I've
>     just realized that with options you're proposing usecase I'm looking
>     for is not covered.
> 
>     Right now, before BIP70, I'm sending BIP21 URI via NFC or QR code,
>     and I need to still be able to use it for backwards compatibility.
>     But at the same time I want to be able to support BIP70. And also I
>     want to avoid using external servers, the concept of my POS is that
>     everything is happening between just payer's phone and payee's POS
>     device. This means that BIP72 HTTP(S) link inside Bitcoin URI is not
>     suitable for me. 
> 
>     You're also offering an option to include Base43 encoded PR body
>     right inside the Bitcoin URI, but in a way that is not backwards
>     compatible with BIP21. 
> 
>     In the end this all means that there is no way for me to at the same
>     time keep backwards compatibility with all wallets not supporting
>     NFC and BIP70 (all other wallets right now), and keep things inside
>     POS without need for external servers. 
> 
>     I understand your intention behind base43 encoding and noncompatible
>     URI - you want to make most possible use of QR codes. But I wonder -
>     did you compare this base43 to base64 encoded request in a binary QR
>     code format? How much do we actually win in total bytes capacity at
>     a price of noncompatibility and increased complexity?
> 
>     And also maybe we can extend BIP72 to include encoded payment
>     request in the URL directly in a backwards compatible way?
> 
> 
>     Best regards, 
>     Alex Kotenko
> 
> 
>     2014-03-02 11:50 GMT+00:00 Mike Hearn <mike@plan99.net
>     <mailto:mike@plan99.net>>:
> 
>         Thanks Andreas.
> 
>         For BIP standardisation, I think the VIEW intent seems like an
>         obvious one. Bluetooth support probably should come later
>         if/when we put encryption/auth on the RFCOMM link (probably SSL).
> 
>         ------------------------------------------------------------------------------
>         Flow-based real-time traffic analytics software. Cisco certified
>         tool.
>         Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow
>         Analyzer
>         Customize your own dashboards, set traffic alerts and generate
>         reports.
>         Network behavioral analysis & security monitoring. All-in-one tool.
>         http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
> 
>         _______________________________________________
>         Bitcoin-development mailing list
>         Bitcoin-development@lists.sourceforge.net
>         <mailto:Bitcoin-development@lists.sourceforge.net>
>         https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> 
> 
> 
>     ------------------------------------------------------------------------------
>     Learn Graph Databases - Download FREE O'Reilly Book
>     "Graph Databases" is the definitive new guide to graph databases and
>     their
>     applications. Written by three acclaimed leaders in the field,
>     this first edition is now available. Download your free book today!
>     http://p.sf.net/sfu/13534_NeoTech
>     _______________________________________________
>     Bitcoin-development mailing list
>     Bitcoin-development@lists.sourceforge.net
>     <mailto:Bitcoin-development@lists.sourceforge.net>
>     https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> 
> 
> 
> 
> -- 
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc.      https://bitpay.com/
> 
> 
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> 
> 
> 
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>