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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XmKwJ-000695-SV for bitcoin-development@lists.sourceforge.net; Thu, 06 Nov 2014 11:09:19 +0000 X-ACL-Warn: Received: from mail1.bemta5.messagelabs.com ([195.245.231.141]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1XmKwH-0001XE-PQ for bitcoin-development@lists.sourceforge.net; Thu, 06 Nov 2014 11:09:19 +0000 Received: from [85.158.139.163] by server-5.bemta-5.messagelabs.com id F7/FC-27584-5D65B545; Thu, 06 Nov 2014 11:09:09 +0000 X-Env-Sender: thomas@thomaszander.se X-Msg-Ref: server-2.tower-188.messagelabs.com!1415272147!7554487!1 X-Originating-IP: [83.145.56.68] X-StarScan-Received: X-StarScan-Version: 6.12.4; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17422 invoked from network); 6 Nov 2014 11:09:08 -0000 Received: from unknown (HELO mail.infront.no) (83.145.56.68) by server-2.tower-188.messagelabs.com with AES128-SHA encrypted SMTP; 6 Nov 2014 11:09:08 -0000 Received: from SE8EX13-MBX01.osl.infront.as (10.234.180.15) by SE8TMG.osl.infront.as (10.234.180.35) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 6 Nov 2014 12:09:07 +0100 Received: from SE8EX13-CAS.osl.infront.as (10.234.180.10) by SE8EX13-MBX01.osl.infront.as (10.234.180.15) with Microsoft SMTP Server (TLS) id 15.0.775.38; Thu, 6 Nov 2014 12:09:06 +0100 Received: from debian.localnet (10.234.92.34) by SE8EX13-CAS.osl.infront.as (10.234.180.11) with Microsoft SMTP Server (TLS) id 15.0.775.38 via Frontend Transport; Thu, 6 Nov 2014 12:09:06 +0100 From: Thomas Zander To: Date: Thu, 6 Nov 2014 12:09:06 +0100 User-Agent: KMail/1.13.7 (Linux/3.2.0-4-486; KDE/4.8.4; i686; ; ) References: <545B44AA.7030107@numlog.fr> In-Reply-To: <545B44AA.7030107@numlog.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-ID: <201411061209.06322.thomas@thomaszander.se> X-Spam-Score: 0.0 (/) 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 [195.245.231.141 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 0.0 NORMAL_HTTP_TO_IP URI: URI host has a public dotted-decimal IPv4 address X-Headers-End: 1XmKwH-0001XE-PQ Subject: Re: [Bitcoin-development] Running a full node 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: Thu, 06 Nov 2014 11:09:20 -0000 On Thursday 6. November 2014 10.51.38 Francis GASCHET wrote: > Dear all, > > I'm currently discovering the Bitcoin's universe. > I installed bitcoind on my PC and I'm currently testing different things > on testnet. I just read an article saying that the risk for Bitcoin in the > future is the decreasing number of full nodes, with appropriate resources. > There are only few of them in France ! > > My company operates a dual homed Internet access and has some capacity to > host an HA server in a secured environment. So I'm thinking about setting > up a full node. But I'd like to know what storage, RAM and bandwidth > resources are needed. I guess that the problem is not the CPU. There is a stats script running on this node; http://213.165.91.169/ more peoples opinions; https://bitcointalk.org/index.php?topic=760094.0 -- Thomas Zander