Message-ID: <54D485A6.4010708@voskuil.org>
Date: Fri, 06 Feb 2015 01:13:10 -0800
From: Eric Voskuil <eric@voskuil.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Roy Badami <roy@gnomon.org.uk>
References: <54D3D636.1030308@voskuil.org>
	<CANEZrP3ekWQWeV=Yw_E=n0grORBLHaXLUh3w0EFQdz=HsjWvZw@mail.gmail.com>
	<279489A5-1E46-48A2-8F58-1A25821D4D96@gmail.com>
	<CANEZrP3VAWajxE=mNxb6sLSQbhaQHD=2TgRKvYrEax2PAzCi2A@mail.gmail.com>
	<6AEDF3C4-DEE0-4E31-83D0-4FD92B125452@voskuil.org>
	<CABdy8DLRGyy5dvmVb_B3vao7Qwz-zdAC3-+2nJkg9rSsU6FLbw@mail.gmail.com>
	<C28CD881-DAB8-4EDB-B239-7D45A825EAF0@voskuil.org>
	<CABjHNoTmj=wfjRwApZCJJTDhhwePh=VtXkJN0e3t1uQqmeMu6Q@mail.gmail.com>
	<20150205233421.GP39876@giles.gnomon.org.uk>
	<54D403E5.5090606@voskuil.org>
	<20150206085922.GQ39876@giles.gnomon.org.uk>
In-Reply-To: <20150206085922.GQ39876@giles.gnomon.org.uk>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="JvTEgaNTFb4BpbNNSwll8IinDIb9fDoaD"
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Paul Puey <paul@airbitz.co>
Subject: Re: [Bitcoin-development] Proposal for P2P Wireless (Bluetooth LE)
 transfer of Payment URI
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--JvTEgaNTFb4BpbNNSwll8IinDIb9fDoaD
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 02/06/2015 12:59 AM, Roy Badami wrote:
>> In this case there is no need for P2P communication, just pay to an
>> address you already have for the other party. If you want to avoid
>> address reuse, use stealth addressing.
>>
>> But yes, if you don't have a stealth address for the other party you c=
an
>> certainly communicate in private as peers where you trust that you sha=
re
>> a public key. The core issue here is really bootstrapping of that trus=
t
>> in an ad hoc manner.
>=20
> Something interactive might still be nicer, though, to avoid the risk
> of paying to an address that the payee no longer has the private key
> for.  "Nooo!! Don't pay to that address.  I lost my old phone so I
> generated a new wallet."

Certainly, which brings us back to proximity.

Which reminds me - it's important to keep in mind the scenario that
arises when there is no person present to represent the receiver. Such
as a vending machine purchase.

Proximity in these cases is insufficient, as the receiver is not able to
prevent application of a fraudulent NFC device or replacement of a
static QR code. In these cases BIP-70 becomes essential.

e


--JvTEgaNTFb4BpbNNSwll8IinDIb9fDoaD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJU1IWmAAoJEDzYwH8LXOFOe8AH/RMjJY8f1NTgW3IZklUIAGXP
B5VkmCkGqkT9y5L0CTDBw+HctaZT3w5QRcz6Qi8bfCVpcV/KFRHL7UrGGb6kJumV
5Y3UwbJAYDBlV/WOJzNgqzCcbqaMjXat1ar3U4Xk7NmzpIMz+4Q6omwGoYMnYaRi
/qPLVFBaF5XBE4OlEf5StbIluk7x1j0nGEKh/G4aPAsjQcFcR6logkd1Gw11q73K
IA+pArwNGJkcKBBWom0NkZzZqpfVZOTkEchECy/q4K+JSJewnlBCeWWaFqg/VXcL
Fci37muLc9fZ/8O8xpS/EfLl7rfE251RwVAPwSu7CNYL8Mjd9JTjKM2+9zNB2lY=
=5ih2
-----END PGP SIGNATURE-----

--JvTEgaNTFb4BpbNNSwll8IinDIb9fDoaD--