Base/Fallback node setup - Tips & Hints Requested

[Mikej0h]

Hi all,

Not sure if I'm posting this in the right subforum, please move if needed.

Since I like Bitcoin, I want to make a contribution to the network by making my servers which I own available as Bitcoin nodes.
I not want to do any form of mining, and making profit out of it is definitely not the intention.

I want to setup a reliable base-node (fallback node is the right term I suppose), which people can connect to.
I suspect the 'usual' bitcoin-qt client might not be optimized for that.

What software can I used best? I've linux and windows servers available.
The servers are located in NL (Datacenter), and connected by Gbit Uplink.

Please give me some suggestions.
Thanks in advance.

[1538088836]

1538088836

[grau]

Running bitcoind, the service behind qt is the simplest valuable contribution to the network.

[Mikej0h]

Running bitcoind, the service behind qt is the simplest valuable contribution to the network.

Perfect, thanks for your suggestion.
Using the bitcoind service is definitely the right way to go (didn't know this, as I was normally using the windows Qt client).

I guess I should disable the default 8332 port (and open 8333), right?
Also because I've to specify username/pass for that configuration, as this is unknown to user "Anonymous".

My goal is to be a "supernode" for relaying blocks and transactions, and clients can use my server to download the blockchain.

Could you guys give me a few hints regarding the configuration?

Also regarding the fact this server is directly connected to the internet and has IPv4 & IPv6 available. Besides that, under the Windows client I'm often facing I'm not getting higher than 8 connected clients, of course I not want this for this "supernode" (the server used should be able of 1000+ connections).
Any idea's regards to that issue, as using UPnP doesn't make sence (as it's directly connected to the internet)?

[zvs]

Running bitcoind, the service behind qt is the simplest valuable contribution to the network.

Perfect, thanks for your suggestion.
Using the bitcoind service is definitely the right way to go (didn't know this, as I was normally using the windows Qt client).

I guess I should disable the default 8332 port (and open 8333), right?
Also because I've to specify username/pass for that configuration, as this is unknown to user "Anonymous".

My goal is to be a "supernode" for relaying blocks and transactions, and clients can use my server to download the blockchain.

Could you guys give me a few hints regarding the configuration?

Also regarding the fact this server is directly connected to the internet and has IPv4 & IPv6 available. Besides that, under the Windows client I'm often facing I'm not getting higher than 8 connected clients, of course I not want this for this "supernode" (the server used should be able of 1000+ connections).
Any idea's regards to that issue, as using UPnP doesn't make sence (as it's directly connected to the internet)?

edit the source code to allow more

set a decent password, like 4o3@OJdmXZLF:M4 l23jO$:J343$OJCMZXLK:OIDPWJA and 8332 doesn't need to be disabled.  there are some programs you might use where you'd want to have your rpc port open.  change the port # if the password itself doesnt make you feel safe.   8333 needs to be open if you want to accept outgoing connections

edit your ethernet settings to accomodate a thousand people sending mostly small bits of data

[kjj]

Running bitcoind, the service behind qt is the simplest valuable contribution to the network.

Perfect, thanks for your suggestion.
Using the bitcoind service is definitely the right way to go (didn't know this, as I was normally using the windows Qt client).

I guess I should disable the default 8332 port (and open 8333), right?
Also because I've to specify username/pass for that configuration, as this is unknown to user "Anonymous".

My goal is to be a "supernode" for relaying blocks and transactions, and clients can use my server to download the blockchain.

Could you guys give me a few hints regarding the configuration?

Also regarding the fact this server is directly connected to the internet and has IPv4 & IPv6 available. Besides that, under the Windows client I'm often facing I'm not getting higher than 8 connected clients, of course I not want this for this "supernode" (the server used should be able of 1000+ connections).
Any idea's regards to that issue, as using UPnP doesn't make sence (as it's directly connected to the internet)?

edit the source code to allow more

set a decent password, like 4o3@OJdmXZLF:M4 l23jO$:J343$OJCMZXLK:OIDPWJA and 8332 doesn't need to be disabled.  there are some programs you might use where you'd want to have your rpc port open.  change the port # if the password itself doesnt make you feel safe.   8333 needs to be open if you want to accept outgoing connections

edit your ethernet settings to accomodate a thousand people sending mostly small bits of data

If you don't need RPC, disable it.  If you do need RPC, but only internally, block the RPC port at your firewall and specify only your internal IPs in the bitcoin.conf.  If you need RPC from the internet, use a good password and SSL.