Bitcoin Wiki - User contributions [en]

Remote miner

2010-12-20T14:47:10Z

RichardG: Created page with "{{stub}}The '''remote miner''' is a Bitcoin pooled miner created by puddinpop. It mines through a proprietary JSON-based protocol, and supports mining through CPU and GPU (OpenCL..."

{{stub}}The '''remote miner''' is a Bitcoin pooled miner created by puddinpop. It mines through a proprietary JSON-based protocol, and supports mining through CPU and GPU (OpenCL and CUDA).

==Pooled mining servers==
*doublec's server: (dead)
*sjaak's server: 91.121.29.91

Cpu Miner

2010-12-20T14:43:44Z

RichardG:

{{stub}}'''cpu-miner''' is a Bitcoin pooled miner created by jgarzik. It mines through a proprietary JSON-RPC pooled mining protocol, and supports several algorithms for doing encryption required to build a block.

==Algorithms==
*'''c:''' Linux kernel (but not restricted to Linux) implementation of SHA256.
*'''4way:''' 128-bit SSE2 optimizations which are already available as a compile-time option on the classic Bitcoin client.
*'''padlock:''' Implementation of the Padlock encryption optimizations on VIA CPUs.
*'''cryptopp:''' (Experimental) algorithm which uses the Crypto++ library.

==Pooled mining servers==
*[http://mining.bitcoin.cz slush's server]

[[Category:Bitcoin miners]]

User:RichardG

2010-12-20T14:36:25Z

RichardG: Created page with "Contributors Award participant: 16vHMG18F3wXFMKquGtSTEkkGzcSHdR7i6"

Contributors Award participant: 16vHMG18F3wXFMKquGtSTEkkGzcSHdR7i6

Talk:Bitcoin Map

2010-12-20T14:34:14Z

RichardG:

==Resolving==
I think the map should resolve (PTR/rDNS) the IPs it finds for statistic reasons. It shouldn't hurt, unless if it's applied in mass (see below).
''Curious corner:'' I am running a resolver I wrote on mIRC script which takes IPs off KML placemark names and resolves them. It's at 33% parsing the current map, running for 1-2 hours or so.
--[[User:RichardG|RichardG]] 14:33, 20 December 2010 (GMT)

Talk:Bitcoin Map

2010-12-20T14:33:14Z

RichardG: Created page with "==Resolving== I think that the map should resolve (PTR/rDNS) the IPs it finds for statistic reasons. It shouldn't hurt, unless if it's applied in mass. Curious corner: I am runni..."

==Resolving==
I think that the map should resolve (PTR/rDNS) the IPs it finds for statistic reasons. It shouldn't hurt, unless if it's applied in mass.
Curious corner: I am running a resolver I wrote on mIRC script which takes IPs off KML placemark names and resolves them. It's at 33% parsing the current map, running for 1-2 hours or so.
--[[User:RichardG|RichardG]] 14:33, 20 December 2010 (GMT)

Cpu Miner

2010-12-20T12:21:42Z

RichardG: lol, if 4way was SSE, I could use it on my Athlon XP!

{{stub}}'''cpu-miner''' is a Bitcoin miner created by jgarzik. It mines through a proprietary JSON-RPC pooled mining protocol, and supports several algorithms for doing encryption required to build a block.

==Algorithms==
*'''c:''' Linux kernel (but not restricted to Linux) implementation of SHA256.
*'''4way:''' 128-bit SSE2 optimizations which are already available as a compile-time option on the classic Bitcoin client.
*'''padlock:''' Implementation of the Padlock encryption optimizations on VIA CPUs.
*'''cryptopp:''' (Experimental) algorithm which uses the Crypto++ library.

==Pooled mining servers==
*[http://mining.bitcoin.cz slush's server]

[[Category:Bitcoin miners]]

OpenCL miner

2010-12-20T12:20:10Z

RichardG: blank lines blah blah blah

{{stub}}The '''OpenCL miner''' is a Bitcoin miner created by m0mchil. It requires an OpenCL or CUDA compatible graphics card, and uses OpenCL to generate a block using your graphics card's GPU.

This miner is highly looked for, as mining performance on a GPU may outperform a similarly priced CPU in many times.

[[Category:Bitcoin miners]]

Cpu Miner

2010-12-20T12:20:00Z

RichardG: blank lines blah blah blah

{{stub}}'''cpu-miner''' is a Bitcoin miner created by jgarzik. It mines through a proprietary JSON-RPC pooled mining protocol, and supports several algorithms for doing encryption required to build a block.

==Algorithms==
*'''c:''' Linux kernel (but not restricted to Linux) implementation of SHA256.
*'''4way:''' SSE optimizations which are already available as a compile-time option on the classic Bitcoin client.
*'''padlock:''' Implementation of the Padlock encryption optimizations on VIA CPUs.
*'''cryptopp:''' (Experimental) algorithm which uses the Crypto++ library.

==Pooled mining servers==
*[http://mining.bitcoin.cz slush's server]

[[Category:Bitcoin miners]]

Fallback Nodes

2010-12-19T21:15:47Z

RichardG: /* 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 theymos.ath.cx |sed s/"^.*has address "//)

=== IP Transactions ===

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

=== Tor network ===

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

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

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

== Nodes list ==

=== IPv4 Nodes ===

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

| bitcoin-otc.com || nanotube || 69.163.132.101 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 21:00:02 || No
|-
| 91.121.222.175 || MagicalTux [FR] || 91.121.222.175 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 21:00:02 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 21:00:03 || No
|-
| 174.120.185.74 || MagicalTux [US] || 174.120.185.74 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 21:00:03 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 21:00:03 || No
|-
| 212.17.86.234 || ? || 212.17.86.234 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 21:00:03 || Yes
|-
| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 21:00:03 || ?
|-
| lfmcal.dontexist.org || lfm || 75.158.131.108 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 21:00:04 || Yes
|-
| bitlex.co.cc || BitLex || 78.34.68.114 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 21:00:04 || Yes
|-
| athome.xta.net || MagicalTux [JP] || 114.145.96.119 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 21:00:04 || ?
|-
| mining.bitcoin.cz || slush_cz || 109.74.195.190 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.18}} || 2010-12-19 21:00:04 || ?
|-
| pastecoin.com || genjix || 178.33.13.4 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.17[.4]}} || 2010-12-19 21:00:05 || ?
|-
| artforz.ath.cx || ArtForz || 84.146.43.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.15[.4]}} || 2010-12-19 21:00:05 || No
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.14[.3]}} || 2010-12-19 21:00:05 || Yes
|-
| 200.35.150.50 || rodin || 200.35.150.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.13}} || 2010-12-19 21:00:11 || No
|-
| 189.126.103.109 || RichardG || 189.126.103.109 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.12}} || 2010-12-19 21:00:11 || ?
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2010-12-19 21:00:11 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2010-12-19 21:00:11 || ?
|-
| lzsaver.dlinkddns.com || lzsaver || 109.226.64.44 || {{Table Value No}} || {{Fallback Nodes/Node Down}} || 2010-12-19 20:00:28 || ?
|-
| richardg.ath.cx || RichardG

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2010-11-13 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2010-11-13 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2010-11-13 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2010-11-13 || Yes
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2010-11-13 || Yes
|-
| rnam4cxam62nkcyf.onion || BitLex || ? || 2010-11-13 || Yes
|-
| lhkz56zqrjo3jsmp.onion || fuzzylogic || ? || 2010-11-14 || Yes
|}

== Adding a node ==

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

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

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

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

Fallback Nodes

2010-12-19T20:34:30Z

RichardG: /* 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 theymos.ath.cx |sed s/"^.*has address "//)

=== IP Transactions ===

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

=== Tor network ===

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

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

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

== Nodes list ==

=== IPv4 Nodes ===

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

| bitcoin-otc.com || nanotube || 69.163.132.101 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 20:00:02 || No
|-
| 91.121.222.175 || MagicalTux [FR] || 91.121.222.175 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 20:00:03 || No
|-
| 109.75.176.193 || MagicalTux [DE] || 109.75.176.193 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 20:00:03 || No
|-
| 174.120.185.74 || MagicalTux [US] || 174.120.185.74 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 20:00:03 || No
|-
| 178.63.62.15 || MagicalTux [DE] || 178.63.62.15 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 20:00:03 || No
|-
| 212.17.86.234 || ? || 212.17.86.234 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 20:00:03 || Yes
|-
| ndrix.com || mndrix || 64.22.103.150 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 20:00:04 || ?
|-
| lfmcal.dontexist.org || lfm || 75.158.131.108 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 20:00:04 || Yes
|-
| bitlex.co.cc || BitLex || 78.34.68.114 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 20:00:04 || Yes
|-
| athome.xta.net || MagicalTux [JP] || 114.145.96.119 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.19}} || 2010-12-19 20:00:04 || ?
|-
| mining.bitcoin.cz || slush_cz || 109.74.195.190 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.18}} || 2010-12-19 20:00:05 || ?
|-
| pastecoin.com || genjix || 178.33.13.4 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.17[.4]}} || 2010-12-19 20:00:06 || ?
|-
| artforz.ath.cx || ArtForz || 84.146.43.123 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.15[.4]}} || 2010-12-19 20:00:06 || No
|-
| theymos.ath.cx || theymos || 99.27.237.13 || {{Table Value Unknown}} || {{Fallback Nodes/Node Up|version=0.3.14[.3]}} || 2010-12-19 20:00:06 || Yes
|-
| lzsaver.dlinkddns.com || lzsaver || 109.226.64.44 || {{Table Value No}} || {{Fallback Nodes/Node Up|version=0.3.13[.4]}} || 2010-12-19 20:00:28 || ?
|-
| 200.35.150.50 || rodin || 200.35.150.50 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.13}} || 2010-12-19 20:00:07 || No
|-
| 74.82.216.10 || thufir || 74.82.216.10 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.10}} || 2010-12-19 20:00:07 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2010-12-19 20:00:07 || ?
|-
| 189.126.103.109 || RichardG

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2010-11-13 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2010-11-13 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2010-11-13 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2010-11-13 || Yes
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2010-11-13 || Yes
|-
| rnam4cxam62nkcyf.onion || BitLex || ? || 2010-11-13 || Yes
|-
| lhkz56zqrjo3jsmp.onion || fuzzylogic || ? || 2010-11-14 || Yes
|}

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

OpenCL miner

2010-12-19T20:16:37Z

RichardG:

{{stub}}
The '''OpenCL miner''' is a Bitcoin miner created by m0mchil. It requires an OpenCL or CUDA compatible graphics card, and uses OpenCL to generate a block using your graphics card's GPU.

This miner is highly looked for, as mining performance on a GPU may outperform a similarly priced CPU in many times.

[[Category:Bitcoin miners]]

Cpu Miner

2010-12-19T20:14:09Z

RichardG: minor touchups

{{stub}}
'''cpu-miner''' is a Bitcoin miner created by jgarzik. It mines through a proprietary JSON-RPC pooled mining protocol, and supports several algorithms for doing encryption required to build a block.

==Algorithms==
*'''c:''' Linux kernel (but not restricted to Linux) implementation of SHA256.
*'''4way:''' SSE optimizations which are already available as a compile-time option on the classic Bitcoin client.
*'''padlock:''' Implementation of the Padlock encryption optimization on VIA CPUs.
*'''cryptopp:''' (Experimental) algorithm which uses the Crypto++ library.

==Pooled mining servers==
*[http://mining.bitcoin.cz slush's server]

[[Category:Bitcoin miners]]

Cpu Miner

2010-12-19T20:11:56Z

RichardG: added PMSes

{{stub}}
'''cpu-miner''' is a Bitcoin miner created by jgarzik. It mines through a proprietary JSON-RPC pooled mining protocol, and supports several algorithms for doing encryption required to build a block.

==Algorithms==
*'''c:''' Linux kernel (but can also be used on Windows) implementation of SHA256.
*'''4way:''' SSE optimizations available as a compile-time option on the classic Bitcoin client.
*'''padlock:''' Implementation of the Padlock encryption optimizations on VIA CPUs.
*'''cryptopp:''' (Experimental) algorithm which uses the Crypto++ library.

==Pooled mining servers==
*[http://mining.bitcoin.cz slush's server]

[[Category:Bitcoin miners]]

OpenCL miner

2010-12-19T20:09:52Z

RichardG: Created page with "{{stub}} The '''OpenCL miner''' is a Bitcoin miner created by m0mchil. It requires an OpenCL or CUDA compatible graphics card, and uses OpenCL to generate a block using your grap..."

{{stub}}
The '''OpenCL miner''' is a Bitcoin miner created by m0mchil. It requires an OpenCL or CUDA compatible graphics card, and uses OpenCL to generate a block using your graphics card's GPU.

This miner is highly looked for, as mining performance on a GPU may outperform a similarly priced CPU in many times.

Cpu Miner

2010-12-19T20:05:10Z

RichardG: Created page with "{{stub}} '''cpu-miner''' is a Bitcoin miner created by jgarzik. It mines through a proprietary JSON-based remote protocol, and supports several algorithms for doing encryption re..."

{{stub}}
'''cpu-miner''' is a Bitcoin miner created by jgarzik. It mines through a proprietary JSON-based remote protocol, and supports several algorithms for doing encryption required to build a block.

==Algorithms==
*'''c:''' Linux kernel (but can also be used on Windows) implementation of SHA256.
*'''4way:''' SSE optimizations available as a compile-time option on the classic Bitcoin client.
*'''padlock:''' Implementation of the Padlock encryption optimizations on VIA CPUs.
*'''cryptopp:''' (Experimental) algorithm which uses the Crypto++ library.

[[Category:Bitcoin miners]]