Fallback Nodes

This is a list of nodes which are considered reliable. Nodes from this list which are down for more than 24 hours will be automatically removed and status of each node is displayed and updated every hour by WikiBot . Wikibot is currently malfunctioning and is incorrectly marking nodes running version 0.6 as being down.

How to use this list

Connect to 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.

Nodes without a fixed ip

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)

IP Transactions

You can also send IP Transactions to these nodes. If you include your bitcoin address in the "message" field, you may have your coins back.

Tor network

To use tor .onion addresses (listed below), you will need to map virtual ips via the torrc file:

mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion

And then put these IPs in your bitcoin.conf (or run bitcoin with -connect)

connect=192.0.2.2
connect=192.0.2.3
connect=192.0.2.4

You can use any arbitrary IP addresses with MapAddress, though some of the common non-routable ranges (10.*, 192.168.*) will not work due to a Bitcoin bug (reference?). 192.0.2.1-192.0.2.255 is the recommended range because it is both non-routable and compatible with Bitcoin.

It is highly recommended that you use "connect" instead of "addnode" so that all of your communications are kept within the tor network.

Since Bitcoin 0.5, the client enables nolisten when the proxy setting is enabled, which in effect prevents the client from becoming a peer node. So the only way to operate a hidden bitcoin seed node would be to revert to an earlier version. Update: This has been fixed in version 0.6.

Nodes list

IPv4 Nodes

Wikibot is currently malfunctioning and is incorrectly marking nodes running 0.6 as being down.

Hostname	Owner	IP	Fixed	Status	Last Seen (GMT)	Accepts IP transactions
li111-4.members.linode.com	unknown	69.164.196.4	Yes	Up (73.68.21[.9])	2012-05-18 15:00:03	Yes
79.160.221.140	K-Norway	79.160.221.140	Yes	Down		Yes
netzbasis.de	unknown3	81.169.129.25	Yes	Down		Yes
progressbar.sk	Progressbar hackerspace	91.210.181.21	Yes	Down		Yes
btcnode.novit.ro	ovidiusoft - novit.ro	93.187.142.114	Yes	Down		Yes
bauhaus.csail.mit.edu	imsaguy	128.30.96.44	Yes	Down		Yes
178.32.7.171	temporary-april-2012	178.32.7.171	Yes	Down		Yes
django.webflows.fr	unknown2	188.165.213.169	Yes	Down		Yes
204.9.55.71	toasty	204.9.55.71	Yes	Down		Yes

There is a list of nodes which have been seen on the network recently at http://blockchain.info/connected-nodes

Tor nodes

Hostname	Owner	Status	Last Seen (GMT)	Accepts IP transactions
bitcoin2bkgm3fke.onion	?	up	2012-01-16	Yes
ijzt2eeizty3p5xe.onion	?	?	2011-02-11	Yes
j43z65b6r2usg3vk.onion	Dybbuk	?	2011-02-11	Yes
pvuif6nonbhj3o3r.onion	?	?	2011-02-11	Yes
c5qvugpewwyyy5oz.onion	?	?	2011-02-11	Yes
vso3r6cmjoomhhgg.onion	echelon	up	2011-02-11	Yes
sjdntqu5roj4q6lo.onion	torservers	up	2012-04-04	?
bitcoinbudtoeks7.onion	?	?	2011-02-11	?
iy6ni3wkqazp4ytu.onion	?	?	2011-02-11	?
h4kklwodpcmo6cbq.onion	?	?	2011-02-11	?
vv6kcfscuntybrzm.onion	?	?	2011-02-11	?
nlnsivjku4x4lu5n.onion	?	?	2011-02-11	?
xqzfakpeuvrobvpj.onion	?	?	2010-11-13	No
4lmduyac3svgrrav.onion	?	?	2011-02-11	No
usasx4urod3yj4az.onion	?	?	2011-02-11	No
sh4ep6zb6vnoa2h5.onion	Gmaxwell	?	2011-10-29	No
e3tn727fywnioxrc.onion	?	?	2011-11-01	No
p2hwc26zdsrqxiix.onion	redemerald	up	2012-04-04	No
bxfna6fhddpzduck.onion	?	?	?	?
esvua6k2gzjj64ad.onion	redemerald	?	2011-12-28	No
7hxvg2lvr2ashzli.onion	Tuxavant	up	2012-04-04	?
siqdznszjf4e6v5j.onion	Tuxavant	up	2012-04-04	?
fpt6orohw2nuf2kn.onion	Tril	up	2012-04-04	No

Adding a node

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the END NODELIST line:

|-
| ip || your name