Fallback Nodes

You can connect to these nodes with the -addnode=ip switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using -addnode=ip more than once. It is usually a good idea to connect to more than one of these nodes.

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the -addnode and -connect parameters, you must additionally provide the -dns parameter. Example:

bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the -addnode parameter, so you must do the resolving part for it. For example on linux:

bitcoind -addnode=$(dig +short bitcoin.es)

Bitcoin Core versions prior to 0.8.0 also could send IP Transactions to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back.

To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter:

bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor

To use Bitcoin with one specific Tor node, run

bitcoin-qt -proxy=127.0.0.1:9050 -connect=abcde.onion

, where abcde.onion needs to be substituted with one of the Tor nodes below. These parameters can be added to bitcoin.conf to make them permanent.

You can find detailed information on running clients and hidden services within Tor in the documentation.

This entire list was last checked on 2017-11-15.

This entire list was last checked on 2018-10-24.