public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Thomas Zander <thomas@thomaszander.se>
To: <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Running a full node
Date: Thu, 6 Nov 2014 12:09:06 +0100	[thread overview]
Message-ID: <201411061209.06322.thomas@thomaszander.se> (raw)
In-Reply-To: <545B44AA.7030107@numlog.fr>

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



  reply	other threads:[~2014-11-06 11:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06  9:51 [Bitcoin-development] Running a full node Francis GASCHET
2014-11-06 11:09 ` Thomas Zander [this message]
2014-11-06 21:38   ` odinn
2014-11-08 15:28 ` Daniel F
2014-11-08 17:44   ` Melvin Carvalho
2014-11-08 21:47     ` Jameson Lopp
     [not found] <545B5323.3000403@numlog.fr>
2014-11-09 15:22 ` Francis GASCHET

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201411061209.06322.thomas@thomaszander.se \
    --to=thomas@thomaszander.se \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox