Fallback Nodes: Difference between revisions
m New node (evolyn) |
m Tor node added |
||
Line 1: | Line 1: | ||
This is a list of nodes which are considered reliable | This is a list of nodes which are considered reliable. | ||
== How to use this list == | == How to use this list == | ||
Line 46: | Line 45: | ||
| x.jine.se || jine || 213.112.52.246 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes | | x.jine.se || jine || 213.112.52.246 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes | ||
|- | |- | ||
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} | | messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || | ||
<!-- END NODELIST --> | <!-- END NODELIST --> | ||
|} | |} | ||
Line 94: | Line 93: | ||
| x.jine.se || jine || 213.112.48.166 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes | | x.jine.se || jine || 213.112.48.166 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes | ||
|- | |- | ||
| www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} | | www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || | ||
|- | |- | ||
| ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} | | ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || | ||
|- | |- | ||
| coin.soul-dev.com || Soul-Dev | | coin.soul-dev.com || Soul-Dev || || || {{Fallback Nodes/Node Up}} || || | ||
|- | |- | ||
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} | | messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || | ||
|- | |- | ||
| btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes | | btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes | ||
Line 117: | Line 116: | ||
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions | ! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions | ||
|- | |- | ||
| bitcoin2u5jnjzzz.onion || anonymous || Up || 2014-01- | | evolynhit7shzeet.onion || Evolyn || Up || 2014-01-27 || Yes | ||
|- | |||
| bitcoin2u5jnjzzz.onion || anonymous || Up || 2014-01-27 || Yes | |||
|- | |- | ||
| btc4ulpftizx5b72.onion || TorNode || Up || 2013-05-10 || Yes | | btc4ulpftizx5b72.onion || TorNode || Up || 2013-05-10 || Yes |
Revision as of 23:34, 26 January 2014
This is a list of nodes which are considered reliable.
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 Bitcoin with a Tor hidden service, open a Terminal/Console and start it like this (where abcde.onion needs to be substituted with one of the Tor nodes below):
bitcoin-qt -proxy=127.0.0.1:9050 -connect=abcde.onion
You can find detailed information on running clients and hidden services within Tor in the documentation.
These parameters can be added to bitcoin.conf to make them permanent.
Nodes list
IPv6 Nodes
Hostname | Owner | IP | Fixed | Status | Last Seen (GMT) | Accepts IP transactions |
---|---|---|---|---|---|---|
InductiveSoul.US | Inductive Soul | 2601:7:6680:2ac:4d29:40ff:7513:fcc7 | Yes | Up () | 11-13-2013 (MDY) | Yes |
caffeinator.net | Atrophy | Up () | 2013-05-10 | |||
2001:470:8:2e1::40 | ? | 2001:470:8:2e1::40 | Yes | Down | Yes | |
x.jine.se | jine | 213.112.52.246 | No | Down | Yes | |
messier.bzfx.net | BZFX/A Meteorite | 2001:41d0:1:d632::1 | Yes | Up () |
IPv4 Nodes
Hostname | Owner | IP | Fixed | Status | Last Seen (GMT) | Accepts IP transactions |
---|---|---|---|---|---|---|
btcnode1.evolyn.net | Evolyn | 85.214.251.25 | Yes | Up () | 2014-01-26 | Yes |
InductiveSoul.US | Inductive Soul | 67.186.224.85 | Yes | Up () | 2013-11-13 | Yes |
archivum.info | Ferraro Ltd. | 88.198.58.172 | Yes | Up () | Yes | |
62.75.216.13 | exMULTI, Inc. | 62.75.216.13 | Yes | Down | No | |
69.64.34.118 | exMULTI, Inc. | 69.64.34.118 | Yes | Down | No | |
79.160.221.140 | K-Norway | 79.160.221.140 | Yes | Down | Yes | |
netzbasis.de | unknown3 | 81.169.129.25 | Yes | Down | Yes | |
btc.turboadmin.com | osmosis | 98.143.152.14 | Yes | Down | No | |
fallback.bitcoin.zhoutong.com | Zhou Tong | 117.121.241.140 | Yes | Down | No | |
bauhaus.csail.mit.edu | imsaguy | 128.30.96.44 | Yes | Down | Yes | |
jun.dashjr.org | Luke-Jr | 173.242.112.53 | Yes | Down | ||
cheaperinbitcoins.com | Xenland/Shane | 184.154.36.82 | 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 | |
btcnode.novit.ro | ovidiusoft - novit.ro | 93.187.142.114 | No | Down | Yes | |
porgressbar.sk | progressbar hackerspace | 91.210.181.21 | Yes | Up () | Yes | |
faucet.bitcoin.st | bitcoin street | 64.27.57.225 | Yes | Up () | Yes | |
bitcoin.securepayment.cc | SecurePayment CC | 63.247.147.163 | Yes | Up () | Yes | |
x.jine.se | jine | 213.112.48.166 | Yes | Up () | Yes | |
www.dcscdn.com | Danw12 | 199.115.228.181 | Yes | Up () | ||
ns2.dcscdn.com | Danw12 | 199.115.228.182 | Yes | Up () | ||
coin.soul-dev.com | Soul-Dev | Up () | ||||
messier.bzfx.net | BZFX/A Meteorite | 91.121.205.50 | Yes | Up () | ||
btcnode1.bitgroup.cc | BitGroup | 198.211.116.191 | Yes | Up () | Yes | |
btcnode2.bitgroup.cc | BitGroup | 162.243.120.138 | Yes | Up () | Yes | |
btcnode3.bitgroup.cc | BitGroup | 95.85.8.237 | Yes | Up () | 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 |
---|---|---|---|---|
evolynhit7shzeet.onion | Evolyn | Up | 2014-01-27 | Yes |
bitcoin2u5jnjzzz.onion | anonymous | Up | 2014-01-27 | Yes |
btc4ulpftizx5b72.onion | TorNode | Up | 2013-05-10 | Yes |
vso3r6cmjoomhhgg.onion | echelon | Up | 2013-05-10 | Yes |
yyl3ipdmyjkfypmx.onion | redemerald | Up | 2013-05-10 | Yes |
pqosrh6wfaucet32.onion | bitcoin street | Up | 2013-05-10 | No |
fpt6orohw2nuf2kn.onion | Tril | Up | 2013-05-10 | No |
e3tn727fywnioxrc.onion | Zedd | Up | 2013-05-10 | No |
6hgmaxwellgpv2oe.onion | Gmaxwell | Down | 2012-07-01 | No |
kjy2eqzk4zwi5zd3.onion | sipa | Up | 2013-05-10 | No |
siqdznszjf4e6v5j.onion | Tuxavant | Up | 2013-05-10 | ? |
sjdntqu5roj4q6lo.onion | torservers | Down | 2012-05-19 | ? |
bitcoin2bkgm3fke.onion | ? | Down | 2012-05-19 | Yes |
7hxvg2lvr2ashzli.onion | Tuxavant | Down | 2013-05-10 | ? |
j43z65b6r2usg3vk.onion | Dybbuk | Down | 2011-02-11 | Yes |
pvuif6nonbhj3o3r.onion | ? | Down | 2011-02-11 | Yes |
c5qvugpewwyyy5oz.onion | ? | Down | 2011-02-11 | Yes |
mutqcuh7hwxmhx3k.onion | Xirafe | Down | 2012-06-23 | ? |
ijzt2eeizty3p5xe.onion | ? | Down | 2011-02-11 | Yes |
r4de4zf4lyniu4mx.onion:8444 | ? | Down | 2012-06-26 | ? |
bitcoinprwwpuinm.onion:8333 | ? | Down | 2012-06-26 | ? |
x3danbeag2kyx644.onion | redemerald | Down | 2013-01-04 | Yes |
bitcoinbudtoeks7.onion | ? | Down | 2011-02-11 | ? |
iy6ni3wkqazp4ytu.onion | ? | Down | 2011-02-11 | ? |
h4kklwodpcmo6cbq.onion | ? | Down | 2011-02-11 | ? |
vv6kcfscuntybrzm.onion | ? | Down | 2011-02-11 | ? |
nlnsivjku4x4lu5n.onion | ? | Down | 2011-02-11 | ? |
xqzfakpeuvrobvpj.onion | ? | Down | 2010-11-13 | No |
4lmduyac3svgrrav.onion | ? | Down | 2011-02-11 | No |
usasx4urod3yj4az.onion | ? | ? | 2011-02-11 | 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
See Also
- Bitcoin Network
- Fallback Nodes List of longest running Bitcoin Nodes listed by Country.