Message-ID: <54D3D9C4.9090400@voskuil.org>
Date: Thu, 05 Feb 2015 12:59:48 -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: Mike Hearn <mike@plan99.net>
References: <CABdy8DKS4arkkCLGC=66SUJm5Ugib1EWP7B6MkQRX1k-yd3WBw@mail.gmail.com>	<CANEZrP3v=ySS4gragaWuBMWi_swocRRRq_kw2edo6+9kifgrFQ@mail.gmail.com>	<54D3D636.1030308@voskuil.org>
	<CANEZrP3ekWQWeV=Yw_E=n0grORBLHaXLUh3w0EFQdz=HsjWvZw@mail.gmail.com>
In-Reply-To: <CANEZrP3ekWQWeV=Yw_E=n0grORBLHaXLUh3w0EFQdz=HsjWvZw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="CtXFt5m9co6nCFo4kodR78ptX4WaQJuXP"
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)
--CtXFt5m9co6nCFo4kodR78ptX4WaQJuXP
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 02/05/2015 12:50 PM, Mike Hearn wrote:
>     I'm imagining myself walking around broadcasting my photo and MAC
>     address while hucksters push payment requests to me for approval
>=20
> I hate to break it to you, but you broadcast a photo of your face every=

> time you walk outside ;)
>=20
> Bluetooth MAC addresses are random, they aren't useful identifiers. If
> someone can see you, a face is a far more uniquely identifying thing
> than a MAC.

Interesting take on privacy. But the market will of course decide.

Would the merchant be broadcasting payment requests in the clear, or
would they be encrypted with a public key of the spender?

> "Payment spam" might be a problem. I can imagine a wallet requiring tha=
t
> such requests are signed and then spammers can be blacklisted in the
> usual fashion so they can't push things to your phone anymore. Anyway, =
a
> hurdle that can be jumped if/when it becomes an issue.

Not sure I'd shoot for a system that's guaranteed to require PKI with
blacklisting and spam filtering.

e


--CtXFt5m9co6nCFo4kodR78ptX4WaQJuXP
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

iQEcBAEBAgAGBQJU09nEAAoJEDzYwH8LXOFO8t4H+wQd9LW+BIVauUw2kgQytuOw
TpVIf0UtgSyTQWYJHeloj6WFMVeXAHZfBDZanWnx6vsDhwSRihX7pWwUiH907fkX
3A/wBiJfzB1q11rHdyv9AQh9UswklLVYxklFJ1cQrYhIlqXIMpMEkiDZU3Be3a+t
hCPsYpnU2Yogzg3pkqe8cf7pGddXA3UWg/eBb7j2rYPsfX8q7EPUJ8rt26unoq/N
skNRbdGn8+eCUCF/paDtFjOj7IHSrhsq22UFiwtHVUJldLsmfLlgRH7KR/ukD5Cf
KTGPW8Xyf/yUpA+XSco/vuPCljKd1qbBJ9wM5h2hQBm+pcUktde+NfAwOFN5PTI=
=h5gf
-----END PGP SIGNATURE-----

--CtXFt5m9co6nCFo4kodR78ptX4WaQJuXP--