Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YJUbc-0006aQ-5A for bitcoin-development@lists.sourceforge.net; Thu, 05 Feb 2015 22:09:00 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of airbitz.co designates 74.125.82.44 as permitted sender) client-ip=74.125.82.44; envelope-from=paul@airbitz.co; helo=mail-wg0-f44.google.com; Received: from mail-wg0-f44.google.com ([74.125.82.44]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YJUbY-0006Ts-DT for bitcoin-development@lists.sourceforge.net; Thu, 05 Feb 2015 22:09:00 +0000 Received: by mail-wg0-f44.google.com with SMTP id z12so10137959wgg.3 for ; Thu, 05 Feb 2015 14:08:50 -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=XV9OJESHwR8RX44xO/fucMVYFUFAPl4ZthBMirvJA2U=; b=QpwI8UGpmms6hEqt/eRT0bl8CVBqBhC28B6ouDPc5youIraDsQFIuoVfwLcNp45/Op is/1lsXfMXphu/C4XX0+HhG022wNJwxG48Kc0FA6CPqXkFyEQUm/weKWPhAwv58DwTdG lypsLMwffv/On6URyYK/DbfEm8wxIMDRujM6UGl+8+a3Rc5rglng+6+Ah1v7+iGsQ1VK ulgfbr8n8r4aAW7IP/xDWyy/2o91t6GwIrSfh6m9IQe7XXR+iDDYFl6vJMOM4PMcC8Jw Sy/HX87EFocHWd0+WEJPDGmAs+GaR3oNqjH6A9vO1BpfxzrInmY/HKa2NJLqWZJpxiUe qLYQ== X-Gm-Message-State: ALoCoQlFraOKT0ZkU3k+Ly+yfnLz56hsxzXBiXsJhhBIsd+CZioa1GpMK+pPyitjWr3d7usr3WFi X-Received: by 10.180.228.72 with SMTP id sg8mr802895wic.48.1423174129380; Thu, 05 Feb 2015 14:08:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.37.137 with HTTP; Thu, 5 Feb 2015 14:08:28 -0800 (PST) X-Originating-IP: [166.170.38.32] In-Reply-To: <87E6D928-B615-4A8D-8BBB-3610DB1C08A2@voskuil.org> References: <54D3D636.1030308@voskuil.org> <87E6D928-B615-4A8D-8BBB-3610DB1C08A2@voskuil.org> From: Paul Puey Date: Thu, 5 Feb 2015 14:08:28 -0800 Message-ID: To: Eric Voskuil Content-Type: multipart/alternative; boundary=001a1134cc4e6f80d8050e5e8c83 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 -0.0 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1YJUbY-0006Ts-DT 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:09:00 -0000 --001a1134cc4e6f80d8050e5e8c83 Content-Type: text/plain; charset=UTF-8 Although not perfect, and it may require visual/verbal verification, I don't see what the trust issue is. [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 2:05 PM, Eric Voskuil wrote: > Hi Paul, > > The issue is in the establishment of trust. Anyone can broadcast the > initial information. > > e > > On Feb 5, 2015, at 2:01 PM, Paul Puey wrote: > > 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. > > 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. >> > > --001a1134cc4e6f80d8050e5e8c83 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Although not perfect, and it may require visual/verbal ver= ification, I don't see what the trust issue is.


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 2:05 PM, Eric Voskuil= <eric@voskuil.org> wrote:
=
Hi Paul,

The issue is in th= e establishment of trust. Anyone can broadcast the initial information.
=
e

On Feb 5, 2015, at 2:01 PM, Paul Puey <paul@airbitz.co> wrote:
<= br>
The broadcast is ONLY d= one 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 bro= adcast their name/handle. Not so the recipient would broadcast the name of = the Sender.

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.


--001a1134cc4e6f80d8050e5e8c83--