From mboxrd@z Thu Jan 1 00:00:00 1970 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 1WRP2l-0004WV-90 for bitcoin-development@lists.sourceforge.net; Sat, 22 Mar 2014 16:45:11 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.51 as permitted sender) client-ip=209.85.219.51; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f51.google.com; Received: from mail-oa0-f51.google.com ([209.85.219.51]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WRP2j-0003qP-9o for bitcoin-development@lists.sourceforge.net; Sat, 22 Mar 2014 16:45:11 +0000 Received: by mail-oa0-f51.google.com with SMTP id i4so3972717oah.24 for ; Sat, 22 Mar 2014 09:45:04 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.58.7 with SMTP id m7mr735385oeq.59.1395506703889; Sat, 22 Mar 2014 09:45:03 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.71.231 with HTTP; Sat, 22 Mar 2014 09:45:03 -0700 (PDT) In-Reply-To: References: <20140320121221.GA25052@netbook.cypherspace.org> Date: Sat, 22 Mar 2014 17:45:03 +0100 X-Google-Sender-Auth: 50yqtTjw23uiKhQOSU1uAKRbcmg Message-ID: From: Mike Hearn To: Jeff Garzik Content-Type: multipart/alternative; boundary=089e01538c565dfd1d04f534b9cd 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: 1WRP2j-0003qP-9o Cc: Bitcoin Dev , Andreas Schildbach 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: Sat, 22 Mar 2014 16:45:11 -0000 --089e01538c565dfd1d04f534b9cd Content-Type: text/plain; charset=UTF-8 > > Those locations are completely unsuitable to bitcoin transactions, > since the receiver cannot verify double-spending or anything else > about the transaction. The usual issue is that they lack internet *for some customers*. The place may well have private wifi or hardwired connections that work. Even mobile networks may vary so some customers will have mobile connectivity and others won't. --089e01538c565dfd1d04f534b9cd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Those locations are completely unsuitable to bit= coin transactions,
since the receiver cannot verify double-spending or anything else
about the transaction.

The usual issue is t= hat they lack internet for some customers. The place may well have p= rivate wifi or hardwired connections that work. Even mobile networks may va= ry so some customers will have mobile connectivity and others won't.=C2= =A0
--089e01538c565dfd1d04f534b9cd--