summaryrefslogtreecommitdiff
path: root/f1/ac7e97712a63223267974336873a11e1ceb146
blob: e24bd77ac6b516eb964a012082244310866c20cc (plain)
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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1WLcm8-0007eq-6C
	for bitcoin-development@lists.sourceforge.net;
	Thu, 06 Mar 2014 18:12:08 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.128.170 as permitted sender)
	client-ip=209.85.128.170; envelope-from=mh.in.england@gmail.com;
	helo=mail-ve0-f170.google.com; 
Received: from mail-ve0-f170.google.com ([209.85.128.170])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WLcm7-00076R-FI
	for bitcoin-development@lists.sourceforge.net;
	Thu, 06 Mar 2014 18:12:08 +0000
Received: by mail-ve0-f170.google.com with SMTP id pa12so3031859veb.15
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 06 Mar 2014 10:12:02 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.52.184.73 with SMTP id es9mr131377vdc.55.1394129522015; Thu,
	06 Mar 2014 10:12:02 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.52.24.38 with HTTP; Thu, 6 Mar 2014 10:12:01 -0800 (PST)
In-Reply-To: <CANg-TZBoafXj6AiNGiT63BfX3iJYo5P3Vdmvxi+RuCODcrh0+w@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>
	<CANg-TZBoafXj6AiNGiT63BfX3iJYo5P3Vdmvxi+RuCODcrh0+w@mail.gmail.com>
Date: Thu, 6 Mar 2014 19:12:01 +0100
X-Google-Sender-Auth: O5mOciS4HGGpnqKjP-meq9lvN1w
Message-ID: <CANEZrP3pD2c-UFUZZAJAXBFTynx5Vusdw7As6O3RYuix3mMXDA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Brooks Boyd <boydb@midnightdesign.ws>
Content-Type: multipart/alternative; boundary=bcaec548a113ee463104f3f412de
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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
X-Headers-End: 1WLcm7-00076R-FI
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:12:08 -0000

--bcaec548a113ee463104f3f412de
Content-Type: text/plain; charset=UTF-8

>
> 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)
>

Well now you're getting into the area that I said "rapidly got very
complicated".

Define bitcoin user? What stops me paying myself to accrue positive
reputation? Etc.

--bcaec548a113ee463104f3f412de
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D""><div class=3D"g=
mail_extra">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)</div>
</div></div></blockquote><div><br></div><div>Well now you&#39;re getting in=
to the area that I said &quot;rapidly got very complicated&quot;.</div><div=
><br></div><div>Define bitcoin user? What stops me paying myself to accrue =
positive reputation? Etc.</div>
</div></div></div>

--bcaec548a113ee463104f3f412de--