Fallback Nodes: Difference between revisions

From Bitcoin Wiki
Jump to navigation Jump to search
WikiBot (talk | contribs)
m Checked fallback nodes
BlueMatt (talk | contribs)
→‎Tor nodes: Goodbye, old friend.
 
Line 1: Line 1:
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 [[User:WikiBot|WikiBot]].
This is a list of nodes which are considered reliable.


== How to use this list ==
== How to use this list ==
Line 11: Line 11:
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.
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:
In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
  bitcoind -addnode=$(host ndrix.com |sed s/"^.*has address "//)
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 ===
=== 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.
[[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.


=== Tor network ===
=== Tor network ===


To use tor .onion addresses, you need to map virtual ips via the ''torrc'' file:
BitcoinCore will automatically use Tor if it is available at default (''127.0.0.1:9050''), to use Bitcoin-Qt over Tor hidden services '''only''', in a terminal/console enter:
bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor


  mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
To use Bitcoin with one specific Tor node, run
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
  bitcoin-qt -proxy=127.0.0.1:9050 -connect=abcde.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion
, where abcde.onion needs to be substituted with one of the [[Fallback_Nodes#Tor_nodes|Tor nodes below]]. These parameters can be added to [[Running_Bitcoin#Bitcoin.conf_Configuration_File|bitcoin.conf]] to make them permanent.


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.
More details on how to execute BitcoinCore with Tor see [[Setting_up_a_Tor_hidden_service|Setting up a Tor hidden service]]. You can find detailed information on running clients and hidden services within Tor in the [https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md documentation].


== Nodes list ==
== Nodes list ==


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


{|class="wikitable sortable"
{|class="wikitable sortable"
Line 36: Line 42:
|-
|-
<!-- BEGIN NODELIST -->
<!-- BEGIN NODELIST -->
| 46.4.13.200 || WakiMiko || 46.4.13.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-07-18 11:00:04 || ?
|-
|-
| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2011-07-17 12:00:08 || ?
| bitcoin.moneypot.com || [https://www.moneypot.com moneypot] || 212.47.228.216 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2015-09-15 || No
|-
| node.bitcoin.xxx || [http://www.bitcoin.xxx Bitcoin.xxx] || 66.228.49.201 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-08-28 || Yes
|-
| bitcoin.coinprism.com || [[Coinprism]] || 137.116.225.142 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-04-26 || Yes
|-
| btcnode1.evolyn.net || Evolyn || 85.214.251.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-01-26 || Yes
|-
| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 67.186.224.85 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2013-11-13 || Yes
|-
| archivum.info || Ferraro Ltd.|| 88.198.58.172 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2011-07-18 07:53:14 || No
| 62.75.216.13 || exMULTI, Inc. || 62.75.216.13 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
|-
| fallback2.bitcoin.me.uk || Vladimir [Pool] || 91.209.162.5 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || 2011-07-18 07:53:14 || No
| 69.64.34.118 || exMULTI, Inc. || 69.64.34.118 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
|-
| zack.home.chrishowie.com || cdhowie || 98.222.140.181 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || 2011-07-18 07:41:40 || No
| 79.160.221.140 || K-Norway || 79.160.221.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| netzbasis.de || unknown3 || 81.169.129.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| btc.turboadmin.com || osmosis || 98.143.152.14 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || No
|-
| fallback.bitcoin.zhoutong.com || Zhou Tong || 117.121.241.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || No
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| jun.dashjr.org || Luke-Jr || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2017-11-15 ||
|-
| cheaperinbitcoins.com || Xenland/Shane || 184.154.36.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| django.webflows.fr || unknown2 || 188.165.213.169 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value No}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| porgressbar.sk || progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| faucet.bitcoin.st || bitcoin street || 64.27.57.225 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| bitcoin.securepayment.cc || SecurePayment CC || 63.247.147.163 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  ||
|-
| ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  ||
|-
| coin.soul-dev.com || Soul-Dev || || || {{Fallback Nodes/Node Down}} ||  ||
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  ||
|-
| btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| btcnode2.bitgroup.cc || BitGroup || 162.243.120.138 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| btcnode3.bitgroup.cc || BitGroup || 95.85.8.237 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
|-
| btcnode.xiro.co || Xiro Labs || 91.121.108.61 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2017-11-15 || No
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 185.122.57.203 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| bitcoin.bitdonut.co || James Hartig ||  ||  || {{Fallback Nodes/Node Down}} ||  ||
|-
| coinno.de  || jaknam ||  ||  || {{Fallback Nodes/Node Down}} ||  ||
|-
| 82.165.44.44 || anonymous ||  ||  || {{Fallback Nodes/Node Down}} ||  ||
|-
| bitcoin1.dassori.me || gdassori ||  ||  || {{Fallback Nodes/Node Down}} ||  ||
|-
| bitcoin2.dassori.me || gdassori ||  ||  || {{Fallback Nodes/Node Down}} ||  ||
|-
| blockchainnode.meulie.net || [[User:Evert|Evert]] ||  ||  || {{Fallback Nodes/Node Up}} || 2017-11-15 ||
|-
| fullnode.fybsg.com || Nagato ||  ||  || {{Fallback Nodes/Node Down}} ||  ||
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 62.210.66.227 ||  || {{Fallback Nodes/Node Up}} || 2017-11-15 ||
|-
| homeplex.tk || [[User:Victorsueca|Victorsueca]] || 90.165.120.190 ||  || {{Fallback Nodes/Node Down}} ||  ||
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || 91.121.83.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} ||  || Yes
<!-- END NODELIST -->
<!-- END NODELIST -->
|}
|}


=== Tor nodes ===
=== IPv6 Nodes ===
 
{|class="wikitable sortable"
{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-02-11 || Yes
<!-- BEGIN NODELIST -->
| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 2601:7:6680:2ac:4d29:40ff:7513:fcc7 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 11-13-2013 (MDY) || Yes
|-
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-02-11 || Yes
| caffeinator.net || [[User:Atrophy|Atrophy]] || ||  || {{Fallback Nodes/Node Up}} || 2013-05-10 ||
|-
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-02-11 || Yes
| 2001:470:8:2e1::40 || ? || 2001:470:8:2e1::40 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-02-11 || Yes
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-02-11 || Yes
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 2a06:8ec0:3::1:2e47 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} ||  || No
|-
|-
| bitcoinbudtoeks7.onion || ? || ? || 2011-02-11 || ?
| bitcoin.bitdonut.co || James Hartig ||  || || || ||
|-
|-
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-02-11 || ?
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 2001:bc8:c087:2001::1 ||  ||  ||  ||
|-
|-
| h4kklwodpcmo6cbq.onion || ? || ? || 2011-02-11 || ?
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || || || || ||
|-
<!-- END NODELIST -->
| vv6kcfscuntybrzm.onion || ? || ? || 2011-02-11 || ?
|}
|-
 
| nlnsivjku4x4lu5n.onion || ? || ? || 2011-02-11 || ?
=== Tor nodes ===
 
This entire list was last checked on 2022-07-25.
 
{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
| pcxlvkgabsowmrx54b5bgqglershgfchr6xavrhbfngridplzhf2pwqd.onion || BlueMatt || Up || 2022-07-25 || No
|-
| 4lmduyac3svgrrav.onion || ? || ? || 2011-02-11 || No
|-
| usasx4urod3yj4az.onion || ? || ? || 2011-02-11 || No
|}
|}


== Adding a node ==
== 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.
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 <tt>END NODELIST</tt> line:
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 <tt>END NODELIST</tt> line:
Line 89: Line 167:
| ip || your name</nowiki>
| ip || your name</nowiki>


Please note that a bot will connect to your node every hour to check its status and version.
==See Also==
 
* [[Network|Bitcoin Network]]
* [http://nodes.bitcoin.st Fallback Nodes] List of longest running Bitcoin Nodes listed by Country.
* [https://getaddr.bitnodes.io/ Bitnodes project]
* [https://blockchain.info/connected-nodes Recently connected nodes at blockchain.info]
 
{{Bitcoin Core documentation}}

Latest revision as of 05:44, 25 July 2022

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

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.

Tor network

BitcoinCore will automatically use Tor if it is available at default (127.0.0.1:9050), to use Bitcoin-Qt over Tor hidden services only, 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.

More details on how to execute BitcoinCore with Tor see Setting up a Tor hidden service. You can find detailed information on running clients and hidden services within Tor in the documentation.

Nodes list

IPv4 Nodes

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

Hostname Owner IP Fixed Status Last Seen (GMT) Accepts IP transactions
bitcoin.moneypot.com moneypot 212.47.228.216 Yes Down 2015-09-15 No
node.bitcoin.xxx Bitcoin.xxx 66.228.49.201 Yes Down 2014-08-28 Yes
bitcoin.coinprism.com Coinprism 137.116.225.142 Yes Down 2014-04-26 Yes
btcnode1.evolyn.net Evolyn 85.214.251.25 Yes Down 2014-01-26 Yes
InductiveSoul.US Inductive Soul 67.186.224.85 Yes Down 2013-11-13 Yes
archivum.info Ferraro Ltd. 88.198.58.172 Yes Down 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 Up () 2017-11-15
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 Down Yes
faucet.bitcoin.st bitcoin street 64.27.57.225 Yes Down Yes
bitcoin.securepayment.cc SecurePayment CC 63.247.147.163 Yes Down Yes
www.dcscdn.com Danw12 199.115.228.181 Yes Down
ns2.dcscdn.com Danw12 199.115.228.182 Yes Down
coin.soul-dev.com Soul-Dev Down
messier.bzfx.net BZFX/A Meteorite 91.121.205.50 Yes Down
btcnode1.bitgroup.cc BitGroup 198.211.116.191 Yes Down Yes
btcnode2.bitgroup.cc BitGroup 162.243.120.138 Yes Down Yes
btcnode3.bitgroup.cc BitGroup 95.85.8.237 Yes Down Yes
btcnode.xiro.co Xiro Labs 91.121.108.61 Yes Up () 2017-11-15 No
stuff.liam-w.io Liam W 185.122.57.203 Yes Down No
bitcoin.bitdonut.co James Hartig Down
coinno.de jaknam Down
82.165.44.44 anonymous Down
bitcoin1.dassori.me gdassori Down
bitcoin2.dassori.me gdassori Down
blockchainnode.meulie.net Evert Up () 2017-11-15
fullnode.fybsg.com Nagato Down
n.bitcoin-fr.io Arthur 62.210.66.227 Up () 2017-11-15
homeplex.tk Victorsueca 90.165.120.190 Down
mars.jordandoyle.uk Jordan Doyle 91.121.83.82 Yes Down Yes

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
messier.bzfx.net BZFX/A Meteorite 2001:41d0:1:d632::1 Yes Up ()
stuff.liam-w.io Liam W 2a06:8ec0:3::1:2e47 Yes Up () No
bitcoin.bitdonut.co James Hartig
n.bitcoin-fr.io Arthur 2001:bc8:c087:2001::1
mars.jordandoyle.uk Jordan Doyle

Tor nodes

This entire list was last checked on 2022-07-25.

Hostname Owner Status Last Seen (GMT) Accepts IP transactions
pcxlvkgabsowmrx54b5bgqglershgfchr6xavrhbfngridplzhf2pwqd.onion BlueMatt Up 2022-07-25 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