Fallback Nodes: Difference between revisions
MagicalTux (talk | contribs) →IPv4 Nodes: Added Bitcoin Faucet IP |
MagicalTux (talk | contribs) →IPv4 Nodes: re-adding home |
||
| Line 67: | Line 67: | ||
|- | |- | ||
| 69.164.218.197 || Gavin Andresen | | 69.164.218.197 || Gavin Andresen | ||
|- | |||
| athome.xta.net || MagicalTux [JP] | |||
<!-- END NODELIST --> | <!-- END NODELIST --> | ||
|} | |} | ||
Revision as of 09:35, 24 December 2010
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 |
|---|---|---|---|---|---|---|
| bitcoin-otc.com | nanotube | 69.163.132.101 | Yes | Up (0.3.19) | 2010-12-24 09:00:03 | No |
| 91.121.222.175 | MagicalTux [FR] | 91.121.222.175 | Yes | Up (0.3.19) | 2010-12-24 09:00:03 | No |
| 109.75.176.193 | MagicalTux [DE] | 109.75.176.193 | Yes | Up (0.3.19) | 2010-12-24 09:00:03 | No |
| 174.120.185.74 | MagicalTux [US] | 174.120.185.74 | Yes | Up (0.3.19) | 2010-12-24 09:00:03 | No |
| 178.63.62.15 | MagicalTux [DE] | 178.63.62.15 | Yes | Up (0.3.19) | 2010-12-24 09:00:04 | No |
| ndrix.com | mndrix | 64.22.103.150 | ?? | Up (0.3.19) | 2010-12-24 09:00:04 | ? |
| lfmcal.dontexist.org | lfm | 75.158.131.108 | ?? | Up (0.3.19) | 2010-12-24 09:00:04 | Yes |
| bitlex.co.cc | BitLex | 78.34.68.114 | No | Up (0.3.19) | 2010-12-24 09:00:04 | Yes |
| mining.bitcoin.cz | slush_cz | 109.74.195.190 | Yes | Up (0.3.18) | 2010-12-24 09:00:04 | ? |
| pastecoin.com | genjix | 178.33.13.4 | Yes | Up (0.3.17[.4]) | 2010-12-24 09:00:05 | ? |
| artforz.ath.cx | ArtForz | 84.146.74.132 | No | Up (0.3.15[.4]) | 2010-12-24 09:00:05 | No |
| theymos.ath.cx | theymos | 99.27.237.13 | ?? | Up (0.3.14[.3]) | 2010-12-24 09:00:05 | Yes |
| 200.35.150.50 | rodin | 200.35.150.50 | Yes | Up (0.3.13) | 2010-12-24 09:00:05 | No |
| 74.82.216.10 | thufir | 74.82.216.10 | Yes | Up (0.3.10) | 2010-12-24 09:00:05 | Yes |
| 74.57.236.239 | ? | 74.57.236.239 | Yes | Old (0.3.0) | 2010-12-24 09:00:06 | ? |
| 69.164.218.197 | Gavin Andresen | |||||
| athome.xta.net | MagicalTux [JP] |
Tor nodes
| Hostname | Owner | Status | Last Seen (GMT) | Accepts IP transactions |
|---|---|---|---|---|
| ijzt2eeizty3p5xe.onion | ? | ? | 2010-11-13 | Yes |
| j43z65b6r2usg3vk.onion | Dybbuk | ? | 2010-11-13 | Yes |
| pvuif6nonbhj3o3r.onion | ? | ? | 2010-11-13 | Yes |
| c5qvugpewwyyy5oz.onion | ? | ? | 2010-11-13 | Yes |
| xqzfakpeuvrobvpj.onion | ? | ? | 2010-11-13 | No |
| vso3r6cmjoomhhgg.onion | echelon | ? | 2010-11-13 | Yes |
| rnam4cxam62nkcyf.onion | BitLex | ? | 2010-11-13 | Yes |
| lhkz56zqrjo3jsmp.onion | fuzzylogic | ? | 2010-11-14 | Yes |
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.