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
114
115
116
117
118
119
120
121
122
123
124
125
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bitcoin-list@bluematt.me>) id 1QcRGl-0003q6-V2
for bitcoin-development@lists.sourceforge.net;
Fri, 01 Jul 2011 00:07:39 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bluematt.me
designates 208.79.240.5 as permitted sender)
client-ip=208.79.240.5; envelope-from=bitcoin-list@bluematt.me;
helo=smtpauth.rollernet.us;
Received: from smtpauth.rollernet.us ([208.79.240.5])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1QcRGi-0006cs-Vh
for bitcoin-development@lists.sourceforge.net;
Fri, 01 Jul 2011 00:07:39 +0000
Received: from smtpauth.rollernet.us (localhost [127.0.0.1])
by smtpauth.rollernet.us (Postfix) with ESMTP id DF573594011
for <bitcoin-development@lists.sourceforge.net>;
Thu, 30 Jun 2011 17:07:15 -0700 (PDT)
Received: from mail.bluematt.me (unknown
[IPv6:2001:470:9ff2:2:20c:29ff:fe16:f239])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
(Authenticated sender: @bluematt.me)
by smtpauth.rollernet.us (Postfix) with ESMTPSA
for <bitcoin-development@lists.sourceforge.net>;
Thu, 30 Jun 2011 17:07:13 -0700 (PDT)
Received: from [IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b] (unknown
[IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b])
by mail.bluematt.me (Postfix) with ESMTPSA id 509AB2586
for <bitcoin-development@lists.sourceforge.net>;
Fri, 1 Jul 2011 02:07:18 +0200 (CEST)
From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/signed; micalg="pgp-sha1";
protocol="application/pgp-signature";
boundary="=-+9MepevR10L/35WYB8Vv"
Date: Fri, 01 Jul 2011 02:07:18 +0200
Message-ID: <1309478838.3689.25.camel@Desktop666>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2
X-Rollernet-Abuse: Processed by Roller Network Mail Services. Contact
abuse@rollernet.us to report violations. Abuse policy:
http://rollernet.us/abuse.php
X-Rollernet-Submit: Submit ID 4734.4e0d0fb1.c1d1f.0
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 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1QcRGi-0006cs-Vh
Subject: [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 00:07:40 -0000
--=-+9MepevR10L/35WYB8Vv
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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/df94ed7ac0ed7bb3a96cf434ca3c64c4b47=
5e37e), dnsseed on by default, and maybe UPnP enabled by default as well.
I just got a DNSSeed up with reliable hosting which dynamically fills
its hostname with random nodes known to be up and accepting connections
(and on port 8333 and on version 0.3.19 or higher) (dnsseed.bluematt.me)
and I hope others follow suit with
https://github.com/TheBlueMatt/dnsseed (its poorly done but works just
fine). This was added to master in 44d16327. Since its no longer a
static list, I think its time to enable dnsseed by default (I have one
or two connections by the time the GUI opens when I use -dnsseed
-noirc).
Also, I think UPnP by default would be a good idea as it could increase
the percent of nodes which accept incoming connection (and other P2P
applications which depend on the ability to accept incoming connections
have it on by default as well, such as Skype). Jgarzik has also
suggested this, and I really dont see much of a reason not to.
Also,
https://github.com/bitcoin/bitcoin/commit/3a3eabb57ae41dd2162ca8230423abf4a=
90ef644 should be included to fix the no-connections-up segfault.
Matt
--=-+9MepevR10L/35WYB8Vv
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAABAgAGBQJODQ+sAAoJEBrh01BD4I5UdeAP/AicimfRGxsFHg3Gx3ILogfM
0xyGdiooDg/tI3oAdnaq/JnsPqg8V0KwT08PTOwFeJUnClXIcnPyFb5GYw81aXhQ
4cTIr3tvOe+0SBHyqMApKtAJ+nbV/IjIkkUDrnC9ZNK3OcHc1vklHGDAyhfEeuyI
5tAaCcZX6AR1htE1Q74ix7HLWexSF3POmhx04o6PYDIuOOEgCcDJbjEyv1yX84NV
M8GPddBZdBCvpoh9eQ2Y3J+wZEMEpBLVEV92A19+GaJFjB6bt5LEoKqeQJKvfcPA
r5qKNapbAcvQVTIOdWdJ8tXJwvCDbTzO56fR/6dcPlolvhIEyljtb59hxVjFYw8P
fZCqagi3uv1KrFFv1g8TcBqm5R6YycWWy8T8ykVDJa3XwtRzkyB+WM4xj5jJ97uX
9rC/VZN7yxAFoa6Qt9hDDFZCJi6nQhQiE1KoZ22ns0bgjvM+HPXjquviHKNz/NZU
wtlo5H7gKD2AeBEaoTyBI/5gg1h0wpNrHjD+3ScvkSD7/Mma09oYGGhPDjYCD0HS
bS4tps3LkQ0Sbcl6+bpPFAIvzCq4om4tmIa4D4hIk0Z+YIcBp5bNxbV+0eIXeRYp
/vp/kR4OoqRaQFdcG+ENzJ9skg4mHHkVIiQqPcoQ/MuD6hIUImnoIzpjg/6onDvq
3SDUUCFe1KFIoSg9J/Os
=Mhjg
-----END PGP SIGNATURE-----
--=-+9MepevR10L/35WYB8Vv--
|
