Fallback Nodes

From Bitcoin Wiki
Revision as of 14:00, 3 April 2011 by WikiBot (talk | contribs) (Checked fallback nodes)
Jump to navigation Jump to search

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.

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.

The Original Bitcoin client do not support hostnames to the -addnode parameter, so you must do the resolving part for it. For example on linux:

bitcoind -addnode=$(host theymos.ath.cx |sed s/"^.*has address "//)

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, you 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

Once you have configured and restarted tor, 192.0.2.2 will connect to ijzt2eeizty3p5xe.onion when accessed through the Tor proxy (and likewise for the other IPs/onions). You can then run Bitcoin with -addnode=192.0.2.2, or even send bitcoins to that IP address. 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. 192.0.2.1-192.0.2.255 is the recommended range because it is both non-routable and compatible with Bitcoin.

Nodes list

IPv4 Nodes

Hostname Owner IP Fixed Status Last Seen (GMT) Accepts IP transactions
69.164.218.197 Gavin Andresen 69.164.218.197 Yes Up (0.3.21) 2011-04-03 14:00:44 ?
jun.dashjr.org Lightfoot Hosting 173.242.112.53 Yes Up (0.3.21) 2011-04-03 14:00:44 ?
mining.bitcoin.cz slush 178.79.147.99 Yes Up (0.3.21) 2011-04-03 14:00:44 No
nat.router.dashjr.org Luke-Jr 71.1.73.218 No Up (0.3.21) 2011-04-03 14:00:45 ?
ndrix.com mndrix 64.22.103.150 Yes Up (0.3.20[.2]) 2011-04-03 14:00:45 ?
bitcoin.chrishowie.com cdhowie 68.169.45.99 Yes Up (0.3.20[.2]) 2011-04-03 14:00:45 No
btc1.justmoon.net justmoon 109.75.176.226 Yes Up (0.3.20[.2]) 2011-04-03 14:00:46 Yes
bitcoins.ca humble 142.58.248.28 Yes Up (0.3.20[.2]) 2011-04-03 14:00:46 Yes
217.157.1.202 kseistrup 217.157.1.202 Yes Up (0.3.20[.2]) 2011-04-03 14:00:46 ?
178.63.15.200 hendi 178.63.15.200 Yes Up (0.3.20[.1]) 2011-04-03 14:00:46 ?
bitcoin.sipa.be sipa 178.18.90.41 Yes Up (0.3.19[.2]) 2011-04-03 14:00:47 No
theymos.ath.cx theymos 99.27.237.13 ?? Up (0.3.19[.2]) 2011-04-03 14:00:47 Yes
fallback1.bitcoin.me.uk Vladimir 91.85.220.84 Yes Up (0.3.19) 2011-04-03 14:00:47 No
109.75.176.193 MagicalTux [DE] 109.75.176.193 Yes Up (0.3.19) 2011-04-03 14:00:47 No
173.224.125.222 MagicalTux [US] 173.224.125.222 Yes Up (0.3.19) 2011-04-03 14:00:47 No
bitlex.co.cc BitLex 78.34.69.123 No Up (0.3.19) 2011-04-03 14:00:52 Yes
74.82.216.10 thufir 74.82.216.10 Yes Up (0.3.10) 2011-04-03 14:00:52 Yes
74.57.236.239 ? 74.57.236.239 Yes Old (0.3.0) 2011-04-03 14:00:52 ?
84.114.155.197 sniffy 84.114.155.197 Yes Down 2011-04-03 02:00:05 Yes
178.63.62.15 MagicalTux [DE] 178.63.62.15 Yes Down 2011-04-03 13:00:13 No
zack.home.chrishowie.com cdhowie 0.0.0.0 No Down 2011-04-03 05:00:08 No

Tor nodes

Hostname Owner Status Last Seen (GMT) Accepts IP transactions
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 ? 2011-02-11 Yes
rnam4cxam62nkcyf.onion BitLex ? 2011-02-11 Yes
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

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 accept IP transactions you will have to add the -allowreceivebyip flag to your command line parameters.

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

Please note that a bot will connect to your node every hour to check its status and version.