Bitcoin Wiki - User contributions [en]

Fallback Nodes

2020-07-26T07:22:53Z

Victorsueca: Updated IPv4 and removed Tor node as it is no longer online consistently

This is a list of nodes which are considered reliable.

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

[[Bitcoin Core]] versions prior to 0.8.0 also could send [[IP Transactions]] to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back.

=== Tor network ===

To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter:
bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor

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

You can find detailed information on running clients and hidden services within Tor in the [https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md documentation].

== Nodes list ==

=== IPv4 Nodes ===

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

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

|-
| bitcoin.moneypot.com || [https://www.moneypot.com moneypot] || 212.47.228.216 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2015-09-15 || No
|-
| node.bitcoin.xxx || [http://www.bitcoin.xxx Bitcoin.xxx] || 66.228.49.201 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-08-28 || Yes
|-
| bitcoin.coinprism.com || [[Coinprism]] || 137.116.225.142 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-04-26 || Yes
|-
| btcnode1.evolyn.net || Evolyn || 85.214.251.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-01-26 || Yes
|-
| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 67.186.224.85 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2013-11-13 || Yes
|-
| archivum.info || Ferraro Ltd.|| 88.198.58.172 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 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 Up}} || 2017-11-15 ||
|-
| cheaperinbitcoins.com || Xenland/Shane || 184.154.36.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| django.webflows.fr || unknown2 || 188.165.213.169 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| porgressbar.sk || progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| faucet.bitcoin.st || bitcoin street || 64.27.57.225 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| bitcoin.securepayment.cc || SecurePayment CC || 63.247.147.163 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| coin.soul-dev.com || Soul-Dev || || || {{Fallback Nodes/Node Down}} || ||
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode2.bitgroup.cc || BitGroup || 162.243.120.138 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode3.bitgroup.cc || BitGroup || 95.85.8.237 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.xiro.co || Xiro Labs || 91.121.108.61 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2017-11-15 || No
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 185.122.57.203 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| bitcoin.bitdonut.co || James Hartig || || || {{Fallback Nodes/Node Down}} || ||
|-
| coinno.de || jaknam || || || {{Fallback Nodes/Node Down}} || ||
|-
| 82.165.44.44 || anonymous || || || {{Fallback Nodes/Node Down}} || ||
|-
| bitcoin1.dassori.me || gdassori || || || {{Fallback Nodes/Node Down}} || ||
|-
| bitcoin2.dassori.me || gdassori || || || {{Fallback Nodes/Node Down}} || ||
|-
| blockchainnode.meulie.net || [[User:Evert|Evert]] || || || {{Fallback Nodes/Node Up}} || 2017-11-15 ||
|-
| fullnode.fybsg.com || Nagato || || || {{Fallback Nodes/Node Down}} || ||
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 62.210.66.227 || || {{Fallback Nodes/Node Up}} || 2017-11-15 ||
|-
| homeplex.tk || [[User:Victorsueca|Victorsueca]] || 90.165.120.190 || || {{Fallback Nodes/Node Down}} || ||
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || 91.121.83.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes

|}

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

| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 2601:7:6680:2ac:4d29:40ff:7513:fcc7 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 11-13-2013 (MDY) || Yes
|-
| caffeinator.net || [[User:Atrophy|Atrophy]] || || || {{Fallback Nodes/Node Up}} || 2013-05-10 ||
|-
| 2001:470:8:2e1::40 || ? || 2001:470:8:2e1::40 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 2a06:8ec0:3::1:2e47 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| bitcoin.bitdonut.co || James Hartig || || || || ||
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 2001:bc8:c087:2001::1 || || || ||
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || || || || ||

|}

=== Tor nodes ===

This entire list was last checked on 2018-10-24.

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| nkf5e6b7pl4jfd4a.onion || BlueMatt || Up || 2018-10-24 || 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>

==See Also==

* [[Network|Bitcoin Network]]
* [http://nodes.bitcoin.st Fallback Nodes] List of longest running Bitcoin Nodes listed by Country.
* [https://getaddr.bitnodes.io/ Bitnodes project]
* [https://blockchain.info/connected-nodes Recently connected nodes at blockchain.info]

{{Bitcoin Core documentation}}

Fallback Nodes

2018-09-10T11:04:52Z

Victorsueca: Updated node IP due to ISP reorg

This is a list of nodes which are considered reliable.

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

[[Bitcoin Core]] versions prior to 0.8.0 also could send [[IP Transactions]] to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back.

=== Tor network ===

To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter:
bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor

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

You can find detailed information on running clients and hidden services within Tor in the [https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md documentation].

== Nodes list ==

=== IPv4 Nodes ===

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

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

|-
| bitcoin.moneypot.com || [https://www.moneypot.com moneypot] || 212.47.228.216 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2015-09-15 || No
|-
| node.bitcoin.xxx || [http://www.bitcoin.xxx Bitcoin.xxx] || 66.228.49.201 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-08-28 || Yes
|-
| bitcoin.coinprism.com || [[Coinprism]] || 137.116.225.142 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-04-26 || Yes
|-
| btcnode1.evolyn.net || Evolyn || 85.214.251.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-01-26 || Yes
|-
| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 67.186.224.85 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2013-11-13 || Yes
|-
| archivum.info || Ferraro Ltd.|| 88.198.58.172 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 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 Up}} || 2017-11-15 ||
|-
| cheaperinbitcoins.com || Xenland/Shane || 184.154.36.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| django.webflows.fr || unknown2 || 188.165.213.169 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| porgressbar.sk || progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| faucet.bitcoin.st || bitcoin street || 64.27.57.225 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| bitcoin.securepayment.cc || SecurePayment CC || 63.247.147.163 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| coin.soul-dev.com || Soul-Dev || || || {{Fallback Nodes/Node Down}} || ||
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode2.bitgroup.cc || BitGroup || 162.243.120.138 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode3.bitgroup.cc || BitGroup || 95.85.8.237 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.xiro.co || Xiro Labs || 91.121.108.61 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2017-11-15 || No
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 185.122.57.203 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| bitcoin.bitdonut.co || James Hartig || || || {{Fallback Nodes/Node Down}} || ||
|-
| coinno.de || jaknam || || || {{Fallback Nodes/Node Down}} || ||
|-
| 82.165.44.44 || anonymous || || || {{Fallback Nodes/Node Down}} || ||
|-
| bitcoin1.dassori.me || gdassori || || || {{Fallback Nodes/Node Down}} || ||
|-
| bitcoin2.dassori.me || gdassori || || || {{Fallback Nodes/Node Down}} || ||
|-
| blockchainnode.meulie.net || [[User:Evert|Evert]] || || || {{Fallback Nodes/Node Up}} || 2017-11-15 ||
|-
| fullnode.fybsg.com || Nagato || || || {{Fallback Nodes/Node Down}} || ||
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 62.210.66.227 || || {{Fallback Nodes/Node Up}} || 2017-11-15 ||
|-
| homeplex.tk || [[User:Victorsueca|Victorsueca]] || 90.171.117.252 || || {{Fallback Nodes/Node Down}} || ||
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || 91.121.83.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes

|}

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

| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 2601:7:6680:2ac:4d29:40ff:7513:fcc7 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 11-13-2013 (MDY) || Yes
|-
| caffeinator.net || [[User:Atrophy|Atrophy]] || || || {{Fallback Nodes/Node Up}} || 2013-05-10 ||
|-
| 2001:470:8:2e1::40 || ? || 2001:470:8:2e1::40 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 2a06:8ec0:3::1:2e47 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| bitcoin.bitdonut.co || James Hartig || || || || ||
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 2001:bc8:c087:2001::1 || || || ||
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || || || || ||

|}

=== Tor nodes ===

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

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| gyn2vguc35viks2b.onion || [[User:ChievOk|ChievOk]] || Up || 2017-11-15 || No
|-
| kvd44sw7skb5folw.onion || [[User:ChievOk|ChievOk]] || Up || 2017-11-15 || No
|-
| nkf5e6b7pl4jfd4a.onion || BlueMatt || Up || 2017-11-15 || No
|-
| yu7sezmixhmyljn4.onion || [[User:Victorsueca|Victorsueca]] || Up || 2017-11-15 || ?
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

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

==See Also==

* [[Network|Bitcoin Network]]
* [http://nodes.bitcoin.st Fallback Nodes] List of longest running Bitcoin Nodes listed by Country.
* [https://getaddr.bitnodes.io/ Bitnodes project]
* [https://blockchain.info/connected-nodes Recently connected nodes at blockchain.info]

{{Bitcoin Core documentation}}

Fallback Nodes

2018-03-20T23:37:40Z

Victorsueca: Updated my node after some host and ISP changes

This is a list of nodes which are considered reliable.

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

[[Bitcoin Core]] versions prior to 0.8.0 also could send [[IP Transactions]] to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back.

=== Tor network ===

To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter:
bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor

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

You can find detailed information on running clients and hidden services within Tor in the [https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md documentation].

== Nodes list ==

=== IPv4 Nodes ===

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

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

|-
| bitcoin.moneypot.com || [https://www.moneypot.com moneypot] || 212.47.228.216 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2015-09-15 || No
|-
| node.bitcoin.xxx || [http://www.bitcoin.xxx Bitcoin.xxx] || 66.228.49.201 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-08-28 || Yes
|-
| bitcoin.coinprism.com || [[Coinprism]] || 137.116.225.142 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-04-26 || Yes
|-
| btcnode1.evolyn.net || Evolyn || 85.214.251.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2014-01-26 || Yes
|-
| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 67.186.224.85 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || 2013-11-13 || Yes
|-
| archivum.info || Ferraro Ltd.|| 88.198.58.172 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 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 Up}} || 2017-11-15 ||
|-
| cheaperinbitcoins.com || Xenland/Shane || 184.154.36.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| django.webflows.fr || unknown2 || 188.165.213.169 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| porgressbar.sk || progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| faucet.bitcoin.st || bitcoin street || 64.27.57.225 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| bitcoin.securepayment.cc || SecurePayment CC || 63.247.147.163 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| coin.soul-dev.com || Soul-Dev || || || {{Fallback Nodes/Node Down}} || ||
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode2.bitgroup.cc || BitGroup || 162.243.120.138 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode3.bitgroup.cc || BitGroup || 95.85.8.237 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.xiro.co || Xiro Labs || 91.121.108.61 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2017-11-15 || No
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 185.122.57.203 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| bitcoin.bitdonut.co || James Hartig || || || {{Fallback Nodes/Node Down}} || ||
|-
| coinno.de || jaknam || || || {{Fallback Nodes/Node Down}} || ||
|-
| 82.165.44.44 || anonymous || || || {{Fallback Nodes/Node Down}} || ||
|-
| bitcoin1.dassori.me || gdassori || || || {{Fallback Nodes/Node Down}} || ||
|-
| bitcoin2.dassori.me || gdassori || || || {{Fallback Nodes/Node Down}} || ||
|-
| blockchainnode.meulie.net || [[User:Evert|Evert]] || || || {{Fallback Nodes/Node Up}} || 2017-11-15 ||
|-
| fullnode.fybsg.com || Nagato || || || {{Fallback Nodes/Node Down}} || ||
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 62.210.66.227 || || {{Fallback Nodes/Node Up}} || 2017-11-15 ||
|-
| homeplex.tk || [[User:Victorsueca|Victorsueca]] || 90.71.117.212 || || {{Fallback Nodes/Node Down}} || ||
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || 91.121.83.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes

|}

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

| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 2601:7:6680:2ac:4d29:40ff:7513:fcc7 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 11-13-2013 (MDY) || Yes
|-
| caffeinator.net || [[User:Atrophy|Atrophy]] || || || {{Fallback Nodes/Node Up}} || 2013-05-10 ||
|-
| 2001:470:8:2e1::40 || ? || 2001:470:8:2e1::40 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 2a06:8ec0:3::1:2e47 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| bitcoin.bitdonut.co || James Hartig || || || || ||
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 2001:bc8:c087:2001::1 || || || ||
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || || || || ||

|}

=== Tor nodes ===

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

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| gyn2vguc35viks2b.onion || [[User:ChievOk|ChievOk]] || Up || 2017-11-15 || No
|-
| kvd44sw7skb5folw.onion || [[User:ChievOk|ChievOk]] || Up || 2017-11-15 || No
|-
| nkf5e6b7pl4jfd4a.onion || BlueMatt || Up || 2017-11-15 || No
|-
| yu7sezmixhmyljn4.onion || [[User:Victorsueca|Victorsueca]] || Up || 2017-11-15 || ?
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

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

==See Also==

* [[Network|Bitcoin Network]]
* [http://nodes.bitcoin.st Fallback Nodes] List of longest running Bitcoin Nodes listed by Country.
* [https://getaddr.bitnodes.io/ Bitnodes project]
* [https://blockchain.info/connected-nodes Recently connected nodes at blockchain.info]

{{Bitcoin Core documentation}}

Bitcoin

2017-11-14T09:11:17Z

Victorsueca: Updated information about transaction fees

'''Bitcoin''' is a decentralized [[digital currency]] created by developer [[Satoshi Nakamoto]]. It does not rely on a central server to process transactions or store funds. There are a maximum of 2,099,999,997,690,000 Bitcoin elements (called satoshis), which are currently most commonly measured in units of 100,000,000 known as BTC. Stated another way, no more than 21 million BTC can ever be created.

{{As of|April 2014}}, it is the most widely used alternative currency,<ref name="Quantitative Analysis of the Full Bitcoin Transaction Graph">{{cite web|title=Quantitative Analysis of the Full Bitcoin Transaction Graph|url=http://eprint.iacr.org/2012/584.pdf|publisher=Cryptology ePrint Archive|accessdate=18 October 2012|author=Ron Dorit|coauthors=Adi Shamir|page=17|quote=The Bitcoin system is the best known and most widely used alternative payment scheme,...}}</ref><ref name="Mt.Gox data">{{Cite web|title=Mt.Gox data|url=http://bitcoincharts.com/markets/mtgoxUSD.html|publisher=Bitcoincharts}}</ref> now with the total market cap over 6 billion US dollars<ref>{{cite web|title=Market Capitalization|url=https://blockchain.info/charts/market-cap|publisher= [[BlockChain.info]] |accessdate=21 April 2014}}</ref>.

Bitcoin has no central issuer; instead, the peer-to-peer network regulates Bitcoins, transactions and issuance according to consensus in network software.
Bitcoins are issued to various nodes that verify transactions through computing power;
it is established that there will be a limited and scheduled release of no more than 21 million BTC worth of coins, which will be fully issued by the year 2140.

Internationally, Bitcoins can be exchanged and managed through various websites and [[software]] along with physical banknotes and coins.<ref>{{Cite web|title=Physical Bitcoins by Casascius|url=https://www.casascius.com/|publisher=Casascius Coins|accessdate=29 September 2012}}</ref><ref>{{Cite web|title=Bitbills|url=http://www.bitbills.com/|publisher=Bitbills|accessdate=29 September 2012}}</ref>

==History==
{{main|History}}

A cryptographic system for untraceable payments was first described by David Chaum in 1982.<ref>[http://blog.koehntopp.de/uploads/Chaum.BlindSigForPayment.1982.PDF David Chaum, Blind signatures for untraceable payments], Advances in Cryptology - Crypto '82, Springer-Verlag (1983), 199–203.</ref> In 1990 Chaum extended this system to create the first cryptographic anonymous electronic cash system.,<ref>{{cite journal|journal=Lecture Notes in Computer Science|last1=Chaum|first1=David|last2=Fiat|first2=Amos|last3=Naor|first3=Moni|title=Untraceable Electronic Cash|url=http://blog.koehntopp.de/uploads/chaum_fiat_naor_ecash.pdf}}</ref> which became known as ecash.
<ref>{{cite web|url=http://www.wired.com/wired/archive/2.12/emoney.html|publisher=Wired|title=E-Money (That's What I Want)|date=1994–2012|author=Steven Levy}}</ref> In 1998 [[Wei Dai]] published a description of an anonymous, distributed electronic cash system which he called "b-money".<ref>{{cite web|title=B-Money|url=http://www.weidai.com/bmoney.txt|author=Wei Dai|year=1998}}</ref> Around the same time, Nick Szabo created ''bit gold''.<ref>{{cite web|url=http://spectrum.ieee.org/computing/software/bitcoin-the-cryptoanarchists-answer-to-cash/0|title=Bitcoin: The Cryptoanarchists’ Answer to Cash|publisher=IEEE Spectrum|quote=Around the same time, Nick Szabo, a computer scientist who now blogs about law and the history of money, was one of the first to imagine a new digital currency from the ground up. Although many consider his scheme, which he calls “bit gold,” to be a precursor to Bitcoin}}</ref><ref name="bitgold">{{cite web|title=Bit gold|url=http://unenumerated.blogspot.co.uk/2005/12/bit-gold.html|author=Nick Szabo|quote=My proposal for bit gold is based on computing a string of bits from a string of challenge bits, using functions called variously "client puzzle function," "proof of work function," or "secure benchmark function.". The resulting string of bits is the proof of work.... The last-created string of bit gold provides the challenge bits for the next-created string.}}</ref> Like Bitcoin, ''Bit gold'' was a currency system where users would compete to solve a [[proof of work]] function, with solutions being cryptographically chained together and published via a distributed property title registry. A variant of ''Bit gold'', called ''Reusable Proofs of Work'', was implemented by Hal Finney.<ref name="bitgold"/>

In 2008, Satoshi Nakamoto published a [[Bitcoin_white_paper|paper]]<ref name="whitepaper">{{cite web
|last= Nakamoto
|first= Satoshi
|title= Bitcoin: A Peer-to-Peer Electronic Cash System
|url= http://www.cs.kent.edu/~JAVED/class-P2P12F/papers-2012/PAPER2012-p2p-bitcoin-satoshinakamoto.pdf
|accessdate = 14 December 2010
|date= 24 May 2009
|postscript=
}}</ref><ref>{{cite web
|url= http://article.gmane.org/gmane.comp.encryption.general/12588/
|title= Bitcoin P2P e-cash paper
}}</ref> on The Cryptography Mailing list at metzdowd.com<ref>[http://www.mail-archive.com/search?l=cryptography@metzdowd.com&q=from:%22Satoshi+Nakamoto%22 Satoshi's posts to Cryptography mailing list]</ref> describing the Bitcoin protocol.

The Bitcoin network came into existence on 3 January 2009 with the release of the first Bitcoin client, [[wxBitcoin]], and the issuance of the first Bitcoins.<ref>{{cite web |title=Block 0 – Bitcoin Block Explorer |url=http://blockexplorer.com/block/000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f }}</ref><ref>{{cite web |url=http://www.mail-archive.com/cryptography@metzdowd.com/msg10142.html |title=Bitcoin v0.1 released}}</ref><ref>{{cite web |url=http://sourceforge.net/news/?group_id=244765 |title=SourceForge.net: Bitcoin}}</ref>
A year after, the initial exchange rates for Bitcoin were set by individuals on the bitcointalk forums.{{Citation needed|date=October 2012}} The most significant transaction involved a 10,000 BTC pizza.<ref>{{cite web|title=The Rise and Fall of Bitcoin|url=http://www.wired.com/magazine/2011/11/mf_bitcoin/|publisher=Wired|accessdate=13 October 2012}}</ref>
Today, the majority of Bitcoin exchanges occur on the [[Bitstamp]] Bitcoin exchange.<ref>{{cite web | title = Exchange volume distribution | work = by market | publisher = [[Bitcoin Charts]] | date = April 15, 2014 | url = http://bitcoincharts.com/charts/volumepie/ | accessdate = 2014-04-15 }}</ref>

In 2011, Wikileaks,<ref>{{cite news
|last= Greenberg
|first= Andy
|url= http://blogs.forbes.com/andygreenberg/2011/06/14/wikileaks-asks-for-anonymous-bitcoin-donations/
|title= WikiLeaks Asks For Anonymous Bitcoin Donations – Andy Greenberg – The Firewall – Forbes
|publisher= Blogs.forbes.com
|date= 2011-06-14
|accessdate = 2011-06-22
}}</ref> [[Freenet]],<ref>{{cite web
|url= https://freenetproject.org/donate.html
|title= /donate
|publisher= The Freenet Project
|date=
|accessdate = 2011-06-22
}}</ref> Singularity Institute,<ref>[http://singinst.org/donate/ SIAI donation page]</ref> Internet Archive,<ref>[http://www.archive.org/donate/index.php Internet Archive donation page]</ref> Free Software Foundation<ref>[https://my.fsf.org/donate/other/ Other ways to donate]</ref> and others, began to accept donations in Bitcoin. The Electronic Frontier Foundation did so for a while but has since stopped, citing concerns about a lack of legal precedent about new currency systems, and because they "generally don't endorse any type of product or service."<ref>{{cite web
|url= https://www.eff.org/deeplinks/2011/06/eff-and-bitcoin
|title= EFF and Bitcoin | Electronic Frontier Foundation
|publisher= Eff.org
|date= 2011-06-14
|accessdate = 2011-06-22
}}</ref> Some small businesses had started to adopt Bitcoin. LaCie, a public company, accepts Bitcoin for its Wuala service.<ref>{{Cite web|url=http://www.wuala.com/en/bitcoin |title=Secure Online Storage – Backup. Sync. Share. Access Everywhere |publisher=Wuala |date= |accessdate = 2012-01-24}}</ref>

In 2012, BitPay reports of having over 1000 merchants accepting Bitcoin under its payment processing service.<ref>{{cite web|title=BitPay Signs 1,000 Merchants to Accept Bitcoin Payments|url=http://www.americanbanker.com/issues/177_176/bitpay-signs-1000-merchants-to-accept-bitcoin-payments-1052538-1.html|publisher=American Banker|accessdate=12 October 2012}}</ref>

==Administration==
Bitcoin is administered through a decentralized peer-to-peer network.<ref name="whitepaper"/> Cryptographic technologies and the peer-to-peer network of computing power enables users to make and verify irreversible, instant online Bitcoin payments, without an obligation to trust and use centralized banking institutions and authorities. Dispute resolution services are not made directly available. Instead it is left to the users to verify and trust the parties they are sending money to through their choice of methods.

Bitcoins are issued according to rules agreed to by the majority of the computing power within the Bitcoin network. The core rules describing the predictable issuance of Bitcoins to its verifying servers, a voluntary and competitive transaction fee system and the hard limit of no more than 21 million BTC issued in total.<ref name="whitepaper"/>

Bitcoin does not require a central bank, State,<ref>{{cite web
|url= http://spectrum.ieee.org/computing/software/bitcoin-the-cryptoanarchists-answer-to-cash/3
|title= Bitcoin: The Cryptoanarchists' Answer to Cash
|publisher= IEEE.org
|date= June 2012
|accessdate = 2012-06-05
}}</ref> or incorporated backers.

==Services==
{{main|Wallet}}

Bitcoins are sent and received through software and websites called wallets. They send and confirm transactions to the network through Bitcoin addresses, the identifiers for users' Bitcoin wallets within the network.<ref name="whitepaper"/>

===Bitcoin addresses===
{{main|Address}}

Payments are made to Bitcoin "addresses": human-readable strings of numbers and letters around 33 characters in length, always beginning with the digit 1 or 3, as in the example of ''31uEbMgunupShBVTewXjtqbBv5MndwfXhb''.

Users obtain new Bitcoin addresses from their Bitcoin software. Creating a new address can be a completely offline process and require no communication with the Bitcoin network. Web services often generate a new Bitcoin address for every user, allowing them to have their custom deposit addresses.{{dubious}}

===Transaction fees===
{{main|Transaction fees}}
Transaction fees may be included with any transfer of Bitcoins. While it's technically possible to send a transaction with zero fee, {{as of|2017}} it's highly unlikely that one of these transactions confirms in a realistic amount of time, causing most nodes on the network to drop it. For transactions which consume or produce many outputs (and therefore have a large data size), higher transaction fees are usually expected.

===Confirmations===
{{main|Confirmation}}

The network's software confirms a transaction when it records it in a block. Further blocks of transactions confirm it even further. After six confirmations/blocks, a transaction is confirmed beyond reasonable doubt.

The network must store the whole transaction history inside the blockchain, which grows constantly as new records are added and never removed. Nakamoto conceived that as the database became larger, users would desire applications for Bitcoin that didn't store the entire database on their computer. To enable this, the blockchain uses a [[merkle tree]] to organize the transaction records in such a way that client software can locally delete portions of its own database it knows it will never need, such as earlier transaction records of Bitcoins that have changed ownership multiple times.

==Economics==

===Initial distribution===

Bitcoin has no centralized issuing authority.<ref name="ars-06-08-11">
{{Cite news
|first= Thomas
|last= Lowenthal
|title= Bitcoin: inside the encrypted, peer-to-peer digital currency
|newspaper= Ars Technica
|date= 8 June 2011
|url= http://arstechnica.com/tech-policy/news/2011/06/bitcoin-inside-the-encrypted-peer-to-peer-currency.ars
}}</ref><ref>{{cite news
|author= Sponsored by
|url= http://www.economist.com/blogs/babbage/2011/06/virtual-currency
|title= Virtual currency: Bits and bob
|publisher= The Economist
|date=
|accessdate = 2011-06-22
}}</ref><ref>{{cite web
|last= Geere
|first= Duncan
|url= http://www.wired.co.uk/news/archive/2011-05/16/bitcoin-p2p-currency
|title= Peer-to-peer currency Bitcoin sidesteps financial institutions (Wired UK)
|publisher= Wired.co.uk
|date=
|accessdate = 2011-06-22
}}</ref> The network is programmed to increase the money supply as a geometric series until the total number of Bitcoins reaches 21 million BTC.<ref name="Quantitative Analysis of the Full Bitcoin Transaction Graph"/> {{As of|2012|10}} slightly over 10 million of the total 21 million BTC had been created; the current total number created is available online.<ref>{{cite web
|title= Total Number of Bitcoins in Existence
|url= http://blockexplorer.com/q/totalbc
|work= Bitcoin Block Explorer
|accessdate = 2012-10-03
}}</ref> By 2013 half of the total supply will have been generated, and by 2017, three-quarters will have been generated. To ensure sufficient granularity of the [[money supply]], clients can divide each BTC unit down to eight decimal places (a total of 2.1 × 1015 or 2.1 quadrillion units).<ref name="lwn">{{Cite news
|author= Nathan Willis
|date= 2010-11-10
|title= Bitcoin: Virtual money created by CPU cycles
|publisher= LWN.net
|url= http://lwn.net/Articles/414452/
}}</ref>

The network {{As of|2012|lc=on}} required over one million times more work for confirming a block and receiving an award (25 BTC {{As of|2012|2|lc=on}}) than when the first blocks were confirmed.
The difficulty is automatically adjusted every 2016 blocks based on the time taken to find the previous 2016 blocks such that one block is created roughly every 10 minutes.

Those who chose to put computational and electrical resources toward mining early on had a greater chance at receiving awards for block generations. This served to make available enough processing power to process blocks. Indeed, without miners there are no transactions and the Bitcoin economy comes to a halt.

===Exchange rate===
Prices fluctuate relative to goods and services more than more widely accepted currencies;
the price of a Bitcoin is not static.

In August 2012, 1 BTC traded at around $10.00 USD. Taking into account the total number of Bitcoins mined, the monetary base of the Bitcoin network stands at over 110 million USD.<ref>[http://www.bitcoinwatch.com/ http://www.bitcoinwatch.com/] Bitcoin statistics</ref>

== Anonymity ==
{{main|Anonymity & Security}}

=== Transactions ===

While using bitcoins is an excellent way to make your purchases, donations, and p2p payments, without losing money through inflated transaction fees, transactions are never truly anonymous. Buying Bitcoin you pass identification, Bitcoin transactions are stored publicly and permanently on the network, which means anyone can see the balance and transactions of any Bitcoin address. Bitcoin activities are recorded and available publicly via the [[blockchain]], a comprehensive database which keeps a record of bitcoin transactions.

=== Buying/selling bitcoins ===

All exchanges require the user to scan ID documents, and large transactions must be reported to the proper governmental authority. When you use Bitcoin to pay for goods and services, you will of course need to provide your name and address to the seller for delivery purposes.

This means that a third party with an interest in tracking your activities can use your visible balance and ID information as a basis from which to track your future transactions or to study previous activity. In short, you have compromised your [[security]] and [[privacy]].

In addition to conventional exchanges like Bitstamp, Bitfinex, Kraken and Coinable there are also Peer to peer exchanges like localbitcoins and Paxful. Peer to peer exchanges will often not collect KYC and identity information directly from users, instead they let the users handle KYC amongst themselves. These can often be a better alternative for those looking to purchase bitcoin quickly and without KYC delay.

=== Mixing services ===

[http://anonymity.co.in/mixing_services.html Mixing services] are used to avoid compromising of privacy and security. Mixing services provide to periodically exchange your bitcoins for different ones which cannot be associated with the original owner.

== Security ==
{{seealso|Weaknesses}}

In the history of bitcoin, there have been a few [[incidents]], caused by problematic as well as malicious transactions. In the worst such incident, and the only one of its type, a person was able to pretend that he had a practically infinite supply of bitcoins, for almost 9 hours.

Bitcoin relies, among other things, on [http://en.wikipedia.org/wiki/Public-key_cryptography public key cryptography] and thus may be vulnerable to [http://en.wikipedia.org/wiki/Elliptic_curve_cryptography#Quantum_computing_attacks quantum computing attacks] if and when practical quantum computers can be constructed.

If multiple different software packages, whose usage becomes widespread on the Bitcoin network, disagree on the protocol and the rules for transactions, this could potentially cause a fork in the block chain, with each faction of users being able to accept only their own version of the history of transactions. This could influence the price of bitcoins.

A global, organized campaign against the currency or the software could also influence the demand for bitcoins, and thus the exchange price.

==Bitcoin mining==
{{main|Mining}}

Bitcoin mining nodes are responsible for managing the Bitcoin network.

Bitcoins are awarded to Bitcoin nodes known as "miners" for the solution to a difficult [[proof-of-work]] problem which confirms transactions and prevents double-spending. This incentive, as the Nakamoto white paper describes it, encourages "nodes to support the network, and provides a way to initially distribute coins into circulation, since no central authority issues them."<ref name="whitepaper" />

Nakamoto compared the generation of new coins by expending CPU time and electricity to gold miners expending resources to add gold to circulation.<ref name="whitepaper"/>

===Node operation===

The node software for the Bitcoin network is based on peer-to-peer networking, digital signatures and cryptographic proof to make and verify transactions. Nodes broadcast transactions to the network, which records them in a public record of all transactions, called the ''blockchain'', after validating them with a [[proof-of-work|proof-of-work system]].

Satoshi Nakamoto designed the first Bitcoin node and mining software<ref name="processors">{{Cite news
|last= Davis
|first= Joshua
|title= The Crypto-Currency
|url= http://www.wired.com/magazine/2011/11/mf_bitcoin/all
|accessdate = 11 November 2011
|newspaper= Wired Magazine
|date= 10 November 2011
}}</ref> and developed the majority of the first implementation, Bitcoind, from 2007 to mid-2010.<ref name="code_start">{{cite web
|url= https://bitcointalk.org/index.php?topic=13.msg46#msg46
|title= Questions about Bitcoin
|publisher= Bitcoin forum
|date= 2009-12-10
}}</ref>

Node implementations include core software such as Bitcoind/Bitcoin-Qt, [[libbitcoin]], [[cbitcoin]]<ref>{{Cite web|title=cbitcoin|url=https://github.com/MatthewLM/cbitcoin|accessdate=3 October 2012}}</ref> and [[BitCoinJ|bitcoinj]].<ref>{{cite web
|url= http://news.slashdot.org/story/11/03/23/0210207/Google-Engineer-Releases-Open-Source-Bitcoin-Client
|title= Google Engineer Releases Open Source Bitcoin Client
|author= angry tapir, timothy
|date= 23 March 2011
|publisher= Slashdot
|accessdate = 2011-05-18
}}</ref><ref>{{cite web
|url= http://www.javaworld.com/javaworld/jw-01-2012/120110-bitcoin-for-beginners-3.html?page=1
|title= Bitcoin for beginners: The BitcoinJ API
|author= Dirk Merkel
|date= 10 January 2012
|publisher= JavaWorld
|accessdate = 2012-08-03
}}</ref>

Every node in the Bitcoin network collects all the unacknowledged transactions it knows of in a file called a ''block'', which also contains a reference to the previous valid block known to that node. It then appends a [[nonce]] value to this previous block and computes the SHA-256 cryptographic hash of the block and the appended nonce value. The node repeats this process until it adds a nonce that allows for the generation of a hash with a value lower than a specified ''target''. Because computers cannot practically reverse the hash function, finding such a nonce is hard and requires on average a predictable amount of repetitious trial and error. This is where the ''[[proof-of-work]]'' concept comes in to play. When a node finds such a solution, it announces it to the rest of the network. Peers receiving the new solved block validate it by computing the hash and checking that it really starts with the given number of zero bits (i.e., that the hash is within the target). Then they accept it and add it to the chain.

===Mining rewards===
In addition to receiving the pending transactions confirmed in the block, a generating node adds a ''generate'' transaction, which awards new Bitcoins to the operator of the node that generated the block. The system sets the payout of this generated transaction according to its defined inflation schedule. The miner that generates a block also receives the fees that users have paid as an incentive to give particular transactions priority for faster confirmation.<ref>[https://www.bitcoinmining.com Bitcoin Mining]</ref>

The network never creates more than a 50 BTC reward per block and this amount will decrease over time towards zero, such that no more than 21 million BTC will ever exist.<ref name="lwn" /> As this payout decreases, the incentive for users to run block-generating nodes is intended to change to earning [[#Transaction fees|transaction fees]].

===Mining pools===
{{main|Pooled mining}}

Bitcoin users often pool computational effort to increase the stability of the collected fees and subsidy they receive.<ref name="We Use Coins Mining">{{cite web|title=About Bitcoin Mining|url=https://www.weusecoins.com/en/mining-guide/|publisher=We Use Coins|accessdate=27 May 2015}}</ref>

===Mining difficulty===
{{main|Difficulty}}

In order to throttle the creation of blocks, the difficulty of generating new blocks is adjusted over time. If mining output increases or decreases, the difficulty increases or decreases accordingly.

The adjustment is done by changing the threshold that a hash is required to be less than. A lower threshold means fewer possible hashes can be accepted, and thus a higher degree of difficulty. The target rate of block generation is one block every 10 minutes, or 2016 blocks every two weeks. Bitcoin changes the difficulty of finding a valid block every 2016 blocks, using the difficulty that would have been most likely to cause the prior 2016 blocks to have taken two weeks to generate, according to the timestamps on the blocks. Technically, this is done by modeling the generation of Bitcoins as Poisson process. All nodes perform and enforce the same difficulty calculation.

Difficulty is intended as an automatic stabilizer allowing mining for Bitcoins to remain profitable in the long run for the most efficient miners, independently of the fluctuations in demand of Bitcoin in relation to other currencies.

===Mining hardware===
{{main|Mining Hardware Comparison}}

Bitcoins used to be mined through Intel/AMD CPUs. {{As of | 2012}}, mining has gradually moved to [[GPU]] and [[FPGA]] hardware.<ref name="bitcoinmag-butterfly" /> [[Application-specific integrated circuit|ASIC]]-based hardware for Bitcoin mining has been announced by several manufacturers who intend to ship products from late 2012 to early 2013.<ref name="bitcoinmag-butterfly">{{Cite web|title=Bitpay Breaks Daily Volume Record with Butterfly ASIC mining release|url=http://bitcoinmagazine.net/bitpay-breaks-daily-volume-record-with-butterfly-asic-mining-release/|publisher=Bitcoin Magazine}}</ref>

==Concerns==

===As an investment===
Bitcoin describes itself as an experimental digital currency. Reuben Grinberg has noted that Bitcoin's supporters have argued that Bitcoin is neither a security or an investment because it fails to meet the criteria for either category.<ref name="grinberg">{{cite web | url=http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1817857 | title=Bitcoin: An Innovative Alternative Digital Currency | publisher=SSRN | date=9 December 2011 | accessdate=4 December 2012 | author=Grinberg, Reuben}}</ref> Although it is a virtual currency, some people see it as an investment<ref name="cnbc">{{cite web | url=http://www.cnbc.com/id/45030812/The_Pros_And_Cons_Of_Biting_on_Bitcoins | title=The Pros And Cons Of Biting on Bitcoins | publisher=CNBC | date=23 November 2011 | accessdate=4 December 2012 | author=Gustke, Constance}}</ref> or accuse it of being a form of investment fraud known as a Ponzi scheme.<ref>{{cite web |url=http://www.theregister.co.uk/2011/06/08/bitcoin_under_attack/ |title=US senators draw a bead on Bitcoin |last1=Chirgwin |first1=Richard |date=8 June 2011 |publisher=The Register |accessdate=14 November 2012}}</ref><ref>{{cite web |url=http://uk.reuters.com/article/2012/04/01/uk-traders-bitcoin-idUKBRE8300JL20120401 |title=Bitcoin, the City traders' anarchic new toy |last1=O'Leary |first1=Naomi |date=2 April 2012 |publisher=Reuters |accessdate=14 November 2012}}</ref> A report by the European Central Bank, using the U.S. Securities and Exchange Commission's definition of a Ponzi scheme, found that the use of bitcoins shares some characteristics with Ponzi schemes, but also has characteristics of its own which contradict several common aspects of Ponzi schemes.<ref name="ecbreport">{{cite web | url=http://www.ecb.europa.eu/pub/pdf/other/virtualcurrencyschemes201210en.pdf | title=Virtual Currency Schemes | publisher=European Central Bank | date=October 2012 | accessdate=4 December 2012}}</ref>

===Privacy===
Because transactions are broadcast to the entire network, they are inherently public. Unlike regular banking,<ref>{{cite web
|url= http://spectrum.ieee.org/computing/software/bitcoin-the-cryptoanarchists-answer-to-cash/0
|title= Bitcoin: The Cryptoanarchists' Answer to Cash
|publisher= IEEE.org
|date= June 2012
|accessdate = 2012-06-05
}}</ref> which preserves customer privacy by keeping transaction records private, loose transactional privacy is accomplished in Bitcoin by using many unique addresses for every wallet, while at the same time publishing all transactions. As an example, if Alice sends 123.45 BTC to Bob, the network creates a public record that allows anyone to see that 123.45 has been sent from one address to another. However, unless Alice or Bob make their ownership of these addresses known, it is difficult for anyone else to connect the transaction with them. However, if someone connects an address to a user at any point they could follow back a series of transactions as each participant likely knows who paid them and may disclose that information on request or under duress.

It can be difficult to associate Bitcoin identities with real-life identities.<ref name="An Analysis of Anonymity in the Bitcoin System">Fergal Reid and Martin Harrigan (24 July 2011). [http://anonymity-in-bitcoin.blogspot.com/2011/07/bitcoin-is-not-anonymous.html An Analysis of Anonymity in the Bitcoin System]. An Analysis of Anonymity in the Bitcoin System.</ref> This property makes Bitcoin transactions attractive to sellers of illegal products.<ref name="Forbes">Andy Greenberg (20 April 2011). [http://www.forbes.com/forbes/2011/0509/technology-psilocybin-bitcoins-gavin-andresen-crypto-currency.html Crypto Currency]. Forbes Magazine.</ref><ref>{{cite web
|last= Madrigal
|first= Alexis
|title= Libertarian Dream? A Site Where You Buy Drugs With Digital Dollars
|publisher= The Atlantic Monthly
|date= 2011-06-01
|url= http://www.theatlantic.com/technology/archive/2011/06/libertarian-dream-a-site-where-you-buy-drugs-with-digital-dollars/239776/
|accessdate = 2011-06-05
}}</ref>

===Illicit use===

====Cracking====
The cracking organization "LulzSec" accepted donations in Bitcoin, having said that the group "needs Bitcoin donations to continue their hacking efforts".<ref name="CNET">{{cite web
|last= Reisinger
|first= Don
|url= http://news.cnet.com/8301-13506_3-20070268-17/senators-target-bitcoin-currency-citing-drug-sales/
|title= Senators target Bitcoin currency, citing drug sales | The Digital Home – CNET News
|publisher= News.cnet.com
|date= 2011-06-09
|accessdate = 2011-06-22
}}</ref><ref>{{cite news
|last= Olson
|first= Parmy
|url= http://blogs.forbes.com/parmyolson/2011/06/06/lulzsec-hackers-posts-sony-dev-source-code-get-7k-donation/
|title= LulzSec Hackers Post Sony Dev. Source Code, Get $7K Donation – Parmy Olson – Disruptors – Forbes
|publisher= Blogs.forbes.com
|date= 6 June 2011
|accessdate = 2011-06-22
}}</ref>

====Silk Road====
[[Silk Road]] is an anonymous black market that uses only the Bitcoin.<ref name="npr-06-12-11">
{{Cite news
|url= http://www.npr.org/2011/06/12/137138008/silk-road-not-your-fathers-amazon-com
|date= 12 June 2011
|newspaper= NPR
|title= Silk Road: Not Your Father's Amazon.com
|author= Staff
}}</ref>

In a 2011 letter to Attorney General Eric Holder and the Drug Enforcement Administration, senators Charles Schumer of New York and Joe Manchin of West Virginia called for an investigation into Silk Road and the Bitcoin.<ref name="npr-06-12-11"/>
Schumer described the use of Bitcoins at Silk Road as a form of money laundering.<ref name="ars-06-08-11"/>

====Botnet mining====
In June 2011, Symantec warned about the possibility of botnets engaging in covert "mining" of Bitcoins,<ref>{{Cite web|author=Updated: 17 June 2011 | Translations available: 日本語 |url=http://www.symantec.com/connect/blogs/bitcoin-botnet-mining |title=Bitcoin Botnet Mining | Symantec Connect Community |publisher=Symantec.com |date=2011-06-17 |accessdate = 2012-01-24}}</ref><ref>{{Cite web|url=http://www.zdnet.com/blog/security/researchers-find-malware-rigged-with-bitcoin-miner/8934 |title=Researchers find malware rigged with Bitcoin miner |publisher=ZDNet |date=2011-06-29 |accessdate = 2012-01-24}}</ref> consuming computing cycles, using extra electricity and possibly increasing the temperature of the computer (not associated with [http://snowafter.com Snow Day Calculator]). Later that month, the Australian Broadcasting Corporation caught an employee using the company's servers to generate Bitcoins without permission.<ref>{{Cite web|url=http://thenextweb.com/au/2011/06/23/abc-employee-caught-mining-for-bitcoins-on-company-servers/ |title=ABC employee caught mining for Bitcoins on company servers |publisher=The Next Web |date=2011-06-23 |accessdate = 2012-01-24}}</ref> Some malware also uses the parallel processing capabilities of the GPUs built into many modern-day video cards.<ref>{{Cite news |url=http://www.theregister.co.uk/2011/08/16/gpu_bitcoin_brute_forcing/ |title=Malware mints virtual currency using victim's GPU |date=16 August 2011|first=Dan |last=Goodin }}</ref> In mid August 2011, Bitcoin miner botnets were found;<ref>{{Cite web|url=http://www.infosecurity-magazine.com/view/20211/researcher-discovers-distributed-bitcoin-cracking-trojan-malware/ |title=Infosecurity – Researcher discovers distributed bitcoin cracking trojan malware |publisher=Infosecurity-magazine.com |date=2011-08-19 |accessdate = 2012-01-24}}</ref> trojans infecting Mac OS X have also been uncovered.<ref>{{Cite web|url=http://www.techworld.com.au/article/405849/mac_os_x_trojan_steals_processing_power_produce_bitcoins |title=Mac OS X Trojan steals processing power to produce Bitcoins – sophos, security, malware, Intego – Vulnerabilities – Security |publisher=Techworld |date=2011-11-01 |accessdate = 2012-01-24}}</ref>

===Theft and fraud===
On 19 June 2011, a security breach of the Mt.Gox (an acronym for ''M''agic: ''T''he ''G''athering ''O''nline E''x''change, its original purpose) Bitcoin Exchange caused the price of a Bitcoin to briefly drop to US$0.01 on the Mt.Gox exchange (though it remained unaffected on other exchanges) after a hacker allegedly used credentials from a Mt.Gox auditor's compromised computer to illegally transfer a large number of Bitcoins to him- or herself and sell them all, creating a massive "ask" order at any price. Within minutes the price rebounded to over $15 before Mt.Gox shut down their exchange and canceled all trades that happened during the hacking period.<ref>[https://mtgox.com/press_release_20110630.html Clarification of Mt Gox Compromised Accounts and Major Bitcoin Sell-Off]</ref><ref>[http://www.youtube.com/watch?v=T1X6qQt9ONg YouTube. Bitcoin Report]</ref> The exchange rate of Bitcoins quickly returned to near pre-crash values.<ref name="mick">Jason Mick, 19 June 2011, [http://www.dailytech.com/Inside+the+MegaHack+of+Bitcoin+the+Full+Story/article21942.htm Inside the Mega-Hack of Bitcoin: the Full Story], DailyTech</ref><ref>Timothy B. Lee, 19 June 2011, [http://arstechnica.com/tech-policy/news/2011/06/bitcoin-price-plummets-on-compromised-exchange.ars Bitcoin prices plummet on hacked exchange], Ars Technica</ref><ref>Mark Karpeles, 20 June 2011, [https://support.mtgox.com/entries/20208066-huge-bitcoin-sell-off-due-to-a-compromised-account-rollback Huge Bitcoin sell off due to a compromised account – rollback], Mt.Gox Support</ref><ref name="register1">{{Cite news
|title= Bitcoin collapses on malicious trade – Mt Gox scrambling to raise the Titanic
|url= http://www.theregister.co.uk/2011/06/19/bitcoin_values_collapse_again/
|date= 2011-06-19
|author= Chirgwin, Richard
|publisher= The Register
}}</ref> Accounts with the equivalent of more than USD 8,750,000 were affected.<ref name="mick" />

In July 2011, The operator of Bitomat, the third largest Bitcoin exchange, announced that he lost access to his wallet.dat file with about 17,000 BitCoins (roughly equivalent to 220,000 USD at that time). He announced that he would sell the service for the missing amount, aiming to use funds from the sale to refund his customers.<ref>[http://siliconangle.com/blog/2011/08/01/third-largest-bitcoin-exchange-bitomat-lost-their-wallet-over-17000-bitcoins-missing/ Third Largest Bitcoin Exchange Bitomat Lost Their Wallet, Over 17,000 Bitcoins Missing]. SiliconAngle</ref>

In August 2011, MyBitcoin, one of popular Bitcoin transaction processors, declared that it was hacked, which resulted in it being shut down, with paying 49% on customer deposits, leaving more than 78,000 BitCoins (roughly equivalent to 800,000 USD at that time) unaccounted for.<ref>[http://betabeat.com/2011/08/mybitcoin-spokesman-finally-comes-forward-what-did-you-think-we-did-after-the-hack-we-got-shitfaced/ MyBitcoin Spokesman Finally Comes Forward: “What Did You Think We Did After the Hack? We Got Shitfaced”]. BetaBeat</ref><ref>[http://betabeat.com/2011/08/search-for-owners-of-mybitcoin-loses-steam/ Search for Owners of MyBitcoin Loses Steam]. BetaBeat</ref>

In early August 2012, a lawsuit was filed in San Francisco court against Bitcoinica, claiming about 460,000 USD from the company. Bitcoinica was hacked twice in 2012, which led to allegations of neglecting the safety of customers' money and cheating them out of withdrawal requests.<ref>[http://arstechnica.com/tech-policy/2012/08/bitcoinica-users-sue-for-460k-in-lost-bitcoins/ Bitcoinica users sue for $460k in lost Bitcoins]. Arstechnica</ref><ref>[http://spectrum.ieee.org/tech-talk/computing/networks/first-bitcoin-lawsuit-filed-in-san-francisco First Bitcoin Lawsuit Filed In San Francisco]. IEEE Spectrum</ref>

In late August 2012, Bitcoin Savings and Trust was shut down by the owner, allegedly leaving around $5.6 million in debts; this led to allegations of the operation being a Ponzi scheme.<ref>{{Cite web|title=Bitcoin ponzi scheme – investors lose $5 million USD in online hedge fund|url=http://rt.com/usa/news/investors-currency-digital-fund-868/|publisher=RT}}</ref><ref>{{Cite web|last=Jeffries|first=Adrianne|title=Suspected multi-million dollar Bitcoin pyramid scheme shuts down, investors revolt|url=http://www.theverge.com/2012/8/27/3271637/bitcoin-savings-trust-pyramid-scheme-shuts-down|publisher=The Verge}}</ref><ref>{{Cite web|last=Mick|first=Jason|title="Pirateat40" Makes Off $5.6M USD in BitCoins From Pyramid Scheme|url=http://www.dailytech.com/Pirateat40+Makes+Off+56M+USD+in+BitCoins+From+Pyramid+Scheme/article25538.htm|publisher=DailyTech}}</ref><ref>[http://pandodaily.com/2012/08/31/bitcoin-how-a-virtual-currency-became-real-with-a-5-6m-fraud/ Bitcoin: How a Virtual Currency Became Real with a $5.6M Fraud]. PandoDaily</ref> In September 2012, it was reported that U.S. Securities and Exchange Commission has started an investigation on the case.<ref>[http://blogs.telegraph.co.uk/technology/willardfoxton2/100007836/bitcoin-pirate-scandal-sec-steps-in-amid-allegations-that-the-whole-thing-was-a-ponzi-scheme/ Bitcoin 'Pirate' scandal: SEC steps in amid allegations that the whole thing was a Ponzi scheme ]. The Telegraph</ref>

In September 2012, Bitfloor Bitcoin exchange also reported being hacked, with 24,000 BitCoins (roughly equivalent to 250,000 USD) stolen. As a result, Bitfloor suspended operations.<ref>[http://www.bbc.co.uk/news/technology-19486695 Bitcoin theft causes Bitfloor exchange to go offline]. BBC</ref><ref>[http://www.theverge.com/2012/9/5/3293375/bitfloor-bitcoin-exchange-suspended-theft Bitcoin exchange BitFloor suspends operations after $250,000 theft Bitcoin exchange BitFloor suspends operations after $250,000 theft]. The Verge</ref> The same month, Bitfloor resumed operations, with its founder saying that he reported the theft to FBI, and that he is planning to repay the victims, though the time frame for such repayment is unclear.<ref>[http://www.pcworld.com/article/2010586/bitcoin-exchange-back-online-after-hack.html?tk=rel_news Bitcoin exchange back online after hack]. PCWorld</ref>

===Taxation===
In September 2012, the Intra-European Organization of Tax Administrations (IOTA), in Tbilisi, Georgia, held a workshop titled "Auditing Individuals and Legal Entities in the Use of e-Money." The workshop was attended by representatives from 23 countries.<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> Jerry Taylor, IOTA's technical taxation expert, said, "There's an awful lot happening on the Internet environment which is fascinating at the moment and introducing new challenges for auditors when it comes to virtual currency."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> Bitcoin was mentioned during the workshop.<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref>

Matthew Elias, founder of the [[Cryptocurrency Legal Advocacy Group]] (CLAG) published "Staying Between the Lines: A Survey of U.S. Income Taxation and its Ramifications on Cryptocurrencies", which discusses "the taxability of cryptocurrencies such as bitcoin."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> CLAG "stressed the importance for taxpayers to determine on their own whether taxes are due on a bitcoin-related transaction based on whether one has "experienced a realization event."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> Such examples are "when a taxpayer has provided a service in exchange for bitcoins, a realization event has probably occurred, and any gain or loss would likely be calculated using fair market values for the service provided."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref>

[[Peter Vessenes]], [[Bitcoin Foundation|Bitcoin Foundation's]] executive director, said, since the foundation is trying to pay for everything in bitcoin, including salaries, "How do we W-2 someone for their bitcoins? Do we mark-to-market every time a transfer happens? Payroll companies cringe."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> The Bitcoin Foundation hopes "to push for solid guidance about its legal and tax treatment." [[Patrick Murck]], legal counsel for the Bitcoin Foundation, said he would like "to help regulators understand the technology better so they can make better decisions."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref> Murck said, "Bitcoin has the potential to become much more than a niche currency, but it needs the guidance and understanding of regulators." and "The full potential of bitcoin could be realized through clearer guidelines and a better understanding by financial and tax regulators." and "Part of making that happen is to talk to regulators, the IRS, and tax professionals and helping them understand that bitcoin is not this nefarious thing, it's just software, it's a community, and there's nothing inherently nefarious about either of those things."<ref name="BitCoin Tax issues Oct 2012">{{cite journal | title=2012 TNT 209-4 NEWS ANALYSIS: VIRTUAL CURRENCY: A NEW WORRY FOR TAX ADMINISTRATORS?. (Release Date: OCTOBER 17, 2012) (Doc 2012-21516) | author=Stewart, David D. and Soong Johnston, Stephanie D. | journal=Tax Notes Today | year=2012 | month=October 29 | volume=2012 TNT 209-4 | issue=2012 TNT 209-4}}</ref>

==See Also==
* [[Introduction]]
* [[Getting started]]
* [[Using_Bitcoin|Detailed tutorial]]
* [[FAQ]]
* [https://www.weusecoins.com What Is Bitcoin?]
* [https://www.bitcoinmining.com What Is Bitcoin Mining?]

==References==
<references />

[[Category:Digital currencies]]
{{wp}}{{p-move}}{{good}}
[[es:Bitcoin]][[de:Bitcoin]]

User:Victorsueca

2017-04-29T19:07:51Z

Victorsueca:

Hello World! 
My name is Victor Oliver and I live in Valencia, Spain 
You can find me in most internet places and comunities as Victorsueca or Victor_sueca 
I've first heard of bitcoin in 2013, but I didn't really get into it until summer 2015. 
Since then, I've learnt a lot about bitcoin. I know how transactions work, how blocks are mined and what data they contain, how full nodes work generally; all with a bit of technical insight. You don't need a grade in "Blockchain Technical Analysis" or master in "Blockchain apps developement" or whatever fancy names they put, all will end with a arbitrary certificate, signed by an arbitrarily choosed person that certifies that you passed some arbitrary tests to check that you have some knowledge that they arbitrarily consider important..... NOPE. I learnt everything just reading the documentation and asking the great comunity. And remember, when in doubt, google is your friend.

Fallback Nodes

2017-02-14T11:38:05Z

Victorsueca: Removed my node from IPv6 list as it is no longer available through the IPv6 protocol due to breaking changes by my ISP

This is a list of nodes which are considered reliable.

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

[[Bitcoin Core]] versions prior to 0.8.0 also could send [[IP Transactions]] to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back.

=== Tor network ===

To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter:
bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor

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

You can find detailed information on running clients and hidden services within Tor in the [https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md documentation].

== Nodes list ==

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

|-
| bitcoin.moneypot.com || [https://www.moneypot.com moneypot] || 212.47.228.216 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2015-09-15 || No
|-
| node.bitcoin.xxx || [http://www.bitcoin.xxx Bitcoin.xxx] || 66.228.49.201 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-08-28 || Yes
|-
| bitcoin.coinprism.com || [[Coinprism]] || 137.116.225.142 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-04-26 || Yes
|-
|-
| btcnode1.evolyn.net || Evolyn || 85.214.251.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-01-26 || Yes
|-
| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 67.186.224.85 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2013-11-13 || Yes
|-
| archivum.info || Ferraro Ltd.|| 88.198.58.172 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 62.75.216.13 || exMULTI, Inc. || 62.75.216.13 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 69.64.34.118 || exMULTI, Inc. || 69.64.34.118 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 79.160.221.140 || K-Norway || 79.160.221.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| netzbasis.de || unknown3 || 81.169.129.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btc.turboadmin.com || osmosis || 98.143.152.14 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| fallback.bitcoin.zhoutong.com || Zhou Tong || 117.121.241.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| jun.dashjr.org || Luke-Jr || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| cheaperinbitcoins.com || Xenland/Shane || 184.154.36.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| django.webflows.fr || unknown2 || 188.165.213.169 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| porgressbar.sk || progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| faucet.bitcoin.st || bitcoin street || 64.27.57.225 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| bitcoin.securepayment.cc || SecurePayment CC || 63.247.147.163 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| coin.soul-dev.com || Soul-Dev || || || {{Fallback Nodes/Node Up}} || ||
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode2.bitgroup.cc || BitGroup || 162.243.120.138 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode3.bitgroup.cc || BitGroup || 95.85.8.237 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode.xiro.co || Xiro Labs || 91.121.108.61 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 185.122.57.203 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| bitcoin.bitdonut.co || James Hartig
|-
| coinno.de || jaknam
|-
| 82.165.44.44 || anonymous
|-
| bitcoin1.dassori.me || gdassori
|-
| bitcoin2.dassori.me || gdassori
|-
| blockchainnode.meulie.net || [[User:Evert|Evert]]
|-
| fullnode.fybsg.com || Nagato
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 62.210.66.227
|-
| softnet.homenet.org || [[User:Victorsueca|Victorsueca]] || 90.71.117.90
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || 91.121.83.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes

|}

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

| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 2601:7:6680:2ac:4d29:40ff:7513:fcc7 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 11-13-2013 (MDY) || Yes
|-
| caffeinator.net || [[User:Atrophy|Atrophy]] || || || {{Fallback Nodes/Node Up}} || 2013-05-10 ||
|-
| 2001:470:8:2e1::40 || ? || 2001:470:8:2e1::40 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 2a06:8ec0:3::1:2e47 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| bitcoin.bitdonut.co || James Hartig
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 2001:bc8:c087:2001::1
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle]

|}

=== Tor nodes ===

This entire list was last checked on 2015-02-22.

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| 4iuf2zac6aq3ndrb.onion || Hades || Up || 2015-12-16 || No
|-
| ccfxptj3yi2ysa7w.onion || redfish
|-
| nkf5e6b7pl4jfd4a.onion || BlueMatt || Up || 2015-11-11 || No
|-
| hhiv5pnxenvbf4am.onion || ? || Up || 2015-03-17 || No
|-
| bpdlwholl7rnkrkw.onion || kenansulayman || Up || 2015-03-17 || ?
|-
| bk5ejfe56xakvtkk.onion || dserrano5 || Up || 2015-03-17 || No
|-
| wxvp2d4rspn7tqyu.onion || lunokhod || Up || 2015-08-17 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || Down || 2015-03-17 || Yes
|-
| e3tn727fywnioxrc.onion || Zedd || Down || 2015-03-17 || No
|-
| pqosrh6wfaucet32.onion || bitcoin street || Down || 2015-03-17 || No
|-
| r4de4zf4lyniu4mx.onion:8444 || ? || Down || 2015-01-20 || ?
|-
| zy3kdqowmrb7xm7h.onion || Tril || Down || 2015-01-20 || No
|-
| smith4mfhwcq7x3b.onion || Smithtrader || Down || 2014-11-22 || ?
|-
| i2r5tbaizb75h26f.onion || TorDude || Down || 2014-07-24 || No
|-
| btcnet3utgzyz2bf.onion || anonymous || Down || 2014-07-24 || Yes
|-
| kjy2eqzk4zwi5zd3.onion || sipa || Down || 2014-07-24 || No
|-
| tsyvzsqwa2kkf6b2.onion || TorDude || Down || 2014-05-19 || No
|-
| igpdszqrbqjhak5z.onion || anonymous || Down || 2014-05-15 || ?
|-
| evolynhit7shzeet.onion || Evolyn || Down || 2014-05-15 || Yes
|-
| z55v4ostefnwfy32.onion || Tril || Down || 2014-04-09 || No
|-
| bitcoin2u5jnjzzz.onion || anonymous || Down || 2014-01-27 || Yes
|-
| btc4ulpftizx5b72.onion || TorNode || Down || 2013-05-10 || Yes
|-
| yyl3ipdmyjkfypmx.onion || redemerald || Down || 2013-05-10 || Yes
|-
| siqdznszjf4e6v5j.onion || Tuxavant || Down || 2013-05-10 || ?
|-
| 7hxvg2lvr2ashzli.onion || Tuxavant || Down || 2013-05-10 || ?
|-
| x3danbeag2kyx644.onion || redemerald || Down || 2013-01-04 || Yes
|-
| 6hgmaxwellgpv2oe.onion || Gmaxwell || Down || 2012-07-01 || No
|-
| bitcoinprwwpuinm.onion:8333 || ? || Down || 2012-06-26 || ?
|-
| mutqcuh7hwxmhx3k.onion || Xirafe || Down || 2012-06-23 || ?
|-
| sjdntqu5roj4q6lo.onion || torservers || Down || 2012-05-19 || ?
|-
| bitcoin2bkgm3fke.onion || ? || Down || 2012-05-19 || Yes
|-
| ceeji4qpfs3ms3zc.onion || creepa || ? || ? || ?
|-
| yu7sezmixhmyljn4.onion || [[User:Victorsueca|Victorsueca]]
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

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

==See Also==

* [[Network|Bitcoin Network]]
* [http://nodes.bitcoin.st Fallback Nodes] List of longest running Bitcoin Nodes listed by Country.
* [https://getaddr.bitnodes.io/ Bitnodes project]
* [https://blockchain.info/connected-nodes Recently connected nodes at blockchain.info]

{{Bitcoin Core documentation}}

P2Pool

2017-02-13T15:07:40Z

Victorsueca: Updated block reward

{{Infobox company
|name=P2Pool
|trading_name=P2Pool
|industry=[[Mining pool]]
|foundation=July 17, 2011
|hashrate=1.6 Phash/s
|website= http://p2pool.in
}}
[[Image:P2pool_chain.png‎|thumb|350px|right|Visualization of the P2Pool share chain]]

'''P2Pool''' is a decentralized [[Bitcoin]] [[Bitcoin Pool|mining pool]] that works by creating a peer-to-peer network of miner nodes.

<blockquote>P2Pool creates a new block chain in which the difficulty is adjusted so a new block is found every 30 seconds. The blocks that get into the P2Pool block chain (called the "share chain") are the same blocks that would get into the Bitcoin block chain, only they have a lower difficulty target. Whenever a peer announces a new share found (new block in the P2Pool block chain), it is received by the other peers, and the other peers verify that this block contains payouts for all the previous miners who found a share (and announced it) that made it into the P2Pool share chain. This continues until some peer finds a block that has a difficulty that meets the Bitcoin network's difficulty target. This peer announces this block to the Bitcoin network and miners who have submitted shares for this block are paid in the generation transaction, proportionally to how many shares they have found in the last while. - Unknown author</blockquote>

Decentralized payout pooling solves the problem of centralized mining pools degrading the decentralization of Bitcoin and avoids the risk of hard to detect theft by pool operators.

Miners are configured to connect to a P2Pool node that can be run locally, alongside the miner. P2Pool users must run a full Bitcoin node which serves the purpose of independently validating transactions and the Bitcoin blockchain. P2Pool also supports merged mining and several alternative blockchains.

P2Pool nodes work on a chain of shares similar to Bitcoin's blockchain. Each node works on a block that includes payouts to the previous shares' owners and the node itself, which can also result in a share if it meets P2Pool's difficulty.

Because of the importance of strengthening Bitcoin's decentralization, some Bitcoin supporters donate to P2Pool miners, resulting in average returns above 100% of the expected reward.
However, it should be noted that there are other pools (such as [[BitPenny]] and [[Eligius]]) which can provide this same level of decentralization.

== Overview ==

P2Pool shares form a "sharechain" with each share referencing the previous share's hash. Each share contains a standard Bitcoin block header, some P2Pool-specific data that is used to compute the generation transaction (total subsidy, payout script of this share, a nonce, the previous share's hash, and the current target for shares), and a Merkle branch linking that generation transaction to the block header's Merkle hash.

The chain continuously regulates its target to keep generation around one share every thirty seconds, just as Bitcoin regulates it to generate one block every ten minutes.
This means that finding shares becomes more difficult (resulting in higher variance) the more people mine on P2Pool, though large miners have the option to raise their difficulty, and so reduce the impact of their mining on P2Pool's minimum difficulty.

Unlike Bitcoin, nodes do not know the entire chain - instead they only hold the last 8640 shares (the last 3 day's worth). In order to prevent an attacker from working on a chain in secret and then releasing it, overriding the existing chain, chains are judged by how much work they have since a point in the past. To ascertain that the work has been done since that point, nodes look at the Bitcoin blocks that the shares reference, establishing a provable timestamp. (If a share points to a block, it was definitely made after that block was made.)

=== Payout logic ===

Each share contains a generation transaction that pays to the previous ''n'' shares, where ''n'' is the number of shares whose total work is equal to 3 times the average work required to solve a block, or 8640 (= 24 hours of shares), whichever is smaller. Payouts are weighted based on the amount of work each share took to solve, which is proportional to the p2pool difficulty at that time.

The block reward (currently 12.5BTC) and the transaction fees are combined and apportioned according to these rules:

A subsidy of 0.5% is sent to the node that solved the block in order to discourage not sharing solutions that qualify as a block. (A miner with the aim to harm others could withhold the block, thereby preventing anybody from getting paid. He can NOT redirect the payout to himself.) The remaining 99.5% is distributed evenly to miners based on work done recently.

In the event that a share qualifies as a block, this generation transaction is exposed to the Bitcoin network and takes effect, transferring each node its payout.

=== Stales ===

On P2Pool stales refer to shares which can't make it into the sharechain. Because the sharechain is 20 times faster than the Bitcoin chain many stales are common and expected. However, because the payout is [[Comparison_of_mining_pools|PPLNS]] only your stale rate relative to other nodes is relevant; the absolute rate is not.

There are two reported kinds of stales in P2Pool: "DEAD ON ARRIVAL" shares and orphan shares. Dead shares were too old by the time they arrived at your local P2Pool. Very high dead rates can indicate miner misconfiguration. Orphan shares are shares which were not extended by the rest of the P2Pool network, because some other miner's share was accepted first. Very high orphan rates may indicate network connectivity problems.

The P2Pool console output shows your relative stale rate compared to other P2Pool miners in the 'Own efficiency' column:
<pre>
2012-01-07 20:57:51.797420 Pool stales: 13% Own: 13±2% Own efficiency: 100±2%
</pre>

When you first start P2Pool claimed efficiency will be low and the error bounds on this estimate will be large, but as it runs the numbers will converge to their correct values.

If your efficiency is unusually low, make sure your network connection isn't overloaded, that your miners support long polling and are not set to work for excessive amounts of time, and that your bitcoind has multiple connections.

== Joining the pool ==

Follow these steps to join the pool:

* Run Bitcoin with the RPC interface enabled: edit bitcoin.conf to include:
rpcuser=USER
rpcpassword=LONG_RANDOM_SECRET_VALUE
server=1
**'''Replace LONG_RANDOM_SECRET_VALUE with something long and random like the output of smashing your keyboard for a bit like fju4M78yAj3ds39pak92raK'''. You don't need to be able to remember it. If your RPC port becomes exposed to the internet a thief could steal your bitcoin if they could guess it, or use a brute force attack in order to find it.
** Bitcoin 0.8.5 or later is required
** It's important that your Bitcoin client be fully synchronized before starting. It's also better if you have the Bitcoin port forwarded
* Download p2pool:
** Windows binary: See http://forum.bitcoin.org/index.php?topic=18313.0
** Source download: https://github.com/forrestv/p2pool/tags
** git: git clone git://github.com/forrestv/p2pool.git
* Run p2pool: (See below for additional options.)
** Windows py2exe: run_p2pool.exe
** Source: python run_p2pool.py
* Run a miner daemon with long polling connecting to 127.0.0.1 (or the IP of the host running p2pool if it isn't on the same computer as the miner) on port 9332 with any username and password
** bfgminer -O u:p -o http://127.0.0.1:9332/ --submit-stale
* Subscribe to the [https://groups.google.com/forum/#!forum/p2pool-notifications P2Pool notifications] mailing list for urgent pool status updates

Dependencies if running from source:
* Python 2.6 or higher (but not 3.x)
* python-argparse
* Twisted (Ubuntu package python-twisted)

=== Frequently Asked Questions ===

'''Q:''' "Why does my miner report so many longpoll events when mining on p2pool? - P4Man" 
'''A:''' "Once every ~30 seconds is normal. That is how often p2pool shares are generated (as opposed to ~10 min for bitcoin blocks) - cabin"

'''Q:''' "Do the 'orphan' and 'dead' shares in P2Pool's status display hurt me?" 
'''A:''' They shouldn't - It's normal for some fraction of everyone's shares to end up orphaned or dead. Because payouts are calculated by counting how many shares you have relative to others, everyone with normal configurations is equally "hurt" by this. However, if you have a large proportion of stales, your payout will be hurt. You can see how well you're doing by looking at P2Pool's "Efficiency" (ex: ''Efficiency: ~110.6% (40-111%)''). If 100% doesn't lie within the [http://en.wikipedia.org/wiki/Confidence_interval confidence interval] at the end, something is probably wrong (with 95% confidence).

'''Q:''' "What do I do if my efficiency is low?" 
'''A:''' Make sure the computers you're running P2Pool and the miner on have enough memory and CPU time. If you have a lot of dead shares or the "Local dead on arrival" number is higher than a few percent, that means that something is wrong with your miner. Check to make sure that it is one of the working versions in the ''Miners'' section on this page. Lower the intensity or raise the FPS of your miner. If you have a lot of orphan shares, something is wrong with P2Pool's P2P connection. Decrease the load on your internet connection or enable QoS (Quality of Service) on your router.

'''Q:''' What is PPLNS? 
'''A:''' Pay-Per-Last-N-Shares is a payout method that is completely resistant to pool hoppers.

'''Q:''' Why am I not getting very many shares?! 
'''A:''' The P2Pool difficulty is hundreds of times higher than on other pools. It can take time to get a share. P2Pool displays an estimate of how long you have to wait in the console output.

'''Q:''' Why does my miner say it has found a lot of shares but p2pool say I have only found a few?! 
'''A:''' The real P2Pool difficulty is hundreds of times higher than on normal pools, but p2pool essentially lies to your miner and tells it to work on relatively easy shares so that it submits shares every few seconds instead of every few hours. P2Pool then ignores any submitted shares that don't match the real share difficulty. By doing this, P2Pool can more accurately report your local hash rate and you can see if you are having problems with too many stale shares quickly

'''Q:''' Why am I getting so many rejects? 
'''A:''' You're using an incompatible miner. See the miners section here, increase your FPS on the miner, decrease the intensity, upgrade your miner, or try a different miner.

'''Q:''' What stops the pool operator or the block finder from stealing a block? 
'''A:''' A block solution is only worth anything because its hash matches Bitcoin's target. Altering anything within the block will change its hash and make it worthless. If you are concerned about the pool operator stealing a block, you should try to inspect the source code of each new version.

'''Q:''' Why does it say "Generated?" I want to spend my coins now! 
'''A:''' P2Pool includes payouts in generation transactions, which must mature (taking 120 blocks or 20 hours) before they can be spent. The reason for this is that a block could be orphaned, which would make its payout invalid and could reverse transactions.

'''Q:''' Do I get paid transaction fees? 
'''A:''' Yes. They are split among P2Pool miners.

'''Q:''' What are these payments I'm getting that aren't generated? 
'''A:''' These are subsidies that people who support the idea of P2Pool send to miners.

'''Q:''' Cool Subsidies sound like an awesome idea! How do I send some BTC to these awesome miners? 
'''A:''' See end of this page.

'''Q:''' Do I really need the WHOLE blockchain? 
'''A:''' Yes. Your node needs to be able to independently make decisions about what transactions to mine.

'''Q:''' How do merged mining payments work? 
'''A:''' Merged mining is handled entirely by namecoind, so you're solo mining and payouts will go into namecoind's wallet.

=== Miners ===

This is all for the latest p2pool version, as it includes several new workarounds.

With all miners, using a HIGH FPS target (100?) or a LOW intensity (8 for bfgminer?) helps a lot with reducing stales.

* bfgminer, cgminer, and ufasoft work perfectly without any extra options.
* DiabloMiner works fine after commit 3b731b9.
* Phoenix works fine after commit a658ef2.
* Poclbm works fine after commit 5e994e7.

P2Pool uses higher difficulty shares than most centralized pools, so you'll see fewer shares reported. This is normal and doesn't reduce your payments. It's also normal to see longpoll messages once per every ten seconds on average.

====Tips to configure bfgminer to reduce stale/doa:====
* "gpu-threads" : "1", (2 by default)
* "queue" : "0", (1 by default)

Because of fast longpooling in p2pool it is better not NOT fetch work ahead.

On non-dedicated machines intensity=3 allows normal usage of PC, set it to 7 or more to get full hashrate.

On most cards best is diablo and phatk kernel, looks like poclbm kernel have unstable rate.

=== Useful features ===

* If upgrading P2Pool or changing its configuration, you can start another instance of P2Pool in parallel with the first. It will start normally, but realize that the worker and P2P listening ports are busy and keep trying to bind to them in the background. Thus, you can do almost-completely-seamless upgrades of P2Pool.
* If you run multiple P2Pool nodes or have trusted friends that run P2Pool, you can use ''-n'' to establish a constant extra P2P connection to them.
* You can make P2Pool use a configuration file by running run_p2pool.py @FILENAME, with FILENAME being the path to a file containing the command-line arguments (newlines are ignored) Example:
<pre>
--net bitcoin
-n 1.2.3.4
</pre>
* Setting the username of your miner connecting to P2Pool to a Bitcoin address will make it mine to that address instead of the one requested from bitcoind or set by -a
* Appending "/1000" to a miner's username will increase the difficulty of producing a P2Pool share to at most 1000. This is useful to large miners because doing this can make it easier for small miners while minimally impacting the large miners themselves. See [https://bitcointalk.org/index.php?topic=18313.msg816322#msg816322 recommended values].
** Appending "+1" (for example) after that will make P2Pool always give your miners work with a difficulty of 1

=== Web interface ===

Lots of data and useful tools are available at http://127.0.0.1:9332/something:
* /static/ - Lots of information from shares to graphs to payouts.
* /rate
* /users
* /fee
* /current_payouts
* /patron_sendmany - Gives sendmany outputs for fair donations to P2Pool
* /global_stats
* /local_stats
* /peer_addresses
* /payout_addr
* /recent_blocks
* /uptime
* /web/log - Some different stats collected over the last day

=== Included README ===
<pre>Requirements:
Generic:
Bitcoin >=0.6.0rc4 or Bitcoin >=0.5.4 (for BIP16 support) or Litecoin
Python
Twisted
python-argparse (for Python <=2.6)

Linux:
sudo apt-get install python-zope.interface python-twisted python-twisted-web
sudo apt-get install python-argparse # if on Python 2.6 or older

Windows:
Install Python 2.7: http://www.python.org/getit/
Install Twisted: http://twistedmatrix.com/trac/wiki/Downloads
Install Zope.Interface: http://pypi.python.org/pypi/zope.interface/3.8.0
Unzip the files into C:\Python27\Lib\site-packages

Running P2Pool:
To use P2Pool, you must be running your own local bitcoind. For standard
configurations, using P2Pool should be as simple as:

python run_p2pool.py

Then run your miner program, connecting to 127.0.0.1 on port 9332 with any
username and password.

If you are behind a NAT, you should enable TCP port forwarding on your
router. Forward port 9333 to the host running P2Pool.

Run "python run_p2pool.py --help" for additional options.

Notes for Litecoin:
Requirements:
In order to run P2Pool with the Litecoin network, you would need to build and install the
ltc_scrypt module that includes the scrypt proof of work code that Litecoin uses for hashes.

Linux:
cd litecoin_scrypt
sudo python setup.py install

Windows:
Install MinGW: http://www.mingw.org/wiki/Getting_Started
Install Python 2.7: http://www.python.org/getit/

cd litecoin_scrypt
C:\Python27\python.exe setup.py build --compile=mingw32 install

If you run into an error with unrecognized command line option '-mno-cygwin', see this:
http://stackoverflow.com/questions/6034390/compiling-with-cython-and-mingw-produces-gcc-error-unrecognized-command-line-o

Running P2Pool:
Run P2Pool with the "--net litecoin" option.
Run your miner program, connecting to 127.0.0.1 on port 9327.
Forward port 9338 to the host running P2Pool.

Litecoin's use of ports 9332 and 9332 conflicts with P2Pool running on
the Bitcoin network. To avoid problems, add these lines to litecoin.conf
and restart litecoind:
rpcport=10332
port=10333
</pre>

=== Option Reference ===
<pre>
usage: run_p2pool.py [-h] [--version] [--net {bitcoin,litecoin}] [--testnet]
[--debug] [-a ADDRESS] [--datadir DATADIR]
[--logfile LOGFILE] [--merged MERGED_URLS]
[--give-author DONATION_PERCENTAGE] [--iocp]
[--irc-announce] [--no-bugreport] [--p2pool-port PORT]
[-n ADDR[:PORT]] [--disable-upnp] [--max-conns CONNS]
[-w PORT or ADDR:PORT] [-f FEE_PERCENTAGE]
[--bitcoind-address BITCOIND_ADDRESS]
[--bitcoind-rpc-port BITCOIND_RPC_PORT]
[--bitcoind-p2p-port BITCOIND_P2P_PORT]
[BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]

p2pool (version 0.11.1-8-ged9359d)

optional arguments:
-h, --help show this help message and exit
--version show program's version number and exit
--net {bitcoin,litecoin}
use specified network (default: bitcoin)
--testnet use the network's testnet
--debug enable debugging mode
-a ADDRESS, --address ADDRESS
generate payouts to this address (default: <address
requested from bitcoind>)
--datadir DATADIR store data in this directory (default: <directory
run_p2pool.py is in>/data)
--logfile LOGFILE log to this file (default: data/<NET>/log)
--merged MERGED_URLS call getauxblock on this url to get work for merged
mining (example:
http://ncuser:ncpass@127.0.0.1:10332/)
--give-author DONATION_PERCENTAGE
donate this percentage of work towards the development
of p2pool (default: 0.5)
--iocp use Windows IOCP API in order to avoid errors due to
large number of sockets being open
--irc-announce announce any blocks found on
irc://irc.freenode.net/#p2pool
--no-bugreport disable submitting caught exceptions to the author
--disable-upnp don't attempt to use UPnP to forward p2pool's P2P port
from the Internet to this computer

p2pool interface:
--p2pool-port PORT use port PORT to listen for connections (forward this
port from your router!) (default: bitcoin:9333,
litecoin:9338)
-n ADDR[:PORT], --p2pool-node ADDR[:PORT]
connect to existing p2pool node at ADDR listening on
port PORT (defaults to default p2pool P2P port) in
addition to builtin addresses
--max-conns CONNS maximum incoming connections (default: 40)

worker interface:
-w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
listen on PORT on interface with ADDR for RPC
connections from miners (default: all interfaces,
bitcoin:9332, litecoin:9327)
-f FEE_PERCENTAGE, --fee FEE_PERCENTAGE
charge workers mining to their own bitcoin address (by
setting their miner's username to a bitcoin address)
this percentage fee to mine on your p2pool instance.
Amount displayed at http://127.0.0.1:WORKER_PORT/fee
(default: 0)

bitcoind interface:
--bitcoind-address BITCOIND_ADDRESS
connect to this address (default: 127.0.0.1)
--bitcoind-rpc-port BITCOIND_RPC_PORT
connect to JSON-RPC interface at this port (default:
bitcoin:8332, litecoin:9332 <read from bitcoin.conf if
password not provided>)
--bitcoind-p2p-port BITCOIND_P2P_PORT
connect to P2P interface at this port (default:
bitcoin:8333, litecoin:9333 <read from bitcoin.conf if
password not provided>)
BITCOIND_RPCUSERPASS bitcoind RPC interface username, then password, space-
separated (only one being provided will cause the
username to default to being empty, and none will
cause P2Pool to read them from bitcoin.conf)
</pre>

== Interoperability table ==
P2pool works fine with most hardware. This lists some of the hardware confirmed to work and any special configuration required.

* ASICminer blade 10GH/s (Requires adding +1 to username or proxy)
* Avalon 110nm 60-110 GH/s (All batches)
* Avalon based 55nm 200 GH/s (specific makers?)
* Avalon prototype 55nm 120GH/s (~ 20 exist)
* Icarus FPGA
* Bitfury strikes back H-card and M-card ([https://bitcointalk.org/index.php?topic=18313.msg4424081#msg4424081 instructions])
* Bitmain Antminer S1 180GH/s ([https://github.com/AntMiner/AntGen1/tree/master/firmware Requires 20131226 firmware.])
* Bitmain Antminer S3 440GH/s
* BFL SC Jalapeno, SC Single 30, 50, & 60 GH/s
* Spondoolies Tech SP 10
* Spondoolies Tech SP 30

(Various GPU and most FPGAs other than BFL single FPGAs work fine too)

This is a list of hardware with known issues that should not be used on p2pool.

* Cointerra Terraminer IV (10-20% hash rate loss when mining on p2pool)
* Btimain Antminer S2 (10-20% hash rate loss when mining on p2pool, the S1 & S3 both work well on p2pool)

== Protocol description ==

P2Pool's protocol mirrors Bitcoin's P2P protocol in many ways. It uses the same framing (prefix, command, length, checksum, payload) and similar commands:

* '''version''' - sent to establish a connection - contains (''version'', ''services'', ''addr_to'', ''addr_from'', ''nonce'', ''sub_version'', ''mode'', ''best_share_hash'')
* '''setmode''' - sent to update the ''mode'' sent in the '''version''' message - contains (''mode'')
* '''ping''' - sent to keep connection alive - contains ()
* '''addrme''' - request that the receiving node send out an addr for the sending node - contains (''port'')
* '''addrs''' - broadcast list of nodes' addresses - contains (''addrs'')
* '''getaddrs''' - request that the receiving node send ''count'' addrs - contains (''count'')
* '''getshares''' - request that the receiving node send the shares referenced by ''hashes'' and ''parents'' of their parents, stopping at any share referenced by ''stops'' - contains (''hashes'', ''parents'', ''stops'')
* '''shares''' - broadcast message of the contents of shares - contains (''shares'')

==History==

This project was announced on June 17, 2011 by Forrest Voight<ref>[https://forum.bitcoin.org/index.php?topic=18313.0 p2pool: Decentralized, DoS-resistant, Hop-Proof - Now active on mainnet!]</ref>.

The pool began testing against mainnet in mid-July, 2011. The pool was reviewed on a [[Bitcoin Miner]] post on July 26, 2011<ref>[http://www.bitcoinminer.com/post/8101660461 P2Pool Decentralized Pool Nearly Ready For Prime-Time]</ref>.

The software author's address for donations can be found in the signature section of his [http://forum.bitcoin.org/index.php?action=profile;u=6447 forum profile].

==Donating to P2Pool miners==
In order to encourage people to mine to P2Pool you can donate to the recent miners in proportion using a sendmany:

For example, a bash script to donate 10 btc is:
<pre>
~/src/bitcoin/src/bitcoind sendmany "" "$(GET http://127.0.0.1:9332/patron_sendmany/10)"
</pre>

You can replace "" with "accountname" if you want to pay from some specific bitcoind account, and you need to replace 127.0.0.1 with the address of your P2Pool node if you're not running one locally.

Note that the amount you donate will be allocated to recent miners in proportion to the amount of work they've done in the last 24 hours or so, but all the miner whose shares of the donated amount are less than 0.01 BTC will have their shares combined into a single amount which is awarded to one of them at random, with the chance of winning this 'lottery' weighted by the miner's recent amount of work done. You can change this 0.01 BTC threshold like this, for example, which says to pay 10 BTC, but to share it amongst more miners that the default, cutting off at 0.001 BTC instead of at 0.01 BTC.
<pre>
~/src/bitcoin/src/bitcoind sendmany "" "$(GET http://127.0.0.1:9332/patron_sendmany/10/0.001)"
</pre>

If you decide to donate you should announce it on the forums so that your donations provide the most incentive possible.

==Sponsors==

Thanks to:

* The [https://bitcoinfoundation.org/ Bitcoin Foundation] for its generous support of P2Pool
* The [https://litecoin.org/ Litecoin Project] for its generous donations to P2Pool

==See Also==

* [[Comparison of mining pools]]
* [[Pooled Mining]]
* [[P2Pool code documentation]]

==External Links==

* [http://forum.bitcoin.org/index.php?topic=18313.0 P2Pool forum]
* [https://github.com/forrestv/p2pool p2pool] project on GitHub
* {{Freenode IRC|p2pool}} discussion and support
* [http://minefast.coincadence.com/p2pool-stats.php P2Pool Global Stats] stats page
* Up-to-date P2Pool mining stats: [http://minefast.coincadence.com/p2pool-stats.php Minefast.CoinCadence.com P2Pool stats]
* [http://poolnode.info poolnode.info] Public list of P2Pool BTC/LTC nodes.
* [https://www.bitcoinmining.com/bitcoin-mining-pools/ Bitcoin Mining Pools]
* [http://whatisp2pool.com whatisp2pool.com] An easy introduction to mining and P2Pool.
* [https://bitcointalk.org/index.php?topic=18313 Bitcointalk thread]
* [http://organofcorti.blogspot.com/2012/11/52-p2pool-achieving-expectations.html?m=1 Statistical analysis of P2Pool from Neighborhood Pool Watch]
* [http://chimera.labs.oreilly.com/books/1234000001802/ch08.html#mining_pools P2Pool section] of [[Mastering Bitcoin]] by [[Wikipedia:Andreas Antonopoulos|Andreas M. Antonopoulos]]

==References==
<references />

[[Category:Pool Operators]]
{{Pools}}

Bitcoind

2016-11-21T18:05:44Z

Victorsueca: Updated version history

'''bitcoind''' is a program that implements the Bitcoin protocol for remote procedure call (RPC) use. It is also the second Bitcoin [[Clients|client]] in the network's history. It is available under the [http://www.opensource.org/licenses/mit-license.php MIT license] in 32-bit and 64-bit versions for Windows, GNU/Linux-based OSes, and Mac OS X.

As part of Bitcoin Core, bitcoind has been bundled with the original client from version 0.2.6 to 0.4.9, and with [[Bitcoin-Qt]] since 0.5.0.

=== Running ===

See [[Running_bitcoind|running bitcoind]] for more detail and an example of the configuration file.

Bitcoind is a headless daemon, and also bundles a testing tool for the same daemon. It provides a JSON-RPC interface, allowing it to be controlled locally or remotely which makes it useful for integration with other software or in larger payment systems. [[Original Bitcoin client/API Calls list|Various commands]] are made available by the API.

To use locally, first start the program in daemon mode:
:bitcoind -daemon

Then you can execute [[Original Bitcoin client/API Calls list|API commands]], e.g.:
:bitcoin-cli getinfo
:bitcoin-cli listtransactions

To stop the bitcoin daemon, execute:
:bitcoin-cli stop

==History of official bitcoind (and predecessor) releases==
{| class="wikitable"
|-
! Version
! Date
! Supported platforms
! Reference
|-
| 0.13.1
| 2016-Oct-16
| Windows32/64, Linux, ARM Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.13.1 Bitcoin Core version 0.13.1 released]</ref>
|-
| 0.13.0
| 2016-Aug-23
| Windows32/64, Linux, ARM Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.13.0 Bitcoin Core version 0.13.0 released]</ref>
|-
| 0.12.1
| 2016-Apr-15
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.12.1 Bitcoin Core version 0.12.1 released]</ref>
|-
| 0.12.0
| 2016-Feb-23
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.12.0 Bitcoin Core version 0.12.0 released]</ref>
|-
| 0.11.2
| 2015-Nov-13
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.11.2 Bitcoin Core version 0.11.2 released]</ref>
|-
| 0.11.1
| 2015-Oct-15
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.11.1 Bitcoin Core version 0.11.1 released]</ref>
|-
| 0.10.3
| 2015-Oct-14
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.3 Bitcoin Core version 0.10.3 released]</ref>
|-
| 0.11.0
| 2015-Jul-12
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.11.0 Bitcoin Core version 0.11.0 released]</ref>
|-
| 0.10.2
| 2015-May-19
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.2 Bitcoin Core version 0.10.2 released]</ref>
|-
| 0.10.1
| 2015-Apr-27
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.1 Bitcoin Core version 0.10.1 released]</ref>
|-
| 0.10.0
| 2015-Feb-16
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.0 Bitcoin Core version 0.10.0 released]</ref>
|-
| 0.9.3
| 2014-Sep-27
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.3 Bitcoin Core version 0.9.3 released]</ref>
|-
| 0.9.2.1
| 2014-Jun-19
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.2.1 Bitcoin Core version 0.9.2.1 released]</ref>
|-
| 0.9.2
| 2014-Jun-16
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.2 Bitcoin Core version 0.9.2 released]</ref>
|-
| 0.9.1
| 2014-Apr-8
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.1 Bitcoin Core version 0.9.1 released]</ref>
|-
| 0.9.0
| 2014-Mar-19
| Windows32/64, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.0 Bitcoin Core version 0.9.0 released]</ref>
|-
| 0.8.6
| 2013-Dec-9
| Windows32, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.6 Bitcoin-Qt version 0.8.6 released]</ref>
|-
| 0.8.5
| 2013-Sep-13
| Windows32, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.5 Bitcoin-Qt version 0.8.5 released]</ref>
|-
| 0.8.4
| 2013-Sep-3
| Windows32, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.4 Bitcoin-Qt version 0.8.4 released]</ref>
|-
| 0.8.3
| 2013-Jun-25
| Windows32, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.3 Bitcoin-Qt version 0.8.3 released]</ref>
|-
| 0.8.2
| 2013-May-29
| Windows32, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.2 Bitcoin-Qt version 0.8.2 released]</ref>
|-
| 0.8.1
| 2013-Mar-18
| Windows32, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.1 Bitcoin-Qt version 0.8.1 released]</ref>
|-
| 0.8.0
| 2013-Feb-19
| Windows32, Linux, MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.0 Bitcoin-Qt version 0.8.0 released]</ref>
|-
| 0.7.2
| 2012-Dec-14
| Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=130819.msg1399721#msg1399721 Bitcoin-Qt/bitcoind version 0.7.2 released]</ref>
|-
| 0.5.7
| 2012-Nov-23
|
|
|-
| 0.7.1
| 2012-Oct-19
| Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=119277.msg1283232#msg1283232 Bitcoin-Qt/bitcoind version 0.7.1 released]</ref>
|-
| 0.7.0
| 2012-Sep-17
| Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=110243.msg1199467 Bitcoin-Qt/bitcoind version 0.7.0 released]</ref>
|-
| 0.5.6
| 2012-Jul-22
| Windows32, Linux, MacOS X
|
|-
| 0.4.7
| 2012-Jul-22
| Windows32
|
|-
| 0.6.0.9
| 2012-Jul-08
|
|
|-
| 0.6.3
| 2012-Jun-25
| Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=89877.msg989356#msg989356 Bitcoin-Qt / bitcoind version 0.6.3 released]</ref>
|-
| 0.6.2
| 2012-May-08
| Windows32, Linux, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=78829.msg888578#msg888578 Re: Version 0.6.1 release candidate 2]</ref>
|-
| 0.6.1
| 2012-May-04
| Windows32, Linux, MacOS X
|
|-
| 0.6.0.7
| 2012-May-04
|
|
|-
| 0.5.5
| 2012-May-04
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=79651 Version 0.5.5 and 0.4.6 released]</ref>
|-
| 0.4.6
| 2012-May-04
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=79651 Version 0.5.5 and 0.4.6 released]</ref>
|-
| 0.5.4
| 2012-Apr-15
| Windows32, Linux
| <ref>[https://bitcointalk.org/index.php?topic=76808.0 Version 0.5.4 released]</ref>
|-
| 0.4.5
| 2012-Apr-15
|
|
|-
| 0.6.0
| 2012-Mar-30
| Windows32, Linux, MacOS X
| <ref>[http://www.bitcoinforum.com/bitcoin-discussion/bitcoin-org-bitcoin-version-0-6-0-released/ bitcoin.org: Bitcoin version 0.6.0 released]</ref>
|-
| 0.5.3.1
| 2012-Mar-17
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=69120.0 URGENT: Windows Bitcoin-Qt update]</ref>
|-
| 0.5.3
| 2012-Mar-14
| Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=68895.0 Bitcoin-Qt, bitcoind version 0.5.3 released]</ref>
|-
| 0.4.4
| 2012-Mar-14
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=70566.0 bitcoind version 0.4.4 released]</ref>
|-
| 0.5.2
| 2012-Jan-09
| Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=60146.0 Bitcoin-Qt, bitcoind version 0.5.2 released]</ref>
|-
| 0.4.3
| 2012-Jan-09
| Windows32, Linux
| <ref>[https://bitcointalk.org/index.php?topic=57734.0 bitcoind version 0.4.3 released]</ref>
|-
| 0.5.1
| 2011-Dec-15
| Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=54717.0 Bitcoin-Qt, bitcoind version 0.5.1 released]</ref>
|-
| 0.4.2
| 2011-Dec-12
|
|
|-
| 0.5.0
| 2011-Nov-21
| Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=52480.0 Bitcoin-Qt/bitcoind version 0.5.0]</ref>
|-
| 0.4.1
| 2011-Nov-21
| Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=52503.0 wxBitcoin/bitcoind version 0.4.1]</ref>
|-
| 0.4.0
| 2011-Sep-23
| Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=45410.0 Bitcoin version 0.4.0 released]</ref>
|-
| 0.3.24
| 2011-Jul-08
| Windows32, Linux, MacOS X
| <ref>[http://forum.bitcoin.org/index.php?topic=27187.0 Bitcoin version 0.3.24 released]</ref>
|-
| 0.3.23
| 2011-Jun-13
| Windows32, Linux, MacOS X
| <ref>[http://forum.bitcoin.org/index.php?topic=16553.0 Bitcoin version 0.3.23 released]</ref>
|-
| 0.3.22
| 2011-Jun-05
| Windows32, Linux, MacOS X
| <ref>[http://forum.bitcoin.org/index.php?topic=12269.0 Bitcoin version 0.3.22]</ref>
|-
| 0.3.21
| 2011-Apr-27
| Windows32, Linux, MacOS X
| <ref>[http://bitcointalk.org/?topic=6642.0 Bitcoin version 0.3.21]</ref>
|-
| 0.3.20
| 2011-Feb-21
| Windows32, Linux, MacOS X
| <ref>[http://www.bitcoin.org/smf/index.php?topic=3704.0 Version 0.3.20]</ref>
|-
|0.3.19
|2010-12-12
|Windows32, Linux, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=2228.msg29479#msg29479 Added some DoS limits, removed safe mode (0.3.19)]</ref>
|-
|0.3.18
|2010-12-08
|Windows32, Linux, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=2162.0 Version 0.3.18]</ref>
|-
|0.3.17
|2010-11-25
|Windows32, Linux, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=1946.0 Version 0.3.17]</ref>
|-
|0.3.15
|2010-11-13
|Windows32, Linux
|<ref>[https://bitcointalk.org/index.php?topic=1780.0 Version 0.3.15]</ref>
|-
|0.3.14
|2010-10-21
|Windows32, Linux
|<ref>[https://bitcointalk.org/index.php?topic=1528.0 Version 0.3.14]</ref>
|-
|0.3.13
|2010-10-01
|Windows32, Linux, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=1327.0 Version 0.3.13, please upgrade]</ref>
|-
|0.3.12
|2010-09-07
|Windows32, Linux
|<ref>[https://bitcointalk.org/index.php?topic=999.0 Version 0.3.12 is now available.]</ref>
|-
|0.3.11
|2010-08-27
|Windows32, Linux, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=941.0 Version 0.3.11 is now available.]</ref>
|-
|0.3.10
|2010-08-15
|Windows32, Linux32/64, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=820.msg9452#msg9452 tcatm's 4-way SSE2 for Linux 32/64-bit is in 0.3.10]</ref>
|-
|0.3.8.1
|2010-08-09
|Linux64
|<ref>[https://bitcointalk.org/index.php?topic=765.0 Version 0.3.8.1 update for Linux 64-bit]</ref>
|-
|0.3.8
|2010-08-03
|Windows32, Linux, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=696.0 Please upgrade to 0.3.8!]</ref>
|-
|0.3.7
|2010-08-01
|Windows32, Linux, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=664.0 0.3.7 Changes]</ref>
|-
|0.3.6
|2010-07-29
|Windows32, Linux, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=626.0 *** ALERT *** Upgrade to 0.3.6]</ref>
|-
|0.3.3
|2010-07-25
|Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=570.0 Bitcoin 0.3.3 released -- PLEASE UPGRADE]</ref>
|-
|0.3.2.5
|2010-07-24
|Windows32, Linux
| <ref>[https://bitcointalk.org/index.php?topic=556.0 Version 0.3.2.5 -- please test!]</ref>
|-
|0.3.2
|2010-07-17
|Windows32, Linux, MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=437.0 Bitcoin 0.3.2 released]</ref>
|-
|0.3.1
|2010-07-15
|Windows32, Linux
|<ref>[https://bitcointalk.org/index.php?topic=383.0 Bitcoin 0.3.1 released]</ref>
|-
|0.3.0
|2010-07-06
|Windows32, Linux, MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=238.0 Bitcoin 0.3 released!]</ref><ref>[http://sourceforge.net/mailarchive/message.php?msg_id=25686730 Bitcoin 0.3 released!]</ref>
|-
|0.2.0
|2009-12-17 06:52
|Windows XP /Vista, Linux
|<ref>[https://bitcointalk.org/index.php?topic=16.0 Bitcoin 0.2 released!]</ref><ref>[http://sourceforge.net/mailarchive/message.php?msg_id=24205662 Bitcoin 0.2 released]</ref>
|-
|0.1.5
|2009-02-04 19:46
|Windows NT/2000/XP
|<ref>[http://sourceforge.net/mailarchive/message.php?msg_id=21500063 Bitcoin v0.1.5 released]</ref>
|-
|0.1.3
|2009-01-12 22:48
|Windows NT/2000/XP
|<ref>[http://sourceforge.net/mailarchive/message.php?msg_id=21313152 Bitcoin v0.1.3]</ref>
|-
|0.1.2
|2009-01-11 22:32
|Windows NT/2000/XP
|<ref>[http://sourceforge.net/mailarchive/message.php?msg_id=21303153 Bitcoin v0.1.2 now available]</ref>
|-
|0.1.0
|2009-01-09
|Windows NT/2000/XP
|
|}

Up to and including version 0.3.19 is the "Satoshi code". The founder retired from development with end of 2010. [https://bitcointalk.org/index.php?topic=68121.10;wap2/ Here] are three URLs given where you still(!) (2013-01-04) can download one of the [[Satoshi client|"original Satoshi codes"]]. So also this [http://www.antepedia.com/detail/p/237812136.html Bitcoin release history].

==Theory of Operation==

bitcoind is a multithreaded C++ program. It is designed to be portable across Windows, Mac, and Linux systems. The multithreaded aspect leads to some complexity and the use of certain code patterns to deal with concurrency that may be unfamiliar to many programmers. Also, the code is aggressive in the use of C++ constructs, so it will help to be fluent with map, multimap, set, string, vector, iostream, and templates. As is typical of a C++ program, a lot of code tends to end up in the header files so be sure to search both the .cpp and .h files when looking for a function.

The client is oriented around several major operations, which are described in separate detailed articles and summarized in the following sections.

===[[Satoshi Client Initialization and Startup|Initialization and Startup]]===
Upon startup, the client performs various initialization routines including starting multiple threads to handle concurrent operations.

===[[Satoshi Client Node Discovery|Node Discovery]]===
The client uses various techniques to find out about other Bitcoin nodes that are currently connected to the network.

===[[Satoshi Client Node Connectivity|Node Connectivity]]===
The client initiates and maintains connections to other nodes.

===[[Satoshi Client Sockets and Messages|Sockets and Messages]]===
The client processes messages from other nodes and sends messages to other nodes using socket connections.

===[[Satoshi Client Block Exchange|Block Exchange]]===
Nodes advertise their inventory of blocks to each other and exchange blocks to build block chains.

===[[Satoshi Client Transaction Exchange|Transaction Exchange]]===
Nodes exchange and relay transactions with each other. The client associates transactions with bitcoin addresses in the local wallet.

===Wallet Services===
The client can create transactions using the local wallet. The client associates transactions with bitcoin addresses in the local wallet. The client provides a service for managing the local wallet.

===RPC Interface===
The client offers an JSON-RPC interface over HTTP over sockets to perform various operational functions and to manage the local wallet.

===User Interface===
Bitcoind's current user interface is the command line while it used to be based on [http://www.wxwidgets.org wxWidgets]. A graphical user interface is now provided by [[Bitcoin-qt]] in version 0.5+ for the reference client.

==Troubleshooting==

===I get "Error loading blkindex.dat" when I try to run the client===

<code>blkindex.dat</code> is part of the database that stores the local copy of the blockchain which may have become corrupted.

Open the Bitcoin [[data directory]]:

* Windows: <code>%APPDATA%\Bitcoin</code>
* Linux: <code>~/.bitcoin</code>
* Mac: <code>~/Library/Application Support/Bitcoin/</code>

Make a backup of that entire folder, then delete everything EXCEPT <code>[[Wallet|wallet.dat]]</code>. [[Running Bitcoin|Start bitcoin]] again and it will download a fresh copy of the [[blockchain]] (WARNING: This will take a long time).

==See Also==

* [[Original Bitcoin client/API calls list]]
* [[Protocol specification|Bitcoin network protocol]]
* [[Development process]]
* [[Release process]]
* [[Changelog]]

==External Links==
* [https://github.com/bitcoin/bitcoin/ Bitcoin Core project on GitHub]

==References==
<references />
`
[[es:Bitcoind]]

[[Category:Nodes]]
[[Category:Wallets]]
[[Category:User Interfaces]]
[[Category:Clients]]
[[Category:Developer]]
[[Category:Technical]]
[[Category:Free Software]]
[[Category:License/MIT-X11]]
[[Category:Open Source]]
{{lowercase}}

Fallback Nodes

2016-09-26T10:56:40Z

Victorsueca: Updated my IP after ISP change

This is a list of nodes which are considered reliable.

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

[[Bitcoin Core]] versions prior to 0.8.0 also could send [[IP Transactions]] to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back.

=== Tor network ===

To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter:
bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor

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

You can find detailed information on running clients and hidden services within Tor in the [https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md documentation].

== Nodes list ==

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

|-
| bitcoin.moneypot.com || [https://www.moneypot.com moneypot] || 212.47.228.216 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2015-09-15 || No
|-
| node.bitcoin.xxx || [http://www.bitcoin.xxx Bitcoin.xxx] || 66.228.49.201 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-08-28 || Yes
|-
| bitcoin.coinprism.com || [[Coinprism]] || 137.116.225.142 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-04-26 || Yes
|-
|-
| btcnode1.evolyn.net || Evolyn || 85.214.251.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-01-26 || Yes
|-
| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 67.186.224.85 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2013-11-13 || Yes
|-
| archivum.info || Ferraro Ltd.|| 88.198.58.172 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 62.75.216.13 || exMULTI, Inc. || 62.75.216.13 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 69.64.34.118 || exMULTI, Inc. || 69.64.34.118 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 79.160.221.140 || K-Norway || 79.160.221.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| netzbasis.de || unknown3 || 81.169.129.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btc.turboadmin.com || osmosis || 98.143.152.14 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| fallback.bitcoin.zhoutong.com || Zhou Tong || 117.121.241.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| jun.dashjr.org || Luke-Jr || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| cheaperinbitcoins.com || Xenland/Shane || 184.154.36.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| django.webflows.fr || unknown2 || 188.165.213.169 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| porgressbar.sk || progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| faucet.bitcoin.st || bitcoin street || 64.27.57.225 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| bitcoin.securepayment.cc || SecurePayment CC || 63.247.147.163 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| coin.soul-dev.com || Soul-Dev || || || {{Fallback Nodes/Node Up}} || ||
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode2.bitgroup.cc || BitGroup || 162.243.120.138 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode3.bitgroup.cc || BitGroup || 95.85.8.237 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode.xiro.co || Xiro Labs || 91.121.108.61 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 185.122.57.203 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| bitcoin.bitdonut.co || James Hartig
|-
| coinno.de || jaknam
|-
| 82.165.44.44 || anonymous
|-
| bitcoin1.dassori.me || gdassori
|-
| bitcoin2.dassori.me || gdassori
|-
| blockchainnode.meulie.net || [[User:Evert|Evert]]
|-
| fullnode.fybsg.com || Nagato
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 62.210.66.227
|-
| softnet.homenet.org || [[User:Victorsueca|Victorsueca]] || 90.71.117.90
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || 91.121.83.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes

|}

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

| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 2601:7:6680:2ac:4d29:40ff:7513:fcc7 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 11-13-2013 (MDY) || Yes
|-
| caffeinator.net || [[User:Atrophy|Atrophy]] || || || {{Fallback Nodes/Node Up}} || 2013-05-10 ||
|-
| 2001:470:8:2e1::40 || ? || 2001:470:8:2e1::40 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| stuff.liam-w.io || [[User:liamwli|Liam W]] || 2a06:8ec0:3::1:2e47 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| bitcoin.bitdonut.co || James Hartig
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 2001:bc8:c087:2001::1
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle]
|-
| softnet.homenet.org || [[User:Victorsueca|Victorsueca]] || 2001:0:9d38:6ab8:181a:1638:a5b8:8aa5

|}

=== Tor nodes ===

This entire list was last checked on 2015-02-22.

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| 4iuf2zac6aq3ndrb.onion || Hades || Up || 2015-12-16 || No
|-
| ccfxptj3yi2ysa7w.onion || redfish
|-
| nkf5e6b7pl4jfd4a.onion || BlueMatt || Up || 2015-11-11 || No
|-
| hhiv5pnxenvbf4am.onion || ? || Up || 2015-03-17 || No
|-
| bpdlwholl7rnkrkw.onion || kenansulayman || Up || 2015-03-17 || ?
|-
| bk5ejfe56xakvtkk.onion || dserrano5 || Up || 2015-03-17 || No
|-
| wxvp2d4rspn7tqyu.onion || lunokhod || Up || 2015-08-17 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || Down || 2015-03-17 || Yes
|-
| e3tn727fywnioxrc.onion || Zedd || Down || 2015-03-17 || No
|-
| pqosrh6wfaucet32.onion || bitcoin street || Down || 2015-03-17 || No
|-
| r4de4zf4lyniu4mx.onion:8444 || ? || Down || 2015-01-20 || ?
|-
| zy3kdqowmrb7xm7h.onion || Tril || Down || 2015-01-20 || No
|-
| smith4mfhwcq7x3b.onion || Smithtrader || Down || 2014-11-22 || ?
|-
| i2r5tbaizb75h26f.onion || TorDude || Down || 2014-07-24 || No
|-
| btcnet3utgzyz2bf.onion || anonymous || Down || 2014-07-24 || Yes
|-
| kjy2eqzk4zwi5zd3.onion || sipa || Down || 2014-07-24 || No
|-
| tsyvzsqwa2kkf6b2.onion || TorDude || Down || 2014-05-19 || No
|-
| igpdszqrbqjhak5z.onion || anonymous || Down || 2014-05-15 || ?
|-
| evolynhit7shzeet.onion || Evolyn || Down || 2014-05-15 || Yes
|-
| z55v4ostefnwfy32.onion || Tril || Down || 2014-04-09 || No
|-
| bitcoin2u5jnjzzz.onion || anonymous || Down || 2014-01-27 || Yes
|-
| btc4ulpftizx5b72.onion || TorNode || Down || 2013-05-10 || Yes
|-
| yyl3ipdmyjkfypmx.onion || redemerald || Down || 2013-05-10 || Yes
|-
| siqdznszjf4e6v5j.onion || Tuxavant || Down || 2013-05-10 || ?
|-
| 7hxvg2lvr2ashzli.onion || Tuxavant || Down || 2013-05-10 || ?
|-
| x3danbeag2kyx644.onion || redemerald || Down || 2013-01-04 || Yes
|-
| 6hgmaxwellgpv2oe.onion || Gmaxwell || Down || 2012-07-01 || No
|-
| bitcoinprwwpuinm.onion:8333 || ? || Down || 2012-06-26 || ?
|-
| mutqcuh7hwxmhx3k.onion || Xirafe || Down || 2012-06-23 || ?
|-
| sjdntqu5roj4q6lo.onion || torservers || Down || 2012-05-19 || ?
|-
| bitcoin2bkgm3fke.onion || ? || Down || 2012-05-19 || Yes
|-
| ceeji4qpfs3ms3zc.onion || creepa || ? || ? || ?
|-
| yu7sezmixhmyljn4.onion || [[User:Victorsueca|Victorsueca]]
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

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

==See Also==

* [[Network|Bitcoin Network]]
* [http://nodes.bitcoin.st Fallback Nodes] List of longest running Bitcoin Nodes listed by Country.
* [https://getaddr.bitnodes.io/ Bitnodes project]
* [https://blockchain.info/connected-nodes Recently connected nodes at blockchain.info]

{{Bitcoin Core documentation}}

Fallback Nodes

2016-07-09T11:43:37Z

Victorsueca: Updated my nodes

This is a list of nodes which are considered reliable.

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

[[Bitcoin Core]] versions prior to 0.8.0 also could send [[IP Transactions]] to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back.

=== Tor network ===

To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter:
bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor

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

You can find detailed information on running clients and hidden services within Tor in the [https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md documentation].

== Nodes list ==

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

|-
| bitcoin.moneypot.com || [https://www.moneypot.com moneypot] || 212.47.228.216 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2015-09-15 || No
|-
| node.bitcoin.xxx || [http://www.bitcoin.xxx Bitcoin.xxx] || 66.228.49.201 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-08-28 || Yes
|-
| bitcoin.coinprism.com || [[Coinprism]] || 137.116.225.142 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-04-26 || Yes
|-
|-
| btcnode1.evolyn.net || Evolyn || 85.214.251.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-01-26 || Yes
|-
| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 67.186.224.85 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2013-11-13 || Yes
|-
| archivum.info || Ferraro Ltd.|| 88.198.58.172 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 62.75.216.13 || exMULTI, Inc. || 62.75.216.13 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 69.64.34.118 || exMULTI, Inc. || 69.64.34.118 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 79.160.221.140 || K-Norway || 79.160.221.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| netzbasis.de || unknown3 || 81.169.129.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btc.turboadmin.com || osmosis || 98.143.152.14 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| fallback.bitcoin.zhoutong.com || Zhou Tong || 117.121.241.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| jun.dashjr.org || Luke-Jr || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| cheaperinbitcoins.com || Xenland/Shane || 184.154.36.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| django.webflows.fr || unknown2 || 188.165.213.169 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| porgressbar.sk || progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| faucet.bitcoin.st || bitcoin street || 64.27.57.225 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| bitcoin.securepayment.cc || SecurePayment CC || 63.247.147.163 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| coin.soul-dev.com || Soul-Dev || || || {{Fallback Nodes/Node Up}} || ||
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode2.bitgroup.cc || BitGroup || 162.243.120.138 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode3.bitgroup.cc || BitGroup || 95.85.8.237 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode.xiro.co || Xiro Labs || 91.121.108.61 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| occult.xf-liam.com || [[User:liamwli|Liam W]] || 216.189.157.221 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| bitcoin.bitdonut.co || James Hartig
|-
| coinno.de || jaknam
|-
| 82.165.44.44 || anonymous
|-
| bitcoin1.dassori.me || gdassori
|-
| bitcoin2.dassori.me || gdassori
|-
| blockchainnode.meulie.net || [[User:Evert|Evert]]
|-
| fullnode.fybsg.com || Nagato
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 62.210.66.227
|-
| softnet.homenet.org || [[User:Victorsueca|Victorsueca]] || 81.203.121.194
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || 91.121.83.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes

|}

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

| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 2601:7:6680:2ac:4d29:40ff:7513:fcc7 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 11-13-2013 (MDY) || Yes
|-
| caffeinator.net || [[User:Atrophy|Atrophy]] || || || {{Fallback Nodes/Node Up}} || 2013-05-10 ||
|-
| 2001:470:8:2e1::40 || ? || 2001:470:8:2e1::40 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| occult.xf-liam.com || [[User:liamwli|Liam W]] || 2602:ffc5:40::1:c373 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| bitcoin.bitdonut.co || James Hartig
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 2001:bc8:c087:2001::1
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle]
|-
| softnet.homenet.org || [[User:Victorsueca|Victorsueca]] || 2001:0:5ef5:79fb:477:c3:ae34:863d

|}

=== Tor nodes ===

This entire list was last checked on 2015-02-22.

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| 4iuf2zac6aq3ndrb.onion || Hades || Up || 2015-12-16 || No
|-
| ccfxptj3yi2ysa7w.onion || redfish
|-
| nkf5e6b7pl4jfd4a.onion || BlueMatt || Up || 2015-11-11 || No
|-
| hhiv5pnxenvbf4am.onion || ? || Up || 2015-03-17 || No
|-
| bpdlwholl7rnkrkw.onion || kenansulayman || Up || 2015-03-17 || ?
|-
| bk5ejfe56xakvtkk.onion || dserrano5 || Up || 2015-03-17 || No
|-
| wxvp2d4rspn7tqyu.onion || lunokhod || Up || 2015-08-17 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || Down || 2015-03-17 || Yes
|-
| e3tn727fywnioxrc.onion || Zedd || Down || 2015-03-17 || No
|-
| pqosrh6wfaucet32.onion || bitcoin street || Down || 2015-03-17 || No
|-
| r4de4zf4lyniu4mx.onion:8444 || ? || Down || 2015-01-20 || ?
|-
| zy3kdqowmrb7xm7h.onion || Tril || Down || 2015-01-20 || No
|-
| smith4mfhwcq7x3b.onion || Smithtrader || Down || 2014-11-22 || ?
|-
| i2r5tbaizb75h26f.onion || TorDude || Down || 2014-07-24 || No
|-
| btcnet3utgzyz2bf.onion || anonymous || Down || 2014-07-24 || Yes
|-
| kjy2eqzk4zwi5zd3.onion || sipa || Down || 2014-07-24 || No
|-
| tsyvzsqwa2kkf6b2.onion || TorDude || Down || 2014-05-19 || No
|-
| igpdszqrbqjhak5z.onion || anonymous || Down || 2014-05-15 || ?
|-
| evolynhit7shzeet.onion || Evolyn || Down || 2014-05-15 || Yes
|-
| z55v4ostefnwfy32.onion || Tril || Down || 2014-04-09 || No
|-
| bitcoin2u5jnjzzz.onion || anonymous || Down || 2014-01-27 || Yes
|-
| btc4ulpftizx5b72.onion || TorNode || Down || 2013-05-10 || Yes
|-
| yyl3ipdmyjkfypmx.onion || redemerald || Down || 2013-05-10 || Yes
|-
| siqdznszjf4e6v5j.onion || Tuxavant || Down || 2013-05-10 || ?
|-
| 7hxvg2lvr2ashzli.onion || Tuxavant || Down || 2013-05-10 || ?
|-
| x3danbeag2kyx644.onion || redemerald || Down || 2013-01-04 || Yes
|-
| 6hgmaxwellgpv2oe.onion || Gmaxwell || Down || 2012-07-01 || No
|-
| bitcoinprwwpuinm.onion:8333 || ? || Down || 2012-06-26 || ?
|-
| mutqcuh7hwxmhx3k.onion || Xirafe || Down || 2012-06-23 || ?
|-
| sjdntqu5roj4q6lo.onion || torservers || Down || 2012-05-19 || ?
|-
| bitcoin2bkgm3fke.onion || ? || Down || 2012-05-19 || Yes
|-
| ceeji4qpfs3ms3zc.onion || creepa || ? || ? || ?
|-
| yu7sezmixhmyljn4.onion || [[User:Victorsueca|Victorsueca]]
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

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

==See Also==

* [[Network|Bitcoin Network]]
* [http://nodes.bitcoin.st Fallback Nodes] List of longest running Bitcoin Nodes listed by Country.
* [https://getaddr.bitnodes.io/ Bitnodes project]
* [https://blockchain.info/connected-nodes Recently connected nodes at blockchain.info]

{{Bitcoin Core documentation}}

Transaction broadcasting

2016-07-06T16:10:23Z

Victorsueca: Removed dead pages

{{seealso|Satoshi Client Transaction Exchange}}

==See Also==

Third party sites to (re-)submit a raw, signed transaction to the network; sometimes referred to as "pushtx":

* https://insight.bitpay.com/tx/send
* https://blockchain.info/pushtx
* https://blockexplorer.com/tx/send
* https://btc.blockr.io/tx/push
* https://coinb.in/#broadcast
* https://chain.localbitcoins.com/tx/send
* http://webbtc.com/relay_tx
* https://www.smartbit.com.au/txs/pushtx
* https://live.blockcypher.com/btc/pushtx/
* https://www.f2pool.com/pushtx (Needs referral code from pool operator.)
* https://wallet.la/pushtx (Expired https certificate)

Currently defunct:

* <ref>Messages following: https://bitcointalk.org/index.php?topic=441465.msg10027173#msg10027173</ref> http://eligius.st/~wizkid057/newstats/pushtxn.php (Contact wizkid057 directly if you need a transaction mined.)
* https://helloblock.io/propagate
* https://armory.online/tx/send
* https://search.bitaccess.ca/tx/send
* https://services.moloch.net/broadcast

==References==

Myths

2016-07-06T09:15:47Z

Victorsueca: Changed the bitcoin nodes map as the old google maps custom map seems to not be available anymore.

Let's clear up some common Bitcoin misconceptions.

== Bitcoin is just like all other digital currencies; nothing new ==

Nearly all other digital currencies are centrally controlled. This means that:
* They can be printed at the subjective whims of the controllers
* They can be destroyed by attacking the central point of control
* Arbitrary rules can be imposed upon their users by the controllers

Being decentralized, Bitcoin solves all of these problems.

== Bitcoins don't solve any problems that fiat currency and/or gold doesn't solve ==

Unlike gold, bitcoins are:
* Easy to transfer
* Easy to secure
* Easy to verify
* Easy to granulate

Unlike fiat currencies, bitcoins are:
* Predictable and limited in [[Controlled_Currency_Supply|supply]]
* Not controlled by a central authority (such as [http://en.wikipedia.org/wiki/Federal_Reserve The United States Federal Reserve])
* Not debt-based

Unlike electronic fiat currency systems, bitcoins are:
* Potentially anonymous
* Freeze-proof
* Faster to transfer
* Cheaper to transfer

== Bitcoin is backed by processing power ==

It is not correct to say that Bitcoin is "backed by" processing power. A currency being "backed" means that it is pegged to something else via a central party at a certain exchange rate yet you cannot exchange bitcoins for the computing power that was used to create them. Bitcoin is in this sense not backed by anything. It is a currency in its own right. Just as gold is not backed by anything, the same applies to Bitcoin.

The Bitcoin currency is ''created'' via processing power, and the integrity of the block chain is ''protected'' by the existence of a network of powerful computing nodes from certain [[Weaknesses#Attacker_has_a_lot_of_computing_power|attacks]].

== Bitcoins are worthless because they aren't backed by anything ==

One could argue that gold isn't backed by anything either. Bitcoins have properties resulting from the system's design that allows them to be subjectively valued by individuals. This valuation is demonstrated when individuals freely exchange for or with bitcoins. Please refer to the [http://en.wikipedia.org/wiki/Subjective_theory_of_value Subjective Theory of Value].

See also: the "[[#Bitcoin_is_backed_by_processing_power|Bitcoin is backed by processing power]]" myth.

== The value of bitcoins are based on how much electricity and computing power it takes to mine them ==

This statement is an attempt to apply to Bitcoin the [http://en.wikipedia.org/wiki/Labor_theory_of_value labor theory of value], which is generally accepted as false. Just because something takes X resources to create does not mean that the resulting product will be worth X. It can be worth more, or less, depending on the utility thereof to its users.

In fact the causality is the reverse of that (this applies to the labor theory of value in general). The cost to mine bitcoins is based on how much they are worth. If bitcoins go up in value, more people will mine (because [[Mining|mining]] is profitable), thus [[difficulty]] will go up, thus the cost of mining will go up. The inverse happens if bitcoins go down in value. These effects balance out to cause mining to always cost an amount proportional to the value of bitcoins it produces<ref>[https://www.bitcoinmining.com Bitcoin Mining]</ref>.

== Bitcoins have no intrinsic value (unlike some other things) ==

This is simply not true. Each bitcoin gives the holder the ability to embed a large number of short in-transaction messages in a globally distributed and timestamped permanent data store, namely the bitcoin blockchain. There is no other similar datastore which is so widely distributed. There is a tradeoff between the exact number of messages and how quickly they can be embedded. But as of December 2013, it's fair to say that one bitcoin allows around 1000 such messages to be embedded, each within about 10 minutes of being sent, since a fee of 0.001 BTC is enough to get transactions confirmed quickly. This message embedding certainly has intrinsic value since it can be used to prove ownership of a document at a certain time, by including a one-way hash of that document in a transaction. Considering that electronic notarization services charge something like $10/document, this would give an intrinsic value of around $10,000 per bitcoin.

While some other tangible commodities do have intrinsic value, that value is generally much less than its trading price. Consider for example that gold, if it were not used as an inflation-proof store of value, but rather only for its industrial uses, would certainly not be worth what it is today, since the industrial requirements for gold are far smaller than the available supply thereof.

In any event, while historically intrinsic value, as well as other attributes like divisibility, fungibility, scarcity, durability, helped establish certain commodities as mediums of exchange, it is certainly not a prerequisite. While bitcoins are accused of lacking 'intrinsic value' in this sense, they make up for it in spades by possessing the other qualities necessary to make it a good medium of exchange, equal to or better than [http://en.wikipedia.org/wiki/Commodity_money commodity money].

Another way to think about this is to consider the value of bitcoin the global network, rather than each bitcoin in isolation. The value of an individual telephone is derived from the network it is connected to. If there was no phone network, a telephone would be useless. Similarly the value of an individual bitcoin derives from the global network of bitcoin-enabled merchants, exchanges, wallets, etc... Just like a phone is necessary to transmit vocal information through the network, a bitcoin is necessary to transmit economic information through the network.

Value is ultimately determined by what people are willing to trade for - by supply and demand.

== Bitcoins are illegal because they're not legal tender ==
In March 2013, the U.S. [http://en.wikipedia.org/wiki/Financial_Crimes_Enforcement_Network Financial Crimes Enforcement Network] issues a new set of guidelines on "de-centralized virtual currency", clearly targeting Bitcoin. Under the new guidelines, "a user of virtual currency is not a Money Services Businesses (MSB) under FinCEN's regulations and therefore is not subject to MSB registration, reporting, and record keeping regulations." <ref>[http://arstechnica.com/tech-policy/2013/03/us-regulator-bitcoin-exchanges-must-comply-with-money-laundering-laws/ US regulator: Bitcoin exchanges must comply with money-laundering laws | Ars Technica]</ref> [[Mining|Miners]], when mining bitcoins for their own personal use, aren't required to register as a MSB or Money Transmitter. <ref>[http://fincen.gov/news_room/rp/rulings/html/FIN-2014-R001.html Application of FinCEN’s Regulations to Virtual Currency Mining Operations | Fincen]</ref>

In general, there are a [http://en.wikipedia.org/wiki/Local_currency number of currencies] in existence that are not official government-backed currencies. A currency is, after all, nothing more than a convenient unit of account. While national laws may vary from country to country, and you should certainly check the laws of your jurisdiction, in general trading in any commodity, including digital currency like Bitcoin, [http://en.wikipedia.org/wiki/BerkShares BerkShares], game currencies like WoW gold, or Linden dollars, is not illegal.

== Bitcoin is a form of domestic terrorism because it only harms the economic stability of the USA and its currency ==

According to [http://en.wikipedia.org/wiki/Definitions_of_terrorism#United_States the definition of terrorism in the United States], you need to do violent activities to be considered a terrorist for legal purposes. Recent off-the-cuff remarks by politicians have no basis in law or fact.

Also, Bitcoin isn't domestic to the US or any other country. It's a worldwide community, as can be seen in this [https://bitnodes.21.co/nodes/live-map/ map of Bitcoin nodes].

== Bitcoin will only enable tax evaders which will lead to the eventual downfall of civilization ==

Cash transactions hold the same level of anonymity but are still taxed successfully. It is up to you to follow the applicable state laws in your home country, or face the consequences.

While it may be easy to transfer bitcoins anonymously, ''spending'' them anonymously on tangibles is just as hard as spending any other kind of money anonymously. Tax evaders are often caught because their lifestyle and assets are inconsistent with their reported income, and not necessarily because government is able to follow their money.

== Bitcoins can be printed/minted by anyone and are therefore worthless ==

Bitcoins are not printed/minted. Instead, [[Blocks]] are computed by miners and for their efforts they are awarded a specific amount of bitcoins and transaction fees paid by others. See [[Mining]] for more information on how this process works.

== Bitcoins are worthless because they're based on unproven cryptography ==

SHA256 and [[ECDSA]] which are used in Bitcoin are well-known industry standard algorithms. SHA256 is endorsed and used by the US Government and is standardized (FIPS180-3 Secure Hash Standard). If you believe that these algorithms are untrustworthy then you should not trust Bitcoin, credit card transactions or any type of electronic bank transfer. Bitcoin has a sound basis in well understood cryptography.

== Early adopters are unfairly rewarded ==

Early adopters are rewarded for taking the higher risk with their time and money. The capital invested in bitcoin at each stage of its life invigorated the community and helped the currency to reach subsequent milestones. Arguing that early adopters do not deserve to profit from this is akin to saying that early investors in a company, or people who buy stock at a company IPO (Initial Public Offering), are unfairly rewarded.

This argument also depends on bitcoin early adopters using bitcoins to store rather than transfer value. The daily trade on the exchanges (as of Jan 2012) indicates that smaller transactions are becoming the norm, indicating trade rather than investment. In more pragmatic terms, "fairness" is an arbitrary concept that is improbable to be agreed upon by a large population. Establishing "fairness" is no goal of Bitcoin, as this would be impossible.

Looking forwards, considering the amount of publicity bitcoin received as of April 2013, there can be no reasonable grounds for complaint for people who did not invest at that time, and then see the value (possibly) rising drastically higher.

By starting to mine or acquire bitcoins today, you too can become an early adopter.

== 21 million coins isn't enough; doesn't scale ==

One Bitcoin is divisible down to eight decimal places. There are really 2,099,999,997,690,000 (just over 2 quadrillion) maximum possible atomic units in the bitcoin system.

The value of "1 BTC" represents 100,000,000 of these. In other words, each bitcoin is divisible by up to 108.

As the value of the unit of 1 BTC grew too large to be useful for day to day transactions, people started dealing in smaller [[Units|units]], such as milli-bitcoins (mBTC) or micro-bitcoins (μBTC).

== Bitcoins are stored in wallet files, just copy the wallet file to get more coins! ==

No, your wallet contains your secret keys, giving you the rights to spend your bitcoins. Think of it like having bank details stored in a file. If you give your bank details (or bitcoin wallet) to someone else, that doesn't double the amount of money in your account. You can spend your money or they can spend your money, but not both.

== Lost coins can't be replaced and this is bad ==

Bitcoins are divisible to 0.00000001, so there being fewer bitcoins remaining is not a problem for the currency itself. If you lose your coins, all other coins will go up in value a little. Consider it a donation to all other bitcoin users.

A related question is: Why don't we have a mechanism to replace lost coins? The answer is that it is impossible to distinguish between a 'lost' coin and one that is simply sitting unused in someone's wallet.

== It's a giant ponzi scheme ==
In a [[Wikipedia:Ponzi_scheme|Ponzi Scheme]], the founders persuade investors that they’ll profit. Bitcoin does not make such a guarantee. There is no central entity, just individuals building an economy.

A Ponzi scheme is a zero sum game. In a ponzi scheme, early adopters can only profit at the expense of late adopters, and the late adopters always lose. Bitcoin can have a win-win outcome. Earlier adopters profit from the rise in value as Bitcoin becomes better understood and in turn demanded by the public at large. All adopters benefit from the usefulness of a reliable and widely-accepted decentralized peer-to-peer currency.<ref name=Jeff_Tucker>cf. {{cite news | author-link = Wikipedia:Jeffrey_Tucker | url = http://libertarianstandard.com/2013/12/01/ponzi-logic-debunking-gary-north/ | title = Ponzi Logic: Debunking Gary North | last = Tucker | first = Jeffrey | date = 1 December 2013 | work = The Libertarian Standard | accessdate = 2015-04-11}}</ref>

It is also important to note that [[Satoshi Nakamoto]], creator of bitcoin, has never spent a bitcoin (other than giving them away when they were worthless) which we can verify by checking the blockchain.

== Finite coins plus lost coins means deflationary spiral ==
As deflationary forces may apply, economic factors such as hoarding are offset by human factors that may lessen the chances that a [[Deflationary spiral]] will occur.

== Bitcoin can't work because there is no way to control inflation ==

Inflation is simply a rise of prices over time, which is generally the result of the devaluing of a currency. This is a function of supply and demand. Given the fact that the supply of bitcoins is fixed at a certain amount, unlike fiat money, the only way for inflation to get out of control is for demand to disappear. Temporary inflation is possible with a rapid adoption of Fractional Reserve Banking but will stabilize once a substantial number of the 21 million "hard" bitcoins are stored as reserves by banks.

Given the fact that Bitcoin is a distributed system of currency, if demand were to decrease to almost nothing, the currency would be doomed anyway.

The key point here is that Bitcoin as a currency can't be inflated by any single person or entity, like a government, as there's no way to increase supply past a certain amount.

Indeed, the most likely scenario, as Bitcoin becomes more popular and demand increases, is for the currency to increase in value, or deflate, until demand stabilizes.

== The Bitcoin community consists of anarchist/conspiracy theorist/gold standard 'weenies' ==

The members of the community vary in their ideological stances. While it may have been started by ideological enthusiasts, Bitcoin now speaks to a large number of regular pragmatic folk, who simply see its potential for reducing the costs and friction of global e-commerce.

== Anyone with enough computing power can take over the network ==

CONFIRMED, see [[Weaknesses]].

That said, as the network grows, it becomes harder and harder for a single entity to do so. Already the Bitcoin network's computing power is quite ahead of the world's fastest supercomputers, together.

What an attacker can do once the network is taken over is quite limited. Under no circumstances could an attacker create counterfeit coins, fake transactions, or take anybody else's money. An attacker's capabilities are limited to taking back their own money that they very recently spent, and preventing other people's transactions from receiving confirmations. Such an attack would be very costly in resources, and for such meager benefits there is little rational economic incentive to do such a thing.

Furthermore, this attack scenario would only be feasible for as long as it was actively underway. As soon as the attack stopped, the network would resume normal operation.

== Bitcoin violates governmental regulations ==

There is no known governmental regulation which disallows the use of Bitcoin.

See also: the "[[#Bitcoins_are_illegal_because_they.27re_not_legal_tender|Bitcoins are illegal because they're not legal tender]]" myth.

== Fractional reserve banking is not possible ==

It is possible. See the main article, [[Fractional Reserve Banking and Bitcoin]]

== After 21 million coins are mined, no one will generate new blocks ==

When operating costs can't be covered by the block creation bounty, which will happen some time before the total amount of BTC is reached, miners will earn some profit from [[transaction fees]]. However unlike the block reward, there is [http://bitcoin.stackexchange.com/questions/876/how-much-will-transaction-fees-eventually-be/895#895 no coupling between transaction fees and the need for security], so there is less of a guarantee that the amount of [[Mining|mining]] being performed will be sufficient to maintain the network's security.

== Bitcoin has no built-in chargeback mechanism, and this isn't good ==

'''Why some people think this is bad''': Chargebacks are useful for limiting fraud. The person handling your money has a responsibility to prevent fraud. If you buy something on eBay and the seller never ships it, PayPal takes funds from the seller's account and gives you back the money. This strengthens the eBay economy, because people recognize that their risk is limited and are more willing to purchase items from risky sellers.

'''Why it's actually a good thing''': Bitcoin is designed such that your money is yours and yours alone. Allowing chargebacks implies that it is possible for another entity to take your money from you. You can have either total ownership rights of your money, or fraud protection, but not both. That said, nothing inherent in the dollar or euro or any other currency is necessary for chargebacks to be possible, and likewise, nothing prevents the creation of PayPal-like services denominated in Bitcoin that provide chargebacks or fraud protection.

The statement "The person handling your money has a responsibility to prevent fraud" is still true; the power has been shifted into your own hands. Fraud will always exist. It's up to you to only send bitcoins to trusted entities. It is possible to trust an online identity without ever knowing their physical identity; see the [http://wiki.bitcoin-otc.com/wiki/OTC_Rating_System OTC Web of Trust].

== Quantum computers would break Bitcoin's security ==

While ECDSA is indeed not secure under quantum computing, quantum computers don't yet exist and probably won't for a while.
The DWAVE system often written about in the press is, even if all their claims are true, not a quantum computer of a kind that could be used for cryptography.
Bitcoin's security, when used properly with a new address on each transaction, depends on more than just ECDSA: Cryptographic hashes are much stronger than ECDSA under QC.
Bitcoin's security was designed to be upgraded in a forward compatible way and could be [http://en.wikipedia.org/wiki/Post-quantum_cryptography upgraded] if this were considered an imminent threat.

See the implications of quantum computers on public key cryptography here http://en.wikipedia.org/wiki/Quantum_computer#Potential

The ''risk'' of quantum computers is also there for financial institutions, like banks, because they heavily rely on cryptography when doing transactions.

== Bitcoin makes self-sufficient artificial intelligence possible ==
[[StorJ]]<ref>[http://garzikrants.blogspot.com/2013/01/storj-and-bitcoin-autonomous-agents.html StorJ And Bitcoin Autonomous Agents]</ref>, a theorized autonomous agent which utilizes humans to build itself and issues autonomous payments for improvement work done, is not a conscious entity. Whatever AI is possible, is not going to be magically more possible simply because it could incentivize human behaviour with pseudonymous Bitcoin payments.

== [[Mining|Bitcoin mining]] is a waste of energy and harmful for ecology ==
No more so than the wastefulness of mining gold out of the ground, melting it down and shaping it into bars, and then putting it back underground again. Not to mention the building of big fancy buildings, the waste of energy printing and minting all the various fiat currencies, the transportation thereof in armored cars by no less than two security guards for each who could probably be doing something more productive, etc.

As far as mediums of exchange go, Bitcoin is actually quite economical of resources, compared to others.

'''Economic Argument 1'''

[[Mining|Bitcoin mining]] is a highly competitive, dynamic, almost [http://en.wikipedia.org/wiki/Perfect_market perfect], market. Mining rigs can be set up and dismantled almost anywhere in the world with relative ease. Thus, market forces are constantly pushing mining activity to ''places'' and ''times'' where the marginal price of electricity is low or zero. These electricity products are cheap for a reason. Often it’s because the electricity is difficult (and wasteful) to transport, difficult to store, or because there is low demand and high supply. Using electricity in this way is a lot less wasteful than simply plugging a mining rig into the mains indiscriminately.

For example, Iceland produces an excess of cheap electricity from renewable sources, but it has no way of exporting electricity because of its remote location. It is conceivable that at some point in future Bitcoin mining will only be profitable in places like Iceland, and unprofitable in places like central Europe, where electricity comes mostly from nuclear and fossil sources.

Market forces could even push mining into innovative solutions that have an effective electricity consumption of ''zero''. Mining always produces heat equivalent to the energy consumed - for example, 1000 watts of mining equipment produces the same amount of heat as a 1000 watt heating element used in an electric space heater, hot tub, water heater, or similar appliance. Someone already in a willing position to incur the cost of electricity for its heat value alone could run mining equipment specially designed to mine bitcoins while capturing and utilizing the heat produced, without incurring any energy costs beyond what they already intended to spend on heating.

(Note that this is just an example; mining will not always produce heat equivalent to the energy consumed because some energy is inevitably released as electromagnetic radiation, among others.)

'''Economic Argument 2'''

When the environmental costs of mining are considered, they need to be weighed up against the benefits. If you question Bitcoin on the grounds that it consumes electricity, then you should also ask questions like this: Will Bitcoin promote economic growth by freeing up trade? Will this speed up the rate of technological innovation? Will this lead to faster development of green technologies? Will Bitcoin enable new, border crossing [http://en.wikipedia.org/wiki/Smart_grid smart grid] technologies? …

Dismissal of Bitcoin because of its costs, while ignoring its benefits, is a dishonest argument. In fact, any environmental argument of this type is dishonest, not just pertaining to Bitcoin. Along similar lines, it could be argued that wind turbines are bad for the environment because making the steel structure consumes energy.

'''Ratio of Capital Costs versus Electrical Costs'''

The BFL Jalapeno hashes at 5.5 Gh/s using 30W. That device consumes about $40 per year in electricity (using U.S. residential average of about $0.15 per kWh.) But the device costs over $300 including shipping. Thus just about a quarter of all costs over a two-year useful life goes to electricity. This compares to GPUs where more than 90% of costs over a two-year life went to electricity. Even more efficient designs can be expected in the future.

== Shopkeepers can't seriously set prices in bitcoins because of the volatile exchange rate ==

The assumption is that bitcoins must be sold immediately to cover operating expenses. If the shopkeeper's back-end expenses were transacted in bitcoins as well, then the exchange rate would be irrelevant. Larger adoption of Bitcoin would make prices [http://en.wikipedia.org/wiki/Sticky_%28economics%29 sticky]. Future volatility is expected to decrease, as the size and depth of the market grows.

In the meantime, many merchants simply regularly pull the latest market rates from the exchanges and automatically update the prices on their websites. Also you might be able to buy a put option in order to sell at a fixed rate for a given amount of time. This would protect you from drops in price and simplify your operations for that time period.

== Like Flooz and e-gold, bitcoins serve as opportunities for criminals and will be shut down ==

* Visa, MasterCard, PayPal, and cash all serve as opportunities for criminals as well, but society keeps them around due to their recognized net benefit.
* Hopefully Bitcoin will grow to the point where no single organization can disrupt the network, or would be better served by helping it.
* Terrorists fly aircraft into buildings, but the governments have not yet abolished consumer air travel. Obviously the public good outweighs the possible bad in their opinion.
* Criminal law differs between jurisdictions.

== Bitcoins will be shut down by the government just like Liberty Dollars were ==

Liberty Dollars started as a commercial venture to establish an alternative US currency, including physical banknotes and coins, backed by precious metals. This, in and of itself, is not illegal. They were prosecuted under counterfeiting laws because the silver coins allegedly resembled US currency.

Bitcoins do not resemble the currency of the US or of any other nation in any way, shape, or form. The word "dollar" is not attached to them in any way. The "$" symbol is not used in any way.

Bitcoins have no representational similarity whatsoever to US dollars.

Of course, actually 'shutting down' Liberty Dollars was as easy as arresting the head of the company and seizing the offices and the precious metals used as backing. The decentralized Bitcoin, with no leader, no servers, no office, and no tangible asset backing, does not have the same vulnerability.

== Bitcoin is not decentralized because the developers can dictate the software's behavior ==

The Bitcoin protocol was originally defined by Bitcoin's inventor, [[Satoshi Nakamoto]], and this protocol has now been widely accepted as the standard by the community of miners and users.

Though the developers of the original Bitcoin client still exert influence over the Bitcoin community, their power to arbitrarily modify the protocol is very limited. Since the release of Bitcoin v0.3, changes to the protocol have been minor and always in agreement with community consensus.

Protocol modifications, such as increasing the block award from 25 to 50 BTC, are not compatible with clients already running in the network. If the developers were to release a new client that the majority of miners perceives as corrupt, or in violation of the project’s aims, that client would simply not catch on, and the few users who do try to use it would find that their transactions get rejected by the network.

There are also other [[:Category:Clients|Bitcoin clients made by other developers]] that adhere to the Bitcoin protocol. As more developers create alternative clients, less power will lie with the developers of the original Bitcoin client.

== Bitcoin is a pyramid scheme ==

Bitcoin is nearly opposite of a [[Wikipedia:Pyramid_scheme|pyramid scheme]] in a mathematical sense. Because Bitcoins are algorithmically made scarce, no exponential benefit is derived from introducing new users to use of it. There is a quantitative benefit in having additional interest or demand, but this is in no way exponential.<ref name="Jeff_Tucker" />

== Bitcoin was hacked ==

In the history of Bitcoin, there has never been an attack on the [[block chain]] that resulted in stolen money from a confirmed output. Neither has there ever been a reported theft resulting directly from a vulnerability in the [[Original Bitcoin client|original Bitcoin client]], or a vulnerability in the protocol. Bitcoin is secured by standard cryptographic functions. These functions have been peer reviewed by cryptography experts and are considered unlikely to be breakable in the foreseeable future.

It is safe to say that the currency itself has never been 'hacked'. However, several major ''websites'' using the currency have been hacked, often resulting in high profile Bitcoin heists. These heists are misreported in some media as hacks on Bitcoin itself. An analogy: Just because someone stole US dollars from a supermarket till, doesn’t mean that the US dollar as a currency has been 'hacked'.

Most bitcoin thefts are the result of inadequate [[Securing your wallet|wallet security]]. In response to the wave of thefts in 2011 and 2012, the community has developed risk-mitigating measures such as [[Wallet_encryption|wallet encryption]], support for [[BIP_0011|multiple signatures]], [[How_to_set_up_a_secure_offline_savings_wallet|offline wallets]], [[Paper_wallet|paper wallets]], and [[Hardware_wallet|hardware wallets]]. As these measures gain adoption by merchants and users, the number of thefts drop.

==References==
<references/>

[[de:Mythen]]
[[ru:Мифы о биткоине]]

Fallback Nodes

2016-05-28T13:36:39Z

Victorsueca: Added a Tor Node

This is a list of nodes which are considered reliable.

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

[[Bitcoin Core]] versions prior to 0.8.0 also could send [[IP Transactions]] to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back.

=== Tor network ===

To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter:
bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor

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

You can find detailed information on running clients and hidden services within Tor in the [https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md documentation].

== Nodes list ==

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

|-
| bitcoin.moneypot.com || [https://www.moneypot.com moneypot] || 212.47.228.216 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2015-09-15 || No
|-
| node.bitcoin.xxx || www.BitCoin.xxx || 66.228.49.201 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-08-28 || Yes
|-
| bitcoin.coinprism.com || [[Coinprism]] || 137.116.225.142 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-04-26 || Yes
|-
|-
| btcnode1.evolyn.net || Evolyn || 85.214.251.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-01-26 || Yes
|-
| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 67.186.224.85 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2013-11-13 || Yes
|-
| archivum.info || Ferraro Ltd.|| 88.198.58.172 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 62.75.216.13 || exMULTI, Inc. || 62.75.216.13 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 69.64.34.118 || exMULTI, Inc. || 69.64.34.118 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 79.160.221.140 || K-Norway || 79.160.221.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| netzbasis.de || unknown3 || 81.169.129.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btc.turboadmin.com || osmosis || 98.143.152.14 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| fallback.bitcoin.zhoutong.com || Zhou Tong || 117.121.241.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| jun.dashjr.org || Luke-Jr || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| cheaperinbitcoins.com || Xenland/Shane || 184.154.36.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| django.webflows.fr || unknown2 || 188.165.213.169 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| porgressbar.sk || progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| faucet.bitcoin.st || bitcoin street || 64.27.57.225 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| bitcoin.securepayment.cc || SecurePayment CC || 63.247.147.163 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| coin.soul-dev.com || Soul-Dev || || || {{Fallback Nodes/Node Up}} || ||
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode2.bitgroup.cc || BitGroup || 162.243.120.138 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode3.bitgroup.cc || BitGroup || 95.85.8.237 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode.xiro.co || Xiro Labs || 91.121.108.61 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| occult.xf-liam.com || [[User:liamwli|Liam W]] || 216.189.157.221 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| bitcoin.bitdonut.co || James Hartig
|-
| coinno.de || jaknam
|-
| 82.165.44.44 || anonymous
|-
| bitcoin1.dassori.me || gdassori
|-
| bitcoin2.dassori.me || gdassori
|-
| blockchainnode.meulie.net || [[User:Evert|Evert]]
|-
| fullnode.fybsg.com || Nagato
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 62.210.66.227
|-
| softnet.homenet.org || [[User:Victorsueca|Victorsueca]]
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle] || 91.121.83.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes

|}

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

| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 2601:7:6680:2ac:4d29:40ff:7513:fcc7 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 11-13-2013 (MDY) || Yes
|-
| caffeinator.net || [[User:Atrophy|Atrophy]] || || || {{Fallback Nodes/Node Up}} || 2013-05-10 ||
|-
| 2001:470:8:2e1::40 || ? || 2001:470:8:2e1::40 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| occult.xf-liam.com || [[User:liamwli|Liam W]] || 2602:ffc5:40::1:c373 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| bitcoin.bitdonut.co || James Hartig
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 2001:bc8:c087:2001::1
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle]

|}

=== Tor nodes ===

This entire list was last checked on 2015-02-22.

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| 4iuf2zac6aq3ndrb.onion || Hades || Up || 2015-12-16 || No
|-
| ccfxptj3yi2ysa7w.onion || redfish
|-
| nkf5e6b7pl4jfd4a.onion || BlueMatt || Up || 2015-11-11 || No
|-
| hhiv5pnxenvbf4am.onion || ? || Up || 2015-03-17 || No
|-
| bpdlwholl7rnkrkw.onion || kenansulayman || Up || 2015-03-17 || ?
|-
| bk5ejfe56xakvtkk.onion || dserrano5 || Up || 2015-03-17 || No
|-
| wxvp2d4rspn7tqyu.onion || lunokhod || Up || 2015-08-17 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || Down || 2015-03-17 || Yes
|-
| e3tn727fywnioxrc.onion || Zedd || Down || 2015-03-17 || No
|-
| pqosrh6wfaucet32.onion || bitcoin street || Down || 2015-03-17 || No
|-
| r4de4zf4lyniu4mx.onion:8444 || ? || Down || 2015-01-20 || ?
|-
| zy3kdqowmrb7xm7h.onion || Tril || Down || 2015-01-20 || No
|-
| smith4mfhwcq7x3b.onion || Smithtrader || Down || 2014-11-22 || ?
|-
| i2r5tbaizb75h26f.onion || TorDude || Down || 2014-07-24 || No
|-
| btcnet3utgzyz2bf.onion || anonymous || Down || 2014-07-24 || Yes
|-
| kjy2eqzk4zwi5zd3.onion || sipa || Down || 2014-07-24 || No
|-
| tsyvzsqwa2kkf6b2.onion || TorDude || Down || 2014-05-19 || No
|-
| igpdszqrbqjhak5z.onion || anonymous || Down || 2014-05-15 || ?
|-
| evolynhit7shzeet.onion || Evolyn || Down || 2014-05-15 || Yes
|-
| z55v4ostefnwfy32.onion || Tril || Down || 2014-04-09 || No
|-
| bitcoin2u5jnjzzz.onion || anonymous || Down || 2014-01-27 || Yes
|-
| btc4ulpftizx5b72.onion || TorNode || Down || 2013-05-10 || Yes
|-
| yyl3ipdmyjkfypmx.onion || redemerald || Down || 2013-05-10 || Yes
|-
| siqdznszjf4e6v5j.onion || Tuxavant || Down || 2013-05-10 || ?
|-
| 7hxvg2lvr2ashzli.onion || Tuxavant || Down || 2013-05-10 || ?
|-
| x3danbeag2kyx644.onion || redemerald || Down || 2013-01-04 || Yes
|-
| 6hgmaxwellgpv2oe.onion || Gmaxwell || Down || 2012-07-01 || No
|-
| bitcoinprwwpuinm.onion:8333 || ? || Down || 2012-06-26 || ?
|-
| mutqcuh7hwxmhx3k.onion || Xirafe || Down || 2012-06-23 || ?
|-
| sjdntqu5roj4q6lo.onion || torservers || Down || 2012-05-19 || ?
|-
| bitcoin2bkgm3fke.onion || ? || Down || 2012-05-19 || Yes
|-
| ceeji4qpfs3ms3zc.onion || creepa || ? || ? || ?
|-
| zmadblayz5aj5to2.onion || [[User:Victorsueca|Victorsueca]]
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

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

==See Also==

* [[Network|Bitcoin Network]]
* [http://nodes.bitcoin.st Fallback Nodes] List of longest running Bitcoin Nodes listed by Country.
* [https://getaddr.bitnodes.io/ Bitnodes project]
* [https://blockchain.info/connected-nodes Recently connected nodes at blockchain.info]

{{Bitcoin Core documentation}}

User:Victorsueca

2016-02-25T15:58:15Z

Victorsueca: Created The Page

Hello World! 
My name is Victor Oliver and I live in Valencia, Spain 
You can find me in most internet places and comunities as Victorsueca or Victor_sueca

Bitcoind

2016-02-23T12:49:02Z

Victorsueca: Added 0.12.0 to release history

'''bitcoind''' is a program that implements the Bitcoin protocol for remote procedure call (RPC) use. It is also the second Bitcoin [[Clients|client]] in the network's history. It is available under the [http://www.opensource.org/licenses/mit-license.php MIT license] in 32-bit and 64-bit versions for Windows, GNU/Linux-based OSes, and Mac OS X.

As part of Bitcoin Core, bitcoind has been bundled with the original client from version 0.2.6 to 0.4.9, and with [[Bitcoin-Qt]] since 0.5.0.

=== Running ===

See [[Running_bitcoind|running bitcoind]] for more detail and an example of the configuration file.

Bitcoind is a headless daemon, and also bundles a testing tool for the same daemon. It provides a JSON-RPC interface, allowing it to be controlled locally or remotely which makes it useful for integration with other software or in larger payment systems. [[Original Bitcoin client/API Calls list|Various commands]] are made available by the API.

To use locally, first start the program in daemon mode:
:bitcoind -daemon

Then you can execute [[Original Bitcoin client/API Calls list|API commands]], e.g.:
:bitcoin-cli getinfo
:bitcoin-cli listtransactions

To stop the bitcoin daemon, execute:
:bitcoin-cli stop

==History of official bitcoind (and predecessor) releases==
{| class="wikitable"
|-
! Version
! Date
! Supported platforms
! Reference
|-
| 0.12.0
| 2016-Feb-23
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.12.0 Bitcoin Core version 0.12.0 released]</ref>
|-
| 0.11.2
| 2015-Nov-13
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.11.2 Bitcoin Core version 0.11.2 released]</ref>
|-
| 0.11.1
| 2015-Oct-15
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.11.1 Bitcoin Core version 0.11.1 released]</ref>
|-
| 0.10.3
| 2015-Oct-14
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.3 Bitcoin Core version 0.10.3 released]</ref>
|-
| 0.11.0
| 2015-Jul-12
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.11.0 Bitcoin Core version 0.11.0 released]</ref>
|-
| 0.10.2
| 2015-May-19
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.2 Bitcoin Core version 0.10.2 released]</ref>
|-
| 0.10.1
| 2015-Apr-27
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.1 Bitcoin Core version 0.10.1 released]</ref>
|-
| 0.10.0
| 2015-Feb-16
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.0 Bitcoin Core version 0.10.0 released]</ref>
|-
| 0.9.3
| 2014-Sep-27
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.3 Bitcoin Core version 0.9.3 released]</ref>
|-
| 0.9.2.1
| 2014-Jun-19
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.2.1 Bitcoin Core version 0.9.2.1 released]</ref>
|-
| 0.9.2
| 2014-Jun-16
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.2 Bitcoin Core version 0.9.2 released]</ref>
|-
| 0.9.1
| 2014-Apr-8
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.1 Bitcoin Core version 0.9.1 released]</ref>
|-
| 0.9.0
| 2014-Mar-19
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.0 Bitcoin Core version 0.9.0 released]</ref>
|-
| 0.8.6
| 2013-Dec-9
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.6 Bitcoin-Qt version 0.8.6 released]</ref>
|-
| 0.8.5
| 2013-Sep-13
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.5 Bitcoin-Qt version 0.8.5 released]</ref>
|-
| 0.8.4
| 2013-Sep-3
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.4 Bitcoin-Qt version 0.8.4 released]</ref>
|-
| 0.8.3
| 2013-Jun-25
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.3 Bitcoin-Qt version 0.8.3 released]</ref>
|-
| 0.8.2
| 2013-May-29
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.2 Bitcoin-Qt version 0.8.2 released]</ref>
|-
| 0.8.1
| 2013-Mar-18
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.1 Bitcoin-Qt version 0.8.1 released]</ref>
|-
| 0.8.0
| 2013-Feb-19
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.0 Bitcoin-Qt version 0.8.0 released]</ref>
|-
| 0.7.2
| 2012-Dec-14
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=130819.msg1399721#msg1399721 Bitcoin-Qt/bitcoind version 0.7.2 released]</ref>
|-
| 0.5.7
| 2012-Nov-23
|
|
|-
| 0.7.1
| 2012-Oct-19
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=119277.msg1283232#msg1283232 Bitcoin-Qt/bitcoind version 0.7.1 released]</ref>
|-
| 0.7.0
| 2012-Sep-17
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=110243.msg1199467 Bitcoin-Qt/bitcoind version 0.7.0 released]</ref>
|-
| 0.5.6
| 2012-Jul-22
| Windows32 / Linux / MacOS X
|
|-
| 0.4.7
| 2012-Jul-22
| Windows32
|
|-
| 0.6.0.9
| 2012-Jul-08
|
|
|-
| 0.6.3
| 2012-Jun-25
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=89877.msg989356#msg989356 Bitcoin-Qt / bitcoind version 0.6.3 released]</ref>
|-
| 0.6.2
| 2012-May-08
| Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=78829.msg888578#msg888578 Re: Version 0.6.1 release candidate 2]</ref>
|-
| 0.6.1
| 2012-May-04
| Windows32 / Linux / MacOS X
|
|-
| 0.6.0.7
| 2012-May-04
|
|
|-
| 0.5.5
| 2012-May-04
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=79651 Version 0.5.5 and 0.4.6 released]</ref>
|-
| 0.4.6
| 2012-May-04
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=79651 Version 0.5.5 and 0.4.6 released]</ref>
|-
| 0.5.4
| 2012-Apr-15
| Windows32 / Linux
| <ref>[https://bitcointalk.org/index.php?topic=76808.0 Version 0.5.4 released]</ref>
|-
| 0.4.5
| 2012-Apr-15
|
|
|-
| 0.6.0
| 2012-Mar-30
| Windows32 / Linux / MacOS X
| <ref>[http://www.bitcoinforum.com/bitcoin-discussion/bitcoin-org-bitcoin-version-0-6-0-released/ bitcoin.org: Bitcoin version 0.6.0 released]</ref>
|-
| 0.5.3.1
| 2012-Mar-17
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=69120.0 URGENT: Windows Bitcoin-Qt update]</ref>
|-
| 0.5.3
| 2012-Mar-14
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=68895.0 Bitcoin-Qt, bitcoind version 0.5.3 released]</ref>
|-
| 0.4.4
| 2012-Mar-14
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=70566.0 bitcoind version 0.4.4 released]</ref>
|-
| 0.5.2
| 2012-Jan-09
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=60146.0 Bitcoin-Qt, bitcoind version 0.5.2 released]</ref>
|-
| 0.4.3
| 2012-Jan-09
| Windows32 / Linux
| <ref>[https://bitcointalk.org/index.php?topic=57734.0 bitcoind version 0.4.3 released]</ref>
|-
| 0.5.1
| 2011-Dec-15
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=54717.0 Bitcoin-Qt, bitcoind version 0.5.1 released]</ref>
|-
| 0.4.2
| 2011-Dec-12
|
|
|-
| 0.5.0
| 2011-Nov-21
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=52480.0 Bitcoin-Qt/bitcoind version 0.5.0]</ref>
|-
| 0.4.1
| 2011-Nov-21
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=52503.0 wxBitcoin/bitcoind version 0.4.1]</ref>
|-
| 0.4.0
| 2011-Sep-23
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=45410.0 Bitcoin version 0.4.0 released]</ref>
|-
| 0.3.24
| 2011-Jul-08
| Windows32 / Linux / MacOS X
| <ref>[http://forum.bitcoin.org/index.php?topic=27187.0 Bitcoin version 0.3.24 released]</ref>
|-
| 0.3.23
| 2011-Jun-13
| Windows32 / Linux / MacOS X
| <ref>[http://forum.bitcoin.org/index.php?topic=16553.0 Bitcoin version 0.3.23 released]</ref>
|-
| 0.3.22
| 2011-Jun-05
| Windows32 / Linux / MacOS X
| <ref>[http://forum.bitcoin.org/index.php?topic=12269.0 Bitcoin version 0.3.22]</ref>
|-
| 0.3.21
| 2011-Apr-27
| Windows32 / Linux / MacOS X
| <ref>[http://bitcointalk.org/?topic=6642.0 Bitcoin version 0.3.21]</ref>
|-
| 0.3.20
| 2011-Feb-21
| Windows32 / Linux / MacOS X
| <ref>[http://www.bitcoin.org/smf/index.php?topic=3704.0 Version 0.3.20]</ref>
|-
|0.3.19
|2010-12-12
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=2228.msg29479#msg29479 Added some DoS limits, removed safe mode (0.3.19)]</ref>
|-
|0.3.18
|2010-12-08
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=2162.0 Version 0.3.18]</ref>
|-
|0.3.17
|2010-11-25
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=1946.0 Version 0.3.17]</ref>
|-
|0.3.15
|2010-11-13
|Windows32 / Linux
|<ref>[https://bitcointalk.org/index.php?topic=1780.0 Version 0.3.15]</ref>
|-
|0.3.14
|2010-10-21
|Windows32 / Linux
|<ref>[https://bitcointalk.org/index.php?topic=1528.0 Version 0.3.14]</ref>
|-
|0.3.13
|2010-10-01
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=1327.0 Version 0.3.13, please upgrade]</ref>
|-
|0.3.12
|2010-09-07
|Windows32 / Linux
|<ref>[https://bitcointalk.org/index.php?topic=999.0 Version 0.3.12 is now available.]</ref>
|-
|0.3.11
|2010-08-27
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=941.0 Version 0.3.11 is now available.]</ref>
|-
|0.3.10
|2010-08-15
|Windows32 / Linux32/64 / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=820.msg9452#msg9452 tcatm's 4-way SSE2 for Linux 32/64-bit is in 0.3.10]</ref>
|-
|0.3.8.1
|2010-08-09
|Linux64
|<ref>[https://bitcointalk.org/index.php?topic=765.0 Version 0.3.8.1 update for Linux 64-bit]</ref>
|-
|0.3.8
|2010-08-03
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=696.0 Please upgrade to 0.3.8!]</ref>
|-
|0.3.7
|2010-08-01
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=664.0 0.3.7 Changes]</ref>
|-
|0.3.6
|2010-07-29
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=626.0 *** ALERT *** Upgrade to 0.3.6]</ref>
|-
|0.3.3
|2010-07-25
|Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=570.0 Bitcoin 0.3.3 released -- PLEASE UPGRADE]</ref>
|-
|0.3.2.5
|2010-07-24
|Windows32 / Linux
| <ref>[https://bitcointalk.org/index.php?topic=556.0 Version 0.3.2.5 -- please test!]</ref>
|-
|0.3.2
|2010-07-17
|Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=437.0 Bitcoin 0.3.2 released]</ref>
|-
|0.3.1
|2010-07-15
|Windows32 / Linux
|<ref>[https://bitcointalk.org/index.php?topic=383.0 Bitcoin 0.3.1 released]</ref>
|-
|0.3.0
|2010-07-06
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=238.0 Bitcoin 0.3 released!]</ref><ref>[http://sourceforge.net/mailarchive/message.php?msg_id=25686730 Bitcoin 0.3 released!]</ref>
|-
|0.2.0
|2009-12-17 06:52
|Windows XP /Vista / Linux
|<ref>[https://bitcointalk.org/index.php?topic=16.0 Bitcoin 0.2 released!]</ref><ref>[http://sourceforge.net/mailarchive/message.php?msg_id=24205662 Bitcoin 0.2 released]</ref>
|-
|0.1.5
|2009-02-04 19:46
|Windows NT/2000/XP
|<ref>[http://sourceforge.net/mailarchive/message.php?msg_id=21500063 Bitcoin v0.1.5 released]</ref>
|-
|0.1.3
|2009-01-12 22:48
|Windows NT/2000/XP
|<ref>[http://sourceforge.net/mailarchive/message.php?msg_id=21313152 Bitcoin v0.1.3]</ref>
|-
|0.1.2
|2009-01-11 22:32
|Windows NT/2000/XP
|<ref>[http://sourceforge.net/mailarchive/message.php?msg_id=21303153 Bitcoin v0.1.2 now available]</ref>
|-
|0.1.0
|2009-01-09
|Windows NT/2000/XP
|
|}

Up to and including version 0.3.19 is the "Satoshi code". The founder retired from development with end of 2010. [https://bitcointalk.org/index.php?topic=68121.10;wap2/ Here] are three URLs given where you still(!) (2013-01-04) can download one of the [[Satoshi client|"original Satoshi codes"]]. So also this [http://www.antepedia.com/detail/p/237812136.html Bitcoin release history].

==Theory of Operation==

bitcoind is a multithreaded C++ program. It is designed to be portable across Windows, Mac, and Linux systems. The multithreaded aspect leads to some complexity and the use of certain code patterns to deal with concurrency that may be unfamiliar to many programmers. Also, the code is aggressive in the use of C++ constructs, so it will help to be fluent with map, multimap, set, string, vector, iostream, and templates. As is typical of a C++ program, a lot of code tends to end up in the header files so be sure to search both the .cpp and .h files when looking for a function.

The client is oriented around several major operations, which are described in separate detailed articles and summarized in the following sections.

===[[Satoshi Client Initialization and Startup|Initialization and Startup]]===
Upon startup, the client performs various initialization routines including starting multiple threads to handle concurrent operations.

===[[Satoshi Client Node Discovery|Node Discovery]]===
The client uses various techniques to find out about other Bitcoin nodes that are currently connected to the network.

===[[Satoshi Client Node Connectivity|Node Connectivity]]===
The client initiates and maintains connections to other nodes.

===[[Satoshi Client Sockets and Messages|Sockets and Messages]]===
The client processes messages from other nodes and sends messages to other nodes using socket connections.

===[[Satoshi Client Block Exchange|Block Exchange]]===
Nodes advertise their inventory of blocks to each other and exchange blocks to build block chains.

===[[Satoshi Client Transaction Exchange|Transaction Exchange]]===
Nodes exchange and relay transactions with each other. The client associates transactions with bitcoin addresses in the local wallet.

===Wallet Services===
The client can create transactions using the local wallet. The client associates transactions with bitcoin addresses in the local wallet. The client provides a service for managing the local wallet.

===RPC Interface===
The client offers an JSON-RPC interface over HTTP over sockets to perform various operational functions and to manage the local wallet.

===User Interface===
Bitcoind's current user interface is the command line while it used to be based on [http://www.wxwidgets.org wxWidgets]. A graphical user interface is now provided by [[Bitcoin-qt]] in version 0.5+ for the reference client.

==Troubleshooting==

===I get "Error loading blkindex.dat" when I try to run the client===

blkindex.dat is part of the database that stores the local copy of the blockchain which may have become corrupted. Open the Bitcoin data dir:

Windows: %APPDATA%\Bitcoin
Linux: ~/.bitcoin
Mac: ~/Library/Application Support/Bitcoin/

Make a backup of that entire folder, then delete everything EXCEPT wallet.dat. Start bitcoind again and it will download a fresh copy of the blockchain.

==See Also==

* [[Original Bitcoin client/API calls list]]
* [[Protocol specification|Bitcoin network protocol]]
* [[Development process]]
* [[Release process]]
* [[Changelog]]

==External Links==
* [https://github.com/bitcoin/bitcoin/ Bitcoin Client project on Github]

==References==
<references />
`
[[es:Bitcoind]]

[[Category:Nodes]]
[[Category:Wallets]]
[[Category:User Interfaces]]
[[Category:Clients]]
[[Category:Developer]]
[[Category:Technical]]
[[Category:Free Software]]
[[Category:License/MIT-X11]]
[[Category:Open Source]]
{{lowercase}}

Bitcoind

2016-02-17T18:29:05Z

Victorsueca: Updated version table

'''bitcoind''' is a program that implements the Bitcoin protocol for remote procedure call (RPC) use. It is also the second Bitcoin [[Clients|client]] in the network's history. It is available under the [http://www.opensource.org/licenses/mit-license.php MIT license] in 32-bit and 64-bit versions for Windows, GNU/Linux-based OSes, and Mac OS X.

As part of Bitcoin Core, bitcoind has been bundled with the original client from version 0.2.6 to 0.4.9, and with [[Bitcoin-Qt]] since 0.5.0.

=== Running ===

See [[Running_bitcoind|running bitcoind]] for more detail and an example of the configuration file.

Bitcoind is a headless daemon, and also bundles a testing tool for the same daemon. It provides a JSON-RPC interface, allowing it to be controlled locally or remotely which makes it useful for integration with other software or in larger payment systems. [[Original Bitcoin client/API Calls list|Various commands]] are made available by the API.

To use locally, first start the program in daemon mode:
:bitcoind -daemon

Then you can execute [[Original Bitcoin client/API Calls list|API commands]], e.g.:
:bitcoin-cli getinfo
:bitcoin-cli listtransactions

To stop the bitcoin daemon, execute:
:bitcoin-cli stop

==History of official bitcoind (and predecessor) releases==
{| class="wikitable"
|-
! Version
! Date
! Supported platforms
! Reference
|-
| 0.11.2
| 2015-Nov-13
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.11.2 Bitcoin Core version 0.11.2 released]</ref>
|-
| 0.11.1
| 2015-Oct-15
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.11.1 Bitcoin Core version 0.11.1 released]</ref>
|-
| 0.10.3
| 2015-Oct-14
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.3 Bitcoin Core version 0.10.3 released]</ref>
|-
| 0.11.0
| 2015-Jul-12
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.11.0 Bitcoin Core version 0.11.0 released]</ref>
|-
| 0.10.2
| 2015-May-19
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.2 Bitcoin Core version 0.10.2 released]</ref>
|-
| 0.10.1
| 2015-Apr-27
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.1 Bitcoin Core version 0.10.1 released]</ref>
|-
| 0.10.0
| 2015-Feb-16
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.10.0 Bitcoin Core version 0.10.0 released]</ref>
|-
| 0.9.3
| 2014-Sep-27
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.3 Bitcoin Core version 0.9.3 released]</ref>
|-
| 0.9.2.1
| 2014-Jun-19
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.2.1 Bitcoin Core version 0.9.2.1 released]</ref>
|-
| 0.9.2
| 2014-Jun-16
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.2 Bitcoin Core version 0.9.2 released]</ref>
|-
| 0.9.1
| 2014-Apr-8
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.1 Bitcoin Core version 0.9.1 released]</ref>
|-
| 0.9.0
| 2014-Mar-19
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.9.0 Bitcoin Core version 0.9.0 released]</ref>
|-
| 0.8.6
| 2013-Dec-9
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.6 Bitcoin-Qt version 0.8.6 released]</ref>
|-
| 0.8.5
| 2013-Sep-13
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.5 Bitcoin-Qt version 0.8.5 released]</ref>
|-
| 0.8.4
| 2013-Sep-3
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.4 Bitcoin-Qt version 0.8.4 released]</ref>
|-
| 0.8.3
| 2013-Jun-25
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.3 Bitcoin-Qt version 0.8.3 released]</ref>
|-
| 0.8.2
| 2013-May-29
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.2 Bitcoin-Qt version 0.8.2 released]</ref>
|-
| 0.8.1
| 2013-Mar-18
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.1 Bitcoin-Qt version 0.8.1 released]</ref>
|-
| 0.8.0
| 2013-Feb-19
| Windows32 / Linux / MacOS X
| <ref>[https://bitcoin.org/en/release/v0.8.0 Bitcoin-Qt version 0.8.0 released]</ref>
|-
| 0.7.2
| 2012-Dec-14
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=130819.msg1399721#msg1399721 Bitcoin-Qt/bitcoind version 0.7.2 released]</ref>
|-
| 0.5.7
| 2012-Nov-23
|
|
|-
| 0.7.1
| 2012-Oct-19
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=119277.msg1283232#msg1283232 Bitcoin-Qt/bitcoind version 0.7.1 released]</ref>
|-
| 0.7.0
| 2012-Sep-17
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=110243.msg1199467 Bitcoin-Qt/bitcoind version 0.7.0 released]</ref>
|-
| 0.5.6
| 2012-Jul-22
| Windows32 / Linux / MacOS X
|
|-
| 0.4.7
| 2012-Jul-22
| Windows32
|
|-
| 0.6.0.9
| 2012-Jul-08
|
|
|-
| 0.6.3
| 2012-Jun-25
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=89877.msg989356#msg989356 Bitcoin-Qt / bitcoind version 0.6.3 released]</ref>
|-
| 0.6.2
| 2012-May-08
| Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=78829.msg888578#msg888578 Re: Version 0.6.1 release candidate 2]</ref>
|-
| 0.6.1
| 2012-May-04
| Windows32 / Linux / MacOS X
|
|-
| 0.6.0.7
| 2012-May-04
|
|
|-
| 0.5.5
| 2012-May-04
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=79651 Version 0.5.5 and 0.4.6 released]</ref>
|-
| 0.4.6
| 2012-May-04
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=79651 Version 0.5.5 and 0.4.6 released]</ref>
|-
| 0.5.4
| 2012-Apr-15
| Windows32 / Linux
| <ref>[https://bitcointalk.org/index.php?topic=76808.0 Version 0.5.4 released]</ref>
|-
| 0.4.5
| 2012-Apr-15
|
|
|-
| 0.6.0
| 2012-Mar-30
| Windows32 / Linux / MacOS X
| <ref>[http://www.bitcoinforum.com/bitcoin-discussion/bitcoin-org-bitcoin-version-0-6-0-released/ bitcoin.org: Bitcoin version 0.6.0 released]</ref>
|-
| 0.5.3.1
| 2012-Mar-17
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=69120.0 URGENT: Windows Bitcoin-Qt update]</ref>
|-
| 0.5.3
| 2012-Mar-14
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=68895.0 Bitcoin-Qt, bitcoind version 0.5.3 released]</ref>
|-
| 0.4.4
| 2012-Mar-14
| Windows32
| <ref>[https://bitcointalk.org/index.php?topic=70566.0 bitcoind version 0.4.4 released]</ref>
|-
| 0.5.2
| 2012-Jan-09
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=60146.0 Bitcoin-Qt, bitcoind version 0.5.2 released]</ref>
|-
| 0.4.3
| 2012-Jan-09
| Windows32 / Linux
| <ref>[https://bitcointalk.org/index.php?topic=57734.0 bitcoind version 0.4.3 released]</ref>
|-
| 0.5.1
| 2011-Dec-15
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=54717.0 Bitcoin-Qt, bitcoind version 0.5.1 released]</ref>
|-
| 0.4.2
| 2011-Dec-12
|
|
|-
| 0.5.0
| 2011-Nov-21
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=52480.0 Bitcoin-Qt/bitcoind version 0.5.0]</ref>
|-
| 0.4.1
| 2011-Nov-21
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=52503.0 wxBitcoin/bitcoind version 0.4.1]</ref>
|-
| 0.4.0
| 2011-Sep-23
| Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=45410.0 Bitcoin version 0.4.0 released]</ref>
|-
| 0.3.24
| 2011-Jul-08
| Windows32 / Linux / MacOS X
| <ref>[http://forum.bitcoin.org/index.php?topic=27187.0 Bitcoin version 0.3.24 released]</ref>
|-
| 0.3.23
| 2011-Jun-13
| Windows32 / Linux / MacOS X
| <ref>[http://forum.bitcoin.org/index.php?topic=16553.0 Bitcoin version 0.3.23 released]</ref>
|-
| 0.3.22
| 2011-Jun-05
| Windows32 / Linux / MacOS X
| <ref>[http://forum.bitcoin.org/index.php?topic=12269.0 Bitcoin version 0.3.22]</ref>
|-
| 0.3.21
| 2011-Apr-27
| Windows32 / Linux / MacOS X
| <ref>[http://bitcointalk.org/?topic=6642.0 Bitcoin version 0.3.21]</ref>
|-
| 0.3.20
| 2011-Feb-21
| Windows32 / Linux / MacOS X
| <ref>[http://www.bitcoin.org/smf/index.php?topic=3704.0 Version 0.3.20]</ref>
|-
|0.3.19
|2010-12-12
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=2228.msg29479#msg29479 Added some DoS limits, removed safe mode (0.3.19)]</ref>
|-
|0.3.18
|2010-12-08
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=2162.0 Version 0.3.18]</ref>
|-
|0.3.17
|2010-11-25
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=1946.0 Version 0.3.17]</ref>
|-
|0.3.15
|2010-11-13
|Windows32 / Linux
|<ref>[https://bitcointalk.org/index.php?topic=1780.0 Version 0.3.15]</ref>
|-
|0.3.14
|2010-10-21
|Windows32 / Linux
|<ref>[https://bitcointalk.org/index.php?topic=1528.0 Version 0.3.14]</ref>
|-
|0.3.13
|2010-10-01
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=1327.0 Version 0.3.13, please upgrade]</ref>
|-
|0.3.12
|2010-09-07
|Windows32 / Linux
|<ref>[https://bitcointalk.org/index.php?topic=999.0 Version 0.3.12 is now available.]</ref>
|-
|0.3.11
|2010-08-27
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=941.0 Version 0.3.11 is now available.]</ref>
|-
|0.3.10
|2010-08-15
|Windows32 / Linux32/64 / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=820.msg9452#msg9452 tcatm's 4-way SSE2 for Linux 32/64-bit is in 0.3.10]</ref>
|-
|0.3.8.1
|2010-08-09
|Linux64
|<ref>[https://bitcointalk.org/index.php?topic=765.0 Version 0.3.8.1 update for Linux 64-bit]</ref>
|-
|0.3.8
|2010-08-03
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=696.0 Please upgrade to 0.3.8!]</ref>
|-
|0.3.7
|2010-08-01
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=664.0 0.3.7 Changes]</ref>
|-
|0.3.6
|2010-07-29
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=626.0 *** ALERT *** Upgrade to 0.3.6]</ref>
|-
|0.3.3
|2010-07-25
|Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=570.0 Bitcoin 0.3.3 released -- PLEASE UPGRADE]</ref>
|-
|0.3.2.5
|2010-07-24
|Windows32 / Linux
| <ref>[https://bitcointalk.org/index.php?topic=556.0 Version 0.3.2.5 -- please test!]</ref>
|-
|0.3.2
|2010-07-17
|Windows32 / Linux / MacOS X
| <ref>[https://bitcointalk.org/index.php?topic=437.0 Bitcoin 0.3.2 released]</ref>
|-
|0.3.1
|2010-07-15
|Windows32 / Linux
|<ref>[https://bitcointalk.org/index.php?topic=383.0 Bitcoin 0.3.1 released]</ref>
|-
|0.3.0
|2010-07-06
|Windows32 / Linux / MacOS X
|<ref>[https://bitcointalk.org/index.php?topic=238.0 Bitcoin 0.3 released!]</ref><ref>[http://sourceforge.net/mailarchive/message.php?msg_id=25686730 Bitcoin 0.3 released!]</ref>
|-
|0.2.0
|2009-12-17 06:52
|Windows XP /Vista / Linux
|<ref>[https://bitcointalk.org/index.php?topic=16.0 Bitcoin 0.2 released!]</ref><ref>[http://sourceforge.net/mailarchive/message.php?msg_id=24205662 Bitcoin 0.2 released]</ref>
|-
|0.1.5
|2009-02-04 19:46
|Windows NT/2000/XP
|<ref>[http://sourceforge.net/mailarchive/message.php?msg_id=21500063 Bitcoin v0.1.5 released]</ref>
|-
|0.1.3
|2009-01-12 22:48
|Windows NT/2000/XP
|<ref>[http://sourceforge.net/mailarchive/message.php?msg_id=21313152 Bitcoin v0.1.3]</ref>
|-
|0.1.2
|2009-01-11 22:32
|Windows NT/2000/XP
|<ref>[http://sourceforge.net/mailarchive/message.php?msg_id=21303153 Bitcoin v0.1.2 now available]</ref>
|-
|0.1.0
|2009-01-09
|Windows NT/2000/XP
|
|}

Up to and including version 0.3.19 is the "Satoshi code". The founder retired from development with end of 2010. [https://bitcointalk.org/index.php?topic=68121.10;wap2/ Here] are three URLs given where you still(!) (2013-01-04) can download one of the [[Satoshi client|"original Satoshi codes"]]. So also this [http://www.antepedia.com/detail/p/237812136.html Bitcoin release history].

==Theory of Operation==

bitcoind is a multithreaded C++ program. It is designed to be portable across Windows, Mac, and Linux systems. The multithreaded aspect leads to some complexity and the use of certain code patterns to deal with concurrency that may be unfamiliar to many programmers. Also, the code is aggressive in the use of C++ constructs, so it will help to be fluent with map, multimap, set, string, vector, iostream, and templates. As is typical of a C++ program, a lot of code tends to end up in the header files so be sure to search both the .cpp and .h files when looking for a function.

The client is oriented around several major operations, which are described in separate detailed articles and summarized in the following sections.

===[[Satoshi Client Initialization and Startup|Initialization and Startup]]===
Upon startup, the client performs various initialization routines including starting multiple threads to handle concurrent operations.

===[[Satoshi Client Node Discovery|Node Discovery]]===
The client uses various techniques to find out about other Bitcoin nodes that are currently connected to the network.

===[[Satoshi Client Node Connectivity|Node Connectivity]]===
The client initiates and maintains connections to other nodes.

===[[Satoshi Client Sockets and Messages|Sockets and Messages]]===
The client processes messages from other nodes and sends messages to other nodes using socket connections.

===[[Satoshi Client Block Exchange|Block Exchange]]===
Nodes advertise their inventory of blocks to each other and exchange blocks to build block chains.

===[[Satoshi Client Transaction Exchange|Transaction Exchange]]===
Nodes exchange and relay transactions with each other. The client associates transactions with bitcoin addresses in the local wallet.

===Wallet Services===
The client can create transactions using the local wallet. The client associates transactions with bitcoin addresses in the local wallet. The client provides a service for managing the local wallet.

===RPC Interface===
The client offers an JSON-RPC interface over HTTP over sockets to perform various operational functions and to manage the local wallet.

===User Interface===
Bitcoind's current user interface is the command line while it used to be based on [http://www.wxwidgets.org wxWidgets]. A graphical user interface is now provided by [[Bitcoin-qt]] in version 0.5+ for the reference client.

==Troubleshooting==

===I get "Error loading blkindex.dat" when I try to run the client===

blkindex.dat is part of the database that stores the local copy of the blockchain which may have become corrupted. Open the Bitcoin data dir:

Windows: %APPDATA%\Bitcoin
Linux: ~/.bitcoin
Mac: ~/Library/Application Support/Bitcoin/

Make a backup of that entire folder, then delete everything EXCEPT wallet.dat. Start bitcoind again and it will download a fresh copy of the blockchain.

==See Also==

* [[Original Bitcoin client/API calls list]]
* [[Protocol specification|Bitcoin network protocol]]
* [[Development process]]
* [[Release process]]
* [[Changelog]]

==External Links==
* [https://github.com/bitcoin/bitcoin/ Bitcoin Client project on Github]

==References==
<references />
`
[[es:Bitcoind]]

[[Category:Nodes]]
[[Category:Wallets]]
[[Category:User Interfaces]]
[[Category:Clients]]
[[Category:Developer]]
[[Category:Technical]]
[[Category:Free Software]]
[[Category:License/MIT-X11]]
[[Category:Open Source]]
{{lowercase}}

Fallback Nodes

2016-02-17T16:11:34Z

Victorsueca: /* IPv4 Nodes */

This is a list of nodes which are considered reliable.

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

[[Bitcoin Core]] versions prior to 0.8.0 also could send [[IP Transactions]] to these nodes. If you included your bitcoin address in the "message" field, you might have had your coins back.

=== Tor network ===

To use Bitcoin-Qt over Tor hidden services, in a terminal/console enter:
bitcoin-qt -proxy=127.0.0.1:9050 -onlynet=tor

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

You can find detailed information on running clients and hidden services within Tor in the [https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md documentation].

== Nodes list ==

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

|-
| bitcoin.moneypot.com || [https://www.moneypot.com moneypot] || 212.47.228.216 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2015-09-15 || No
|-
| node.bitcoin.xxx || www.BitCoin.xxx || 66.228.49.201 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-08-28 || Yes
|-
| bitcoin.coinprism.com || [[Coinprism]] || 137.116.225.142 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-04-26 || Yes
|-
|-
| btcnode1.evolyn.net || Evolyn || 85.214.251.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2014-01-26 || Yes
|-
| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 67.186.224.85 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 2013-11-13 || Yes
|-
| archivum.info || Ferraro Ltd.|| 88.198.58.172 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| 62.75.216.13 || exMULTI, Inc. || 62.75.216.13 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 69.64.34.118 || exMULTI, Inc. || 69.64.34.118 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| 79.160.221.140 || K-Norway || 79.160.221.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| netzbasis.de || unknown3 || 81.169.129.25 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btc.turboadmin.com || osmosis || 98.143.152.14 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| fallback.bitcoin.zhoutong.com || Zhou Tong || 117.121.241.140 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || No
|-
| bauhaus.csail.mit.edu || imsaguy || 128.30.96.44 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| jun.dashjr.org || Luke-Jr || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || ||
|-
| cheaperinbitcoins.com || Xenland/Shane || 184.154.36.82 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| django.webflows.fr || unknown2 || 188.165.213.169 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| porgressbar.sk || progressbar hackerspace || 91.210.181.21 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| faucet.bitcoin.st || bitcoin street || 64.27.57.225 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| bitcoin.securepayment.cc || SecurePayment CC || 63.247.147.163 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| www.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.181 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| ns2.dcscdn.com || [[User:Danw12|Danw12]] || 199.115.228.182 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| coin.soul-dev.com || Soul-Dev || || || {{Fallback Nodes/Node Up}} || ||
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 91.121.205.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| btcnode1.bitgroup.cc || BitGroup || 198.211.116.191 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode2.bitgroup.cc || BitGroup || 162.243.120.138 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode3.bitgroup.cc || BitGroup || 95.85.8.237 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || Yes
|-
| btcnode.xiro.co || Xiro Labs || 91.121.108.61 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| murder.xf-liam.com || [[User:liamwli|Liam W]] || 162.245.217.119 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| bitcoin.bitdonut.co || James Hartig
|-
| coinno.de || jaknam
|-
| 82.165.44.44 || anonymous
|-
| bitcoin1.dassori.me || gdassori
|-
| bitcoin2.dassori.me || gdassori
|-
| blockchainnode.meulie.net || [[User:Evert|Evert]]
|-
| fullnode.fybsg.com || Nagato
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 62.210.66.227
|-
| softnet.homenet.org || [[User:Victorsueca|Victorsueca]]

|}

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

| InductiveSoul.US || [[User:Inductivesoul|Inductive Soul]] || 2601:7:6680:2ac:4d29:40ff:7513:fcc7 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || 11-13-2013 (MDY) || Yes
|-
| caffeinator.net || [[User:Atrophy|Atrophy]] || || || {{Fallback Nodes/Node Up}} || 2013-05-10 ||
|-
| 2001:470:8:2e1::40 || ? || 2001:470:8:2e1::40 || {{Table Value Yes}} || {{Fallback Nodes/Node Down}} || || Yes
|-
| messier.bzfx.net || BZFX/[[User:A Meteorite|A Meteorite]] || 2001:41d0:1:d632::1 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || ||
|-
| murder.xf-liam.com || [[User:liamwli|Liam W]] || 2602:ffc5::ffc5:56b6 || {{Table Value Yes}} || {{Fallback Nodes/Node Up}} || || No
|-
| bitcoin.bitdonut.co || James Hartig
|-
| n.bitcoin-fr.io || [[User:Arthur|Arthur]] || 2001:bc8:c087:2001::1

|}

=== Tor nodes ===

This entire list was last checked on 2015-02-22.

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| 4iuf2zac6aq3ndrb.onion || Hades || Up || 2015-12-16 || No
|-
| ccfxptj3yi2ysa7w.onion || redfish
|-
| nkf5e6b7pl4jfd4a.onion || BlueMatt || Up || 2015-11-11 || No
|-
| hhiv5pnxenvbf4am.onion || ? || Up || 2015-03-17 || No
|-
| bpdlwholl7rnkrkw.onion || kenansulayman || Up || 2015-03-17 || ?
|-
| bk5ejfe56xakvtkk.onion || dserrano5 || Up || 2015-03-17 || No
|-
| wxvp2d4rspn7tqyu.onion || lunokhod || Up || 2015-08-17 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || Down || 2015-03-17 || Yes
|-
| e3tn727fywnioxrc.onion || Zedd || Down || 2015-03-17 || No
|-
| pqosrh6wfaucet32.onion || bitcoin street || Down || 2015-03-17 || No
|-
| r4de4zf4lyniu4mx.onion:8444 || ? || Down || 2015-01-20 || ?
|-
| zy3kdqowmrb7xm7h.onion || Tril || Down || 2015-01-20 || No
|-
| smith4mfhwcq7x3b.onion || Smithtrader || Down || 2014-11-22 || ?
|-
| i2r5tbaizb75h26f.onion || TorDude || Down || 2014-07-24 || No
|-
| btcnet3utgzyz2bf.onion || anonymous || Down || 2014-07-24 || Yes
|-
| kjy2eqzk4zwi5zd3.onion || sipa || Down || 2014-07-24 || No
|-
| tsyvzsqwa2kkf6b2.onion || TorDude || Down || 2014-05-19 || No
|-
| igpdszqrbqjhak5z.onion || anonymous || Down || 2014-05-15 || ?
|-
| evolynhit7shzeet.onion || Evolyn || Down || 2014-05-15 || Yes
|-
| z55v4ostefnwfy32.onion || Tril || Down || 2014-04-09 || No
|-
| bitcoin2u5jnjzzz.onion || anonymous || Down || 2014-01-27 || Yes
|-
| btc4ulpftizx5b72.onion || TorNode || Down || 2013-05-10 || Yes
|-
| yyl3ipdmyjkfypmx.onion || redemerald || Down || 2013-05-10 || Yes
|-
| siqdznszjf4e6v5j.onion || Tuxavant || Down || 2013-05-10 || ?
|-
| 7hxvg2lvr2ashzli.onion || Tuxavant || Down || 2013-05-10 || ?
|-
| x3danbeag2kyx644.onion || redemerald || Down || 2013-01-04 || Yes
|-
| 6hgmaxwellgpv2oe.onion || Gmaxwell || Down || 2012-07-01 || No
|-
| bitcoinprwwpuinm.onion:8333 || ? || Down || 2012-06-26 || ?
|-
| mutqcuh7hwxmhx3k.onion || Xirafe || Down || 2012-06-23 || ?
|-
| sjdntqu5roj4q6lo.onion || torservers || Down || 2012-05-19 || ?
|-
| bitcoin2bkgm3fke.onion || ? || Down || 2012-05-19 || Yes
|-
| ceeji4qpfs3ms3zc.onion || creepa || ? || ? || ?
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

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

==See Also==

* [[Network|Bitcoin Network]]
* [http://nodes.bitcoin.st Fallback Nodes] List of longest running Bitcoin Nodes listed by Country.
* [https://getaddr.bitnodes.io/ Bitnodes project]
* [https://blockchain.info/connected-nodes Recently connected nodes at blockchain.info]

{{Bitcoin Core documentation}}