Bitcoin Wiki - User contributions [en]

User:Kseistrup

2011-06-25T19:11:50Z

Kseistrup: /* Contact */ edit bitcoin tip jar

==Klaus Alexander Seistrup==
* Copenhagen, Denmark
* Programmer (Python, Bash)

==Contact==
* hCard: [http://klaus.seistrup.dk/ www.klaus.seistrup.dk]
* Twitter: [https://twitter.com/kseistrup @kseistrup]

Contributors Award participant: 1HPUs9hk9fR2MwTa91aab1MasQXDKAVsqW

[[Category:Freelancers]]
[[Category:Freelancers-Software_Development]]

User:Kseistrup

2011-06-10T07:52:59Z

Kseistrup: /* Contact */ change bitcoin tip jar

==Klaus Alexander Seistrup==
* Copenhagen, Denmark
* Programmer (Python, Bash)

==Contact==
* hCard: [http://klaus.seistrup.dk/ www.klaus.seistrup.dk]
* Twitter: [https://twitter.com/kseistrup @kseistrup]

Contributors Award participant: 1PUt1HEc8ijp4LkxNtXmW7KcXCmaK3KMrF

[[Category:Freelancers]]
[[Category:Freelancers-Software_Development]]

Fallback Nodes

2011-05-14T17:42:01Z

Kseistrup: /* 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
|-

| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| jun.dashjr.org || Lightfoot Hosting || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| mining.bitcoin.cz || slush || 178.79.147.99 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || No
|-
| bitcoin.csy.ca || Martok || 128.189.187.27 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:09 || ?
|-
| nat.router.dashjr.org || Luke-Jr || 71.1.74.69 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:10 || ?
|-
| bitcoin.sipa.be || sipa || 178.18.90.41 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:10 || No
|-
| bluematt.me || BlueMatt || 62.155.236.249 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-05-03 12:29:00 || No
|-
| btc1.justmoon.net || justmoon || 109.75.176.226 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || Yes
|-
| bitcoins.ca || humble || 142.58.248.28 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || Yes
|-
| BiddingPond.com || BiddingPond || 184.106.111.41 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || ?
|-
| zack.home.chrishowie.com || cdhowie || 98.222.140.181 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:11 || No
|-
| 178.63.15.200 || hendi || 178.63.15.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.1]}} || 2011-04-17 12:00:11 || ?
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-04-17 12:00:12 || Yes
|-
| fallback1.bitcoin.me.uk || Vladimir || 91.85.220.84 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 173.224.125.222 || MagicalTux [US] || 173.224.125.222 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| bitlex.org || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:13 || Yes
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-04-17 12:00:13 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-04-17 12:00:13 || ?
|-
| 67.176.86.181 || BobSGI || 67.176.86.181 ||
|-
| BTCSportsBet.com || Cusipzzz || 109.75.176.39 || {{Table Value Yes}}

|}

=== 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
|-
| 4lmduyac3svgrrav.onion || ? || ? || 2011-02-11 || No
|-
| usasx4urod3yj4az.onion || ? || ? || 2011-02-11 || No
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list. To 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-05-14T17:35:22Z

Kseistrup: /* 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
|-

| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| jun.dashjr.org || Lightfoot Hosting || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| mining.bitcoin.cz || slush || 178.79.147.99 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || No
|-
| bitcoin.csy.ca || Martok || 128.189.187.27 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:09 || ?
|-
| nat.router.dashjr.org || Luke-Jr || 71.1.74.69 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:10 || ?
|-
| bitcoin.sipa.be || sipa || 178.18.90.41 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:10 || No
|-
| bluematt.me || BlueMatt || 62.155.236.249 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-05-03 12:29:00 || No
|-
| btc1.justmoon.net || justmoon || 109.75.176.226 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || Yes
|-
| bitcoins.ca || humble || 142.58.248.28 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || Yes
|-
| BiddingPond.com || BiddingPond || 184.106.111.41 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || ?
|-
| zack.home.chrishowie.com || cdhowie || 98.222.140.181 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:11 || No
|-
| 178.63.15.200 || hendi || 178.63.15.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.1]}} || 2011-04-17 12:00:11 || ?
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-04-17 12:00:12 || Yes
|-
| fallback1.bitcoin.me.uk || Vladimir || 91.85.220.84 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 173.224.125.222 || MagicalTux [US] || 173.224.125.222 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| bitlex.org || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:13 || Yes
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-04-17 12:00:13 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-04-17 12:00:13 || ?
|-
| 67.176.86.181 || BobSGI || 67.176.86.181 ||
|-
| BTCSportsBet.com || Cusipzzz || 109.75.176.39 || {{Table Value Yes}}

|}

=== 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
|-
| 4lmduyac3svgrrav.onion || ? || ? || 2011-02-11 || No
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list. To 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-05-03T19:43:25Z

Kseistrup: /* IPv4 Nodes */ Removed 217.157.1.202 (own node)

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

| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| jun.dashjr.org || Lightfoot Hosting || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| mining.bitcoin.cz || slush || 178.79.147.99 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || No
|-
| bitcoin.csy.ca || Martok || 128.189.187.27 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:09 || ?
|-
| nat.router.dashjr.org || Luke-Jr || 71.1.74.69 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:10 || ?
|-
| bitcoin.sipa.be || sipa || 178.18.90.41 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:10 || No
|-
| bluematt.me || BlueMatt || 62.155.236.249 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-05-03 12:29:00 || No
|-
| bitcoin.chrishowie.com || cdhowie || 68.169.45.99 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || No
|-
| btc1.justmoon.net || justmoon || 109.75.176.226 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || Yes
|-
| bitcoins.ca || humble || 142.58.248.28 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || Yes
|-
| BiddingPond.com || BiddingPond || 184.106.111.41 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || ?
|-
| bitcoin.isdigital.com || joecolotti || 50.7.251.192 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:11 || Yes
|-
| zack.home.chrishowie.com || cdhowie || 98.222.140.181 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:11 || No
|-
| 178.63.15.200 || hendi || 178.63.15.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.1]}} || 2011-04-17 12:00:11 || ?
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-04-17 12:00:12 || Yes
|-
| fallback1.bitcoin.me.uk || Vladimir || 91.85.220.84 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 173.224.125.222 || MagicalTux [US] || 173.224.125.222 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| bitlex.co.cc || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:13 || Yes
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-04-17 12:00:13 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-04-17 12:00:13 || ?
|-
| 67.176.86.181 || BobSGI || 67.176.86.181 ||
|-
| BTCSportsBet.com || Cusipzzz || 109.75.176.39 || {{Table Value Yes}}

|}

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

Mining hardware comparison

2011-03-07T20:21:00Z

Kseistrup: /* Intel */ + cpuminer 0.7.1 with algo sse2_64 on Core2Duo

{{stub}}

Below are some statistics about the mining performance of various hardware used in a [[mining rig]]. The GPU lists were originally compiled by ArtForz.

The table shows stock clock numbers. 10-20% performance improvement can be achieved via overclocking.

=Graphics cards=

==AMD==
To get the maximum performance use the 2.1 or 2.2 release of the ATI Stream SDK. 2.3 performance drops by 5-10%.

{| class="wikitable sortable"
|-
! Model !! Mhash/s !! Mhash/W !! W !! Clock !! SP !! SDK !! Miner !! Notes
|-
| 3XXX || || || || || || || || OpenCL Not Supported
|-
| 4350 || 6.93 || 0.346 || 20 || 575 || 80 || || poclbm || -w 32, don't use vectors
|-
| 4550 || 7.23 || 0.289 || 25 || 600 || 80 || || poclbm || -w 32, don't use vectors
|-
| 4650 || 31.33 || 0.653 || 48 || 650 || 320 || || poclbm || -w 32, don't use vectors
|-
| 4670 || 36.14 || 0.613 || 59 || 750 || 320 || || poclbm || -w 32, don't use vectors
|-
| 4730 || 72.29 || 0.657 || 110 || 750 || 640 || || ||
|-
| 4770 || 72.29 || 0.904 || 80 || 750 || 640 || || ||
|-
| 4830 || 55.42 || 0.583 || 95 || 575 || 640 || || ||
|-
| 4850 || 75.30 || 0.685 || 110 || 625 || 800 || || ||
|-
| 4860 || 67.47 || 0.519 || 130 || 700 || 640 || || ||
|-
| 4870 || 90.36 || 0.602 || 150 || 750 || 800 || 2.1 || clmine ||
|-
| 4870 || 78 || || || || || || m0mchil's OpenCL/Vista 64bit || [http://www.bitcoin.org/smf/index.php?topic=1628.msg25069#msg25069 source]
|-
| 4890 || 102.41 || 0.539 || 190 || 850 || 800 || || ||
|-
| 4850X2 || 150.60 || 0.602 || 250 || 625 || 1600 || || ||
|-
| 4870X2 || 180.72 || 0.632 || 286 || 750 || 1600 || || ||
|-
| 5450 || 11.99 || 0.631 || 19 || 650 || 80 || || ||
|-
| 5550 || 40.59 || 1.041 || 39 || 550 || 320 || || ||
|-
|style="background:#FFFFEF;"| 5570 || 59.96 || 1.538 || 39 || 650 || 400 || || ||
|-
|style="background:#FFFFEF;"| 5570 || 64 || 1.641 || 39 || 650 || || || m0mchil's OpenCL/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
| 5650 || 48 || 2.5-3.2 ? || 15-19 ? || || || || m0mchil's OpenCL/Win7-64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26292#msg26292 source] [http://www.notebookcheck.net/ATI-Mobility-Radeon-HD-5650.23697.0.html source]
|-
| 5670 || 71.49 || 1.117 || 64 || 775 || 400 || || ||
|-
| 5750 || 116.24 || 1.352 || 86 || 700 || 720 || || ||
|-
| 5770 || 156.83 || 1.452 || 108 || 850 || 800 || 2.1 || clmine ||
|-
|style="background:#FFFFFF;"| 5830 || 206.64 || 1.181 || 175 || 800 || 1120 || || ||
|-
|style="background:#FFFFFF;"| 5830 || 241 || 1.377 || 175 || 1006 || || 2.3 || poclbm 2011-02-04 ||
|-
|style="background:#EFEFFF;"| 5850 || 240.77 || 1.595 || 151 || 725 || 1440 || || ||
|-
|style="background:#EFEFFF;"| 5850 || 252 || 1.669 || 151 || 765 || || 2.3 || poclbm 2011-01-25 ||
|-
|style="background:#EFEFFF;"| 5850 || 255.3 || 1.690 || 151 || 765 || || 2.2 || poclbm 2011-01-25 ||
|-
|style="background:#EFEFFF;"| 5850 || 300 || 1.987 || 151 || || || || m0mchil's OpenCL || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
|style="background:#EFEFFF;"| 5850 || 250.26 || 1.657 || 151 || || || || opencl client || [http://www.bitcoin.org/smf/index.php?topic=1628.msg29471#msg29471 source]
|-
|style="background:#EFFFEF;"| 5870 || 313.65 || 1.668 || 188 || 850 || 1600 || 2.1 || clmine ||
|-
|style="background:#EFFFEF;"| 5870 || 313 || 1.665 || 188 || 900? || 1600 || 2.3 || Diablo/Linux ||
|-
|style="background:#EFFFEF;"| 5870 || 343 || 1.824 || 188 || 900? || 1600 || 2.1 || Diablo/Linux ||
|-
|style="background:#EFFFEF;"| 5870 || 355 || 1.888 || 188 || 900? || 1600 || 2.1 || poclbm/Linux ||
|-
|style="background:#EFFFEF;"| 5870 || 340 || 1.809 || 188 || 850 || 1600 || || m0mchil's OpenCL || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26363#msg26363 source]
|-
|style="background:#FFEFEF;"| 5970 || 535.06 || 1.820 || 294 || 725 || 3200 || 2.1 || clmine ||
|-
|style="background:#FFEFEF;"| 5970 || 560 || 1.905 || 294 || 725 || || || Diablo ||
|-
|style="background:#FFEFEF;"| 5970 || 565 || 1.922 || 294 || || || 2.1 || clmine2 ||
|-
|style="background:#FFEFEF;"| 5970 || 604 || 2.054 || 294 || || || 2.1 || clmine ||
|-
| 6850 || 171.59 || 1.351 || 127 || 775 || 960 || 2.1 || clmine ||
|-
| 6870 || 232.47 || 1.540 || 151 || 900 || 1120 || || ||
|-
| 6970 || 323 || 1.468 || 220 || 880 || 1536 || 2.3 || poclbm || -w 64
|-
|}

==Intel==

{| class="wikitable sortable"
|-
! Model !! Mhash/s !! Mhash/W !! W !! Clock !! SP !! SDK !! Miner
|-
| HD 2000 || 0.65 || || || || || 2.2 || poclbm 2011-01-25
|-
|}

==Nvidia==

{| class="wikitable sortable"
|-
! Model !! Mhash/s !! Mhash/W !! W !! Clock !! SP !! Comment
|-
| 8600M GT || 4.93 || || || || 32 ||
|-
| 8600GT || 5.66 || || || 1188 || 32 ||
|-
| 8800GT || 25 || 0.24 || 105 || 1300 || ||
|-
| 8800GT || 24.5 || 0.23 || 105 || 1300 || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source]
|-
| 8800GTS || 16.8 || 0.05 || 291 ? || || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg25069#msg25069 source] [http://www.techspot.com/review/79-geforce-8800-gts-512/page11.html source]
|-
| 9300GE || 1.57 || || || 1300 || 8 ||
|-
| 9300GS || 1.69 || || || 1400 || 8 ||
|-
| 9400GT || 3.37 || 0.067 || 50 || 1400 || 16 ||
|-
| 9500GT || 6.75 || 0.135 || 50 || 1400 || 32 ||
|-
| 9600GSO || 19.88 || 0.237 || 84 || 1375 || 96 ||
|-
| 9600GSO512 || 11.75 || 0.131 || 90 || 1625 || 48 ||
|-
| 9600GT || 15.66 || 0.165 || 95 || 1625 || 64 ||
|-
| 9800GT || 30.36 || 0.289 || 105 || 1800 || 112 ||
|-
| 9800GTX || 32.54 || 0.232 || 140 || 1688 || 128 ||
|-
| 9800GTX+ || 35.39 || 0.251 || 141 || 1836 || 128 ||
|-
|style="background-color:#FFEFEF"| 9800GX2 || 57.83 || 0.294 || 197 || || 2x128 ||
|-
|style="background-color:#FFEFEF"| 9800GX2 || 28 || 0.142 || 197 || || 2x128 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37620#msg37620 source]
|-
| G210 || 3.38 || 0.111 || 30.5 || 1402 || 16 ||
|-
| GT220 || 9.83 || 0.170 || 58 || 1360 || 48 ||
|-
| GT240 || 19.37 || 0.281 || 69 || 1340 || 96 ||
|-
| GTS250 || 35.39 || 0.244 || 145 || 1836 || 128 ||
|-
| GTX260 || 35.91 || 0.178 || 202 || 1242 || 192 ||
|-
| GTX260 || 44 || 0.242 || 182 || 1242 || 216 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
| GTX260c216 || 40.40 || 0.236 || 171 || 1242 || 216 ||
|-
| GTX275 || 50.75 || 0.232 || 219 || 1404 || 240 ||
|-
| GTX280 || 46.84 || 0.198 || 236 || 1296 || 240 ||
|-
| GTX285 || 53.35 || 0.262 || 204 || 1476 || 240 ||
|-
| GTX295 || 89.78 || 0.311 || 289 || 1242 || 480 ||
|-
| 320M (MacBook Air) || 6.12 || || || 1212 || 48 ||
|-
| GT430 || 20.24 || 0.413 || 49 || 1400 || 96 ||
|-
| GTS450 || 45.28 || 0.427 || 106 || 1566 || 192 ||
|-
| GTX460SE || 56.39 || 0.376 || 150 || 1300 || 288 ||
|-
| GTX460 || 68.31 || 0.427 || 160 || 1350 || 336 ||
|-
| GTX460 (2 cards) || 102 || 0.319? || 320? || 1350 || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26363#msg26363 source]
|-
| GTX465 || 64.41 || 0.322 || 200 || 1215 || 352 ||
|-
| GTX470 || 81.98 || 0.381 || 215 || 1215 || 448 ||
|-
| GTX480 || 101.28 || 0.405 || 250 || 1401 || 480 ||
|-
| GTX570 || 105.83 || 0.483 || 219 || 1464 || 480 ||
|-
| GTX580 || 119.06 || 0.488 || 244 || 1544 || 512 ||
|-
|}

=CPUs=

A lot of nice data can be pulled from [http://www.bitcoin.org/smf/index.php?topic=1628.0 this thread] to seed this section. Also from [https://www.bitcoin.org/wiki/doku.php?id=bitcoin_miners this page on the old wiki].

==AMD==
{| class="wikitable sortable"
|-
! Model !! nprocs !! Mhash/s !! Mhash/W !! ACP [W] !! Clock !! Version !! Comment
|-
| 2x Opteron 6128 || 16 || 32.4 || 0.203 || 160W || 2 GHz || 0.3.19 || -4way
|-
| Athlon X2 4000+ || 2 || 1.9 || 0.02 || 65W || 2.1 GHz || rpc-miner ||
|-
| Athlon X2 4400+ || || 2.09 || 0.32 || 65W || 2.3GHz || 0.3.19/Win x64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source]
|-
| Athlon X2 6000+ || 2 || 2.81 || 0.02 || 125W || 3 GHz || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg22881#msg22881 source]
|-
| Athlon XP 2000+ || 2 || 0.62 || 0.009 || 70W || 1.67 GHz || 0.3.18/Ubuntu || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source] [http://www.pcstats.com/articleview.cfm?articleid=914&page=4 source]
|-
| Athlon II X2 240e || 2 || 2.71 || 0.06 || 45W || 2.81 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Phenom II X6 1055T || 6 || 15.84 || 0.13 || 125W || 2.82 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Phenom II X6 1100T || 6 || 22 || 0.176 || 125W || 3.82 GHz || bitcoin-miner || Aciid#bitcoin-dev
|-
| Phenom II X3 720 || 3 || 3.8 || 0.04 || 95W || 2.8 GHz || 0.3.1x/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
| Phenom II X3 720 || 3 || 7.2 || 0.08 || 95W || 2.8 GHz || cpu-miner 0.2.1/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|}

==Intel==
{| class="wikitable sortable"
|-
! Model !! p/t !! Mhash/s !! Mhash/W !! ACP [W] !! Clock !! Version !! Comment
|-
| Pentium III mobile ? || 1 || 0.3 || 0.014 || 21W || 1.07 GHz || 0.3.1x/Win2K || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source] [http://ark.intel.com/Product.aspx?id=27380 source]
|-
| Pentium Dual-Core E5400 || 2/2 || 2.27 || 0.03 || 65W || 2.7 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Celeron E330 || 2/2 || 2.2 || 0.03 || 65W || 2.5 GHz || 0.3.19/Ubuntu10.04 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37620#msg37620 source]
|-
| Core i3 M350 || 2/4 || 1.48 || 0.04 || 35W || 2.27 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Core i5 M450 || 2/4 || 1.8 || 0.05 || 35W || 1.2 GHz || 0.3.17/Win7-54 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26292#msg26292 source]
|-
| Core i5-2400 || 4/4 || 4.5 || 0.05 || 95W || 3.1 GHz || cpuminer git (2011-01-22) || cryptopp_asm32
|-
| Core i5-550 ? || 2/4 || 5.1 || 0.04 ? || || 3.2 GHz || cpuminer-0.7 || -4way
|-
| Core i5 ? || 4/? || 6.5 || || || || client from svn || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37621#msg37621 source]
|-
| Core i7 980x || 6/12 || 19.2 || 0.15 || 130 || 4.4 GHz (x33) || cpuminer/Win7-64 ||
|-
| Core i7 980x || 6/12 || 8.7 || || || 3.9 GHz (x27) || 0.3.17/Win7-64 ||
|-
| Core 2 Duo E6550 || 1/2 || 2.45 || ? || ? || 2.33 GHz || cpuminer 0.7.1 (Linux) || --algo=sse2_64
|-
| Core 2 Duo E6850 || 2/2 || 6.75 || 0.10 || 65W || 3.0 Ghz || ufasoft-0.3 ||
|-
| Core 2 Duo E7300 || 2/2 || 7.76 || 0.11 || 70W || 3.33 GHz (o/c?) || ufasoft-0.3 || miner optimized for Intel Core
|-
| Core 2 Duo E7300 || 2/2 || 2.52 || 0.04 || 65W || 2.66 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Xeon E5520 || 4/8 || 6.5 || 0.08 || 80W || 2.27 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Xeon E5530 || 4/8 || 7.14 || 0.09 || 80W || 2.4 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Xeon E5630 (dual) || 2x4/8 || 8 || 0.1 || 80W || 2.53 GHz || 0.3.17/Win7-64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg29471#msg29471 source]
|-
| Atom N270 || 1 || 0.42 || '''0.17''' || 2.5W || 1.6 GHz || 0.3.1x/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|}

[[Category:Mining]]

User:Kseistrup

2011-02-28T10:35:34Z

Kseistrup: + CAp

==Klaus Alexander Seistrup==
* Copenhagen, Denmark
* Programmer (Python, Bash)

==Contact==
* hCard: [http://klaus.seistrup.dk/ www.klaus.seistrup.dk]
* Twitter: [https://twitter.com/kseistrup @kseistrup]

Contributors Award participant: 13EhJEK6r3gZbhJxazhwDHhGRPWBsW9Aak

[[Category:Freelancers]]
[[Category:Freelancers-Software_Development]]

User:Kseistrup

2011-02-22T10:48:11Z

Kseistrup: + ‘Freelancers: Software development’

==Klaus Alexander Seistrup==
* Copenhagen, Denmark
* Programmer (Python, Bash)

==Contact==
* hCard: [http://klaus.seistrup.dk/ www.klaus.seistrup.dk]
* Twitter: [https://twitter.com/kseistrup @kseistrup]

[[Category:Freelancers]]
[[Category:Freelancers-Software_Development]]

User:Kseistrup

2011-02-22T10:44:50Z

Kseistrup: Added ‘Freelancers’ category

User:Kseistrup

2011-02-22T10:43:17Z

Kseistrup: Page creation

Fallback Nodes

2011-02-17T19:19:04Z

Kseistrup: /* IPv4 Nodes */ Added 217.157.1.202

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-17 19:00:03 || No
|-
| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20}} || 2011-02-17 19:00:03 || ?
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19[.2]}} || 2011-02-17 19:00:03 || Yes
|-
| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-17 19: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-17 19:00:06 || No
|-
| bitcoins.ca || humble || 142.58.248.28 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-17 19:00:04 || Yes
|-
| 174.120.185.74 || MagicalTux [US] || 174.120.185.74 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-17 19: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-02-17 19:00:04 || No
|-
| lyasoff.com || ? || 200.35.150.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-17 19:00:04 || ?
|-
| lfmcal.dontexist.org || lfm || 75.158.131.108 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-17 19:00:04 || Yes
|-
| bitlex.co.cc || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-02-17 19:00:05 || Yes
|-
| artforz.ath.cx || ArtForz || 93.199.117.116 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.15[.4]}} || 2011-02-17 19:00:05 || No
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-02-17 19:00:05 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-02-17 19:00:05 || ?
|-
| pastecoin.com || genjix || 109.75.176.48 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || 2011-02-17 16:00:10 || ?
|-
| 217.157.1.202 || kseistrup

|}

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