Bitcoin Wiki - User contributions [en]

Fallback Nodes

2012-09-17T01:14:08Z

Echelon: /* Tor nodes */

This is a list of nodes which are considered reliable. <del>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]] </del>.
'''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 ([[Fallback_Nodes#Tor_nodes|listed below]]), you will need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 vso3r6cmjoomhhgg.onion
mapaddress 192.0.2.3 sjdntqu5roj4q6lo.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

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.

If you would like to use these nodes in addition to the hard-coded node list in the client, you can substitute "connect" with "addnode". However, if you want to keep all your Bitcoin communication strictly within the Tor network, it is recommended that you use "connect."

Additional suggested settings for hidden node operators:

noirc=1
upnp=0
listen=1

== Nodes list ==

=== IPv6 Nodes ===
{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| 2001:470:8:2e1::40 || ? || 2001:470:8:2e1::40 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-


|}

=== IPv4 Nodes ===
'''Wikibot is currently malfunctioning and is incorrectly marking nodes running 0.6 as being down'''.
{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| 62.75.216.13 || exMULTI, Inc. || 62.75.216.13 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 69.64.34.118 || exMULTI, Inc. || 69.64.34.118 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || 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 Down}} || ||
|-
| 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 Up}} || || Yes
|-
| faucet.bitcoin.st || bitcoin street || 64.27.57.225 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes

|}

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

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| 6hgmaxwellgpv2oe.onion|| Gmaxwell || up || 2012-07-01 || No
|-
| pqosrh6wfaucet32.onion|| bitcoin street || up || 2012-08-29 || No
|-
| btc4ulpftizx5b72.onion || TorNode || up || 2012-06-22 || Yes
|-
| 7hxvg2lvr2ashzli.onion || Tuxavant || up || 2012-06-23 || ?
|-
| siqdznszjf4e6v5j.onion || Tuxavant || up || 2012-06-23 || ?
|-
| fpt6orohw2nuf2kn.onion || Tril || up || 2012-06-23 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || up || 2012-09-16 || Yes
|-
| sjdntqu5roj4q6lo.onion || torservers || up || 2012-05-19 || ?
|-
| bitcoin2bkgm3fke.onion || ? || down || 2012-05-19 || 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
|-
| 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
|-
| e3tn727fywnioxrc.onion || ? || ? || 2011-11-01 || No
|-
| p2hwc26zdsrqxiix.onion || redemerald || down || 2012-05-25 || No
|-
| bxfna6fhddpzduck.onion || ? || ? || ? || ?
|-
| kjy2eqzk4zwi5zd3.onion || sipa || up || 2012-06-23 || No
|-
| mutqcuh7hwxmhx3k.onion || Xirafe || up || 2012-06-23 || ?
|-
| r4de4zf4lyniu4mx.onion:8444 || ? || up || 2012-06-26 || ?
|-
| bitcoinprwwpuinm.onion:8333 || ? || up || 2012-06-26 || ?
|}

== 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

==See Also==

* [[Network|Bitcoin Network]]
* [http://nodes.bitcoin.st Fallback Nodes] List of longest running Bitcoin Nodes listed by Country.

Fallback Nodes

2012-05-19T17:37:57Z

Echelon: Updated last seen date

This is a list of nodes which are considered reliable. <del>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]] </del>.
'''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 ([[Fallback_Nodes#Tor_nodes|listed below]]), you will need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 vso3r6cmjoomhhgg.onion
mapaddress 192.0.2.3 sjdntqu5roj4q6lo.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

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.

If you would like to use these nodes in addition to the hard-coded node list in the client, you can substitute "connect" with "addnode". However, if you want to keep all your Bitcoin communication strictly within the Tor network, it is recommended that you use "connect."

Additional suggested settings for hidden node operators:

noirc=1
upnp=0
listen=1

== Nodes list ==

=== IPv4 Nodes ===
'''Wikibot is currently malfunctioning and is incorrectly marking nodes running 0.6 as being down'''.
{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| li111-4.members.linode.com || unknown || 69.164.196.4 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2012-05-19 12:00:03 || Yes
|-
| 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
|-
| progressbar.sk || Progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 178.32.7.171 || temporary-april-2012 || 178.32.7.171 || {{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

|}

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

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| 7hxvg2lvr2ashzli.onion || Tuxavant || up || 2012-05-19 || ?
|-
| siqdznszjf4e6v5j.onion || Tuxavant || up || 2012-05-19 || ?
|-
| fpt6orohw2nuf2kn.onion || Tril || up || 2012-05-19 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || up || 2012-05-19 || Yes
|-
| sjdntqu5roj4q6lo.onion || torservers || up || 2012-05-19 || ?
|-
| bitcoin2bkgm3fke.onion || ? || down || 2012-05-19 || 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
|-
| 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
|}

== 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Fallback Nodes

2012-05-19T17:34:28Z

Echelon: Updated last seen date

This is a list of nodes which are considered reliable. <del>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]] </del>.
'''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 ([[Fallback_Nodes#Tor_nodes|listed below]]), you will need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 vso3r6cmjoomhhgg.onion
mapaddress 192.0.2.3 sjdntqu5roj4q6lo.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

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.

If you would like to use these nodes in addition to the hard-coded node list in the client, you can substitute "connect" with "addnode". However, if you want to keep all your Bitcoin communication strictly within the Tor network, it is recommended that you use "connect."

Additional suggested settings for hidden node operators:

noirc=1
upnp=0
listen=1

== Nodes list ==

=== IPv4 Nodes ===
'''Wikibot is currently malfunctioning and is incorrectly marking nodes running 0.6 as being down'''.
{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| li111-4.members.linode.com || unknown || 69.164.196.4 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2012-05-19 12:00:03 || Yes
|-
| 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
|-
| progressbar.sk || Progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 178.32.7.171 || temporary-april-2012 || 178.32.7.171 || {{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

|}

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

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| esvua6k2gzjj64ad.onion || redemerald || ? || 2011-12-28 || No
|-
| 7hxvg2lvr2ashzli.onion || Tuxavant || up || 2012-05-19 || ?
|-
| siqdznszjf4e6v5j.onion || Tuxavant || up || 2012-05-19 || ?
|-
| fpt6orohw2nuf2kn.onion || Tril || up || 2012-05-19 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || up || 2012-05-19 || Yes
|-
| sjdntqu5roj4q6lo.onion || torservers || up || 2012-05-19 || ?
|-
| bitcoin2bkgm3fke.onion || ? || down || 2012-05-19 || 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
|-
| 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 || ? || ? || ? || ?
|}

== 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Fallback Nodes

2012-05-19T17:17:33Z

Echelon: Updated note status

This is a list of nodes which are considered reliable. <del>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]] </del>.
'''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 ([[Fallback_Nodes#Tor_nodes|listed below]]), you will need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 vso3r6cmjoomhhgg.onion
mapaddress 192.0.2.3 sjdntqu5roj4q6lo.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

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.

If you would like to use these nodes in addition to the hard-coded node list in the client, you can substitute "connect" with "addnode". However, if you want to keep all your Bitcoin communication strictly within the Tor network, it is recommended that you use "connect."

Additional suggested settings for hidden node operators:

noirc=1
upnp=0
listen=1

== Nodes list ==

=== IPv4 Nodes ===
'''Wikibot is currently malfunctioning and is incorrectly marking nodes running 0.6 as being down'''.
{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| li111-4.members.linode.com || unknown || 69.164.196.4 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2012-05-19 12:00:03 || Yes
|-
| 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
|-
| progressbar.sk || Progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 178.32.7.171 || temporary-april-2012 || 178.32.7.171 || {{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

|}

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

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| bitcoin2bkgm3fke.onion || ? || down || 2012-05-19 || 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 || 2012-05-19 || Yes
|-
| sjdntqu5roj4q6lo.onion || torservers || up || 2012-05-19 || ?
|-
| 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Fallback Nodes

2012-05-19T17:06:31Z

Echelon: Updated explanation for using addnode

This is a list of nodes which are considered reliable. <del>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]] </del>.
'''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 ([[Fallback_Nodes#Tor_nodes|listed below]]), you will need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 vso3r6cmjoomhhgg.onion
mapaddress 192.0.2.3 sjdntqu5roj4q6lo.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

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.

If you would like to use these nodes in addition to the hard-coded node list in the client, you can substitute "connect" with "addnode". However, if you want to keep all your Bitcoin communication strictly within the Tor network, it is recommended that you use "connect."

Additional suggested settings for hidden node operators:

noirc=1
upnp=0
listen=1

== Nodes list ==

=== IPv4 Nodes ===
'''Wikibot is currently malfunctioning and is incorrectly marking nodes running 0.6 as being down'''.
{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| li111-4.members.linode.com || unknown || 69.164.196.4 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2012-05-19 12:00:03 || Yes
|-
| 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
|-
| progressbar.sk || Progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 178.32.7.171 || temporary-april-2012 || 178.32.7.171 || {{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

|}

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

=== Tor nodes ===

{|class="wikitable sortable"
! 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Fallback Nodes

2012-05-19T16:52:54Z

Echelon: /* Tor network */

This is a list of nodes which are considered reliable. <del>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]] </del>.
'''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 ([[Fallback_Nodes#Tor_nodes|listed below]]), you will need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 vso3r6cmjoomhhgg.onion
mapaddress 192.0.2.3 sjdntqu5roj4q6lo.onion

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

addnode=192.0.2.2
addnode=192.0.2.3

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.

Additional suggested settings for hidden node operators:

noirc=1
upnp=0
listen=1

== Nodes list ==

=== IPv4 Nodes ===
'''Wikibot is currently malfunctioning and is incorrectly marking nodes running 0.6 as being down'''.
{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| li111-4.members.linode.com || unknown || 69.164.196.4 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2012-05-19 12:00:03 || Yes
|-
| 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
|-
| progressbar.sk || Progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 178.32.7.171 || temporary-april-2012 || 178.32.7.171 || {{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

|}

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

=== Tor nodes ===

{|class="wikitable sortable"
! 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Fallback Nodes

2012-04-19T19:43:54Z

Echelon: /* Tor nodes */

This is a list of nodes which are considered reliable. <del>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]] </del>.
'''Wikibot is currently malfunctioning and is incorrectly marking all the nodes 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 ([[Fallback_Nodes#Tor_nodes|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 all the nodes as being down'''.
{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| 66.158.72.2 || imsaguy || 66.158.72.2 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| coin.soul-dev.com || Soul-Dev || 70.57.156.45 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 178.32.7.171 || temporary-april-2012 || 178.32.7.171 || {{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
|-
| progressbar.sk || Progressbar hackerspace || 91.210.181.21 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes

|}

=== Tor nodes ===

{|class="wikitable sortable"
! 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 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Please note that a bot is supposed to connect to your node every hour to check its status and version. Sadly, this bot appears to be offline.

Fallback Nodes

2012-04-19T19:41:55Z

Echelon: /* Tor network */

This is a list of nodes which are considered reliable. <del>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]] </del>.
'''Wikibot is currently malfunctioning and is incorrectly marking all the nodes 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 ([[Fallback_Nodes#Tor_nodes|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 all the nodes as being down'''.
{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| 66.158.72.2 || imsaguy || 66.158.72.2 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| coin.soul-dev.com || Soul-Dev || 70.57.156.45 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 178.32.7.171 || temporary-april-2012 || 178.32.7.171 || {{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
|-
| progressbar.sk || Progressbar hackerspace || 91.210.181.21 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes

|}

=== Tor nodes ===

{|class="wikitable sortable"
! 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 || ? || 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 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Please note that a bot is supposed to connect to your node every hour to check its status and version. Sadly, this bot appears to be offline.

Fallback Nodes

2012-02-17T01:06:36Z

Echelon: Hidden service seed nodes not supported since Bitcoin 0.5

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]].

== 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 ([[Fallback_Nodes#Tor_nodes|listed below]]), 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

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, or see phantomcircuit's [https://github.com/phantomcircuit/bitcoin-alt bitcoin-alt].

== Nodes list ==

=== IPv4 Nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| BitcoinStats.org || Atheros || 75.186.58.44 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.6.0}} || 2012-02-17 01:00:04 || No
|-
| 46.182.18.245 || ? || 46.182.18.245 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.5.2}} || 2012-02-17 01:00:04 || ?
|-
| 98.143.152.14 || osmosis || 98.143.152.14 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.5.2}} || 2012-02-17 01:00:05 || ?
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.5.2}} || 2012-02-17 01:00:05 || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.5.1}} || 2012-02-17 01:00:05 || ?
|-
| 173.66.83.171 || bitcoin debit || 173.66.83.171 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.5.0[.1]}} || 2012-02-17 01:00:05 || ?
|-
| coin.soul-dev.com || Soul-Dev || 70.57.156.45 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.4.0}} || 2012-02-17 01:00:06 || ?

|}

=== Tor nodes ===

{|class="wikitable sortable"
! 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 || ? || 2011-02-11 || Yes
|-
| sjdntqu5roj4q6lo.onion || torservers || up || 2012-01-11 || ?
|-
| 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 || ? || 2011-12-28 || No
|-
| bxfna6fhddpzduck.onion || ? || ? || ? || ?
|-
| esvua6k2gzjj64ad.onion || redemerald || ? || 2011-12-28 || 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Please note that a bot is supposed to connect to your node every hour to check its status and version. Sadly, this bot appears to be offline.

Talk:Tor

2011-02-25T00:35:59Z

Echelon: Moved proposal to top of page

== Proposal to rename/split Tor page ==

Much of the content here details information that is irrelevant to the subject of Bitcoin. I propose we create a separate wiki page for "Freenode" as that is what the main topic appears to be. We can keep a Tor page for issues related to Tor/Bitcoin and hidden service fallback nodes.

As an aside note we ought to, at the very least, trim down the mIRC section. It is after all, a shareware product. There are more appropriate free open source alternatives that already have SASL support built-in or have implementations that are not broken.

== Tor + Firefox ==

I recommend to start with the Vidalia Bundle.
There Tor comes with a graphical control centre + Tor button for Firefox.
the Tor button is a plugin that allows you with 1 click to turn on/off the Tor routing for Firefox.

== Tor + Bitcoin ==

using Bitcoin with Tor is easy. All you need is to check the proxy option. The predefined values in Bitcoin match the Tor settings. As Bitcoin only saves from & to addresses (and no IP addresses), you should be pretty safe. Tor however does not fix the traceability of BTC from one address to other.

== Tor + IRC (mIRC) ==

This is worked for me on two different computers, drop me a message on Bitcoin forum if you need help.

== additional content? ==

some user started creating a tor page under his user space:
https://en.bitcoin.it/wiki/User:Sawzall/Tor

maybe there's some stuff you guys can pull in from there...

also, xchat instructions for using over tor can be nice to have too. not everyone uses mirc, you know. :)

--[[User:Nanotube|Nanotube]] 05:39, 9 January 2011 (GMT)

There's a bounty for the article at http://www.bitcoin.org/smf/index.php?topic=2602
Thanks for the link to Sawzall's Tor page. I did not know that.
I shouldn't probably edit directly the main article either and should write it in my user space first.
I have no wiki writing habbits :(
As for the xchat, I do not do IRC since I left school and installed it after 7 years only to write the Freenode + Tor + SASL howto.

--[[User:Ptmhd|Ptmhd]] 18:20, 12 January 2011 (GMT)

== hidden services ==

rather than trying to keep a separate list of bitcoind as hidden services, it's probably better to link to the existing list of [[fallback nodes]], which already has a few tor hidden services listed.

In addition, the bitcoin client does not resolve dns, so if you have any nodes added whose dns/.onion addresses are not resolved the connection will fail. You can find an explanation and instructions here http://www.bitcoin.org/smf/index.php?topic=59.0;all#msg14635

== Configuration tips ==

In torrc:
CircuitBuildTimeout 30 #Picks faster nodes
LearnCircuitBuildTimeout 0 #Enables the above setting
MaxCircuitDirtiness 1200 #The number of seconds between each enforced IP change.
#Increasing it can be good in some cases.
WarnUnsafeSocks 0 #Tor doesn't like the way Bitcoin makes requests, and spams
#the log about it. This stops that behavior.

* Privoxy is better than Polipo in every way. It has powerful privacy-assisting options (some disabled by default), and it can almost replace Torbutton on non-Firefox browsers. Firefox doesn't need Privoxy ''or'' Polipo because it can handle SOCKS5 natively.
* The most secure browser configuration is Firefox + Torbutton. You must use either Privoxy or Torbutton.
* Use standalone Tor, which outputs Tor's log to a console. ''Nearly all problems can be quickly solved by looking at the log.''
* The official Vidalia bundles install two torrc files in different locations. One of these is useless. (Can't remember which one.)

Summary: The Tor bundles suck. [[User:Theymos|theymos]] 09:21, 9 January 2011 (GMT)

* for the benefit of all users that run windows, would like to use Bitcoin client + IRC + browse the web via Tor, what would you recommend?
[[User:Ptmhd|Ptmhd]] 23:42, 12 January 2011 (GMT+1)
::Just download the expert bundle, make the torrc modifications I suggested (except the MaxCircuitDirtiness one), run it, and connect Bitcoin to localhost:9050. Same for IRC. If having the Tor window open all the time annoys you, minimize it to the tray with [http://www.abstractpath.com/powermenu/ PowerMenu]. There are also command-line options to tor.exe that [https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#HowdoIrunmyTorrelayasanNTservice create a Tor NT service] -- this is a good idea if you run Tor constantly.

::I never tried using IRC over Tor, so I can't recommend any particular IRC client. As a general rule, however, programs meant to be [http://portableapps.com/ portable] provide better anonymity.

::For browsing, download [http://portableapps.com/apps/internet/firefox_portable Firefox Portable] and install [https://addons.mozilla.org/en-US/firefox/addon/2275/ Torbutton] on it. Privoxy/Polipo are not necessary. [[User:Theymos|theymos]] 08:45, 13 January 2011 (GMT)

Talk:Tor

2011-02-25T00:29:03Z

Echelon: /* Proposal to rename/split Tor page */ new section

== Tor + Firefox ==

I recommend to start with the Vidalia Bundle.
There Tor comes with a graphical control centre + Tor button for Firefox.
the Tor button is a plugin that allows you with 1 click to turn on/off the Tor routing for Firefox.

== Tor + Bitcoin ==

using Bitcoin with Tor is easy. All you need is to check the proxy option. The predefined values in Bitcoin match the Tor settings. As Bitcoin only saves from & to addresses (and no IP addresses), you should be pretty safe. Tor however does not fix the traceability of BTC from one address to other.

== Tor + IRC (mIRC) ==

This is worked for me on two different computers, drop me a message on Bitcoin forum if you need help.

== additional content? ==

some user started creating a tor page under his user space:
https://en.bitcoin.it/wiki/User:Sawzall/Tor

maybe there's some stuff you guys can pull in from there...

also, xchat instructions for using over tor can be nice to have too. not everyone uses mirc, you know. :)

--[[User:Nanotube|Nanotube]] 05:39, 9 January 2011 (GMT)

There's a bounty for the article at http://www.bitcoin.org/smf/index.php?topic=2602
Thanks for the link to Sawzall's Tor page. I did not know that.
I shouldn't probably edit directly the main article either and should write it in my user space first.
I have no wiki writing habbits :(
As for the xchat, I do not do IRC since I left school and installed it after 7 years only to write the Freenode + Tor + SASL howto.

--[[User:Ptmhd|Ptmhd]] 18:20, 12 January 2011 (GMT)

== hidden services ==

rather than trying to keep a separate list of bitcoind as hidden services, it's probably better to link to the existing list of [[fallback nodes]], which already has a few tor hidden services listed.

In addition, the bitcoin client does not resolve dns, so if you have any nodes added whose dns/.onion addresses are not resolved the connection will fail. You can find an explanation and instructions here http://www.bitcoin.org/smf/index.php?topic=59.0;all#msg14635

== Configuration tips ==

In torrc:
CircuitBuildTimeout 30 #Picks faster nodes
LearnCircuitBuildTimeout 0 #Enables the above setting
MaxCircuitDirtiness 1200 #The number of seconds between each enforced IP change.
#Increasing it can be good in some cases.
WarnUnsafeSocks 0 #Tor doesn't like the way Bitcoin makes requests, and spams
#the log about it. This stops that behavior.

* Privoxy is better than Polipo in every way. It has powerful privacy-assisting options (some disabled by default), and it can almost replace Torbutton on non-Firefox browsers. Firefox doesn't need Privoxy ''or'' Polipo because it can handle SOCKS5 natively.
* The most secure browser configuration is Firefox + Torbutton. You must use either Privoxy or Torbutton.
* Use standalone Tor, which outputs Tor's log to a console. ''Nearly all problems can be quickly solved by looking at the log.''
* The official Vidalia bundles install two torrc files in different locations. One of these is useless. (Can't remember which one.)

Summary: The Tor bundles suck. [[User:Theymos|theymos]] 09:21, 9 January 2011 (GMT)

* for the benefit of all users that run windows, would like to use Bitcoin client + IRC + browse the web via Tor, what would you recommend?
[[User:Ptmhd|Ptmhd]] 23:42, 12 January 2011 (GMT+1)
::Just download the expert bundle, make the torrc modifications I suggested (except the MaxCircuitDirtiness one), run it, and connect Bitcoin to localhost:9050. Same for IRC. If having the Tor window open all the time annoys you, minimize it to the tray with [http://www.abstractpath.com/powermenu/ PowerMenu]. There are also command-line options to tor.exe that [https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#HowdoIrunmyTorrelayasanNTservice create a Tor NT service] -- this is a good idea if you run Tor constantly.

::I never tried using IRC over Tor, so I can't recommend any particular IRC client. As a general rule, however, programs meant to be [http://portableapps.com/ portable] provide better anonymity.

::For browsing, download [http://portableapps.com/apps/internet/firefox_portable Firefox Portable] and install [https://addons.mozilla.org/en-US/firefox/addon/2275/ Torbutton] on it. Privoxy/Polipo are not necessary. [[User:Theymos|theymos]] 08:45, 13 January 2011 (GMT)

== Proposal to rename/split Tor page ==

Much of the content here details information that is irrelevant to the subject of Bitcoin. I propose we create a separate wiki page for "Freenode" as that is what the main topic appears to be. We can keep a Tor page for issues related Tor and Bitcoin and hidden service fallback nodes.

As an aside note we ought to, at the very least, trim down the mIRC section. It is after all, a shareware product. There are more appropriate free open source alternatives that already have SASL support built-in or have implementations that are not broken.

Talk:Tor

2011-02-22T05:01:08Z

Echelon: /* hidden services */

MyBitcoin

2011-02-18T20:34:15Z

Echelon: Added additional reference

'''MyBitcoin''' is one of the earliest [[eWallet]] providers for Bitcoin. See [[MyBitcoin SCI]] if you're looking for information on how to use MyBitcoin merchant service.

Bitcoins sent from a MyBitcoin account will not necessarily originate from the same [[Address|bitcoin addresses]] that were used to receive the Bitcoins. This property can be utilised to improve [[Anonymity|anonymity]].

==Features==
*Address forwarding - Anything earned in your mybitcoin account can be transfered automatically to a desired address.
==External links==
*[https://www.mybitcoin.com/ MyBitcoin site]
==Notice==
'''Alert''': As of 02-17-2011, deposits to the mybitcoin.com eWallet service are not being registered to users' accounts.<ref>[http://www.bitcoin.org/smf/index.php?topic=3592.msg50924#msg50924 MyBitcoin & Bitcoin2cc Problems]</ref><ref>[http://www.bitcoin.org/smf/index.php?topic=3598.0 Online wallet]</ref> Do not use the eWallet feature until further notice.

==References==
<references />

[[Category:Services]]
[[Category:eWallets]]

MyBitcoin

2011-02-18T20:28:45Z

Echelon:

'''MyBitcoin''' is one of the earliest [[eWallet]] providers for Bitcoin. See [[MyBitcoin SCI]] if you're looking for information on how to use MyBitcoin merchant service.

Bitcoins sent from a MyBitcoin account will not necessarily originate from the same [[Address|bitcoin addresses]] that were used to receive the Bitcoins. This property can be utilised to improve [[Anonymity|anonymity]].

==Features==
*Address forwarding - Anything earned in your mybitcoin account can be transfered automatically to a desired address.
==External links==
*[https://www.mybitcoin.com/ MyBitcoin site]
==Notice==
'''Alert''': As of 02-17-2011, deposits to the mybitcoin.com eWallet service are not being registered to users' accounts.<ref>[http://www.bitcoin.org/smf/index.php?topic=3592.msg50924#msg50924 MyBitcoin & Bitcoin2cc Problems]</ref> Do not use the eWallet feature until further notice.

==References==
<references />
# [http://www.bitcoin.org/smf/index.php?topic=3598.0 Online wallet]

[[Category:Services]]
[[Category:eWallets]]

MyBitcoin

2011-02-18T19:26:28Z

Echelon:

'''MyBitcoin''' is one of the earliest [[eWallet]] providers for Bitcoin. See [[MyBitcoin SCI]] if you're looking for information on how to use MyBitcoin merchant service.

Bitcoins sent from a MyBitcoin account will not necessarily originate from the same [[Address|bitcoin addresses]] that were used to receive the Bitcoins. This property can be utilised to improve [[Anonymity|anonymity]].

==Features==
*Address forwarding - Anything earned in your mybitcoin account can be transfered automatically to a desired address.
==External links==
*[https://www.mybitcoin.com/ MyBitcoin site]
==Notice==
'''Alert''': As of 02-17-2011, deposits to the mybitcoin.com eWallet service are not being registered to users' accounts. Do not use the eWallet feature until further notice.
[[Category:Services]]
[[Category:eWallets]]

Fallback Nodes

2011-02-11T20:28:52Z

Echelon: /* IPv4 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 [[User:WikiBot|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 ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| bitcoin-otc.com || nanotube || 69.163.132.101 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20}} || 2011-02-11 20:00:08 || No
|-
| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20}} || 2011-02-11 20:00:08 || ?
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-02-11 20:00:08 || Yes
|-
| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 20:00:08 || ?
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 20:00:13 || No
|-
| bitcoins.ca || humble || 142.58.248.28 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 20:00:13 || Yes
|-
| 174.120.185.74 || MagicalTux [US] || 174.120.185.74 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 20:00:13 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 20:00:13 || No
|-
| lfmcal.dontexist.org || lfm || 75.158.131.108 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 20:00:13 || Yes
|-
| bitlex.co.cc || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 20:00:14 || Yes
|-
| pastecoin.com || genjix || 109.75.176.48 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.17[.4]}} || 2011-02-11 20:00:14 || ?
|-
| artforz.ath.cx || ArtForz || 93.199.125.213 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.15[.4]}} || 2011-02-11 20:00:14 || No
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-02-11 20:00:15 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-02-11 20:00:15 || ?
|-
| fallback.bitcoin.me.uk || Vladimir || 91.85.220.84 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2011-02-11 18:00:06 || No
|-
| lyasoff.com || ? || 200.35.150.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2011-02-11 20:00:14 || ?

|}

=== Tor nodes ===

{|class="wikitable sortable"
! 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

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

Fallback Nodes

2011-02-11T18:33:35Z

Echelon: /* Tor 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 [[User:WikiBot|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 ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| bitcoin-otc.com || nanotube || 69.163.132.101 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20}} || 2011-02-11 18:00:04 || No
|-
| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20}} || 2011-02-11 18:00:04 || ?
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-02-11 18:00:04 || Yes
|-
| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 18:00:04 || ?
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 18:00:05 || No
|-
| bitcoins.ca || humble || 142.58.248.28 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 18:00:05 || Yes
|-
| 174.120.185.74 || MagicalTux [US] || 174.120.185.74 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 18:00:05 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 18:00:05 || No
|-
| lfmcal.dontexist.org || lfm || 75.158.131.108 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 18:00:06 || Yes
|-
| bitlex.co.cc || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-11 18:00:06 || Yes
|-
| pastecoin.com || genjix || 109.75.176.48 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.17[.4]}} || 2011-02-11 18:00:06 || ?
|-
| artforz.ath.cx || ArtForz || 93.199.125.213 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.15[.4]}} || 2011-02-11 18:00:06 || No
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-02-11 18:00:07 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-02-11 18:00:07 || ?

|}

=== Tor nodes ===

{|class="wikitable sortable"
! 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

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

Fallback Nodes

2011-01-25T02:20:57Z

Echelon: /* Tor 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 [[User:WikiBot|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 ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20}} || 2011-01-25 02:00:03 || ?
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-01-25 02:00:03 || Yes
|-
| bitcoin-otc.com || nanotube || 69.163.132.101 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:03 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:04 || No
|-
| 174.120.185.74 || MagicalTux [US] || 174.120.185.74 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:04 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:04 || No
|-
| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:04 || ?
|-
| lfmcal.dontexist.org || lfm || 75.158.131.108 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:04 || Yes
|-
| bitlex.co.cc || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:05 || Yes
|-
| mining.bitcoin.cz || slush || 178.79.147.99 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:05 || ?
|-
| pastecoin.com || genjix || 109.75.176.48 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.17[.4]}} || 2011-01-25 02:00:05 || ?
|-
| artforz.ath.cx || ArtForz || 84.146.122.143 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.15[.4]}} || 2011-01-25 02:00:06 || No
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-01-25 02:00:06 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-01-25 02:00:06 || ?

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-01-24 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-01-24 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-01-24 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-01-24 || Yes
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-01-24 || Yes
|-
| rnam4cxam62nkcyf.onion || BitLex || ? || 2011-01-24 || Yes
|-
| bitcoinbudtoeks7.onion || ? || ? || 2011-01-24 || ?
|-
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-01-24 || ?
|}

== 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

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

Fallback Nodes

2011-01-25T02:19:00Z

Echelon: /* Tor 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 [[User:WikiBot|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 ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20}} || 2011-01-25 02:00:03 || ?
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-01-25 02:00:03 || Yes
|-
| bitcoin-otc.com || nanotube || 69.163.132.101 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:03 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:04 || No
|-
| 174.120.185.74 || MagicalTux [US] || 174.120.185.74 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:04 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:04 || No
|-
| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:04 || ?
|-
| lfmcal.dontexist.org || lfm || 75.158.131.108 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:04 || Yes
|-
| bitlex.co.cc || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:05 || Yes
|-
| mining.bitcoin.cz || slush || 178.79.147.99 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-01-25 02:00:05 || ?
|-
| pastecoin.com || genjix || 109.75.176.48 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.17[.4]}} || 2011-01-25 02:00:05 || ?
|-
| artforz.ath.cx || ArtForz || 84.146.122.143 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.15[.4]}} || 2011-01-25 02:00:06 || No
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-01-25 02:00:06 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-01-25 02:00:06 || ?

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-01-24 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-01-24 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-01-24 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-01-24 || Yes
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-01-24 || Yes
|-
| rnam4cxam62nkcyf.onion || BitLex || ? || 2011-01-24 || Yes
| -
| bitcoinbudtoeks7.onion || ? || ? || 2011-01-24 || ?
| -
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-01-24 || ?
|}

== 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 <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

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