Category:Mining

2011-08-15T22:07:24Z

Btcfan: /* Guides */

Reprinted from the [[How_bitcoin_works#Bitcoin_mining|How Bitcoin works]] page:

== High Level Description ==
'''Mining''' bitcoins is the process of generating [[blocks]] for the [[block chain]], which is a way of processing and verifying [[transactions]]. Adding a block to the block chain is difficult, requiring time and processing power to accomplish. So what incentive does anyone have to spend the effort to produce a block, if it takes up all these resources? The answer is that the person who manages to produce a block gets a reward. This reward is two-fold. First, the block producer gets a bounty of some number of bitcoins, which is agreed-upon by the network. (Currently this bounty is 50 bitcoins; this value will halve every 210,000 blocks.) Second, any transaction fees that may be present in the transactions included in the block, get claimed by the block producer.

This gives rise to the activity known as "bitcoin mining" - using processing power to try to produce a valid block, and as a result 'mine' some bitcoins. The network rules are such that the difficulty is adjusted to keep block production to approximately 1 block per 10 minutes. Thus, the more miners engage in the mining activity, the more difficult it becomes for each individual miner to produce a block. The higher the total difficulty, the harder it is for an attacker to overwrite the tip of the block chain with his own blocks (which enables him to double-spend his coins. See the [[weaknesses]] page for more details).

Besides being important for maintaining the transaction database, mining is also the mechanism by which bitcoins get created and distributed among the people in the bitcoin economy. The network rules are such that over the next hundred years, give or take a few decades, a total of 21 million bitcoins will be created. Rather than dropping money out of a helicopter, the bitcoins are awarded to those who contribute to the network by creating blocks in the block chain.

==Guides==

* [http://www.weusecoins.com/mining-guide.php WeUseCoins - Mining Guide]
* [http://ewoah.com/technology/a-very-good-guide-to-building-a-bitcoin-mining-rig-cluster-guide eWoah: How to build a Bitcoin Mining Rig Cluster]
* [http://bitcointalk.org/?topic=7514.0 Ubuntu Natty Narwhal 11.04 Mining Guide / HOWTO]
* [http://www.iscyspace.com Iscyspace] free 10 step guide
* [https://bitcointalk.org/index.php?topic=34226.0 Digbtc.net bitcoin mining]
* [http://bitcointalk.org/index.php?topic=17805.0 MineCo.in pool: Beginners guide to pooled bitcoin mining]
* [http://bitclockers.com/forums/index.php?topic=3.0 BitClockers pool: Getting started mining]

[[zh-cn:Category:开采]]
[[de:Kategorie:Mining]]

Fallback Nodes

2011-06-30T02:40:42Z

Btcfan: /* IPv4 Nodes */

This is a list of nodes which are considered reliable. Nodes from this list which are down for more than 24 hours will be automatically removed and status of each node is displayed and updated every hour by [[User:WikiBot|WikiBot]].

== How to use this list ==

=== Connect to nodes ===

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

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

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

The [[Original Bitcoin client]] do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(host ndrix.com |sed s/"^.*has address "//)

=== IP Transactions ===

You can also send [[IP Transactions]] to these nodes. If you include your bitcoin address in the "message" field, you may have your coins back.

=== Tor network ===

To use tor .onion addresses, you need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion

Once you have configured and restarted tor, 192.0.2.2 will connect to ijzt2eeizty3p5xe.onion when accessed through the Tor proxy (and likewise for the other IPs/onions). You can then run Bitcoin with -addnode=192.0.2.2, or even send bitcoins to that IP address. You can use any arbitrary IP addresses with MapAddress, though some of the common non-routable ranges (10.*, 192.168.*) will not work due to a Bitcoin bug. 192.0.2.1-192.0.2.255 is the recommended range because it is both non-routable and compatible with Bitcoin.

== Nodes list ==

=== IPv4 Nodes ===

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

| 109.72.80.77 || devriesi
|-
| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| 69.164.218.197 || Gavin Andresen || 69.164.218.197 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| jun.dashjr.org || Lightfoot Hosting || 173.242.112.53 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || ?
|-
| mining.bitcoin.cz || slush || 178.79.147.99 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:08 || No
|-
| fallback2.bitcoin.me.uk || Vladimir [Pool] || 178.255.199.86 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:12 || No
|-
| fallback1.kr105.com || kR105 || 190.101.85.148 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.23}} || 2011-06-28 03:38:21 || No
|-
| bitcoin.csy.ca || Martok || 128.189.187.27 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:09 || ?
|-
| nat.router.dashjr.org || Luke-Jr || 71.1.74.69 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:10 || ?
|-
| bitcoin.sipa.be || sipa || 178.18.90.41 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:10 || No
|-
| bluematt.me || BlueMatt || 62.155.236.249 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-05-03 12:29:00 || No
|-
| btc1.justmoon.net || justmoon || 109.75.176.226 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || Yes
|-
| bitcoins.ca || humble || 142.58.248.28 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || Yes
|-
| BiddingPond.com || BiddingPond || 184.106.111.41 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.2]}} || 2011-04-17 12:00:10 || ?
|-
| zack.home.chrishowie.com || cdhowie || 98.222.140.181 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-04-17 12:00:11 || No
|-
| 178.63.15.200 || hendi || 178.63.15.200 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.20[.1]}} || 2011-04-17 12:00:11 || ?
|-
| fallback1.bitcoin.me.uk || Vladimir || 91.85.220.84 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 173.224.125.222 || MagicalTux [US] || 173.224.125.222 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:12 || No
|-
| bitlex.org || BitLex || 78.34.69.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2011-04-17 12:00:13 || Yes
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2011-04-17 12:00:13 || Yes
|-
| 64.31.38.250 || TDT || 64.31.38.250 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.22}} || 2011-06-12 12:00:04 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-04-17 12:00:13 || ?
|-
| 67.176.86.181 || BobSGI || 67.176.86.181 ||
|-
| BTCSportsBet.com || Cusipzzz || 109.75.176.39 || {{Table Value Yes}}
|-
| 86.5.50.90 || ? || 86.5.50.90 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.21}} || 2011-05-21 17:13:00 || ?
|-
| eudemocracia.org.ar || Eudemocracia
|-
| 31.18.88.53 || DaMan || 31.18.88.53 ||
|-
| faucet.bitcoin.st || Bitcoin Street || 64.27.57.225 || {{Table Value Yes}}
|-
| meerkatmischief.com || nallar
|-
| 204.9.55.71 || toasty
|-
| 46.182.18.245 || DontMindMe
|-
| 77.245.75.130 || embreym
|-
| 87.127.127.226 || NiccyB
|-
| tech.dyndns-blog.com || Carsonb
|-
| 184.107.48.198 || meehow
|-
| 178.32.120.164 || meehow
|-
| 89.200.139.134 || Joe59101
|-
| 74.91.19.46 || btcfan

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-02-11 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-02-11 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-02-11 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-02-11 || Yes
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-02-11 || Yes
|-
| bitcoinbudtoeks7.onion || ? || ? || 2011-02-11 || ?
|-
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-02-11 || ?
|-
| h4kklwodpcmo6cbq.onion || ? || ? || 2011-02-11 || ?
|-
| vv6kcfscuntybrzm.onion || ? || ? || 2011-02-11 || ?
|-
| nlnsivjku4x4lu5n.onion || ? || ? || 2011-02-11 || ?
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|-
| 4lmduyac3svgrrav.onion || ? || ? || 2011-02-11 || No
|-
| usasx4urod3yj4az.onion || ? || ? || 2011-02-11 || No
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list. To accept IP transactions you will have to add the ''-allowreceivebyip'' flag to your command line parameters.

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

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

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

Bitcoin Wiki - User contributions [en]

Category:Mining

Fallback Nodes