Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YJUUR-0001OT-4i for bitcoin-development@lists.sourceforge.net; Thu, 05 Feb 2015 22:01:35 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of airbitz.co designates 74.125.82.173 as permitted sender) client-ip=74.125.82.173; envelope-from=paul@airbitz.co; helo=mail-we0-f173.google.com; Received: from mail-we0-f173.google.com ([74.125.82.173]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YJUUO-0007Ae-R2 for bitcoin-development@lists.sourceforge.net; Thu, 05 Feb 2015 22:01:35 +0000 Received: by mail-we0-f173.google.com with SMTP id w62so10244491wes.4 for ; Thu, 05 Feb 2015 14:01:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=gEwCqdQpj+gB8OYIucw4wK8OokXs2Y7RKoDTVFAqKoY=; b=Ov86WGRfVfMcHhjovD9WwRXmARXP/orq3HB/nZI/Ksm9TYhAvLRYBBdOVHyGkwLN6A g+WZX8HfKnE9pWuHiSPgWTfbvrS1/bggcuj3+q9NyIcW7aX0ojBt35iV+b4FhTl+iPsa VJBloptjCOjOWQkN/krzZbXL743RfJoMypBqWwqDiyVXvKVIWAGprcbXUHN3v1TEgDUI 0ljYXRtDxo+7vdQL4uEKBDlJNUg5jzWyiHuUCfpBexlTpGOeEj7oM5vaYHKjjB7mB7rS FJErJgzwHuQhXZoORKIU3iYREGG/zaGSjMpuDpLewhrIaDF2eL1V/7vkKxdgeXiXpoFb gAqw== X-Gm-Message-State: ALoCoQmbSA3aNC++BaEfbE6Gn3EwiaR9T+t7KtVjf7F4eAp0PYmgVRGiE1uMwjDFnoGUCy9zXyGU X-Received: by 10.180.104.34 with SMTP id gb2mr705625wib.7.1423173686683; Thu, 05 Feb 2015 14:01:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.37.137 with HTTP; Thu, 5 Feb 2015 14:01:06 -0800 (PST) X-Originating-IP: [166.170.38.32] In-Reply-To: References: <54D3D636.1030308@voskuil.org> From: Paul Puey Date: Thu, 5 Feb 2015 14:01:06 -0800 Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=f46d044271b00c8030050e5e72cf X-Spam-Score: -0.6 (/) 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 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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 0.0 T_REMOTE_IMAGE Message contains an external image X-Headers-End: 1YJUUO-0007Ae-R2 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proposal for P2P Wireless (Bluetooth LE) transfer of Payment URI 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: Thu, 05 Feb 2015 22:01:35 -0000 --f46d044271b00c8030050e5e72cf Content-Type: text/plain; charset=UTF-8 The broadcast is ONLY done when the wallet is in Receive mode. Same as when the QR code is visible. The use of the *Name* section is specifically so that a recipient can broadcast their name/handle. Not so the recipient would broadcast the name of the Sender. [image: logo] *Paul Puey* CEO / Co-Founder, Airbitz Inc +1-619-850-8624 | http://airbitz.co | San Diego *DOWNLOAD THE AIRBITZ WALLET:* On Thu, Feb 5, 2015 at 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 > > > I hate to break it to you, but you broadcast a photo of your face every > time you walk outside ;) > > 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. > > "Payment spam" might be a problem. I can imagine a wallet requiring that > 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. > --f46d044271b00c8030050e5e72cf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The broadcast is ONLY done when the wallet is in Receive m= ode. Same as when the QR code is visible. The use of the *Name* section is = specifically so that a recipient can broadcast their name/handle. Not so th= e recipient would broadcast the name of the Sender.


3D"logo"==C2=A0=C2=A0=C2=A0
Paul Puey=C2=A0CEO / Co-F= ounder, Airbitz Inc
+1-619-850-8624=C2=A0|=C2=A0http://airbitz.co=C2=A0|=C2=A0San Diego
DOWNLOAD THE AIRBITZ WALLET:
=C2=A0




On Thu, Feb 5, 2015 at 12:50 PM, Mike Hearn = <= mike@plan99.net> wrote:
I'm imagining myself walking around broadcastin= g my photo and MAC
address while hucksters push payment requests to me for approval

I hate to break it to you, but you broadcast a photo = of your face every time you walk outside ;)

Blueto= oth MAC addresses are random, they aren't useful identifiers. If someon= e can see you, a face is a far more uniquely identifying thing than a MAC.<= /div>

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

--f46d044271b00c8030050e5e72cf--