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
|
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 <tier.nolan@gmail.com>) id 1YqjoM-0007DB-95
for bitcoin-development@lists.sourceforge.net;
Fri, 08 May 2015 15:03:34 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.173 as permitted sender)
client-ip=209.85.220.173; envelope-from=tier.nolan@gmail.com;
helo=mail-qk0-f173.google.com;
Received: from mail-qk0-f173.google.com ([209.85.220.173])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YqjoL-00085e-FX
for bitcoin-development@lists.sourceforge.net;
Fri, 08 May 2015 15:03:34 +0000
Received: by qkx62 with SMTP id 62so49750928qkx.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 08 May 2015 08:03:28 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.55.31.218 with SMTP id n87mr1978904qkh.99.1431097408101;
Fri, 08 May 2015 08:03:28 -0700 (PDT)
Received: by 10.140.85.241 with HTTP; Fri, 8 May 2015 08:03:28 -0700 (PDT)
In-Reply-To: <CAOoPuRZo6M1-XTYk6LebADHwQVwKEOYtaHGvEoRkk5AfevvJYw@mail.gmail.com>
References: <CAE-z3OUiK_s-gJtnPquUZbG5aJkJjfo+VYKHgX+Bfcgem+6i9A@mail.gmail.com>
<CANEZrP2OXSmhLsfvpsQdr0QGbGyJWaAp1F0itu4V_C-E+0gO6A@mail.gmail.com>
<CAOoPuRZG4CVxcgExKHjDQd+F-w6xr6cJZD7pShbgPJd9CnqTwg@mail.gmail.com>
<CAE-z3OV30-ds5=5Tm55n+B26sPz3P+iC2TNHTBUidbX=qu08nQ@mail.gmail.com>
<CAOoPuRZo6M1-XTYk6LebADHwQVwKEOYtaHGvEoRkk5AfevvJYw@mail.gmail.com>
Date: Fri, 8 May 2015 16:03:28 +0100
Message-ID: <CAE-z3OVMfxioXUrFVAzcD7kpqsUA9_V=iCx67k+WkbZkFHrVig@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a1147e85ea637040515935442
X-Spam-Score: 1.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(tier.nolan[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
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
1.6 MALFORMED_FREEMAIL Bad headers on message from free email service
-0.6 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YqjoL-00085e-FX
Subject: Re: [Bitcoin-development] Assurance contracts to fund the network
with OP_CHECKLOCKTIMEVERIFY
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: Fri, 08 May 2015 15:03:34 -0000
--001a1147e85ea637040515935442
Content-Type: text/plain; charset=UTF-8
Sorry for the spam of the last mail. I hit send by accident.
Assurance contracts are better than simple donations.
Donating to a project means that you always end up losing the money but the
project might still not get funded.
An assurance contract is like Kickstarter, you only get your CC charged if
the project is fully funded.
There is lower risk, either you get your money back or the project is
funded. It might still be worth risking it and hoping it gets funded.
Kickstarter does have pledge rewards to reward pledgers. That helps with
creating the momentum to encourage people to pledge.
--001a1147e85ea637040515935442
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div><div><div><div>Sorry for the spam of the la=
st mail.=C2=A0 I hit send by accident.<br><br></div>Assurance contracts are=
better than simple donations.<br><br></div>Donating to a project means tha=
t you always end up losing the money but the project might still not get fu=
nded.<br><br></div>An assurance contract is like Kickstarter, you only get =
your CC charged if the project is fully funded. <br><br></div>There is lowe=
r risk, either you get your money back or the project is funded.=C2=A0 It m=
ight still be worth risking it and hoping it gets funded.<br><br></div>Kick=
starter does have pledge rewards to reward pledgers.=C2=A0 That helps with =
creating the momentum to encourage people to pledge.<br></div></div>
--001a1147e85ea637040515935442--
|
