From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1WX9qP-0000sj-24 for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 13:44:13 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of m.gmane.org designates 80.91.229.3 as permitted sender) client-ip=80.91.229.3; envelope-from=gcbd-bitcoin-development@m.gmane.org; helo=plane.gmane.org; Received: from plane.gmane.org ([80.91.229.3]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WX9qN-0003jk-9m for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 13:44:13 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WX9qE-0007To-Pq for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 15:44:02 +0200 Received: from f052238223.adsl.alicedsl.de ([78.52.238.223]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Apr 2014 15:44:02 +0200 Received: from andreas by f052238223.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Apr 2014 15:44:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Andreas Schildbach Date: Mon, 07 Apr 2014 15:43:52 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: f052238223.adsl.alicedsl.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 In-Reply-To: X-Enigmail-Version: 1.5.2 X-Spam-Score: -0.7 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.91.229.3 listed in list.dnswl.org] -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 1.1 DKIM_ADSP_ALL No valid author signature, domain signs all mail -0.0 SPF_PASS SPF: sender matches SPF record -0.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1WX9qN-0003jk-9m Subject: Re: [Bitcoin-development] Why are we bleeding nodes? 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: Mon, 07 Apr 2014 13:44:13 -0000 They're _not_ phasing out into SPV wallets from what I can say. At around the 24th of February, there has been a sharp change of the "current installs" graph of Bitcoin Wallet. That number used to grow at about 20.000 per month. After that date until now, it just barely moves horizontal. My guess is that a large number of users have lost interest after they lost their money in MtGox. The 24th of February coincides with the "final" shutdown, according to http://en.wikipedia.org/wiki/Mt._Gox#February_2014_shutdown_and_bankruptcy On 04/07/2014 02:17 PM, Ricardo Filipe wrote: > phasing out of bitcoinqt into spv wallets? > > 2014-04-07 12:34 GMT+01:00 Mike Hearn : >> 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 >