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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WN6Bm-00049n-8y for bitcoin-development@lists.sourceforge.net; Mon, 10 Mar 2014 19:48:42 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.176 as permitted sender) client-ip=209.85.220.176; envelope-from=alexy.kot.all@gmail.com; helo=mail-vc0-f176.google.com; Received: from mail-vc0-f176.google.com ([209.85.220.176]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WN6Bl-0003LS-7E for bitcoin-development@lists.sourceforge.net; Mon, 10 Mar 2014 19:48:42 +0000 Received: by mail-vc0-f176.google.com with SMTP id lc6so7042867vcb.35 for ; Mon, 10 Mar 2014 12:48:35 -0700 (PDT) X-Received: by 10.58.220.161 with SMTP id px1mr24845625vec.13.1394480915700; Mon, 10 Mar 2014 12:48:35 -0700 (PDT) MIME-Version: 1.0 Sender: alexy.kot.all@gmail.com Received: by 10.59.0.38 with HTTP; Mon, 10 Mar 2014 12:47:55 -0700 (PDT) In-Reply-To: References: <20140308085242.GA5727@odo.localdomain> From: Alex Kotenko Date: Mon, 10 Mar 2014 19:47:55 +0000 X-Google-Sender-Auth: mz5VEJgOtkb9-PAIAL0mLosz7bc Message-ID: To: Andreas Schildbach Content-Type: multipart/alternative; boundary=047d7bdc9e02a063f504f445e3b1 X-Spam-Score: -0.3 (/) 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 (alexy.kot.all[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.3 HTML_FONT_FACE_BAD BODY: HTML font face is not a word -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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: 1WN6Bl-0003LS-7E 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: Mon, 10 Mar 2014 19:48:42 -0000 --047d7bdc9e02a063f504f445e3b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ah, I see, so it's only payee who has to enable it, payer side is on by default. Then fine, situation is better than I thought. We'll look at implementing BIP70 asap. Best regards, Alex Kotenko 2014-03-10 19:28 GMT+00:00 Andreas Schildbach : > On 03/10/2014 04:09 PM, Alex Kotenko wrote: > > > =E2=80=8BYes, =E2=80=8BI'm certain about that we need to switch to BIP7= 0 asap. As I said > > earlier - support among the wallets is the biggest problem here really. > > Only Andreas' Wallet supports it right now AFAIK, and even in there it'= s > > only as "LABS feature", so will be turned off for most of users. > > Just a small clarification here. Bitcoin Wallet supports the customer > side of the protocol since 2011, without any "Labs enabling"! This means > you've got an install base of half a million devices that you can > interoperate with. Sure, a lot of users will have Bluetooth switched > off. The UI flow to enable it while paying is pretty smooth though. > > The merchant side used to have the Labs enabling but this is gone since > a few weeks. > > > > > -------------------------------------------------------------------------= ----- > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and thei= r > 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 > --047d7bdc9e02a063f504f445e3b1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ah, I see, so it's only payee who has to e= nable it, payer side is on by default. Then fine, situation is better than = I thought. We'll look at implementing BIP70 asap.

Best regards,=C2=A0
Alex Kotenko


2014-03-10 19:28 GMT+00:00 Andreas Schil= dbach <andreas@schildbach.de>:
On 03/10/2014 04:09 PM, Alex Kotenko wrote:

> =E2=80=8BYes, =E2=80=8BI'm certain about that we need to switch to= BIP70 asap. As I said
> earlier - support among the wallets is the biggest problem here really= .
> Only Andreas' Wallet supports it right now AFAIK, and even in ther= e it's
> only as "LABS feature", so will be turned off for most of us= ers.

Just a small clarification here. Bitcoin Wallet supports the customer=
side of the protocol since 2011, without any "Labs enabling"! Thi= s means
you've got an install base of half a million devices that you can
interoperate with. Sure, a lot of users will have Bluetooth switched
off. The UI flow to enable it while paying is pretty smooth though.

The merchant side used to have the Labs enabling but this is gone since
a few weeks.



---------------------------------------------------------------------------= ---
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-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--047d7bdc9e02a063f504f445e3b1--