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
148
149
150
151
152
153
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <boydb@midnightdesign.ws>) id 1WLcj7-0002Dz-2i
for bitcoin-development@lists.sourceforge.net;
Thu, 06 Mar 2014 18:09:01 +0000
Received-SPF: pass (sog-mx-1.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-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WLcj5-0006yS-Vz
for bitcoin-development@lists.sourceforge.net;
Thu, 06 Mar 2014 18:09:01 +0000
Received: from [74.125.82.41] (port=40131 helo=mail-wg0-f41.google.com)
by gator3054.hostgator.com with esmtpsa (TLSv1:RC4-SHA:128)
(Exim 4.80.1) (envelope-from <boydb@midnightdesign.ws>)
id 1WLciz-0005EN-EO for bitcoin-development@lists.sourceforge.net;
Thu, 06 Mar 2014 12:08:53 -0600
Received: by mail-wg0-f41.google.com with SMTP id n12so3646970wgh.0
for <bitcoin-development@lists.sourceforge.net>;
Thu, 06 Mar 2014 10:08:51 -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:cc:content-type;
bh=r+twkNwY718X6W7xktffBWqvgAzsvWhLIkDjS395lCY=;
b=XT/YfJfZ5auhABXbuNMV8bSW2MNC4gwVXD0XtEj1Kv9q1laLQjx9QxlRkvtX0DrZeO
NInLRAFxpbSdGNeoXG6/+LJwd4ml6dA4ErB3LJEwpXApeCiyRXtHgBA91ngWB5XuuUCZ
mlfk155pcGYCDgY8QTSv0uquZ84DjRAHwgzrVn4sZVSAAKJ8tNJ1zWGzCQ5M+/HrsVu8
Gpe7RgdbL97rBG3uJCJ91jWnbaegYRRmBCsLgmjL7fUu01yNEmu95FgJeD40ItX7ykMK
6GvUc2CbOHtQ6Fdv+yiGo5oZ1tYvjeRw0lq4qP3bfdoFkR1AmpyTQc20a2ne+qqr9dMe
nGWw==
X-Gm-Message-State: ALoCoQlynb4gQl3ufmc/HuGZ1UTGYxA2M41iKRJHBFPPIkD8DDnZ0EbhbWDAtvBISXs8EZMhsb1k
MIME-Version: 1.0
X-Received: by 10.194.85.168 with SMTP id i8mr12052219wjz.81.1394129331388;
Thu, 06 Mar 2014 10:08:51 -0800 (PST)
Received: by 10.227.71.71 with HTTP; Thu, 6 Mar 2014 10:08:51 -0800 (PST)
In-Reply-To: <CANEZrP38p5O+GJ0AsFUHzfuXpR=Z0m2YCZiOy0nFd8jZFuE64A@mail.gmail.com>
References: <CANEZrP3w9c_UX3dd+7LdWNXCEwjnAG+bYWxqKYo_fzakWQu=Bg@mail.gmail.com>
<CANg-TZBv0zT6PywWJwug0DtzhQkXeE+9nMY14xKAfCysGfgkFg@mail.gmail.com>
<CANEZrP38p5O+GJ0AsFUHzfuXpR=Z0m2YCZiOy0nFd8jZFuE64A@mail.gmail.com>
Date: Thu, 6 Mar 2014 12:08:51 -0600
Message-ID: <CANg-TZBoafXj6AiNGiT63BfX3iJYo5P3Vdmvxi+RuCODcrh0+w@mail.gmail.com>
From: Brooks Boyd <boydb@midnightdesign.ws>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=089e010d7efc91962a04f3f4076c
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.41
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (mail-wg0-f41.google.com) [74.125.82.41]:40131
X-Source-Auth: midnight
X-Email-Count: 2
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: 1WLcj5-0006yS-Vz
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 18:09:01 -0000
--089e010d7efc91962a04f3f4076c
Content-Type: text/plain; charset=ISO-8859-1
On Thu, Mar 6, 2014 at 11:07 AM, Mike Hearn <mike@plan99.net> wrote:
> 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.
>>
> The identity would be the X.520 name in the signing cert that signed the
> payment request. It doesn't have to be a difficult to obtain cert. It could
> even be self signed for this use case, but then you lose the security
> benefits and a key rotation would delete your reputation, so in practice I
> think most people would want the reputation to accrue to the name itself.
>
That makes sense, to have self-signed certificates as a basic start, but
then is it possible to have a Bitcoin user (address) add reputation/sign
such a certificate, rather than having a central signing authority? If
there was a way for a Bitcoin user to provide feedback on a payment (ECDSA
signature from one of the addresses involved in the payment, signing an
identifier of the payment and a feedback score) such that any user can add
to the reputation with just the Bitcoin infrastructure, without having to
learn X.500 certificate signing on top of EC signatures? If there was a
standard structure for a message to be EC-signed with your Bitcoin client,
and then a distributed store of those signed messages, could that form a
reputation score?
--089e010d7efc91962a04f3f4076c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Mar 6, 2014 at 11:07 AM, Mike Hearn <span dir=3D"ltr"><<a href=3D"ma=
ilto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">if some sort of S=
tealth address or HD wallet root was the identity gaining the reputation, t=
hen address re-use wouldn't have to be mandatory.</p>
</blockquote></div><div>The identity would be the X.520 name in the signing=
cert that signed the payment request. It doesn't have to be a difficul=
t to obtain cert. It could even be self signed for this use case, but then =
you lose the security benefits and a key rotation would delete your reputat=
ion, so in practice I think most people would want the reputation to accrue=
to the name itself.</div>
</div></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">That makes sense, t=
o have self-signed certificates as a basic start, but then is it possible t=
o have a Bitcoin user (address) add reputation/sign such a certificate, rat=
her than having a central signing authority? If there was a way for a Bitco=
in user to provide feedback on a payment (ECDSA signature from one of the a=
ddresses involved in the payment, signing an identifier of the payment and =
a feedback score) such that any user can add to the reputation with just th=
e Bitcoin infrastructure, without having to learn X.500 certificate signing=
on top of EC signatures? If there was a standard structure for a message t=
o be EC-signed with your Bitcoin client, and then a distributed store of th=
ose signed messages, could that form a reputation score?</div>
</div>
--089e010d7efc91962a04f3f4076c--
|
