Bitcoin Wiki - User contributions [en]

LinuxCoin

2012-11-20T03:13:11Z

Ziv: fix link to forum, note that website is down

A lightweight Debian-based OS which includes in the image everything that is necessary to run as a Bitcoin client and everything needed to get started mining on ATI hardware.

Linuxcoin has not been updated since August 2011 and is starting to look outdated.
The creator, DrGr33n has stated that he has lost interest in bitcoin and has lost the files used to create linuxcoin.

LinuxCoin installs onto flash media and allows you to take your wallet where ever you go. It's a full Operating system so won't interfere or leave files on the PC's internal HDD and can be encrypted 256bit for added security.

Linuxcoin uses a 64bit kernel so won't work on a computer made before about 2006.

This software was launched on May 06, 2011<ref>[https://bitcointalk.org/index.php?topic=7374.0;all LinuxCoin A lightweight Debian based OS with everything ready to go]</ref>.

The wiki on the linuxcoin site was being frequently spammed and was deleted on the 16 of August 2012.

==External Links==
* [http://www.linuxcoin.co.uk LinuxCoin] official website, offline as of November 2012
* [https://bitcointalk.org/index.php?topic=7374.0;all LinuxCoin] announcement on BitCoin forums.

'''Download LinuxCoin'''
None of these links work as of November 2012
* [http://www.linuxcoin.co.uk/index.php?page=downloads Official download] page
* [http://fastspeedtest.net/mirrors/linuxcoin/linuxcoin-v0.2-final.iso 0.2-Final] direct http mirror
* [http://fastspeedtest.net/mirrors/linuxcoin/linuxcoin-v0.2-final.iso.torrent 0.2 torrent]

==References==
<references />

[[Category:Mining]]
[[Category:Open Source]]

Talk:Tonal Bitcoin

2012-09-21T05:04:28Z

Ziv: proposal to improve the page

The point of Bitcoin is that it is a decentralized peer to peer currency.
That is the novelty about Bitcoin; the novelty is NOT that it comes along with a funky new way of counting things.
So please stop using Bitcoin to promote your own agenda ; this is just going to confuse people.
If you want to introduce a new method for counting currency, I suggest you go talk to the FED and propose the Tonal Dollar, or whatever.
[[User:ThomasV|ThomasV]] 14:33, 20 February 2011 (GMT)
* If Bitcoin has only one purpose, then it will never succeed. There are about as many people that care about a "decentralized peer to peer currency" as there are that care about Tonal. If you want BitCoin to succeed, you should support as many (legal) reasons to use it as possible. Also, whether it's ever enforced or not, vandalism and trolling should be bannable offenses. --[[User:Luke-jr|Luke-jr]] 04:43, 21 February 2011 (GMT)

This page should be deleted.
Nothing against Tonal, if there was a Hexadecimal Bitcoin or an Octal Bitcoin I would suggest those get deleted, too.
* Seconded. Tonal is not a key part of bitcoin, and currently not used in any form. If there is a reasonable number of users using tonal, then I would have no objections against this page. [[User:Mqrius|Mqrius]] 05:11, 2 February 2012 (GMT)

This is silly. I thought you'd removed this already, but it's seeping across to other pages despite me never seeing it in the wild. It serves only to confuse [[User:Gigitrix|Gigitrix]] 01:41, 13 June 2011 (GMT)

I agree with Gavin that this page should be deleted. Regardless of my personal opinion or the technical merits of tonal v. decimal, it's fair to say that tonal attracts scorn and ridicule from the vast majority of the population if they hear about it. Bitcoin's reputation suffers from the association. [[User:ByteCoin|ByteCoin]] 24 June 2011 (GMT)
* It's not fair to say that, no. --[[User:Luke-jr|Luke-jr]] 00:45, 25 June 2011 (GMT)

I have no legitimate stake in the matter, I made a few edits that I hope remove POV and still embrace the idea of Tonal Bitcoin. This is Raize, I am sorry I am not familiar enough with wiki editing to provide my signature. --[[User:Raize|Raize]]

I think this page needs a much clearer explanation of what is being documented and would be better if it had a more descriptive name.

The page could be renamed somthing like "describing and writing amounts of BTC using Tonal numbers"

How about replacing the first couple of sentances with

"Currently most people who use bitcoin use decimal numbers to represent amounts of money. That means numbers using the digits 0 to 9. All known bitcoin software displays amounts of currency to user with decimal numbers.

Luke-jr thinks that there are people out there use a base 16 number system, he is probably right in the sense that it is correct to say that some people speak Latin because there are a few hundred people on the planet who speak Latin fluently.

This page is a proposal for a way that people who use a base 16 number system called the 'tonal system' could talk about or write down amounts of BTC.

This is about as useful as a book about making chocolate teapots written in esperanto. There is no evidence that anyone other than Luke-jr has ever used non-decimal numbers for bitcoin."

--[[User:Ziv|Ziv]]

==Voting about deleting page==

I also think this page should be deleted. There are at least three people suggesting this now, so I will re-add the delete tag to the page. So far there seems to be only one objection to the delete. I will initiate voting on this talk page. --[[User:Rebroad|Rebroad]] 22:48, 20 March 2012 (GMT)
* '''Delete''' - I believe this tonal suggestion will only do harm to the bitcoin project, and so far the only person advocating it is luke-jr, who rarely gives any rational reasons that I nor anyone else AFAIK can understand. Sorry luke-jr, but I'm doing my best to get you to explain the benefits. --[[User:Rebroad|Rebroad]] 22:52, 20 March 2012 (GMT)
*'''Delete''' - I've been lurking for a while, but I registered after seeing this nonsense here. Clearly if luke-jr is simply (and rather immaturely) blanking the discussion rather than responding to the specific points he has few arguments to marshal in his favor. --[[User:Zyzygy|Zyzygy]] ([[User talk:Zyzygy|talk]]) 05:14, 26 August 2012 (GMT)
*'''Delete''' along with all other references to this bullshit one man show in history, firsts and maybe other places. It serves no other thing than to Luke's ego. Why should the wiki as a whole support this? Apparently he realized that he can't win with arguments as he just deleted this very discussion. --[[User:Giszmo|Giszmo]] ([[User talk:Giszmo|talk]]) 15:41, 27 August 2012 (GMT)
*'''Delete''' because:
# nobody knows it - it seems that all sources are from one person [[User:Luke-jr|Luke-jr]] and from 150 years old (!) book. There is no notability. Nobody after cares about it. There are no "tonal system community" or "people that are using tonal system" - tonal system uses just 1 person and he is trying to misappropriate Bitcoin for this
# Tonal system is not at any way related to Bitcoin. Tonal system is related to numbers representation, not to monetary system. Please keep this page in general Wikipedia or some numeric Wikipedia, not in Bitcoin Wikipedia
# Tonal units are very confusing - from technically point of view (font, writing it) and mainly there is very similar to decimal numbers - there are many cases in which is not clear which system is used. Also TBC is common typing error of BTC
:'''Also I propose remove all notation about tonal from other wiki pages''', for example [[Units]] (very confusing), [[History]], [[Wallet protocol]] or [[Vocabulary]], and prevent them from reverting back (as happened several times). At least until Luke-jr (or someone else) find notable cites to keeping it here. [[User:Aleš Janda|Aleš Janda]] ([[User talk:Aleš Janda|talk]]) 19:44, 27 August 2012 (GMT)

Luke-jr comment to voting: This is for discussion, not trolling. Note that this is not an encyclopedia, and does not have any "notability" requirements. If you don't want to use Tonal, don't. Trolling is not acceptable and will be deleted. Reasoned criticism is welcome in the "Criticism" section of the page.

:What exactly from this discussion is "trolling"? I think you regard as trolling ANY critism. Don't clear discussion. Also, "Criticism" section is not good place to talk. [[User:Aleš Janda|Aleš Janda]] ([[User talk:Aleš Janda|talk]]) 09:16, 19 September 2012 (GMT)

Tonal Bitcoin

2012-09-21T03:46:53Z

Ziv: restore deletion discussion in progress banner

{{Delete}}

Tonal Bitcoin is a representation of the Bitcoin network aimed toward providing a use-case for adoption of Bitcoin to people who prefer the Tonal number system.
This is an alternative to the decimal and metric system, which improves usability by allowing for infinite binary division (note that Bitcoin protocol support is still finite).
For more information on the Tonal system in general, please see [http://www.lulu.com/product/file-download/tonal-system/10991091 the book].

Please note, that all numbers of TBC and its divisions/multipliers are written in [http://en.wikipedia.org/wiki/Tonal_System Tonal], not decimal.
This means that instead of counting 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10-- you count: 0, 1, 2, 3, 4, 5, 6, 7, 8, , 9, , , , , , 10. Some higher-value digits may require installing a [http://luke.dashjr.org/education/tonal/glyphs/fonts/ font].

{| border="1" style="text-align:right;font-family:Console, Luxi Mono, fixed"
|- style="background-color:silver"
! Abbreviation
! Pronunciation
! [[Tonal Bitcoin|Tonal (TBC)]]
! Decimal (BTC)
|-
|
| Tam-Bitcoin
| 1 0000 0000     
| 2 814 749.767 106 56
|-
| ᵇTBC
| Bong-Bitcoin
| 1 0000     
| 42.949 672 96
|-
| ᵐTBC
| Mill-Bitcoin
| 1000     
| 2.684 354 56
|-
| ˢTBC
| San-Bitcoin
| 100     
| 0.167 772 16
|-
| ᵗTBC
| Ton-Bitcoin
| 10     
| 0.010 485 76
|-
| TBC
| Bitcoin*
| 1     
| 0.000 655 36
|-
| TBCᵗ
| Bitcoin-ton
| 0.1   
| 0.000 040 96
|-
| TBCˢ
| Bitcoin-san
| 0.01  
| 0.000 002 56
|-
| TBCᵐ
| Bitcoin-mill
| 0.001 
| 0.000 000 16
|-
| TBCᵇ
| Bitcoin-bong
| 0.0001
| 0.000 000 01
|}

* Tonal Bitcoin and Decimal Bitcoin can be differentiated by the pronunciation of the numbers. "One bitcoin", "two bitcoin", etc is decimal, but "an bitcoin", "de bitcoin" is tonal.

The total number of Tonal Bitcoins ever (analogous to the 21mil BTC in decimal representation) is just over 7.75059 tam-bitcoin.

== Compatible Clients ==

While all Bitcoin clients will correctly approximate values in decimal bitcoin, actual Tonal compatibility is sparse.

* [[Spesmilo]], despite its name, can be configured to display TBC

== Guessing TBC or BTC ==

Given variable 'value' in base units (uBTCents/TBCᵇ), one can guess whether it is properly Decimal Bitcoin or Tonal Bitcoin with the following pseudo-code:

if ( ! ( this % 0x10000 ) )
Choose Tonal Bitcoin
if ( ! ( this % 1000000 ) )
Choose Decimal Bitcoin
if ( ! ( this % 0x100 ) )
Choose Tonal Bitcoin

=== Python ===

<pre>import math

def formatBTC(n, addSign = False):
s = "%0.2f BTC" % (math.ceil(n * 100) / 100.,)
if addSign and n >= 0:
s = "+" + s
return s

def Bitcoin2BTC(n):
return n / 100000000.

toTonalDict = dict(((57, u'\ue9d9'), (65, u'\ue9da'), (66, u'\ue9db'), (67, u'\ue9dc'), (68, u'\ue9dd'), (69, u'\ue9de'), (70, u'\ue9df'), (97, u'\ue9da'), (98, u'\ue9db'), (99, u'\ue9dc'), (100, u'\ue9dd'), (101, u'\ue9de'), (102, u'\ue9df')))

def formatTBC(n, addSign = False):
s = "%x" % n
n %= 1
if n:
s += '.'
while n:
n *= 16
s += "%x" % n
n %= 1
s = unicode(s).translate(toTonalDict)
s += " TBC"
if addSign and n >= 0:
s = "+" + s
return s

def Bitcoin2TBC(n):
return n / 65536.

def formatBitcoin(n, addSign = False):
if not n % 0x10000:
return formatTBC(Bitcoin2TBC(n), addSign);
if not n % 1000000:
return formatBTC(Bitcoin2BTC(n), addSign);
if not n % 0x100:
return formatTBC(Bitcoin2TBC(n), addSign);
s = "%d uBTCents" % (n,);
if addSign and n > 0:
s = "+" + s;
return s;</pre>

== Criticism ==

=== Hexadecimal could be done without new fonts as characters ===

The tonal notation requires extra fonts. Within the programming community there is a widely accepted convention for hexadecimal notation: use A-F for the higher order digits. Thus, one counts 0,1,2,3, ... , 9,A,B,C,D,E,F,10,11 .... There are even two conventions, (which are lacking in tonal notation) for distinguishing a base-16 number from a decimal. The C convention prefixes 0x and the Motorola convention suffixes h. So, the number san, 256 (decimal) would be written 0x100 or 100h. In tonal notation, it would only be written 100, and thus potentially confused with decimal 100 which is 0x64, though this confusion is less of a problem for Bitcoin since the context is always explicit (SI/BTC vs Tonal/TBC units).

Thus hexadecimal notation accomplishes most of the same goals as tonal notation, at least for Bitcoin, with no requirement for changing fonts, thus is more suited to wider usage. Further the prefix and suffix conventions lead to less ambiguity within the tonal community.

However, the goal of Tonal Bitcoin is to bring Bitcoin to Tonal, not to redefine Tonal or advocate change to the number system itself, so this is out of scope.

=== Not relevant to Bitcoin ===

Contrary to common myth, Bitcoin is not all about anonymity (and in fact, Bitcoin is *not* even anonymous itself).
Most people in the world don't care about anonymity, and Bitcoin would never get off the ground if it had a niche one-issue purpose.
Bitcoin is many things to many people, and not everyone has the same ideals or goals in mind.
For people who use the Tonal number system, Bitcoin's ability to adapt to it is a "killer feature", and gives them reason to prefer it over their local fiat currencies.

Talk:Tonal Bitcoin

2012-09-21T03:45:33Z

Ziv: revert abusive deletion by Luke-jr. Have the discussion, don't delete others opinions. They are not trolling, Luke, you are being a twat

The point of Bitcoin is that it is a decentralized peer to peer currency.
That is the novelty about Bitcoin; the novelty is NOT that it comes along with a funky new way of counting things.
So please stop using Bitcoin to promote your own agenda ; this is just going to confuse people.
If you want to introduce a new method for counting currency, I suggest you go talk to the FED and propose the Tonal Dollar, or whatever.
[[User:ThomasV|ThomasV]] 14:33, 20 February 2011 (GMT)
* If Bitcoin has only one purpose, then it will never succeed. There are about as many people that care about a "decentralized peer to peer currency" as there are that care about Tonal. If you want BitCoin to succeed, you should support as many (legal) reasons to use it as possible. Also, whether it's ever enforced or not, vandalism and trolling should be bannable offenses. --[[User:Luke-jr|Luke-jr]] 04:43, 21 February 2011 (GMT)

This page should be deleted.
Nothing against Tonal, if there was a Hexadecimal Bitcoin or an Octal Bitcoin I would suggest those get deleted, too.
* Seconded. Tonal is not a key part of bitcoin, and currently not used in any form. If there is a reasonable number of users using tonal, then I would have no objections against this page. [[User:Mqrius|Mqrius]] 05:11, 2 February 2012 (GMT)

This is silly. I thought you'd removed this already, but it's seeping across to other pages despite me never seeing it in the wild. It serves only to confuse [[User:Gigitrix|Gigitrix]] 01:41, 13 June 2011 (GMT)

I agree with Gavin that this page should be deleted. Regardless of my personal opinion or the technical merits of tonal v. decimal, it's fair to say that tonal attracts scorn and ridicule from the vast majority of the population if they hear about it. Bitcoin's reputation suffers from the association. [[User:ByteCoin|ByteCoin]] 24 June 2011 (GMT)
* It's not fair to say that, no. --[[User:Luke-jr|Luke-jr]] 00:45, 25 June 2011 (GMT)

I have no legitimate stake in the matter, I made a few edits that I hope remove POV and still embrace the idea of Tonal Bitcoin. This is Raize, I am sorry I am not familiar enough with wiki editing to provide my signature. --[[User:Raize|Raize]]

==Voting about deleting page==

I also think this page should be deleted. There are at least three people suggesting this now, so I will re-add the delete tag to the page. So far there seems to be only one objection to the delete. I will initiate voting on this talk page. --[[User:Rebroad|Rebroad]] 22:48, 20 March 2012 (GMT)
* '''Delete''' - I believe this tonal suggestion will only do harm to the bitcoin project, and so far the only person advocating it is luke-jr, who rarely gives any rational reasons that I nor anyone else AFAIK can understand. Sorry luke-jr, but I'm doing my best to get you to explain the benefits. --[[User:Rebroad|Rebroad]] 22:52, 20 March 2012 (GMT)
*'''Delete''' - I've been lurking for a while, but I registered after seeing this nonsense here. Clearly if luke-jr is simply (and rather immaturely) blanking the discussion rather than responding to the specific points he has few arguments to marshal in his favor. --[[User:Zyzygy|Zyzygy]] ([[User talk:Zyzygy|talk]]) 05:14, 26 August 2012 (GMT)
*'''Delete''' along with all other references to this bullshit one man show in history, firsts and maybe other places. It serves no other thing than to Luke's ego. Why should the wiki as a whole support this? Apparently he realized that he can't win with arguments as he just deleted this very discussion. --[[User:Giszmo|Giszmo]] ([[User talk:Giszmo|talk]]) 15:41, 27 August 2012 (GMT)
*'''Delete''' because:
# nobody knows it - it seems that all sources are from one person [[User:Luke-jr|Luke-jr]] and from 150 years old (!) book. There is no notability. Nobody after cares about it. There are no "tonal system community" or "people that are using tonal system" - tonal system uses just 1 person and he is trying to misappropriate Bitcoin for this
# Tonal system is not at any way related to Bitcoin. Tonal system is related to numbers representation, not to monetary system. Please keep this page in general Wikipedia or some numeric Wikipedia, not in Bitcoin Wikipedia
# Tonal units are very confusing - from technically point of view (font, writing it) and mainly there is very similar to decimal numbers - there are many cases in which is not clear which system is used. Also TBC is common typing error of BTC
:'''Also I propose remove all notation about tonal from other wiki pages''', for example [[Units]] (very confusing), [[History]], [[Wallet protocol]] or [[Vocabulary]], and prevent them from reverting back (as happened several times). At least until Luke-jr (or someone else) find notable cites to keeping it here. [[User:Aleš Janda|Aleš Janda]] ([[User talk:Aleš Janda|talk]]) 19:44, 27 August 2012 (GMT)

Luke-jr comment to voting: This is for discussion, not trolling. Note that this is not an encyclopedia, and does not have any "notability" requirements. If you don't want to use Tonal, don't. Trolling is not acceptable and will be deleted. Reasoned criticism is welcome in the "Criticism" section of the page.

:What exactly from this discussion is "trolling"? I think you regard as trolling ANY critism. Don't clear discussion. Also, "Criticism" section is not good place to talk. [[User:Aleš Janda|Aleš Janda]] ([[User talk:Aleš Janda|talk]]) 09:16, 19 September 2012 (GMT)

LinuxCoin

2012-08-18T12:00:00Z

Ziv: uses 64bit kernel

A lightweight Debian-based OS which includes in the image everything that is necessary to run as a Bitcoin client and everything needed to get started mining on ATI hardware.

LinuxCoin installs onto flash media and allows you to take your wallet where ever you go. It's a full Operating system so won't interfere or leave files on the PC's internal HDD and can be encrypted 256bit for added security.

LinuxCoin has many ways to communicate with friends / traders to get you buying, selling and purchasing goods with no hassle and peace of mind.

Linuxcoin uses a 64bit kernel so won't work on a computer made before about 2006.

This software was launched on May 06, 2011<ref>[http://www.bitcoin.org/smf/index.php?topic=7374.0 LinuxCoin A lightweight Debian based OS with everything ready to go]</ref>.

Linuxcoin has not been updated since August 2011 and is starting to look outdated.
The creator, DrGr33n has stated that he has lost interest in bitcoin and has lost the files used to create linuxcoin.

The wiki on the linuxcoin site was being frequently spammed and was deleted on the 16 of August 2012.

==External Links==
* [http://www.linuxcoin.co.uk LinuxCoin] official website
* [http://www.bitcoin.org/smf/index.php?topic=7374.0 LinuxCoin] announcement on BitCoin forums.

'''Download LinuxCoin'''
* [http://www.linuxcoin.co.uk/index.php?page=downloads Official download] page
* [http://fastspeedtest.net/mirrors/linuxcoin/linuxcoin-v0.2-final.iso 0.2-Final] direct http mirror
* [http://fastspeedtest.net/mirrors/linuxcoin/linuxcoin-v0.2-final.iso.torrent 0.2 torrent]

==References==
<references />

[[Category:Mining]]
[[Category:Open Source]]

Fallback Nodes

2012-08-07T19:15:05Z

Ziv: readd node thats back up

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

|}

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
|-
| 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-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
|-
| 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 || ?
|-
| uryde6tz4p4ckqy6.onion || Beli || up || 2012-06-26 || No
|-
| 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]]

LinuxCoin

2012-08-07T19:11:53Z

Ziv: update

A lightweight Debian-based OS which includes in the image everything that is necessary to run as a Bitcoin client and everything needed to get started mining on ATI hardware.

LinuxCoin installs onto flash media and allows you to take your wallet where ever you go. It's a full Operating system so won't interfere or leave files on the PC's internal HDD and can be encrypted 256bit for added security.

LinuxCoin has many ways to communicate with friends / traders to get you buying, selling and purchasing goods with no hassle and peace of mind.

This software was launched on May 06, 2011<ref>[http://www.bitcoin.org/smf/index.php?topic=7374.0 LinuxCoin A lightweight Debian based OS with everything ready to go]</ref>.

Linuxcoin has not been updated since August 2011 and is starting to look outdated.
The creator, DrGr33n has stated that he has lost interest in bitcoin and has lost the files used to create linuxcoin.

==External Links==
* [http://www.linuxcoin.co.uk LinuxCoin] official website
* [http://www.bitcoin.org/smf/index.php?topic=7374.0 LinuxCoin] announcement on BitCoin forums.

'''Download LinuxCoin'''
* [http://www.linuxcoin.co.uk/index.php?page=downloads Official download] page
* [http://fastspeedtest.net/mirrors/linuxcoin/linuxcoin-v0.2-final.iso 0.2-Final] direct http mirror
* [http://fastspeedtest.net/mirrors/linuxcoin/linuxcoin-v0.2-final.iso.torrent 0.2 torrent]

==References==
<references />

[[Category:Mining]]
[[Category:Open Source]]

Fallback Nodes

2012-07-05T01:58:25Z

Ziv: remove couple of dead 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

|}

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
|-
| 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-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
|-
| 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 || ?
|-
| uryde6tz4p4ckqy6.onion || Beli || up || 2012-06-26 || No
|-
| 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]]

Fallback Nodes

2012-05-17T02:17:36Z

Ziv: restore Kupsi's colbbered change, blockchain.info list

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 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 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 Up|version=36.79.37[.60]}} || 2012-05-17 02:00:03 || 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
|-
| 79.160.221.140 || K-Norway || 79.160.221.140 || {{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-23T10:49:59Z

Ziv: correction

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 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 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 Up|version=56.93.35[.58]}} || 2012-04-23 10:00:04 || 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

|}

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

User talk:Markbenson

2012-04-23T10:47:53Z

Ziv: spam

Fallback Nodes

2012-04-23T08:49:09Z

Ziv: update ip4 nodes, remove incorrect and outdated words

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

| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| li111-4.members.linode.com || unknown || 69.164.196.4 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| netzbasis.de || unknown3 || 81.169.129.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| django.webflows.fr || unknown2 || 188.165.213.169 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 178.32.7.171 || temporary-april-2012 || 178.32.7.171 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| progressbar.sk || Progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || 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 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>

User talk:MagicalTux

2012-04-15T00:17:14Z

Ziv: wikibot broken, suggest giving some established editors delete and ban rights

Hey MagicalTux, The WikiBot is not following the post-February 20th protocol change and the Fallback nodes page is not functioning. [[User:Atheros|Atheros]] 07:37, 20 February 2012 (GMT)

Wikibot currently malfunctioning, makring all the nodes as down when they arn't.
There is a steady trickle of spammers adding junk pages. How about granting delete and ban privileges to some established editors, it works for some other wiki's. [[User:Ziv|Ziv]] 14 April 2012

User talk:Dengxu

2012-04-15T00:06:06Z

Ziv: blank spam

User talk:Filipusis

2012-04-15T00:05:48Z

Ziv: blank spam

User talk:Backup7070

2012-04-15T00:05:27Z

Ziv: blank spam

User:Camper78brisbane

2012-04-15T00:04:52Z

Ziv: blank spam

Fallback Nodes

2012-04-14T23:44:17Z

Ziv: add a note that wikibot is malfunctioning and incorrectly marking all nodes as down

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

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

| progressbar.sk || Progressbar hackerspace || 91.210.181.21|| {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| coin.soul-dev.com || Soul-Dev || 70.57.156.45 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 178.32.7.171 || temporary-april-2012 || 178.32.7.171 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 66.158.72.2 || imsaguy || 66.158.72.2 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || 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-04-14T20:54:58Z

Ziv: wikibot is broken and has incorrectly marked working nodes as down

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

| progressbar.sk || Progressbar hackerspace || 91.210.181.21|| {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| coin.soul-dev.com || Soul-Dev || 70.57.156.45 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 178.32.7.171 || temporary-april-2012 || 178.32.7.171 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 66.158.72.2 || imsaguy || 66.158.72.2 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || 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-04-14T04:26:18Z

Ziv: update node list