summaryrefslogtreecommitdiff
path: root/8c/aeb95ca603c549cf2befd0080ecb835c345d0b
blob: 8fc96d6c7a7e84202c386a5b439664fb8d2ebc99 (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
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <dhuff@jrbobdobbs.org>) id 1QcTnl-00054t-0w
	for bitcoin-development@lists.sourceforge.net;
	Fri, 01 Jul 2011 02:49:53 +0000
X-ACL-Warn: 
Received: from mail-gy0-f175.google.com ([209.85.160.175])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.76) id 1QcTnj-0002K3-Tq
	for bitcoin-development@lists.sourceforge.net;
	Fri, 01 Jul 2011 02:49:52 +0000
Received: by gyd12 with SMTP id 12so1545004gyd.34
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 30 Jun 2011 19:49:46 -0700 (PDT)
Received: by 10.150.2.20 with SMTP id 20mr2593733ybb.395.1309488284261;
	Thu, 30 Jun 2011 19:44:44 -0700 (PDT)
Received: from devo.home.jrbobdobbs.org (cpe-70-124-63-160.austin.res.rr.com
	[70.124.63.160])
	by mx.google.com with ESMTPS id b36sm435862ybb.10.2011.06.30.19.44.42
	(version=SSLv3 cipher=OTHER); Thu, 30 Jun 2011 19:44:43 -0700 (PDT)
Sender: Doug <mith@jrbobdobbs.org>
References: <1309478838.3689.25.camel@Desktop666>
	<BANLkTi=ZZK5whvEmCj+aqp5q+XBnXZRY2A@mail.gmail.com>
User-Agent: K-9 Mail for Android
In-Reply-To: <BANLkTi=ZZK5whvEmCj+aqp5q+XBnXZRY2A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit
From: Douglas Huff <dhuff@jrbobdobbs.org>
Date: Thu, 30 Jun 2011 21:44:49 -0500
To: Gregory Maxwell <gmaxwell@gmail.com>,
	Matt Corallo <bitcoin-list@bluematt.me>
Message-ID: <3f9adcd5-a2b0-4613-b045-c964102e0d35@email.android.com>
X-Spam-Score: -0.3 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QcTnj-0002K3-Tq
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.3.24
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, 01 Jul 2011 02:49:53 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



Gregory Maxwell <gmaxwell@gmail.com> wrote:

>On Thu, Jun 30, 2011 at 8:07 PM, Matt Corallo
><bitcoin-list@bluematt.me> wrote:
>> Due to the flood control limits becoming an issue again, it would
>appear
>> we need a 0.3.24 release.  The idea is to have sipa's flood limit fix
>>
>(https://github.com/sipa/bitcoin/commit/df94ed7ac0ed7bb3a96cf434ca3c64c4b475e37e),
>dnsseed on by default, and maybe UPnP enabled by default as well.
>
>*Flood fix
>
>I think this is important, slow bringups are problematic and I think
>the flood disconnects have been contributing to network partitioning
>(you'll disconnect nodes that have the full blockchain but keep ones
>that don't), adding to the partitioning problems cause elsewhere.
>
>I've been running it for a couple hours on a large public node which
>was seeing frequent flood disconnects, and it seems to be working
>fine. No more flood disconnects.

I can confirm similar results.


>I'd also like suggest updating the checkpoint in 0.3.24. Difficulty
>has increased almost 17x since the highest one currently in there. A
>rather large number of parties could mine pretty nice forks at 1/16th
>the current difficulty for nodes that they've sibyled.

It's about time for another checkpoint, I agree.
- --
Douglas Huff
-----BEGIN PGP SIGNATURE-----
Version: APG v1.0.8

iQIVAwUBTg00oEPHkQabDWHPAQhtIg/+KqgpNzu9pInI4w1QMl/PyGSEUrin6pHq
94H9UJRtx6kAPbyBDZ2M/DYTAk5logB0jZoZXg5tkYxY+DoGYC5FLYiLV9nfgIa9
oGEOgdSzaVZseINes0FMNcD5DjEmvvW0nDzJyraD7T11R8r+uATEtcPNN9g0aYSF
WCRWEKZSvf6o9k5sibmDGrWe/Zx9PV5Si59fqo1eglHUGG+9wLjP3Fv904HSQWD/
zJ+bMTNyddOi0vP23S5rQM4V94HG2wjgOVk804a/2qJlibXyJi0cYRQj/JIibOIt
KzXHqYAhJK5JcizUcKu3T8YM22ZE04nIqhxg7h8+5vaZHfHgMYjqGrYeEtqx6GUC
6oXKke2dP8bqdX+JkJ9Zrf5uz8ysPf6Rj+77dA1tYyFZc2CEb5wA0cnW5SSzqMe1
5q7saRda3P0RvTtWmJKLPyXbr7EqETKhr37E/lc7viLgQCroggQ4wVkUAj4rfjDZ
HeZtCfBg3U63oe6WPH1MkzuGPBOjdrSK9RlibFanPU/AL+sTYsf5cs+j8WTHa6WA
ee1k01Nke1Pa7ForvWcUXzzLPVk/ikEgmJrrTKcBNAEh5UKq7BveDX0fSw0kQmPO
XdWjlNfOfcObCVLRcJ7ev8H6fDQOFGxUXH3A98PCVtUx05aVoDVoRvdPAGN0kbTo
Xqa58ov1pQY=
=jKOB
-----END PGP SIGNATURE-----