I'm glad to see that I'm not the only one concerned about the consistent dropping of nodes. Though I think that the fundamental question should be: how many nodes do we really need? Obviously more is better, but it's difficult to say how concerned we should be without more information. I posted my thoughts last month: http://coinchomp.com/2014/03/19/bitcoin-nodes-many-enough/
I have begun working on my node monitoring project and will post updates if it results in me gaining any new insights about the network. - Jameson On 04/07/2014 07:34 AM, Mike Hearn wrote: > At the start of February we had 10,000 bitcoin nodes. Now we have 8,500 and > still falling: > > http://getaddr.bitnodes.io/dashboard/chart/?days=60 > > I know all the reasons why people *might* stop running a node (uses too > much disk space, bandwidth, lost interest etc). But does anyone have any > idea how we might get more insight into what's really going on? It'd be > convenient if the subVer contained the operating system, as then we could > tell if the bleed was mostly from desktops/laptops (Windows/Mac), which > would be expected, or from virtual servers (Linux), which would be more > concerning. > > When you set up a Tor node, you can add your email address to the config > file and the Tor project sends you emails from time to time about things > you should know about. If we did the same, we could have a little exit > survey: if your node disappears for long enough, we could email the > operator and ask why they stopped. > > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees_APR > > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees_APR _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
