summaryrefslogtreecommitdiff
path: root/42/24dd9908cf196321801f1951e0806cbe56721a
blob: ae2227c8c71876d5842ffde7b6aee55be00521dd (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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <ampedal@gmail.com>) id 1R3x7q-0001GL-06
	for bitcoin-development@lists.sourceforge.net;
	Wed, 14 Sep 2011 21:36:10 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.175 as permitted sender)
	client-ip=209.85.216.175; envelope-from=ampedal@gmail.com;
	helo=mail-qy0-f175.google.com; 
Received: from mail-qy0-f175.google.com ([209.85.216.175])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1R3x7p-0001H8-7E
	for bitcoin-development@lists.sourceforge.net;
	Wed, 14 Sep 2011 21:36:09 +0000
Received: by qyk10 with SMTP id 10so4562706qyk.13
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 14 Sep 2011 14:36:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.65.147 with SMTP id j19mr318397qci.1.1316036163443; Wed,
	14 Sep 2011 14:36:03 -0700 (PDT)
Received: by 10.229.91.68 with HTTP; Wed, 14 Sep 2011 14:36:03 -0700 (PDT)
In-Reply-To: <CABsx9T2Ot2iErtr48X_QmcZFQOXGH_jWNPrG=Ck6uQXhVXS=QA@mail.gmail.com>
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>
Date: Wed, 14 Sep 2011 17:36:03 -0400
Message-ID: <CAL0fb62X5-yZQbVMd6zeS590jbaa1nKRH-wYWkKXRHxCtuy=kQ@mail.gmail.com>
From: Alex Waters <ampedal@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.1 (-)
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
	(ampedal[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-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
	0.5 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R3x7p-0001H8-7E
Cc: bitcoin-development@lists.sourceforge.net
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 21:36:10 -0000

On Wed, Sep 14, 2011 at 4:28 PM, Gavin Andresen <gavinandresen@gmail.com> w=
rote:

> What do other people think? =A0I think it is too high risk for too
> little benefit and shouldn't be done until we have a really compelling
> reason to introduce a forking change.

Could we bundle this and potential future blockchain-splitting changes
- to implement them in a major release (down the road)? Or save them
for when they are very necessary?

TL;DR shelf it until needed, have it written just in case.

-Alex