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 ) 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 ; 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" 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: <4E6F83C3.9020108@jerviss.org> In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2011 22:07:46 -0000 On Wednesday, September 14, 2011 5:51 PM, "Gregory Maxwell" 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.