From: Francis GASCHET <fg@numlog.fr>
To: bitcoin-list@lists.sourceforge.net,
bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Running a full node
Date: Sun, 09 Nov 2014 16:22:21 +0100 [thread overview]
Message-ID: <545F86AD.3050002@numlog.fr> (raw)
In-Reply-To: <545B5323.3000403@numlog.fr>
Dear all,
+1 !
Thanks to those who sent me some details and links.
My node is up and running on 5.56.40.1:8333
Techno : Linux HA + dual homed Internet transit.
It should be stable as from now.
Best regards
--
Francis
Le 06/11/2014 11:53, Francis GASCHET a écrit :
> Dear all,
>
> I'm currently discovering the Bitcoin's universe.
> I installedbitcoind 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.
>
> Thanks in advance for details.
next parent reply other threads:[~2014-11-09 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <545B5323.3000403@numlog.fr>
2014-11-09 15:22 ` Francis GASCHET [this message]
[not found] ` <CAD2Ti2_AgRK=Fbz+i=HvUZis8ZwLx7PsHWHzgAUOF=jb19oGqQ@mail.gmail.com>
2014-12-04 14:32 ` [Bitcoin-development] [bitcoin-list] Running a full node Martinx - ジェームズ
2014-11-06 9:51 [Bitcoin-development] " Francis GASCHET
2014-11-06 11:09 ` Thomas Zander
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
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=545F86AD.3050002@numlog.fr \
--to=fg@numlog.fr \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=bitcoin-list@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