https://tests.bitcoin.it/w/api.php?action=feedcontributions&user=Cosurgi&feedformat=atomBitcoin Wiki - User contributions [en]2024-03-28T23:11:13ZUser contributionsMediaWiki 1.30.0https://tests.bitcoin.it/w/index.php?title=Base58Check_encoding&diff=35432Base58Check encoding2013-01-25T09:30:47Z<p>Cosurgi: /* Encoding a private key */</p>
<hr />
<div>A modified Base 58 [http://en.wikipedia.org/wiki/Binary-to-text_encoding binary-to-text encoding] known as '''Base58Check''' is used for encoding [[Bitcoin address]]es.<br />
<br />
More generically, Base58Check encoding is used for encoding byte arrays in Bitcoin into human-typable strings. A Bitcoin address is simply a Base58Check-encoded string with a 20-byte payload, the payload being the hash of the [[public key]] associated with the address.<br />
<br />
The original Bitcoin client source code discusses the reasoning behind base58 encoding:<br />
<br />
base58.h:<br />
// Why base-58 instead of standard base-64 encoding?<br />
// - Don't want 0OIl characters that look the same in some fonts and<br />
// could be used to create visually identical looking account numbers.<br />
// - A string with non-alphanumeric characters is not as easily accepted as an account number.<br />
// - E-mail usually won't line-break if there's no punctuation to break at.<br />
// - Doubleclicking selects the whole number as one word if it's all alphanumeric.<br />
<br />
==Features of Base58Check==<br />
Base58Check has the following features:<br />
* An arbitrarily sized payload.<br />
* A set of 58 alphanumeric symbols consisting of easily distinguished uppercase and lowercase letters (0OIl are not used) <br />
* One byte of version/application information. Bitcoin addresses use 0x00 for this byte (future ones may use 0x05).<br />
* Four bytes (32 bits) of SHA256-based error checking code. This code can be used to automatically detect and possibly correct typographical errors.<br />
* An extra step for preservation of leading zeroes in the data.<br />
<br />
==Creating a Base58Check string==<br />
A Base58Check string is created from a version/application byte and payload as follows.<br />
# Take the version/application byte and payload bytes, and concatenate them together (bytewise).<br />
# Take the first four bytes of SHA256(SHA256(results of step 1))<br />
# Concatenate the results of step 1 and the results of step 2 together (bytewise).<br />
# Treating the results of step 3 - a series of bytes - as a single big-endian bignumber, convert to base-58 using normal mathematical steps (bignumber division) and the base-58 alphabet described below. The result should be normalized to not have any leading base-58 zeroes (character '1').<br />
# The leading character '1', which has a value of zero in base58, is reserved for representing an entire leading zero '''byte''', as when it is in a leading position, has no value as a base-58 symbol. There can be one or more leading '1's when necessary to represent one or more leading zero bytes. Count the number of leading zero bytes that were the result of step 3 (for old Bitcoin addresses, there will always be at least one for the version/application byte; for new addresses, there will never be any). Each leading zero byte shall be represented by its own character '1' in the final result.<br />
# Concatenate the 1's from step 5 with the results of step 4. '''This is the Base58Check result.'''<br />
<br />
==Encoding a Bitcoin address==<br />
A Bitcoin address is based on any [[ECDSA]] [[secp256k1]] public/private [[key pair]].<br />
<br />
A Bitcoin address is the Base58Check encoding of the hash of the associated [[script]]. Specifically, it is Base58Check(5,[[RIPEMD160]]([[SHA256]]([[script]]))), with the following constraints:<br />
* [[RIPEMD160]] and [[SHA256]] in this case are always exactly 20 and 32 unsigned bytes respectively. These are big-endian (most significant byte first). (Beware of [[bignumber]] implementations that clip leading 0x00 bytes, or prepend extra 0x00 bytes to indicate sign - your code must handle these cases properly or else you may generate valid-looking addresses which can be sent to, but cannot be spent from - which would lead to the permanent loss of coins.)<br />
* 0 refers to the version/application byte.<br />
<br />
Because of the 0x05 version/application byte, Bitcoin addresses always start with the digit '3'.<br />
<br />
==Encoding a private key==<br />
Base58Check encoding is also used for encoding [[private key]]s in the [[Wallet import format]]. This is formed exactly the same as a Bitcoin address, except that 0x80 is used for the version/application byte, and the payload is 32 bytes instead of 20 (a private key in Bitcoin is a single 32-byte unsigned big-endian integer). Such encodings will always yield a 51-character string that starts with '5', or more specifically, either '5H', '5J', or '5K'.<br />
<br />
==Base58 symbol chart==<br />
The Base58 symbol chart used in Bitcoin is specific to the Bitcoin project and is not intended to be the same as any other Base58 implementation used outside the context of Bitcoin.<br />
{| class="wikitable" <br />
|-<br />
!Value<br />
!Character<br />
!Value<br />
!Character<br />
!Value<br />
!Character<br />
!Value<br />
!Character<br />
|-<br />
|0<br />
|1<br />
|1<br />
|2<br />
|2<br />
|3<br />
|3<br />
|4<br />
|-<br />
|4<br />
|5<br />
|5<br />
|6<br />
|6<br />
|7<br />
|7<br />
|8<br />
|-<br />
|8<br />
|9<br />
|9<br />
|A<br />
|10<br />
|B<br />
|11<br />
|C<br />
|-<br />
|12<br />
|D<br />
|13<br />
|E<br />
|14<br />
|F<br />
|15<br />
|G<br />
|-<br />
|16<br />
|H<br />
|17<br />
|J<br />
|18<br />
|K<br />
|19<br />
|L<br />
|-<br />
|20<br />
|M<br />
|21<br />
|N<br />
|22<br />
|P<br />
|23<br />
|Q<br />
|-<br />
|24<br />
|R<br />
|25<br />
|S<br />
|26<br />
|T<br />
|27<br />
|U<br />
|-<br />
|28<br />
|V<br />
|29<br />
|W<br />
|30<br />
|X<br />
|31<br />
|Y<br />
|-<br />
|32<br />
|Z<br />
|33<br />
|a<br />
|34<br />
|b<br />
|35<br />
|c<br />
|-<br />
|36<br />
|d<br />
|37<br />
|e<br />
|38<br />
|f<br />
|39<br />
|g<br />
|-<br />
|40<br />
|h<br />
|41<br />
|i<br />
|42<br />
|j<br />
|43<br />
|k<br />
|-<br />
|44<br />
|m<br />
|45<br />
|n<br />
|46<br />
|o<br />
|47<br />
|p<br />
|-<br />
|48<br />
|q<br />
|49<br />
|r<br />
|50<br />
|s<br />
|51<br />
|t<br />
|-<br />
|52<br />
|u<br />
|53<br />
|v<br />
|54<br />
|w<br />
|55<br />
|x<br />
|-<br />
|56<br />
|y<br />
|57<br />
|z<br />
|}<br />
<br />
The algorithm for encoding address_byte_string (consisting of 0x01 + hash + 4-byte_check_code) is<br />
<br />
code_string = "123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz"<br />
x = convert_bytes_to_big_integer(hash_result)<br />
<br />
output_string = ""<br />
<br />
while(x > 0) <br />
{<br />
(x, remainder) = divide(x, 58)<br />
output_string.append(code_string[remainder])<br />
}<br />
<br />
repeat(number_of_leading_zero_bytes_in_hash)<br />
{<br />
output_string.append(code_string[0]);<br />
}<br />
<br />
output_string.reverse();<br />
<br />
==Version bytes==<br />
Here are some common version bytes:<br />
<br />
{| class="wikitable" <br />
|-<br />
!Decimal version<br />
!Leading symbol<br />
!Use<br />
|-<br />
|0<br />
|1<br />
|Bitcoin pubkey hash<br />
|-<br />
|5<br />
|3<br />
|Bitcoin script hash<br />
|-<br />
|21<br />
|4<br />
|Bitcoin (compact) public key (proposed)<br />
|-<br />
|52<br />
|M or N<br />
|Namecoin pubkey hash<br />
|-<br />
|128<br />
|5<br />
|Private key<br />
|-<br />
|111<br />
|m or n<br />
|Bitcoin testnet pubkey hash<br />
|-<br />
|196<br />
|2<br />
|Bitcoin testnet script hash<br />
|}<br />
[[List of address prefixes]] is a more complete list.<br />
<br />
== Source code ==<br />
* [https://github.com/bitcoin/bitcoin/blob/master/src/base58.h "Satoshi" C++ codebase (encode/decode using BigNum library)]<br />
* [https://gitorious.org/bitcoin/libblkmaker/blobs/master/base58.c libblkmaker C code (decode only, no external libraries needed)]<br />
<br />
[[Category:Technical]]<br />
<br />
[[es:Codificación Base58Check]]</div>Cosurgihttps://tests.bitcoin.it/w/index.php?title=Comparison_of_mining_pools&diff=11664Comparison of mining pools2011-06-25T21:38:01Z<p>Cosurgi: organize</p>
<hr />
<div>Reward types & explanation:<br />
* '''PPS''' - Pay Per Share. Each submitted share is worth certain amount of BTC. Since finding a block requires <current difficulty> shares ''on average'', a PPS method with 0% fee would be 50 BTC divided by <current difficulty>. It is risky for pool operators, hence the fee is highest.<br />
* '''SMPPS''' - Shared Maximum Pay Per Share. Like Pay Per Share, but never pays more than the pool earns. [http://eligius.st/wiki/index.php/SMaximum_PPS]<br />
* '''Prop.''' - Proportional. When block is found, the reward is distributed among all workers proportionally to how much shares each of them has found. This method is vulnerable to ''pool swapping'' cheat, where a worker would swap to another pool, if this one didn't find a block quickly. Then he would have extra profit on fast rounds, and normal profit on long rounds (because he would be mining on another pool by then). To mitigate this problem pools must introduce extra fees, and hide statistics, so that it is unknown when a block is found.<br />
* '''Score''' - Score based system, the most advanced one. It is a proportional reward, but it is impossible to cheat as described above. Each submitted share is worth more in the function of time ''t'' since start of current round. For each share score is updated by: score += exp(t/C). This makes later shares worth more than earlier shares, thus swapping away to another pool on longer rounds makes the cheater's score to quickly diminish. Rewards are calculated proportionally to scores (and not to shares). Statistics can be shown "live" without fear. The score based method is perfect for 24/7 miners. (at slush's pool C=300 seconds, and every hour scores are normalized)<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Name !! Location !! Hashrate (GHash/sec)<ref name="hashrate">Hashrate is given in gigahash/second.</ref><ref name="hashrate2">Note that pool hashrate is largely irrelevant but can be seen as a popularity measurement. Note however that it is a theoretical security issue if one pool gains above 50% of the total computational power of the network, thus consider joining a pool based on other metrics.</ref> !! Reward Type !! Transaction fees !! Fee PPS !! Fee Prop / Score !! Audits<ref name="auditing">Auditing can be accomplished by third-parties if the pool publishes proofs-of-work for every share.</ref> !! Protocol !! Launched !! Forum Thread !! Homepage<br />
|-<br />
| [[21bitcoin|21bitcoin]] || CN, HK || 2 || Prop. || kept by pool || - || 0% || ? || RPC (+LP) || 2011-06-20 || [http://forum.bitcoin.org/index.php?topic=20056.0] || [http://21bitcoin.com/pool/ Link]<br />
|-<br />
| [[ArsBitcoin|ArsBitcoin]] || USA || 56 || Prop. || kept by pool || - || 0% || ? || RPC (+LP) || 2011-06-15 || [http://forum.bitcoin.org/index.php?topic=18567.0 Link] || [http://arsbitcoin.com/ Link]<br />
|-<br />
| [[Bitclockers|BitClockers]] || USA, EU || 115 || Prop. || kept by pool || - || 1% || ? || RPC (+LP) || 2011-05-27 || [http://forum.bitcoin.org/index.php?topic=10127.0 Link] || [http://bitclockers.com/ Link]<br />
|-<br />
| [[Bitcoin_Pool|Bitcoin Mining Pool]] || USA || 338 || Prop. || kept by pool || - || 0%<ref name="donations">Donations are possible</ref> || ? || RPC (+LP) || Unknown || [http://bitcoinpool.com/forum/ Link] || [http://www.bitcoinpool.com/ Link]<br />
|-<br />
| [[Bitcoin_Pooled_Mining|Bitcoin Pooled Mining (Slush)]] || London || 1491 || Score || kept by pool || - || 2% || ? || RPC || 2010-11-27 || [http://forum.bitcoin.org/index.php?topic=1976.0 Link] || [http://mining.bitcoin.cz/ Link]<br />
|-<br />
| [[Bitcoins.lc]] || EU || 337 || Prop. || kept by pool || - || 0% || ? || RPC (+LP) || 2011-05-27 || [http://forum.bitcoin.org/index.php?topic=10121.0 Link] || [http://www.bitcoins.lc/ Link]<br />
|-<br />
| [[BitLotto Pool]] || Los Angeles || 1 || Prop || kept by pool || - || - || ? || RPC (+LP) || 2011-06-08 || [http://forum.bitcoin.org/index.php?topic=13794.0 Link] || [http://www.bitlottopool.com/ Link]<br />
|-<br />
| [[BTC Guild]] || USA, EU || 2330 || Prop. || kept by pool || - || 0%<ref name="donationsf">Donations are possible to unlock features</ref>|| ? || RPC || 2011-05-09 || [http://forum.bitcoin.org/index.php?topic=7760.0 Link] || [http://www.btcguild.com/ Link]<br />
|-<br />
| [[BTCMine]] || UK || 480 || Score || kept by pool || - || 2% || ? || RPC (+LP) || 2011-03-11 || [http://forum.bitcoin.org/index.php?topic=4251.0 Link] || [http://www.btcmine.com/ Link]<br />
|-<br />
| [[Continuum]] || Canada || 7 || Score || kept by pool || 5% || - || ? || RPC (+LP) || 2011-05-17 || [http://forum.bitcoin.org/index.php?topic=8660.0 Link] || [http://www.continuumpool.com/ Link]<br />
|-<br />
| [[DeepBit]] || Germany || 2661 || PPS / Prop. || kept by pool || 10% || 3% || ? || RPC (+LP) || 2011-02-26 || [http://forum.bitcoin.org/index.php?topic=3889.0 Link] || [http://deepbit.net/ Link]<br />
|-<br />
| [[Eclipse Mining Consortium]] || USA / Europe / AU / Asia || 25 || Prop / Score || kept by pool || 0% || 0% || ? || RPC (+LP) || 2011-06-14 || [http://forum.bitcoin.org/index.php?topic=16385.0 Link] || [https://eclipsemc.com Link]<br />
|-<br />
| [[Eligius]] || USA / Europe || 353 || SMPPS || kept by pool || ~0.0003%<ref name="donations">Donations are possible</ref> || ~0.0003%<ref name="donations">Donations are possible</ref> || Yes<ref name="auditnote">Access to Eligius proofs-of-work is available on request.</ref> || RPC (+LP) || 2011-04-27 || [http://forum.bitcoin.org/index.php?topic=6667.0 Link] || [http://eligius.st Link]<br />
|-<br />
| [[Mineco.in]] || UK || 50 || Prop || Shared || - || 0% || ? || RPC (+LP) || 2011-06-15 || [http://forum.bitcoin.org/index.php?topic=17310.0 Link] || [https://mineco.in/ Link]<br />
|-<br />
| [[Mining Team Reddit]] || USA, EU || 200 || Prop || kept by pool || - || 0%<ref name="donations">Donations are possible</ref> || ? || RPC (+LP) || 2011-05-25 || [http://forum.bitcoin.org/index.php?topic=15929.0 Link] || [http://www.mtred.com/ Link]<br />
|-<br />
| [[NoFeeMining]] || USA || 24 || Prop || Shared || - || 0% || ? || RPC (+LP) || 2011-06-17 || [http://forum.bitcoin.org/index.php?topic=18301.0 Link] || [http://www.nofeemining.com/ Link]<br />
|-<br />
| [[Ozco.in]] || AUS || 41 || Prop || Kept in Pool || 0% || 1% || ? || RPC (+LP) || 2011-06-08 || [http://forum.bitcoin.org/index.php?topic=14085.0/ Link] || [http://www.ozco.in Link]<br />
|-<br />
| [[Simplecoin]] || Unknown || 0 || Prop|| kept by pool || - || 0% || ? || RPC (+LP) || 2011-06-02 || [http://forum.bitcoin.org/index.php?topic=11186.0 Link] || [http://simplecoin.us/ Link]<br />
|-<br />
| [[Swepool]] || Sweden || 13 || Prop || kept by pool || - || - || ? || RPC (+LP) || 2011-05-14 || [http://forum.bitcoin.org/index.php?topic=8288.0 Link] || [http://swepool.net/ Link]<br />
|-<br />
| [[x8s]] || Germany || 4 || Prop || kept by pool || - || - || ? || RPC (+LP) || 2011-06-08 || [http://forum.bitcoin.org/index.php?topic=13275 Link] || [http://btc.x8s.de/ Link]<br />
|-<br />
| [[ZA Bitcoin]] || South Africa|| 0.4 || Score || kept by pool || 0% || 0% || ? || RPC (+LP) || 2011-06-14 || [http://forum.bitcoin.org/index.php?topic=17830.0 Link] || [http://www.zabitcoin.co.za/ Link]<br />
|-<br />
| [[Btcworld.de]] || Germany || 2 || Prop || kept by pool || - || - || ? || RPC (+LP) || 2011-06-18 || || [http://btcworld.de/ Link]<br />
|}<br />
<br />
<references/><br />
<br />
== See also ==<br />
*[[Pooled mining]]<br />
*[http://bcx.me/ Bitcoin Mining Pool Tracker]<br />
<br />
[[Category:Mining]]</div>Cosurgihttps://tests.bitcoin.it/w/index.php?title=Comparison_of_mining_pools&diff=10223Comparison of mining pools2011-06-09T22:19:16Z<p>Cosurgi: </p>
<hr />
<div>Reward types & explanation:<br />
* '''PPS''' - Pay Per Share. Each submitted share is worth certain amount of BTC. Since finding a block requires <current difficulty> shares ''on average'', a PPS method with 0% fee would be 50 BTC divided by <current difficulty>. It is risky for pool operators, hence the fee is highest.<br />
* '''Prop.''' - Proportional. When block is found, the reward is distributed among all workers proportionally to how much shares each of them has found. This method is vulnerable to ''pool swapping'' cheat, where a worker would swap to another pool, if this one didn't find a block quickly. Then he would have extra profit on fast rounds, and normal profit on long rounds (because he would be mining on another pool by then). To mitigate this problem pools must introduce extra fees, and hide statistics, so that it is unknown when a block is found.<br />
* '''Score''' - Score based system, the most advanced one. It is a proportional reward, but it is impossible to cheat as described above. Each submitted share is worth more in the function of time ''t'' since start of current round. For each share score is updated by: score += exp(t/C). This makes later shares worth more than earlier shares, thus swapping away to another pool on longer rounds makes the cheater's score to quickly diminish. Rewards are calculated proportionally to scores (and not to shares). Statistics can be shown "live" without fear. The score based method is perfect for 24/7 miners. (at slush's pool C=300 seconds, and every hour scores are normalized)<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Name !! Location !! Hashrate (GHash/sec)<ref name="hashrate">Hashrate is given in gigahash/second.</ref><ref name="hashrate2">Note that pool hashrate is largely irrelevant but can be seen as a popularity measurement. Note however that it is a theoretical security issue if one pool gains above 50% of the total computational power of the network, thus consider joining a pool based on other metrics.</ref> !! Reward Type !! Transaction fees !! Fee PPS !! Fee Prop / Score !! Audits<ref name="auditing">Auditing can be accomplished by third-parties if the pool publishes proofs-of-work for every share.</ref> !! Protocol !! Launched !! Forum Thread !! Homepage<br />
|-<br />
| [[Bitclockers|BitClockers]] || Unknown || 18 || Prop. || kept by pool || - || 2% || ? || RPC (+LP) || 2011-05-27 || [http://forum.bitcoin.org/index.php?topic=10127.0 Link] || [http://bitclockers.com/ Link]<br />
|-<br />
| [[Bitcoin_Pool|Bitcoin Mining Pool]] || USA || 93 || Prop. || kept by pool || - || 0%<ref name="donations">Donations are possible</ref> || ? || RPC (+LP) || Unknown || [http://bitcoinpool.com/forum/ Link] || [http://www.bitcoinpool.com/ Link]<br />
|-<br />
| [[Bitcoin_Pooled_Mining|Bitcoin Pooled Mining (Slush)]] || London || 1431 || Score || kept by pool || - || 2% || ? || RPC || 2010-11-27 || [http://forum.bitcoin.org/index.php?topic=1976.0 Link] || [http://mining.bitcoin.cz/ Link]<br />
|-<br />
| [[Bitcoins.lc]] || EU || 84 || Prop. || kept by pool || - || 0% || ? || RPC (+LP) || 2011-05-27 || [http://forum.bitcoin.org/index.php?topic=10121.0 Link] || [http://www.bitcoins.lc/ Link]<br />
|-<br />
| [[BitLotto Pool]] || Los Angeles || 1 || Prop || kept by pool || - || - || ? || RPC (+LP) || 2011-06-08 || [http://forum.bitcoin.org/index.php?topic=13794.0 Link] || [http://www.bitlottopool.com/ Link]<br />
|-<br />
| [[BTC Guild]] || USA, EU || 939 || Prop. || kept by pool || - || 0%<ref name="donationsf">Donations are possible to unlock features</ref>|| ? || RPC (+LP) || 2011-05-09 || [http://forum.bitcoin.org/index.php?topic=7760.0 Link] || [http://www.btcguild.com/ Link]<br />
|-<br />
| [[BTCMine]] || UK || 388 || Score || kept by pool || - || 2% || ? || RPC (+LP) || 2011-03-11 || [http://forum.bitcoin.org/index.php?topic=4251.0 Link] || [http://www.btcmine.com/ Link]<br />
|-<br />
| [[Continuum]] || Canada || 8 || PPS / Score || kept by pool || 5% || 0% || ? || RPC (+LP) || 2011-05-17 || [http://forum.bitcoin.org/index.php?topic=8660.0 Link] || [http://www.continuumpool.com/ Link]<br />
|-<br />
| [[DeepBit]] || Germany || 2369 || PPS / Prop. || kept by pool || 10% || 3% || ? || RPC (+LP) || 2011-02-26 || [http://forum.bitcoin.org/index.php?topic=3889.0 Link] || [http://deepbit.net/ Link]<br />
|-<br />
| [[Eligius]] || USA / Europe || 200 || Prop. || kept by pool || - || ~0.0003% || Yes<ref name="auditnote">Access to Eligius proofs-of-work is available on request.</ref> || RPC (+LP) || 2011-04-27 || [http://forum.bitcoin.org/index.php?topic=6667.0 Link] || [http://eligius.st Link]<br />
|-<br />
| [[Mining Team Reddit]] || USA, EU || 28 || Prop || kept by pool || - || 0%<ref name="donations">Donations are possible</ref> || ? || RPC (+LP) || 2011-05-25 || [http://forum.bitcoin.org/index.php?topic=9911.0 Link] || [http://www.mtred.com/ Link]<br />
|-<br />
| [[Ozco.in]] || AUS || 28 || || || - || || ? || RPC (+LP) || 2011-06-08 || || [http://www.ozco.in Link]<br />
|-<br />
| [[Simplecoin]] || Unknown || 19 || Prop|| kept by pool || - || 0% || ? || RPC (+LP) || 2011-06-02 || [http://forum.bitcoin.org/index.php?topic=11186.0 Link] || [http://simplecoin.us/ Link]<br />
|-<br />
| [[Swepool]] || Sweden || 48 || PPS || kept by pool || 8% || - || ? || RPC (+LP) || 2011-05-14 || [http://forum.bitcoin.org/index.php?topic=8288.0 Link] || [http://swepool.net/ Link]<br />
<br />
|}<br />
<br />
<references/><br />
<br />
== See also ==<br />
*[[Pooled mining]]<br />
*[http://bcx.me/ Bitcoin Mining Pool Tracker]<br />
<br />
[[Category:Mining]]</div>Cosurgihttps://tests.bitcoin.it/w/index.php?title=Comparison_of_mining_pools&diff=10222Comparison of mining pools2011-06-09T22:16:25Z<p>Cosurgi: </p>
<hr />
<div>Reward types & explanation:<br />
* '''PPS''' - Pay Per Share. Each submitted share is worth certain amount of BTC. Since finding a block requires <current difficulty> shares ''on average'', a PPS method with 0% fee would be 50 BTC divided by <current difficulty>. It is risky for pool operators, hence the fee is highest.<br />
* '''Prop.''' - Proportional. When block is found, the reward is distributed among all workers proportionally to how much shares each of them has found. This method is vulnerable to ''pool swapping'' cheat, where a worker would swap to another pool, if this one didn't find a block quickly. Then he would have extra profit on fast rounds, and normal profit on long rounds (because he would be mining on another pool by then). To mitigate this problem pools must introduce extra fees, and hide statistics, so that it is unknown when a block is found.<br />
* '''Score''' - Score based system, the most advanced one. It is a proportional reward, but it is impossible to cheat as described above. Each submitted share is worth more in the function of time ''t'' since start of current round. For each share score is updated by: score += exp(t/C). This makes later shares worth more than earlier shares, thus swapping away to another pool on longer rounds makes the cheater's score to quickly diminish. Rewards are calculated proportionally to scores (and not to shares). Statistics can be shown "live" without fear. The score based method is perfect for 24/7 miners.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Name !! Location !! Hashrate (GHash/sec)<ref name="hashrate">Hashrate is given in gigahash/second.</ref><ref name="hashrate2">Note that pool hashrate is largely irrelevant but can be seen as a popularity measurement. Note however that it is a theoretical security issue if one pool gains above 50% of the total computational power of the network, thus consider joining a pool based on other metrics.</ref> !! Reward Type !! Transaction fees !! Fee PPS !! Fee Prop / Score !! Audits<ref name="auditing">Auditing can be accomplished by third-parties if the pool publishes proofs-of-work for every share.</ref> !! Protocol !! Launched !! Forum Thread !! Homepage<br />
|-<br />
| [[Bitclockers|BitClockers]] || Unknown || 18 || Prop. || kept by pool || - || 2% || ? || RPC (+LP) || 2011-05-27 || [http://forum.bitcoin.org/index.php?topic=10127.0 Link] || [http://bitclockers.com/ Link]<br />
|-<br />
| [[Bitcoin_Pool|Bitcoin Mining Pool]] || USA || 93 || Prop. || kept by pool || - || 0%<ref name="donations">Donations are possible</ref> || ? || RPC (+LP) || Unknown || [http://bitcoinpool.com/forum/ Link] || [http://www.bitcoinpool.com/ Link]<br />
|-<br />
| [[Bitcoin_Pooled_Mining|Bitcoin Pooled Mining (Slush)]] || London || 1431 || Score || kept by pool || - || 2% || ? || RPC || 2010-11-27 || [http://forum.bitcoin.org/index.php?topic=1976.0 Link] || [http://mining.bitcoin.cz/ Link]<br />
|-<br />
| [[Bitcoins.lc]] || EU || 84 || Prop. || kept by pool || - || 0% || ? || RPC (+LP) || 2011-05-27 || [http://forum.bitcoin.org/index.php?topic=10121.0 Link] || [http://www.bitcoins.lc/ Link]<br />
|-<br />
| [[BitLotto Pool]] || Los Angeles || 1 || Prop || kept by pool || - || - || ? || RPC (+LP) || 2011-06-08 || [http://forum.bitcoin.org/index.php?topic=13794.0 Link] || [http://www.bitlottopool.com/ Link]<br />
|-<br />
| [[BTC Guild]] || USA, EU || 939 || Prop. || kept by pool || - || 0%<ref name="donationsf">Donations are possible to unlock features</ref>|| ? || RPC (+LP) || 2011-05-09 || [http://forum.bitcoin.org/index.php?topic=7760.0 Link] || [http://www.btcguild.com/ Link]<br />
|-<br />
| [[BTCMine]] || UK || 388 || Score || kept by pool || - || 2% || ? || RPC (+LP) || 2011-03-11 || [http://forum.bitcoin.org/index.php?topic=4251.0 Link] || [http://www.btcmine.com/ Link]<br />
|-<br />
| [[Continuum]] || Canada || 8 || PPS / Score || kept by pool || 5% || 0% || ? || RPC (+LP) || 2011-05-17 || [http://forum.bitcoin.org/index.php?topic=8660.0 Link] || [http://www.continuumpool.com/ Link]<br />
|-<br />
| [[DeepBit]] || Germany || 2369 || PPS / Prop. || kept by pool || 10% || 3% || ? || RPC (+LP) || 2011-02-26 || [http://forum.bitcoin.org/index.php?topic=3889.0 Link] || [http://deepbit.net/ Link]<br />
|-<br />
| [[Eligius]] || USA / Europe || 200 || Prop. || kept by pool || - || ~0.0003% || Yes<ref name="auditnote">Access to Eligius proofs-of-work is available on request.</ref> || RPC (+LP) || 2011-04-27 || [http://forum.bitcoin.org/index.php?topic=6667.0 Link] || [http://eligius.st Link]<br />
|-<br />
| [[Mining Team Reddit]] || USA, EU || 28 || Prop || kept by pool || - || 0%<ref name="donations">Donations are possible</ref> || ? || RPC (+LP) || 2011-05-25 || [http://forum.bitcoin.org/index.php?topic=9911.0 Link] || [http://www.mtred.com/ Link]<br />
|-<br />
| [[Ozco.in]] || AUS || 28 || || || - || || ? || RPC (+LP) || 2011-06-08 || || [http://www.ozco.in Link]<br />
|-<br />
| [[Simplecoin]] || Unknown || 19 || Prop|| kept by pool || - || 0% || ? || RPC (+LP) || 2011-06-02 || [http://forum.bitcoin.org/index.php?topic=11186.0 Link] || [http://simplecoin.us/ Link]<br />
|-<br />
| [[Swepool]] || Sweden || 48 || PPS || kept by pool || 8% || - || ? || RPC (+LP) || 2011-05-14 || [http://forum.bitcoin.org/index.php?topic=8288.0 Link] || [http://swepool.net/ Link]<br />
<br />
|}<br />
<br />
<references/><br />
<br />
== See also ==<br />
*[[Pooled mining]]<br />
*[http://bcx.me/ Bitcoin Mining Pool Tracker]<br />
<br />
[[Category:Mining]]</div>Cosurgihttps://tests.bitcoin.it/w/index.php?title=Comparison_of_mining_pools&diff=10221Comparison of mining pools2011-06-09T22:15:09Z<p>Cosurgi: </p>
<hr />
<div>* '''PPS''' - Pay Per Share. Each submitted share is worth certain amount of BTC. Since finding a block requires <current difficulty> shares ''on average'', a PPS method with 0% fee would be 50 BTC divided by <current difficulty>. It is risky for pool operators, hence the fee is highest.<br />
* '''Prop.''' - Proportional. When block is found, the reward is distributed among all workers proportionally to how much shares each of them has found. This method is vulnerable to ''pool swapping'' cheat, where a worker would swap to another pool, if this one didn't find a block quickly. Then he would have extra profit on fast rounds, and normal profit on long rounds (because he would be mining on another pool by then). To mitigate this problem pools must introduce extra fees, and hide statistics, so that it is unknown when a block is found.<br />
* '''Score''' - Score based system, the most advanced one. It is a proportional reward, but it is impossible to cheat as described above. Each submitted share is worth more in the function of time ''t'' since start of current round. For each share score is updated by: score += exp(t/C). This makes later shares worth more than earlier shares, thus swapping away to another pool on longer rounds makes the cheater's score to quickly diminish. Rewards are calculated proportionally to scores (and not to shares). Statistics can be shown "live" without fear. The score based method is perfect for 24/7 miners.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Name !! Location !! Hashrate (GHash/sec)<ref name="hashrate">Hashrate is given in gigahash/second.</ref><ref name="hashrate2">Note that pool hashrate is largely irrelevant but can be seen as a popularity measurement. Note however that it is a theoretical security issue if one pool gains above 50% of the total computational power of the network, thus consider joining a pool based on other metrics.</ref> !! Reward Type !! Transaction fees !! Fee PPS !! Fee Prop / Score !! Audits<ref name="auditing">Auditing can be accomplished by third-parties if the pool publishes proofs-of-work for every share.</ref> !! Protocol !! Launched !! Forum Thread !! Homepage<br />
|-<br />
| [[Bitclockers|BitClockers]] || Unknown || 18 || Prop. || kept by pool || - || 2% || ? || RPC (+LP) || 2011-05-27 || [http://forum.bitcoin.org/index.php?topic=10127.0 Link] || [http://bitclockers.com/ Link]<br />
|-<br />
| [[Bitcoin_Pool|Bitcoin Mining Pool]] || USA || 93 || Prop. || kept by pool || - || 0%<ref name="donations">Donations are possible</ref> || ? || RPC (+LP) || Unknown || [http://bitcoinpool.com/forum/ Link] || [http://www.bitcoinpool.com/ Link]<br />
|-<br />
| [[Bitcoin_Pooled_Mining|Bitcoin Pooled Mining (Slush)]] || London || 1431 || Score || kept by pool || - || 2% || ? || RPC || 2010-11-27 || [http://forum.bitcoin.org/index.php?topic=1976.0 Link] || [http://mining.bitcoin.cz/ Link]<br />
|-<br />
| [[Bitcoins.lc]] || EU || 84 || Prop. || kept by pool || - || 0% || ? || RPC (+LP) || 2011-05-27 || [http://forum.bitcoin.org/index.php?topic=10121.0 Link] || [http://www.bitcoins.lc/ Link]<br />
|-<br />
| [[BitLotto Pool]] || Los Angeles || 1 || Prop || kept by pool || - || - || ? || RPC (+LP) || 2011-06-08 || [http://forum.bitcoin.org/index.php?topic=13794.0 Link] || [http://www.bitlottopool.com/ Link]<br />
|-<br />
| [[BTC Guild]] || USA, EU || 939 || Prop. || kept by pool || - || 0%<ref name="donationsf">Donations are possible to unlock features</ref>|| ? || RPC (+LP) || 2011-05-09 || [http://forum.bitcoin.org/index.php?topic=7760.0 Link] || [http://www.btcguild.com/ Link]<br />
|-<br />
| [[BTCMine]] || UK || 388 || Score || kept by pool || - || 2% || ? || RPC (+LP) || 2011-03-11 || [http://forum.bitcoin.org/index.php?topic=4251.0 Link] || [http://www.btcmine.com/ Link]<br />
|-<br />
| [[Continuum]] || Canada || 8 || PPS / Score || kept by pool || 5% || 0% || ? || RPC (+LP) || 2011-05-17 || [http://forum.bitcoin.org/index.php?topic=8660.0 Link] || [http://www.continuumpool.com/ Link]<br />
|-<br />
| [[DeepBit]] || Germany || 2369 || PPS / Prop. || kept by pool || 10% || 3% || ? || RPC (+LP) || 2011-02-26 || [http://forum.bitcoin.org/index.php?topic=3889.0 Link] || [http://deepbit.net/ Link]<br />
|-<br />
| [[Eligius]] || USA / Europe || 200 || Prop. || kept by pool || - || ~0.0003% || Yes<ref name="auditnote">Access to Eligius proofs-of-work is available on request.</ref> || RPC (+LP) || 2011-04-27 || [http://forum.bitcoin.org/index.php?topic=6667.0 Link] || [http://eligius.st Link]<br />
|-<br />
| [[Mining Team Reddit]] || USA, EU || 28 || Prop || kept by pool || - || 0%<ref name="donations">Donations are possible</ref> || ? || RPC (+LP) || 2011-05-25 || [http://forum.bitcoin.org/index.php?topic=9911.0 Link] || [http://www.mtred.com/ Link]<br />
|-<br />
| [[Ozco.in]] || AUS || 28 || || || - || || ? || RPC (+LP) || 2011-06-08 || || [http://www.ozco.in Link]<br />
|-<br />
| [[Simplecoin]] || Unknown || 19 || Prop|| kept by pool || - || 0% || ? || RPC (+LP) || 2011-06-02 || [http://forum.bitcoin.org/index.php?topic=11186.0 Link] || [http://simplecoin.us/ Link]<br />
|-<br />
| [[Swepool]] || Sweden || 48 || PPS || kept by pool || 8% || - || ? || RPC (+LP) || 2011-05-14 || [http://forum.bitcoin.org/index.php?topic=8288.0 Link] || [http://swepool.net/ Link]<br />
<br />
|}<br />
<br />
<references/><br />
<br />
== See also ==<br />
*[[Pooled mining]]<br />
*[http://bcx.me/ Bitcoin Mining Pool Tracker]<br />
<br />
[[Category:Mining]]</div>Cosurgihttps://tests.bitcoin.it/w/index.php?title=Comparison_of_mining_pools&diff=10220Comparison of mining pools2011-06-09T21:52:14Z<p>Cosurgi: </p>
<hr />
<div>{| class="wikitable sortable"<br />
|-<br />
! Name !! Location !! Hashrate (GHash/sec)<ref name="hashrate">Hashrate is given in gigahash/second.</ref><ref name="hashrate2">Note that pool hashrate is largely irrelevant but can be seen as a popularity measurement. Note however that it is a theoretical security issue if one pool gains above 50% of the total computational power of the network, thus consider joining a pool based on other metrics.</ref> !! Reward Type !! Transaction fees !! Fee PPS !! Fee Prop / Score !! Audits<ref name="auditing">Auditing can be accomplished by third-parties if the pool publishes proofs-of-work for every share.</ref> !! Protocol !! Launched !! Forum Thread !! Homepage<br />
|-<br />
| [[Bitclockers|BitClockers]] || Unknown || 18 || Prop. || kept by pool || - || 2% || ? || RPC (+LP) || 2011-05-27 || [http://forum.bitcoin.org/index.php?topic=10127.0 Link] || [http://bitclockers.com/ Link]<br />
|-<br />
| [[Bitcoin_Pool|Bitcoin Mining Pool]] || USA || 93 || Prop. || kept by pool || - || 0%<ref name="donations">Donations are possible</ref> || ? || RPC (+LP) || Unknown || [http://bitcoinpool.com/forum/ Link] || [http://www.bitcoinpool.com/ Link]<br />
|-<br />
| [[Bitcoin_Pooled_Mining|Bitcoin Pooled Mining (Slush)]] || London || 1431 || Score || kept by pool || - || 2% || ? || RPC || 2010-11-27 || [http://forum.bitcoin.org/index.php?topic=1976.0 Link] || [http://mining.bitcoin.cz/ Link]<br />
|-<br />
| [[Bitcoins.lc]] || EU || 84 || Prop. || kept by pool || - || 0% || ? || RPC (+LP) || 2011-05-27 || [http://forum.bitcoin.org/index.php?topic=10121.0 Link] || [http://www.bitcoins.lc/ Link]<br />
|-<br />
| [[BitLotto Pool]] || Los Angeles || 1 || Prop || kept by pool || - || - || ? || RPC (+LP) || 2011-06-08 || [http://forum.bitcoin.org/index.php?topic=13794.0 Link] || [http://www.bitlottopool.com/ Link]<br />
|-<br />
| [[BTC Guild]] || USA, EU || 939 || Prop. || kept by pool || - || 0%<ref name="donationsf">Donations are possible to unlock features</ref>|| ? || RPC (+LP) || 2011-05-09 || [http://forum.bitcoin.org/index.php?topic=7760.0 Link] || [http://www.btcguild.com/ Link]<br />
|-<br />
| [[BTCMine]] || UK || 388 || Score || kept by pool || - || 2% || ? || RPC (+LP) || 2011-03-11 || [http://forum.bitcoin.org/index.php?topic=4251.0 Link] || [http://www.btcmine.com/ Link]<br />
|-<br />
| [[Continuum]] || Canada || 8 || PPS / Score || kept by pool || 5% || 0% || ? || RPC (+LP) || 2011-05-17 || [http://forum.bitcoin.org/index.php?topic=8660.0 Link] || [http://www.continuumpool.com/ Link]<br />
|-<br />
| [[DeepBit]] || Germany || 2369 || PPS / Prop. || kept by pool || 10% || 3% || ? || RPC (+LP) || 2011-02-26 || [http://forum.bitcoin.org/index.php?topic=3889.0 Link] || [http://deepbit.net/ Link]<br />
|-<br />
| [[Eligius]] || USA / Europe || 200 || Prop. || kept by pool || - || ~0.0003% || Yes<ref name="auditnote">Access to Eligius proofs-of-work is available on request.</ref> || RPC (+LP) || 2011-04-27 || [http://forum.bitcoin.org/index.php?topic=6667.0 Link] || [http://eligius.st Link]<br />
|-<br />
| [[Mining Team Reddit]] || USA, EU || 28 || Prop || kept by pool || - || 0%<ref name="donations">Donations are possible</ref> || ? || RPC (+LP) || 2011-05-25 || [http://forum.bitcoin.org/index.php?topic=9911.0 Link] || [http://www.mtred.com/ Link]<br />
|-<br />
| [[Ozco.in]] || AUS || 28 || || || - || || ? || RPC (+LP) || 2011-06-08 || || [http://www.ozco.in Link]<br />
|-<br />
| [[Simplecoin]] || Unknown || 19 || Prop|| kept by pool || - || 0% || ? || RPC (+LP) || 2011-06-02 || [http://forum.bitcoin.org/index.php?topic=11186.0 Link] || [http://simplecoin.us/ Link]<br />
|-<br />
| [[Swepool]] || Sweden || 48 || PPS || kept by pool || 8% || - || ? || RPC (+LP) || 2011-05-14 || [http://forum.bitcoin.org/index.php?topic=8288.0 Link] || [http://swepool.net/ Link]<br />
<br />
|}<br />
<br />
<references/><br />
<br />
== See also ==<br />
*[[Pooled mining]]<br />
*[http://bcx.me/ Bitcoin Mining Pool Tracker]<br />
<br />
[[Category:Mining]]</div>Cosurgihttps://tests.bitcoin.it/w/index.php?title=OpenCL_miner&diff=8020OpenCL miner2011-05-04T22:14:31Z<p>Cosurgi: </p>
<hr />
<div>{{stub}}<br />
An '''OpenCL miner''' is a bitcoin miner that uses the [http://en.wikipedia.org/wiki/OpenCL OpenCL framework] to perform the [[hash|hashing]] computations. When used with a modern GPU, this can produce hash rates orders of magnitude higher than what can be achieved with a CPU. Hashing on a GPU requires an OpenCL compatible ([http://developer.amd.com/gpu/AMDAPPSDK/pages/DriverCompatibility.aspx ATI/AMD]) or CUDA compatible ([http://www.nvidia.com/object/cuda_gpus.html NVIDIA]) graphics card.<br />
<br />
The python [[Poclbm]] open source OpenCL bitcoin miner was created by m0mchil<ref>[http://www.bitcoin.org/smf/index.php?topic=1334.0 m0mchil's announcement on the forum]</ref> based on the open source CUDA client originally released by puddinpop<ref>[http://www.bitcoin.org/smf/index.php?topic=133.msg13135#msg13135 puddinpop's open source CUDA miner]</ref>. Subsequently the java [[DiabloMiner]] based on m0mchil's was created by Diablo-D3<ref>[http://www.bitcoin.org/smf/index.php?topic=1721.0 Diablo's announcement on the forum]</ref>. Puddinpop has also released a C++ OpenCL client capable of being compiled into the GUI client or daemon, or as a stand alone RPC miner<ref>[http://www.bitcoin.org/smf/index.php?topic=2444.0 puddinpop's RPC miners]</ref>. Another miner was released by Jedi95 & CFSworks released phoenix miner<ref>[http://www.bitcoin.org/smf/index.php?topic=6458.0 Jedi95 & CFSworks phoenix miner]</ref> which can work with memory underclocked to 300MHz and scans whole 2<sup>32</sup> nonce space.<br />
<br />
See the [[Mining Hardware Comparison]] page for detailed statistics on the hash rates that can be achieved with various hardware.<br />
<br />
==See Also==<br />
<br />
* [[:Category:Miners|Miners]]<br />
* [http://www.bitcoin.org/smf/index.php?topic=4308.msg62882#msg62882 ATI Stream SDK] downloads<br />
* [http://www.pcper.com/article.php?aid=745 ATI Stream vs. NVIDIA CUDA - GPGPU computing battle royale]<br />
* [http://www.overclock.net/graphics-cards-general/363095-processing-cores-vs-stream-processing-units.html Processing Cores vs. Stream Processing Units]<br />
<br />
==References==<br />
<references/><br />
<br />
[[Category:Mining]]</div>Cosurgi