From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WLZ9y-0007Xv-5v for bitcoin-development@lists.sourceforge.net; Thu, 06 Mar 2014 14:20:30 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of midnightdesign.ws designates 50.87.144.70 as permitted sender) client-ip=50.87.144.70; envelope-from=boydb@midnightdesign.ws; helo=gator3054.hostgator.com; Received: from gator3054.hostgator.com ([50.87.144.70]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WLZ9u-0004qK-Sk for bitcoin-development@lists.sourceforge.net; Thu, 06 Mar 2014 14:20:30 +0000 Received: from [74.125.82.176] (port=46515 helo=mail-we0-f176.google.com) by gator3054.hostgator.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1WLZ9o-0004FC-A3 for bitcoin-development@lists.sourceforge.net; Thu, 06 Mar 2014 08:20:20 -0600 Received: by mail-we0-f176.google.com with SMTP id x48so3090027wes.7 for ; Thu, 06 Mar 2014 06:20:17 -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:date :message-id:subject:from:to:content-type; bh=gju0yrL7RgZaDrhT282FIZUOw210DFM0VkqYqg9xdtA=; b=Oc7XuSDh1RnOulYGDGZJSgGBy03qTiq+EV3g57C+DyARLtRVUEo+cKtP6d1oOvmRdC +WG4PVZBm+cfAMyFRYDElBZwvMlyGwCsJfr/CduvYW0Fto/4vFVD0TWIQrXhMn35styd kw19UyIYWAHzMJmM4TgpkwuS/14YttxTVDxJg/H0CoAFN3Sa5iBnzGX1RWFRgP5BhuT5 GnS+biZqHX2bWTCJ+WQDUU5w6b0h7e+OMkBm2YEK0n9y+UM/wKiJ2dq1TARMHqy/Tlw9 YU9g+hKtKWs7dBZrYpeYdVAKfak8j3767uQ9Lzf4G7AtaVIIlnSDy8dsVQ+3hKYmnxzC bCpg== X-Gm-Message-State: ALoCoQmywOBhdFSRVgysurYKOyJfE9a5YWAdF3c3XERR40jfgh7Zgm3riBbHgYLT6mucipQgNKji MIME-Version: 1.0 X-Received: by 10.194.203.200 with SMTP id ks8mr10280593wjc.61.1394115617937; Thu, 06 Mar 2014 06:20:17 -0800 (PST) Received: by 10.227.71.71 with HTTP; Thu, 6 Mar 2014 06:20:17 -0800 (PST) Received: by 10.227.71.71 with HTTP; Thu, 6 Mar 2014 06:20:17 -0800 (PST) In-Reply-To: References: Date: Thu, 6 Mar 2014 08:20:17 -0600 Message-ID: From: Brooks Boyd To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=047d7bb70ae42f138f04f3f0d678 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator3054.hostgator.com X-AntiAbuse: Original Domain - lists.sourceforge.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - midnightdesign.ws X-BWhitelist: no X-Source-IP: 74.125.82.176 X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: (mail-we0-f176.google.com) [74.125.82.176]:46515 X-Source-Auth: midnight X-Email-Count: 1 X-Source-Cap: bWlkbmlnaHQ7bWlkbmlnaHQ7Z2F0b3IzMDU0Lmhvc3RnYXRvci5jb20= 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 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1WLZ9u-0004qK-Sk Subject: Re: [Bitcoin-development] Instant / contactless 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: Thu, 06 Mar 2014 14:20:30 -0000 --047d7bb70ae42f138f04f3f0d678 Content-Type: text/plain; charset=ISO-8859-1 On Mar 6, 2014 3:47 AM, "Mike Hearn" wrote: > > I just did my first contactless nfc payment with a MasterCard. It worked very well and was quite delightful - definitely want to be doing more of these in future. I think people will come to expect this kind of no-friction payment experience and Bitcoin will need to match it, so here are some notes on what's involved. > > 3) Have some kind of decentralised reputation network. I spent some time thinking about this, but it rapidly became very complicated and feels like an entirely separate project that should stand alone from Bitcoin itself. Perhaps rather than try to make a global system, social data could be exchanged (using some fancy privacy preserving protocols?) so if your friends have decided to trust seller X, your phone automatically trusts them too. A reputation network might be an interesting idea, or several different networks with different curators (to prevent complete centralization), like how the US credit score system has three main companies who track your score. Something like a GPG ring of trust, with addresses signing other addresses would work well, if some sort of Stealth address or HD wallet root was the identity gaining the reputation, then address re-use wouldn't have to be mandatory. --047d7bb70ae42f138f04f3f0d678 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On Mar 6, 2014 3:47 AM, "Mike Hearn" <mike@plan99.net> wrote:
>
> I just did my first contactless nfc payment with a MasterCard. It work= ed very well and was quite delightful - definitely want to be doing more of= these in future. I think people will come to expect this kind of no-fricti= on payment experience and Bitcoin will need to match it, so here are some n= otes on what's involved.
>
> 3) Have some kind of decentralised reputation network. I spent some ti= me thinking about this, but it rapidly became very complicated and feels li= ke an entirely separate project that should stand alone from Bitcoin itself= . Perhaps rather than try to make a global system, social data could be exc= hanged (using some fancy privacy preserving protocols?) so if your friends = have decided to trust seller X, your phone automatically trusts them too.

A reputation network might be an interesting idea, or severa= l different networks with different curators (to prevent complete centraliz= ation), like how the US credit score system has three main companies who tr= ack your score. Something like a GPG ring of trust, with addresses signing = other addresses would work well, if some sort of Stealth address or HD wall= et root was the identity gaining the reputation, then address re-use wouldn= 't have to be mandatory.

--047d7bb70ae42f138f04f3f0d678--