📅 Original date posted:2011-07-01
🗒️ Summary of this message: Bitcoin developers discuss the need for a 0.3.24 release to address flood control limits, enable DNS seed and UPnP by default, and fix bugs.
📝 Original message: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
Pieter Wuille [ARCHIVE] /
npub1tj…jtl6r
2023-06-07 01:59:28
in reply to nevent1q…luf6
Author Public Key
npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6rPublished at
2023-06-07 01:59:28Event JSON
{
"id": "35487029855ffffd9c72f62ba3878c8c7e6612f8fde8d5c8445ca0f47ec9e746",
"pubkey": "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6",
"created_at": 1686103168,
"kind": 1,
"tags": [
[
"e",
"b259aa9a612285804c8ca826465b76b8809982948e0ab24ccddc1c8a657cc6bd",
"",
"root"
],
[
"e",
"5354355849db87dde9187345aa7caa1baeb1ce556f0cc183ac660caf6ed32087",
"",
"reply"
],
[
"p",
"304641dbb49ee6a600bce6ea04cb0cb25b3c969f8f11581aedb62736f2bce6b2"
]
],
"content": "📅 Original date posted:2011-07-01\n🗒️ Summary of this message: Bitcoin developers discuss the need for a 0.3.24 release to address flood control limits, enable DNS seed and UPnP by default, and fix bugs.\n📝 Original message:On Fri, Jul 01, 2011 at 02:07:18AM +0200, Matt Corallo wrote:\n\u003e Due to the flood control limits becoming an issue again, it would appear\n\u003e we need a 0.3.24 release. The idea is to have sipa's flood limit fix\n\u003e (https://github.com/sipa/bitcoin/commit/df94ed7ac0ed7bb3a96cf434ca3c64c4b475e37e),\n\nI've cleaned the commit up a bit, and created a pull request (#369) for it.\n\n\u003e dnsseed on by default, and maybe UPnP enabled by default as well.\n\n\u003e I just got a DNSSeed up with reliable hosting which dynamically fills\n\u003e its hostname with random nodes known to be up and accepting connections\n\u003e (and on port 8333 and on version 0.3.19 or higher) (dnsseed.bluematt.me)\n\u003e and I hope others follow suit with\n\u003e https://github.com/TheBlueMatt/dnsseed (its poorly done but works just\n\u003e fine). This was added to master in 44d16327.\n\nNice, we definitely needed something like that. It wouldn't hurt to have multiple\npeople running such a seed, to prevent problems with occasional outages of DNS seeds,\nonce we move away from IRC entirely.\n\n\u003e Since its no longer a\n\u003e static list, I think its time to enable dnsseed by default (I have one\n\u003e or two connections by the time the GUI opens when I use -dnsseed\n\u003e -noirc).\n\nAgree.\n\n\u003e Also, I think UPnP by default would be a good idea as it could increase\n\u003e the percent of nodes which accept incoming connection (and other P2P\n\u003e applications which depend on the ability to accept incoming connections\n\u003e have it on by default as well, such as Skype). Jgarzik has also\n\u003e suggested this, and I really dont see much of a reason not to.\n\nGiven that there is no public outcry against these programs automatically\nopening holes in firewalls, I assume it's safe for us to do the same.\n\nIt should be clearly explained in the release notes, though.\n\n\u003e Also,\n\u003e https://github.com/bitcoin/bitcoin/commit/3a3eabb57ae41dd2162ca8230423abf4a90ef644 should be included to fix the no-connections-up segfault.\n\nYes.\n\nSo: I'm in favor of an emergency release 0.3.24 with upnp default enabled,\ndnsseed default enabled, block send limit, no-connect segfault bugfix.\nAnything else?\n\n-- \nPieter",
"sig": "a515ab77fcbfb59c77c363bf354d28a2a2417c425e87c6995913855d2b3ffe07cac66db8eb3ae5f684774bfd6aef5bee872e573ae294de8088c8a4c451a0d547"
}