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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1Ywx9j-0006JS-GI
for bitcoin-development@lists.sourceforge.net;
Mon, 25 May 2015 18:31:19 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.49 as permitted sender)
client-ip=74.125.82.49; envelope-from=mh.in.england@gmail.com;
helo=mail-wg0-f49.google.com;
Received: from mail-wg0-f49.google.com ([74.125.82.49])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Ywx9i-0006rv-L6
for bitcoin-development@lists.sourceforge.net;
Mon, 25 May 2015 18:31:19 +0000
Received: by wgme6 with SMTP id e6so10142700wgm.2
for <bitcoin-development@lists.sourceforge.net>;
Mon, 25 May 2015 11:31:12 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.12.228 with SMTP id b4mr32725599wic.92.1432578672668;
Mon, 25 May 2015 11:31:12 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.194.143.9 with HTTP; Mon, 25 May 2015 11:31:12 -0700 (PDT)
In-Reply-To: <5550D8BE.6070207@electrum.org>
References: <5550D8BE.6070207@electrum.org>
Date: Mon, 25 May 2015 20:31:12 +0200
X-Google-Sender-Auth: MgjGASiHOoTCf-P-w8ejoFwfPSM
Message-ID: <CANEZrP2x+fBitgcvoaC2qBbJS-Ek_hgS3ZGM55UtURKc-oDZMQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Thomas Voegtlin <thomasv@electrum.org>
Content-Type: multipart/alternative; boundary=001a11c2a3a8e5b9060516ec366c
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: 1Ywx9i-0006rv-L6
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Long-term mining incentives
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: Mon, 25 May 2015 18:31:19 -0000
--001a11c2a3a8e5b9060516ec366c
Content-Type: text/plain; charset=UTF-8
Hi Thomas,
My problem is that this seems to lacks a vision.
>
Are you aware of my proposal for network assurance contracts?
There is a discussion here:
https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg07552.html
But I agree with Gavin that attempting to plan for 20 years from now is
ambitious at best. Bitcoin might not even exist 20 years from now, or might
be an abandoned backwater a la USENET.
--001a11c2a3a8e5b9060516ec366c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi Thomas,<div><br></div><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bord=
er-left-style:solid;padding-left:1ex">My problem is that this seems to lack=
s a vision. <br></blockquote><div><br></div><div>Are you aware of my propos=
al for network assurance contracts?</div><div><br></div><div>There is a dis=
cussion here:</div><div><br></div><div>=C2=A0 =C2=A0 <a href=3D"https://www=
.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg07552.html">=
https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg0=
7552.html</a><br></div><div><br></div><div>But I agree with Gavin that atte=
mpting to plan for 20 years from now is ambitious at best. Bitcoin might no=
t even exist 20 years from now, or might be an abandoned backwater a la USE=
NET.</div></div></div></div>
--001a11c2a3a8e5b9060516ec366c--
|
