Bitcoin Wiki - User contributions [en]

Fallback Nodes

2016-03-12T03:15:19Z

Doyle: /* 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]]
|-
| 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}} || ||
|-
| 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
|-
| 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 || ? || ? || ?
|}

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

Full node

2016-03-10T14:43:40Z

Doyle: Add example implemtntation

Any computer that connects to the Bitcoin [[network]] is called a '''node'''. Nodes that fully enforce all of the rules of Bitcoin are called '''full nodes'''. Most nodes on the network are [[lightweight node]]s instead of full nodes, but full nodes form the backbone of the network.

==What makes a full node?==

Full nodes download every block and transaction and check them against Bitcoin's core consensus rules. Here are examples of consensus rules, though there are many more:
* Blocks may only create a certain number of bitcoins. (Currently 25 BTC per block.)
* Transactions must have correct signatures for the bitcoins being spent.
* Transactions/blocks must be in the correct data format.
* Within a single [[block chain]], a transaction output cannot be double-spent.

If a transaction or block violates the consensus rules, then it is absolutely rejected, even if every other node on the network thinks that it is valid. This is one of the most important characteristics of full nodes: they do what's right ''no matter what''. For full nodes, miners actually have fairly limited power: they can only reorder or remove transactions, and only by expending a lot of computing power. A powerful miner is able to execute [[Weaknesses#Attacker_has_a_lot_of_computing_power|some serious attacks]], but because full nodes rely on miners only for a few things, miners could not completely change or destroy Bitcoin.

Nodes that have different ''consensus'' rules are actually using two different networks/currencies. Changing any of the consensus rules requires a [[hard fork]], which can be thought of as creating a new currency and having everyone move to it. Consensus rules are different from ''policy'' rules, which specify how a node or miner prioritizes or discourages certain things. Policy rules can be changed freely, and different nodes can have different policy rules. Because all full nodes must use ''exactly'' the same consensus rules in order to remain compatible with each other, even duplicating bugs and oddities in the original consensus rules, creating a full node from scratch is extremely difficult and dangerous. It is therefore recommended that everyone who wishes to run a full node use software based on the [[reference client]], which is the only client guaranteed to behave correctly.

At minimum, a full node must download every transaction that has ever taken place, all new transactions, and all block headers and Merkle trees. Additionally, full nodes must store information about every unspent transaction output until it is spent. Modern-day full nodes are inefficient in that they download each new transaction at least twice, and they store the entire block chain (>30 GB) forever, even though only the unspent transaction outputs (<1 GB) are required.

== Why should you run a full node? ==

==== Summary ====
Running a full node is the only way you can use Bitcoin in a trustless way. You will know for sure that all the rules of Bitcoin are being followed, for example that no bitcoins are spent not belonging to the owner, that no coins were spent twice, that no inflation happens outside of the [[Controlled_supply|schedule]] and that all the rules needed to make the system work (e.g. [[difficulty]]) are followed. Full nodes are currently the most [[Privacy|private]] way to use Bitcoin, with no nobody else learning which bitcoin [[Address|addresses]] belong to you. Full nodes are the most secure way to use Bitcoin, they do not suffer from many attacks that affect lightweight wallets.

=== Economic strength ===

This is by far the most important reason for running a full node, though it is a little difficult to understand.

As explained previously, full nodes enforce the consensus rules no matter what. However, lightweight nodes do not do this. Lightweight nodes do whatever the majority of mining power says. Therefore, if most of the miners got together to increase their block reward, for example, lightweight nodes would blindly go along with it. If this ever happened, the network would split such that lightweight nodes and full nodes would end up on separate networks, using separate currencies. People using lightweight nodes would be unable to transact with people using full nodes. If all businesses and many users are using full nodes, then this network split is not a ''critical'' problem because users of lightweight clients will quickly notice that they can't send or receive bitcoins to/from most of the people who they usually do business with, and so they'll stop using Bitcoin until the evil miners are overcome, which is the appropriate response. ''However'', if almost everyone on the network is using lightweight nodes in this situation, then everyone would continue being able to transact with each other, and so Bitcoin could very well end up "hijacked" by evil miners.

In practice, miners are unlikely to attempt anything like the above scenario as long as full nodes are prevalent because the miners would lose a lot of money. But the incentives completely change if everyone uses lightweight nodes. In that case, miners definitely ''do'' have an incentive to change Bitcoin's rules in their favor. It is only reasonably secure to use a lightweight node ''because'' most of the Bitcoin economy uses full nodes.

Therefore, it is critical for Bitcoin's survival that the great majority of the Bitcoin economy be backed by full nodes, not lightweight nodes. This is especially important for Bitcoin businesses, which have more economic weight. To contribute to Bitcoin's economic strength, you must actually use a full node for your real transactions (or use a lightweight node connected to a full node that you personally control). Just running a full node on a server somewhere does not contribute to Bitcoin's economic strength.

More details https://www.reddit.com/r/BitcoinBeginners/comments/3eq3y7/full_node_question/ctk4lnd

=== Network services ===

Full nodes may provide various services to other network participants (if the software is run with -listen=1 as is default). This is especially important for lightweight nodes.

These services include:
* Filtering transactions and blocks on behalf of lightweight nodes so that lightweight nodes do not need to download every transaction ever made on the network in order to find their own transactions.
* Serving historical full blocks to nodes that have been offline for a while.
* Transmitting new transactions from users to miners.
* Broadcasting new blocks from miners to other nodes.

For the most part, these services are only usefully performed by full nodes that are listening on port 8333. Other full nodes and all lightweight nodes are actually a slight drain on the network's resources in this respect. The more full nodes that accept incoming connections there are, the more users the Bitcoin network can support.

=== Privacy ===

Having the blockchain stored on your hard drive is the most private way to have a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>.

For many use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.

=== Security ===

Lightweight nodes are sometimes able to be temporarily tricked into accepting transactions or blocks that are not actually valid. This could cause serious financial damage, especially for websites that automatically process Bitcoin transactions. Full nodes provide the maximum security possible, and so they should be used by all businesses, and also by regular users whenever doing so is convenient.

=== Some are incentivizing it ===
Bitnodes ran a program to incentivize full node operators until the end of 2015.<ref>[https://bitcoinmagazine.com/19620/bitnodes-project-issues-first-incentives-node-operators/ Bitnodes Project Issues First Incentives For Node Operators by Joel Dalas] of [http://bitcoinmagazine.com/ <i>Bitcoin Magazine</i>]; cf. https://blog.bitcoinfoundation.org/bitnodes-project-2015-q1-report-peer-index-and-incentivized-full-nodes/</ref>

== How to run a full node ==

If you run the [[Bitcoin Core]]/[[bitcoind]] wallet, you are running a full node. If you open port 8333, you will contribute to the network's capacity. If you actually use the wallet feature, or if you use a lightweight client like [[MultiBit]] but configure it to connect exclusively to your full node, then you will contribute to the network's economic strength and receive protection from some possible attacks against lightweight nodes.

There are a few alternate full node implementations, but they are not recommended for serious use because it is currently difficult to determine whether they implement the consensus rules with 100% accuracy. Even very slight inaccuracies could cause serious problems for the users of these alternate clients. One widespread example implementation is [https://bitcore.io/guides/full-node/ Bitcore].

==References==
<references />

[[Category:Technical]]

{{Bitcoin Core documentation}}

Full node

2016-03-10T14:41:14Z

Doyle: Remove broken link and change incentivization to past tense

Any computer that connects to the Bitcoin [[network]] is called a '''node'''. Nodes that fully enforce all of the rules of Bitcoin are called '''full nodes'''. Most nodes on the network are [[lightweight node]]s instead of full nodes, but full nodes form the backbone of the network.

==What makes a full node?==

Full nodes download every block and transaction and check them against Bitcoin's core consensus rules. Here are examples of consensus rules, though there are many more:
* Blocks may only create a certain number of bitcoins. (Currently 25 BTC per block.)
* Transactions must have correct signatures for the bitcoins being spent.
* Transactions/blocks must be in the correct data format.
* Within a single [[block chain]], a transaction output cannot be double-spent.

If a transaction or block violates the consensus rules, then it is absolutely rejected, even if every other node on the network thinks that it is valid. This is one of the most important characteristics of full nodes: they do what's right ''no matter what''. For full nodes, miners actually have fairly limited power: they can only reorder or remove transactions, and only by expending a lot of computing power. A powerful miner is able to execute [[Weaknesses#Attacker_has_a_lot_of_computing_power|some serious attacks]], but because full nodes rely on miners only for a few things, miners could not completely change or destroy Bitcoin.

Nodes that have different ''consensus'' rules are actually using two different networks/currencies. Changing any of the consensus rules requires a [[hard fork]], which can be thought of as creating a new currency and having everyone move to it. Consensus rules are different from ''policy'' rules, which specify how a node or miner prioritizes or discourages certain things. Policy rules can be changed freely, and different nodes can have different policy rules. Because all full nodes must use ''exactly'' the same consensus rules in order to remain compatible with each other, even duplicating bugs and oddities in the original consensus rules, creating a full node from scratch is extremely difficult and dangerous. It is therefore recommended that everyone who wishes to run a full node use software based on the [[reference client]], which is the only client guaranteed to behave correctly.

At minimum, a full node must download every transaction that has ever taken place, all new transactions, and all block headers and Merkle trees. Additionally, full nodes must store information about every unspent transaction output until it is spent. Modern-day full nodes are inefficient in that they download each new transaction at least twice, and they store the entire block chain (>30 GB) forever, even though only the unspent transaction outputs (<1 GB) are required.

== Why should you run a full node? ==

==== Summary ====
Running a full node is the only way you can use Bitcoin in a trustless way. You will know for sure that all the rules of Bitcoin are being followed, for example that no bitcoins are spent not belonging to the owner, that no coins were spent twice, that no inflation happens outside of the [[Controlled_supply|schedule]] and that all the rules needed to make the system work (e.g. [[difficulty]]) are followed. Full nodes are currently the most [[Privacy|private]] way to use Bitcoin, with no nobody else learning which bitcoin [[Address|addresses]] belong to you. Full nodes are the most secure way to use Bitcoin, they do not suffer from many attacks that affect lightweight wallets.

=== Economic strength ===

This is by far the most important reason for running a full node, though it is a little difficult to understand.

As explained previously, full nodes enforce the consensus rules no matter what. However, lightweight nodes do not do this. Lightweight nodes do whatever the majority of mining power says. Therefore, if most of the miners got together to increase their block reward, for example, lightweight nodes would blindly go along with it. If this ever happened, the network would split such that lightweight nodes and full nodes would end up on separate networks, using separate currencies. People using lightweight nodes would be unable to transact with people using full nodes. If all businesses and many users are using full nodes, then this network split is not a ''critical'' problem because users of lightweight clients will quickly notice that they can't send or receive bitcoins to/from most of the people who they usually do business with, and so they'll stop using Bitcoin until the evil miners are overcome, which is the appropriate response. ''However'', if almost everyone on the network is using lightweight nodes in this situation, then everyone would continue being able to transact with each other, and so Bitcoin could very well end up "hijacked" by evil miners.

In practice, miners are unlikely to attempt anything like the above scenario as long as full nodes are prevalent because the miners would lose a lot of money. But the incentives completely change if everyone uses lightweight nodes. In that case, miners definitely ''do'' have an incentive to change Bitcoin's rules in their favor. It is only reasonably secure to use a lightweight node ''because'' most of the Bitcoin economy uses full nodes.

Therefore, it is critical for Bitcoin's survival that the great majority of the Bitcoin economy be backed by full nodes, not lightweight nodes. This is especially important for Bitcoin businesses, which have more economic weight. To contribute to Bitcoin's economic strength, you must actually use a full node for your real transactions (or use a lightweight node connected to a full node that you personally control). Just running a full node on a server somewhere does not contribute to Bitcoin's economic strength.

More details https://www.reddit.com/r/BitcoinBeginners/comments/3eq3y7/full_node_question/ctk4lnd

=== Network services ===

Full nodes may provide various services to other network participants (if the software is run with -listen=1 as is default). This is especially important for lightweight nodes.

These services include:
* Filtering transactions and blocks on behalf of lightweight nodes so that lightweight nodes do not need to download every transaction ever made on the network in order to find their own transactions.
* Serving historical full blocks to nodes that have been offline for a while.
* Transmitting new transactions from users to miners.
* Broadcasting new blocks from miners to other nodes.

For the most part, these services are only usefully performed by full nodes that are listening on port 8333. Other full nodes and all lightweight nodes are actually a slight drain on the network's resources in this respect. The more full nodes that accept incoming connections there are, the more users the Bitcoin network can support.

=== Privacy ===

Having the blockchain stored on your hard drive is the most private way to have a wallet. All other lightweight solutions leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, SPV nodes based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet <ref>[https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/ Privacy in BitcoinJ ]</ref>.

For many use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.

=== Security ===

Lightweight nodes are sometimes able to be temporarily tricked into accepting transactions or blocks that are not actually valid. This could cause serious financial damage, especially for websites that automatically process Bitcoin transactions. Full nodes provide the maximum security possible, and so they should be used by all businesses, and also by regular users whenever doing so is convenient.

=== Some are incentivizing it ===
Bitnodes ran a program to incentivize full node operators until the end of 2015.<ref>[https://bitcoinmagazine.com/19620/bitnodes-project-issues-first-incentives-node-operators/ Bitnodes Project Issues First Incentives For Node Operators by Joel Dalas] of [http://bitcoinmagazine.com/ <i>Bitcoin Magazine</i>]; cf. https://blog.bitcoinfoundation.org/bitnodes-project-2015-q1-report-peer-index-and-incentivized-full-nodes/</ref>

== How to run a full node ==

If you run the [[Bitcoin Core]]/[[bitcoind]] wallet, you are running a full node. If you open port 8333, you will contribute to the network's capacity. If you actually use the wallet feature, or if you use a lightweight client like [[MultiBit]] but configure it to connect exclusively to your full node, then you will contribute to the network's economic strength and receive protection from some possible attacks against lightweight nodes.

There are a few alternate full node implementations, but they are not recommended for serious use because it is currently difficult to determine whether they implement the consensus rules with 100% accuracy. Even very slight inaccuracies could cause serious problems for the users of these alternate clients.

==References==
<references />

[[Category:Technical]]

{{Bitcoin Core documentation}}

Fallback Nodes

2016-03-10T14:37:02Z

Doyle: /* IPv6 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]]
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle]

|}

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

== 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-03-10T14:34:58Z

Doyle: /* 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]]
|-
| mars.jordandoyle.uk || [https://doyle.wf Jordan Doyle]

|}

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