+Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]

+ helo=mx.sourceforge.net)

+ by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)

+ (envelope-from <tomh@thinlink.com>) id 1Wx5qN-0007ym-KC

+ for bitcoin-development@lists.sourceforge.net;

+ Wed, 18 Jun 2014 02:43:23 +0000

+X-ACL-Warn:

+Received: from mail-pd0-f175.google.com ([209.85.192.175])

+ by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)

+ (Exim 4.76) id 1Wx5qL-0007OP-Sp

+ for bitcoin-development@lists.sourceforge.net;

+ Wed, 18 Jun 2014 02:43:23 +0000

+Received: by mail-pd0-f175.google.com with SMTP id v10so184018pde.6

+ for <bitcoin-development@lists.sourceforge.net>;

+ Tue, 17 Jun 2014 19:43:16 -0700 (PDT)

+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;

+ d=1e100.net; s=20130820;

+ h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to

+ :subject:references:in-reply-to:content-type

+ :content-transfer-encoding;

+ bh=MklNZR9bA+9o5lSVqRNQWI7J2S6LSe3BE5LkGzhbQEw=;

+ b=NU6S6dFejSDFvlFcLQJdI8VwXnZqrghc2q0e84yvUcv+MtDlf5UWM33v+onLln0Ouj

+ QQjeDkffwi14EwvOXx3yvETeQXeN7B26Y6R4mY4IUVo5Yg647uqbK/g0ikE0y94QGYoS

+ XGqYaJI5PO6j/CtPYZASHiZ/O2ddz3KZn+24Ni/2A039BTpZKJFl1QL3PJFuEJATq0AG

+ urz/LCoMe/43S/FqqRlaeszvU9BYM0ZT1+6JJ9IkjIX1mDvD2xsvFVQT1u1hUXDZ4GAa

+ DIY23IokZMsHpr3mTc10WCuDOgXgRBounvlG0zBFQc6pW6+A88VTmQ7Kx9ecg+gqUTDw

+ xGvA==

+X-Gm-Message-State: ALoCoQnlOlC+NscO7gEKm0x93fuDsnRF1/tlB47dVSDXHwpFKspeDBay1AByCm8+/67EuB0EXpYu

+X-Received: by 10.66.236.161 with SMTP id uv1mr17806283pac.85.1403055579306;

+ Tue, 17 Jun 2014 18:39:39 -0700 (PDT)

+Received: from [192.168.1.89] (99-6-44-248.lightspeed.sntcca.sbcglobal.net.

+ [99.6.44.248])

+ by mx.google.com with ESMTPSA id qw8sm438369pbb.27.2014.06.17.18.39.37

+ for <bitcoin-development@lists.sourceforge.net>

+ (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);

+ Tue, 17 Jun 2014 18:39:38 -0700 (PDT)

+Message-ID: <53A0EDDE.7080801@thinlink.com>

+Date: Tue, 17 Jun 2014 18:39:42 -0700

+From: Tom Harding <tomh@thinlink.com>

+User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;

+ rv:24.0) Gecko/20100101 Thunderbird/24.6.0

+MIME-Version: 1.0

+To: bitcoin-development@lists.sourceforge.net

+References: <CAKrJrGOBSiY5V59eko6g796j3wh9V9ZLjPbyHeS5=zyX6j3Wdw@mail.gmail.com> <CANEZrP0Euc1mPhRc9e41tU4zMDrWesvVyiBpAPq6M3m7K=aU=A@mail.gmail.com> <CAFDyEXgKpbE4WGAqROJ4J1UST=tXWgfn7uKhRO_tngJfVK_Czw@mail.gmail.com> <CADE3-jA8LizD8cjdqKm0pFc8OV7JqPBGhs4uvp6=VhEU2emV6w@mail.gmail.com>

+ <CANEZrP3KKSkD7_R0Dvt600b7vh0oia78vHhPrPqSGBbwf9DsSQ@mail.gmail.com>

+In-Reply-To: <CANEZrP3KKSkD7_R0Dvt600b7vh0oia78vHhPrPqSGBbwf9DsSQ@mail.gmail.com>

+Content-Type: text/plain; charset=ISO-8859-1; format=flowed

+Content-Transfer-Encoding: 7bit

+X-Spam-Score: 0.0 (/)

+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 [209.85.192.175 listed in list.dnswl.org]

+X-Headers-End: 1Wx5qL-0007OP-Sp

+Subject: Re: [Bitcoin-development] instant confirmation via payment protocol

+ backwards compatible proto buffer extension

+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: Wed, 18 Jun 2014 02:43:23 -0000

+

+On 6/16/2014 8:48 AM, Mike Hearn wrote:

+> In practice of course this is something payment processors like Bitpay

+> and Coinbase will think about. Individual cafes etc who are just using

+> mobile wallets won't be able to deal with this complexity: if we can't

+> make native Bitcoin work well enough there, we're most likely to just

+> lose that market or watch it become entirely centralised around a

+> handful of payment processing companies.

+

+I have trouble seeing how could the real-time anonymous payments market

+can be cleanly separated from everything else. If trusted third parties

+become the norm for that market, there will inevitably be a huge overlap

+effect on other markets that bitcoin can serve best, even today. I

+don't see how any currency, any cash, can concede this market.

+

+

+