From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1QcYek-0004nX-Rr for bitcoin-development@lists.sourceforge.net; Fri, 01 Jul 2011 08:00:54 +0000 X-ACL-Warn: Received: from rhcavuit02.kulnet.kuleuven.be ([134.58.240.130] helo=cavuit02.kulnet.kuleuven.be) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1QcYej-0000NO-F2 for bitcoin-development@lists.sourceforge.net; Fri, 01 Jul 2011 08:00:54 +0000 X-KULeuven-Envelope-From: sipa@ulyssis.org X-Spam-Status: not spam, SpamAssassin (not cached, score=-48.798, required 5, autolearn=disabled, DKIM_ADSP_CUSTOM_MED 0.00, FREEMAIL_FROM 0.00, KUL_SMTPS -50.00, NML_ADSP_CUSTOM_MED 1.20) X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: 14095128154.AA7CA X-KULeuven-Information: Katholieke Universiteit Leuven Received: from smtps01.kuleuven.be (smtpshost01.kulnet.kuleuven.be [134.58.240.74]) by cavuit02.kulnet.kuleuven.be (Postfix) with ESMTP id 14095128154; Fri, 1 Jul 2011 10:00:44 +0200 (CEST) Received: from smtp.ulyssis.org (mail.ulyssis.student.kuleuven.be [193.190.253.235]) by smtps01.kuleuven.be (Postfix) with ESMTP id B9C6B31E702; Fri, 1 Jul 2011 10:00:43 +0200 (CEST) Received: from wop.ulyssis.org (wop.intern.ulyssis.org [192.168.0.182]) by smtp.ulyssis.org (Postfix) with ESMTP id 968DD10067; Fri, 1 Jul 2011 10:01:43 +0200 (CEST) Received: by wop.ulyssis.org (Postfix, from userid 615) id CB1AC87C1AC; Fri, 1 Jul 2011 10:00:43 +0200 (CEST) Date: Fri, 1 Jul 2011 10:00:43 +0200 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Pieter Wuille To: Matt Corallo Message-ID: <20110701080042.GA657@ulyssis.org> References: <1309478838.3689.25.camel@Desktop666> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1309478838.3689.25.camel@Desktop666> X-PGP-Key: http://sipa.ulyssis.org/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: 1.2 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (pieter.wuille[at]gmail.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED 1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit, and not from a mailing list 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1QcYej-0000NO-F2 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 08:00:54 -0000 On Fri, Jul 01, 2011 at 02:07:18AM +0200, Matt Corallo 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), I've cleaned the commit up a bit, and created a pull request (#369) for it. > 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. Nice, we definitely needed something like that. It wouldn't hurt to have multiple people running such a seed, to prevent problems with occasional outages of DNS seeds, once we move away from IRC entirely. > 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). Agree. > 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. Given that there is no public outcry against these programs automatically opening holes in firewalls, I assume it's safe for us to do the same. It should be clearly explained in the release notes, though. > Also, > https://github.com/bitcoin/bitcoin/commit/3a3eabb57ae41dd2162ca8230423abf4a90ef644 should be included to fix the no-connections-up segfault. Yes. So: I'm in favor of an emergency release 0.3.24 with upnp default enabled, dnsseed default enabled, block send limit, no-connect segfault bugfix. Anything else? -- Pieter