1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
|
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 <boydb@midnightdesign.ws>) 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 <boydb@midnightdesign.ws>)
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 <bitcoin-development@lists.sourceforge.net>;
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: <CANEZrP3w9c_UX3dd+7LdWNXCEwjnAG+bYWxqKYo_fzakWQu=Bg@mail.gmail.com>
References: <CANEZrP3w9c_UX3dd+7LdWNXCEwjnAG+bYWxqKYo_fzakWQu=Bg@mail.gmail.com>
Date: Thu, 6 Mar 2014 08:20:17 -0600
Message-ID: <CANg-TZBv0zT6PywWJwug0DtzhQkXeE+9nMY14xKAfCysGfgkFg@mail.gmail.com>
From: Brooks Boyd <boydb@midnightdesign.ws>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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" <mike@plan99.net> 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
<p dir=3D"ltr"><br>
On Mar 6, 2014 3:47 AM, "Mike Hearn" <<a href=3D"mailto:mike@p=
lan99.net">mike@plan99.net</a>> wrote:<br>
><br>
> 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.<br>
><br>
> 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.</=
p>
<p dir=3D"ltr">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.</p>
--047d7bb70ae42f138f04f3f0d678--
|
