Author

Topic: My first bitcoin node (Read 2325 times)

copper member
Activity: 1498
Merit: 1499
No I dont escrow anymore.
March 03, 2015, 06:49:45 PM
#13
Hey guys,

Just an update: I updated Bitcoin core to 0.10 for some time now, and I get 90 connections. Because the max connections are set to 120 by default, should I raise it when the connections are near to this number? Or it will not be stable?

I just monitored the server and when it started to act slow or unresponsive I set the number of connections a bit lower than they currently are.
legendary
Activity: 1274
Merit: 1000
March 03, 2015, 06:24:18 PM
#12
I eventually found the time to setup my first Bitcoin node. Hopefully I have the ability to host it in the Greek backbone network, at the Greek Internet Exchange (I don't know how long I'll be able to host it there though). I have a powerful machine as well, with 4 cores and 8 GB of RAM, and it can deliver up to 1 gbps in Greece and up to 100 mpbs overseas.

What I'm asking is how will I be able to optimize it. Considering its location and how powerful the server is, what can I do to have the maximum connections, etc?

Feel free to connect by the way:
IPv4: 83.212.119.206
IPv6: 2001:648:2ffc:1225:a800:bff:fe20:637f

I just set up my first node, too.  I had it up for a couple weeks before I learned that I had to forward port 8333 on my firewall to the pc with the node, but now I'm up and running, too!  Congrats.
legendary
Activity: 975
Merit: 1003
March 03, 2015, 03:56:39 PM
#11
Hey guys,

Just an update: I updated Bitcoin core to 0.10 for some time now, and I get 90 connections. Because the max connections are set to 120 by default, should I raise it when the connections are near to this number? Or it will not be stable?
legendary
Activity: 1540
Merit: 1002
February 09, 2015, 09:16:21 PM
#10
Yeah give it a couple of days. Mine goes up to around 60.
I have heard that too many connections is bad for the network. Not sure how much truth is in this.

with the old clients where wallets only connect to 1 servers its true. think of it as a motorway off ramp with one lane and something goes wrong to close the lane, you then have all those connections finding new nodes and in some situations acting like a ddos attack on weaker nodes
legendary
Activity: 1652
Merit: 1015
February 09, 2015, 06:53:06 PM
#9
Yeah give it a couple of days. Mine goes up to around 60.
I have heard that too many connections is bad for the network. Not sure how much truth is in this.
legendary
Activity: 2954
Merit: 4158
February 09, 2015, 06:51:22 PM
#8
Thanks for the replies. The node has now finished downloading the block chain, and when I did a quick bitcoind getinfo, I realized that I had only 26 connections..

Quote
{
    "version" : 90400,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 342771,
    "timeoffset" : -1,
    "connections" : 26,
    "proxy" : "",
    "difficulty" : 44455415962.34380341,
    "testnet" : false,
    "keypoololdest" : 1423330698,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
You have to give It time for people to discover and connect to your node. Anything above 8 means that you are currently having incoming connections which is already contributing to the network.
legendary
Activity: 975
Merit: 1003
February 09, 2015, 06:47:10 PM
#7
Thanks for the replies. The node has now finished downloading the block chain, and when I did a quick bitcoind getinfo, I realized that I had only 26 connections..

Quote
{
    "version" : 90400,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 342771,
    "timeoffset" : -1,
    "connections" : 26,
    "proxy" : "",
    "difficulty" : 44455415962.34380341,
    "testnet" : false,
    "keypoololdest" : 1423330698,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
sr. member
Activity: 298
Merit: 250
February 09, 2015, 11:29:01 AM
#6
You should have it listed at https://getaddr.bitnodes.io/

He doesn't need to list it. bitnodes has picked it up a while ago.

https://getaddr.bitnodes.io/nodes/83.212.119.206-8333/

oh alright, my bad. I had some issues with syncing a couple days ago that was my go to place thought we have to manually do it.
legendary
Activity: 1358
Merit: 1000
https://gliph.me/hUF
February 09, 2015, 11:27:07 AM
#5
You should have it listed at https://getaddr.bitnodes.io/

He doesn't need to list it. bitnodes has picked it up a while ago.

https://getaddr.bitnodes.io/nodes/83.212.119.206-8333/
sr. member
Activity: 298
Merit: 250
February 09, 2015, 11:25:32 AM
#4
If you gonna keep it going you should have it listed in https://getaddr.bitnodes.io/
legendary
Activity: 2954
Merit: 4158
February 09, 2015, 09:11:03 AM
#3
Great job for setting up the node.

Having a powerful computer would allow more incoming peers to sync and get blocks from you. The default max connection is 125. You can always allow more peers to connect by adding
Code:
maxconnections=n
to your config where n is the maximum amount of peers to connect to you.
legendary
Activity: 1358
Merit: 1000
https://gliph.me/hUF
February 08, 2015, 01:08:19 AM
#2

Since you got port 8333 already open, just let it do it's thing. It will balance the connections it can handle itself.

I see you're only about half way there on the blockchain. You could consider using the latest release candidate which will speed up syncing significantly.
legendary
Activity: 975
Merit: 1003
February 07, 2015, 02:21:17 PM
#1
I eventually found the time to setup my first Bitcoin node. Hopefully I have the ability to host it in the Greek backbone network, at the Greek Internet Exchange (I don't know how long I'll be able to host it there though). I have a powerful machine as well, with 4 cores and 8 GB of RAM, and it can deliver up to 1 gbps in Greece and up to 100 mpbs overseas.

What I'm asking is how will I be able to optimize it. Considering its location and how powerful the server is, what can I do to have the maximum connections, etc?

Feel free to connect by the way:
IPv4: 83.212.119.206
IPv6: 2001:648:2ffc:1225:a800:bff:fe20:637f
Jump to: