Help Support the Bitcoin Network: The Simple Guide to Running a Full Node

What is the purpose of Full Nodes? According to Bitcoin core developer Pieter Wuille:

  • Full nodes provide lookup of historic blocks, which is necessary for new nodes synchronizing.

  • Full nodes provide filtered transaction lookup for SPV clients, which is necessary for those clients to function.

  • Full nodes validate blocks and transactions, and relay them.

Jameson Lopp wrote an interesting piece on the importance of Full Nodes here.

Coindesk wrote their own piece on the subject that can be found here.

You can explore current Full Nodes here.

Unlike with mining, you do not earn any money for operating a Full Node. The only benefit you get is that warm fuzzy feeling that you are helping to support the Bitcoin Network. That being said, if you own any bitcoin or run a Bitcoin based business, you do indirectly benefit from a stronger and more robust network .

The Simple Guide to Running a Full Node

1) First you need a computer or server that can be kept online as much as possible. This computer needs to have at least 30GB of free space. Over time it will need more space as the blockchain grows in size. (May be worth it to purchase a cheap external hard drive)

2) It should also have a fast and reliable internet connection that does not have any usage caps/limits. (Our Full Nodes average about 3-4GB worth of uploads every 24 hours)

3) Install the Bitcoin Core Software.

4) Wait for historical data to download. Bitcoin Core initial sync can take 3-10 hours on first startup.

5) After the download is complete, scroll over the signal bars on the bottom right hand corner of the Bitcoin Core window. It will tell you how many connections you have. If you have more than 8 connections, then everything is working great. If you have 8 or less connections, you need to sign into your router's software and forward port 8333.

Active Connections

Note for Mac/OSX users:

One of our users noticed that when running a node on OSX (10.9.3) the ping time goes through the roof whenever the user account is 'locked' or the screensaver comes on, going up to about 10 seconds. He attributes this to the machine going into some sort of low power mode. The problem is that it isn't obvious at all to the casual node runner. Setting the display sleep to 'never' solved this problem and the latency is now below 100ms.

Running a Node on a Raspberry Pi 2

The Raspberry Pi 2 is a low cost and low power Linux computer that only costs $35. For this reason, the RPi2 makes a great full node for those with uncapped home internet connections.

The Bit-Post wrote a great step by step guide that can be found here:

Need more Details?

The in-depth guide to running a Full Node can be found here. It is more complicated than this guide but is a great resource if for some reason something isn't working after you follow our guide.

We do not serve ads. Tips are always appreciated: 1G6BEVvEeZhuHYV7tiCYUd99UMgzQjC2vb