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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <theymos@mm.st>) id 1R3xcQ-0002Pz-3Y
for bitcoin-development@lists.sourceforge.net;
Wed, 14 Sep 2011 22:07:46 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of mm.st
designates 66.111.4.27 as permitted sender)
client-ip=66.111.4.27; envelope-from=theymos@mm.st;
helo=out3.smtp.messagingengine.com;
Received: from out3.smtp.messagingengine.com ([66.111.4.27])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1R3xcP-0005kR-Fh
for bitcoin-development@lists.sourceforge.net;
Wed, 14 Sep 2011 22:07:46 +0000
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45])
by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 3B10F20F60
for <bitcoin-development@lists.sourceforge.net>;
Wed, 14 Sep 2011 18:07:40 -0400 (EDT)
Received: from web3.nyi.mail.srv.osa ([10.202.2.213])
by compute5.internal (MEProxy); Wed, 14 Sep 2011 18:07:40 -0400
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
id 1B0DA6020D6; Wed, 14 Sep 2011 18:07:40 -0400 (EDT)
Message-Id: <1316038060.2261.140258141234677@webmail.messagingengine.com>
X-Sasl-Enc: BnmeD1LR24BsRwTQUEJ/DgzWdy9jpgD7/43hIooqpFSZ 1316038060
From: "theymos" <theymos@mm.st>
To: bitcoin-development@lists.sourceforge.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-Mailer: MessagingEngine.com Webmail Interface
References: <CABsx9T2XLj4gZVPYodteaVCm0chR1n4WLUoSqB6+NnmWCDqHKQ@mail.gmail.com><4E6F83C3.9020108@jerviss.org><CABsx9T0JvnOaBy+irHtnN1zMWP8FiDTn=kn-01ky+V2MW1suTg@mail.gmail.com><CAB=c7TpFE_28BNpkW27kKK41w8QdaMKJ96=6H=xqonVDdTWUkA@mail.gmail.com><CAAS2fgQOuNKWD09arSzqKxYFRv95q4xyq0Wz4ZkeKdKSWJ-=kA@mail.gmail.com><CABsx9T2Ot2iErtr48X_QmcZFQOXGH_jWNPrG=Ck6uQXhVXS=QA@mail.gmail.com><CAL0fb62X5-yZQbVMd6zeS590jbaa1nKRH-wYWkKXRHxCtuy=kQ@mail.gmail.com>
<CAAS2fgQJqRZ0wPak3Ub1nN6gp9Y1MgU=rgPGTZMwPZZ7Mc5JYg@mail.gmail.com>
In-Reply-To: <CAAS2fgQJqRZ0wPak3Ub1nN6gp9Y1MgU=rgPGTZMwPZZ7Mc5JYg@mail.gmail.com>
Date: Wed, 14 Sep 2011 17:07:40 -0500
X-Spam-Score: -1.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
(theymos[at]mm.st)
-0.0 SPF_PASS SPF: sender matches SPF record
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
0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service
X-Headers-End: 1R3xcP-0005kR-Fh
Subject: Re: [Bitcoin-development] Difficulty adjustment / time issues
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: Wed, 14 Sep 2011 22:07:46 -0000
On Wednesday, September 14, 2011 5:51 PM, "Gregory Maxwell" <gmaxwell@gmail.com> wrote:
> General network health and user security _requires_ periodic upgrades
> in any case, and will for the foreseeable future. The whole notion
> that old versions will _stop working_ would be a pretty good thing at
> this point in bitcoin's existence, judging by the high number of pre-
> .24 listeners still reported.
Backward-compatibility is valuable. I believe version 0.1 will still
more or less work on the current network. This is a real selling point
for Bitcoin: the code is solid enough that even 2-year-old clients are
still working.
|