Bitcoin Wiki - User contributions [en]

List of address prefixes

2012-04-28T18:36:05Z

Graingert:

Blockchain-based currencies use addresses, which are a [[Base58Check encoding]] of some hash, typically that of a public key. The encoding includes a version byte, which affects the first character in the address. The following is a list of some prefixes which are in use.

{| class="wikitable"
|-
!Decimal version
!Leading symbol
!Use
!Example
|-
|0
|1
|Bitcoin pubkey hash
|<tt>12CPLrAUPvhVwjZqBgww3sLdEg4Z888R1j</tt>
|-
|5
|3
|Bitcoin script hash
|
|-
|48
|L
|Litecoin pubkey hash
|<tt>LhK2kQwiaAvhjWY799cZvMyYwnQAcxkarr</tt>
|-
|52
|M or N
|Namecoin pubkey hash
|<tt>NATX6zEUNfxfvgVwz8qVnnw3hLhhYXhgQn</tt>
|-
|95
|f
|Fairbrix pubkey hash
|<tt>fF6o8LeDAfswEpMbCW8BqaqmzMWS7TGgew</tt>
|-
|97
|g
|GeistGeld pubkey hash
|<tt>gQ8YScyiMUTart6kUJpzhjPzAKfiYAwooc</tt>
|-
|105
|j
|i0coin pubkey hash
|<tt>jWmCr5cKeQjV4iyfUyipfLGwVML8MvXhF2</tt>
|-
|111
|m or n
|Bitcoin testnet pubkey hash
|<tt>mkJ7Bf5chdfw61d1m7gnDVAQV3EQQAb8iz</tt>
|-
|125
|s
|Solidcoin pubkey hash
|<tt>sXNaMoYBocjcQJRLK53dkaQ5mWuKfvHB9f</tt>
|-
|127
|t
|Tenebrix pubkey hash
|<tt>tUK2EQTMF6cN6vuNEfJtVf1BMqarvEZJBL</tt>
|-
|128
|5
|Bitcoin Private key
|<tt>5Htn3FzuH3b1X5VF2zLTsAQzBcyzkZNJsa2egXN8ZFJTCqQm3Rq</tt>
|-
|138
|x
|ixcoin pubkey hash
|<tt>xoKDFH4uWpyzxUcCC5jCLFujRKayv3HHcV</tt>
|-
|196
|2
|Testnet script hash
|
|-
|239
|2
|Testnet Private key
|
|}

The following table shows the leading symbol(s) and address length(s) for 160 bit hashes for each of the possible decimal version values:

{| class="wikitable"
|-
!Decimal version
!Leading symbol
!Address length
|-
|0
|1
|up to 34
|-
|1
|Q-Z, a-k, m-o
|33
|-
|2
|o-z, 2
|33 or 34
|-
|3
|2
|34
|-
|4
|2 or 3
|34
|-
|5-6
|3
|34
|-
|7
|3 or 4
|34
|-
|8
|4
|34
|-
|9
|4 or 5
|34
|-
|10-11
|5
|34
|-
|12
|5 or 6
|34
|-
|13
|6
|34
|-
|14
|6 or 7
|34
|-
|15-16
|7
|34
|-
|17
|7 or 8
|34
|-
|18
|8
|34
|-
|19
|8 or 9
|34
|-
|20-21
|9
|34
|-
|22
|9 or A
|34
|-
|23
|A
|34
|-
|24
|A or B
|34
|-
|25-26
|B
|34
|-
|27
|B or C
|34
|-
|28
|C
|34
|-
|29
|C or D
|34
|-
|30-31
|D
|34
|-
|32
|D or E
|34
|-
|33
|E
|34
|-
|34
|E or F
|34
|-
|35-36
|F
|34
|-
|37
|F or G
|34
|-
|38
|G
|34
|-
|39
|G or H
|34
|-
|40-41
|H
|34
|-
|42
|H or J
|34
|-
|43
|J
|34
|-
|44
|J or K
|34
|-
|45-46
|K
|34
|-
|47
|K or L
|34
|-
|48
|L
|34
|-
|49
|L or M
|34
|-
|50-51
|M
|34
|-
|52
|M or N
|34
|-
|53
|N
|34
|-
|54
|N or P
|34
|-
|55-56
|P
|34
|-
|57
|P or Q
|34
|-
|58
|Q
|34
|-
|59
|Q or R
|34
|-
|60-61
|R
|34
|-
|62
|R or S
|34
|-
|63
|S
|34
|-
|64
|S or T
|34
|-
|65-66
|T
|34
|-
|67
|T or U
|34
|-
|68
|U
|34
|-
|69
|U or V
|34
|-
|70-71
|V
|34
|-
|72
|V or W
|34
|-
|73
|W
|34
|-
|74
|W or X
|34
|-
|75-76
|X
|34
|-
|77
|X or Y
|34
|-
|78
|Y
|34
|-
|79
|Y or Z
|34
|-
|80-81
|Z
|34
|-
|82
|Z or a
|34
|-
|83
|a
|34
|-
|84
|a or b
|34
|-
|85
|b
|34
|-
|86
|b or c
|34
|-
|87-88
|c
|34
|-
|89
|c or d
|34
|-
|90
|d
|34
|-
|91
|d or e
|34
|-
|92-93
|e
|34
|-
|94
|e or f
|34
|-
|95
|f
|34
|-
|96
|f or g
|34
|-
|97-98
|g
|34
|-
|99
|g or h
|34
|-
|100
|h
|34
|-
|101
|h or i
|34
|-
|102-103
|i
|34
|-
|104
|i or j
|34
|-
|105
|j
|34
|-
|106
|j or k
|34
|-
|107-108
|k
|34
|-
|109
|k or m
|34
|-
|110
|m
|34
|-
|111
|m or n
|34
|-
|112-113
|n
|34
|-
|114
|n or o
|34
|-
|115
|o
|34
|-
|116
|o or p
|34
|-
|117-118
|p
|34
|-
|119
|p or q
|34
|-
|120
|q
|34
|-
|121
|q or r
|34
|-
|122-123
|r
|34
|-
|124
|r or s
|34
|-
|125
|s
|34
|-
|126
|s or t
|34
|-
|127-128
|t
|34
|-
|129
|t or u
|34
|-
|130
|u
|34
|-
|131
|u or v
|34
|-
|132-133
|v
|34
|-
|134
|v or w
|34
|-
|135
|w
|34
|-
|136
|w or x
|34
|-
|137-138
|x
|34
|-
|139
|x or y
|34
|-
|140
|y
|34
|-
|141
|y or z
|34
|-
|142-143
|z
|34
|-
|144
|z or 2
|34 or 35
|-
|145-255
|2
|35
|}

List of address prefixes

2012-04-28T18:34:41Z

Graingert:

Blockchain-based currencies use addresses, which are a [[Base58Check encoding]] of some hash, typically that of a public key. The encoding includes a version byte, which affects the first character in the address. The following is a list of some prefixes which are in use.

{| class="wikitable"
|-
!Decimal version
!Leading symbol
!Use
!Example
|-
|0
|1
|Bitcoin pubkey hash
|<tt>12CPLrAUPvhVwjZqBgww3sLdEg4Z888R1j</tt>
|-
|5
|3
|Bitcoin script hash
|
|-
|48
|L
|Litecoin pubkey hash
|<tt>LhK2kQwiaAvhjWY799cZvMyYwnQAcxkarr</tt>
|-
|52
|M or N
|Namecoin pubkey hash
|<tt>NATX6zEUNfxfvgVwz8qVnnw3hLhhYXhgQn</tt>
|-
|95
|f
|Fairbrix pubkey hash
|<tt>fF6o8LeDAfswEpMbCW8BqaqmzMWS7TGgew</tt>
|-
|97
|g
|GeistGeld pubkey hash
|<tt>gQ8YScyiMUTart6kUJpzhjPzAKfiYAwooc</tt>
|-
|105
|j
|i0coin pubkey hash
|<tt>jWmCr5cKeQjV4iyfUyipfLGwVML8MvXhF2</tt>
|-
|111
|m or n
|Bitcoin testnet pubkey hash
|<tt>mkJ7Bf5chdfw61d1m7gnDVAQV3EQQAb8iz</tt>
|-
|125
|s
|Solidcoin pubkey hash
|<tt>sXNaMoYBocjcQJRLK53dkaQ5mWuKfvHB9f</tt>
|-
|127
|t
|Tenebrix pubkey hash
|<tt>tUK2EQTMF6cN6vuNEfJtVf1BMqarvEZJBL</tt>
|-
|128
|5
|Bitcoin Private key
|<tt>5Htn3FzuH3b1X5VF2zLTsAQzBcyzkZNJsa2egXN8ZFJTCqQm3Rq</tt>
|-
|138
|x
|ixcoin pubkey hash
|<tt>xoKDFH4uWpyzxUcCC5jCLFujRKayv3HHcV</tt>
|-
|196
|2
|Bitcoin testnet script hash
|
|-
|239
|2
|Testnet Private key
|
|}

The following table shows the leading symbol(s) and address length(s) for 160 bit hashes for each of the possible decimal version values:

{| class="wikitable"
|-
!Decimal version
!Leading symbol
!Address length
|-
|0
|1
|up to 34
|-
|1
|Q-Z, a-k, m-o
|33
|-
|2
|o-z, 2
|33 or 34
|-
|3
|2
|34
|-
|4
|2 or 3
|34
|-
|5-6
|3
|34
|-
|7
|3 or 4
|34
|-
|8
|4
|34
|-
|9
|4 or 5
|34
|-
|10-11
|5
|34
|-
|12
|5 or 6
|34
|-
|13
|6
|34
|-
|14
|6 or 7
|34
|-
|15-16
|7
|34
|-
|17
|7 or 8
|34
|-
|18
|8
|34
|-
|19
|8 or 9
|34
|-
|20-21
|9
|34
|-
|22
|9 or A
|34
|-
|23
|A
|34
|-
|24
|A or B
|34
|-
|25-26
|B
|34
|-
|27
|B or C
|34
|-
|28
|C
|34
|-
|29
|C or D
|34
|-
|30-31
|D
|34
|-
|32
|D or E
|34
|-
|33
|E
|34
|-
|34
|E or F
|34
|-
|35-36
|F
|34
|-
|37
|F or G
|34
|-
|38
|G
|34
|-
|39
|G or H
|34
|-
|40-41
|H
|34
|-
|42
|H or J
|34
|-
|43
|J
|34
|-
|44
|J or K
|34
|-
|45-46
|K
|34
|-
|47
|K or L
|34
|-
|48
|L
|34
|-
|49
|L or M
|34
|-
|50-51
|M
|34
|-
|52
|M or N
|34
|-
|53
|N
|34
|-
|54
|N or P
|34
|-
|55-56
|P
|34
|-
|57
|P or Q
|34
|-
|58
|Q
|34
|-
|59
|Q or R
|34
|-
|60-61
|R
|34
|-
|62
|R or S
|34
|-
|63
|S
|34
|-
|64
|S or T
|34
|-
|65-66
|T
|34
|-
|67
|T or U
|34
|-
|68
|U
|34
|-
|69
|U or V
|34
|-
|70-71
|V
|34
|-
|72
|V or W
|34
|-
|73
|W
|34
|-
|74
|W or X
|34
|-
|75-76
|X
|34
|-
|77
|X or Y
|34
|-
|78
|Y
|34
|-
|79
|Y or Z
|34
|-
|80-81
|Z
|34
|-
|82
|Z or a
|34
|-
|83
|a
|34
|-
|84
|a or b
|34
|-
|85
|b
|34
|-
|86
|b or c
|34
|-
|87-88
|c
|34
|-
|89
|c or d
|34
|-
|90
|d
|34
|-
|91
|d or e
|34
|-
|92-93
|e
|34
|-
|94
|e or f
|34
|-
|95
|f
|34
|-
|96
|f or g
|34
|-
|97-98
|g
|34
|-
|99
|g or h
|34
|-
|100
|h
|34
|-
|101
|h or i
|34
|-
|102-103
|i
|34
|-
|104
|i or j
|34
|-
|105
|j
|34
|-
|106
|j or k
|34
|-
|107-108
|k
|34
|-
|109
|k or m
|34
|-
|110
|m
|34
|-
|111
|m or n
|34
|-
|112-113
|n
|34
|-
|114
|n or o
|34
|-
|115
|o
|34
|-
|116
|o or p
|34
|-
|117-118
|p
|34
|-
|119
|p or q
|34
|-
|120
|q
|34
|-
|121
|q or r
|34
|-
|122-123
|r
|34
|-
|124
|r or s
|34
|-
|125
|s
|34
|-
|126
|s or t
|34
|-
|127-128
|t
|34
|-
|129
|t or u
|34
|-
|130
|u
|34
|-
|131
|u or v
|34
|-
|132-133
|v
|34
|-
|134
|v or w
|34
|-
|135
|w
|34
|-
|136
|w or x
|34
|-
|137-138
|x
|34
|-
|139
|x or y
|34
|-
|140
|y
|34
|-
|141
|y or z
|34
|-
|142-143
|z
|34
|-
|144
|z or 2
|34 or 35
|-
|145-255
|2
|35
|}

Payment methods

2012-02-24T02:28:13Z

Graingert:

When trading bitcoins for national fiat currencies, one issue that frequently comes up is the mismatch between the hardness (non-reversibility) of bitcoin, and the softness (reversibility) of many of the fiat-currency payment methods. This page lists a number of payment methods, hardness ratings, and more detailed info in the notes field.

Hardness goes from 0 (extremely soft) to 10 (completely non-reversible).

{| style="border: 1px solid #c6c9ff; border-collapse: collapse;" cellspacing="0" cellpadding="10" border="1"
|- style="text-align: center; background-color: #f0f0ff;"
! Method !! Currencies !! Hardness || Notes
|-
| [[Liberty Reserve]] || EUR, USD || 10 || Very good match for trading bitcoin. However, it is difficult to get LR funded - it is only possible through third-party exchangers.
|-
| Webmoney || USD, RUB, BYR, EUR, XAU || 10 || Very good match for trading bitcoin. Requires funding by bank wire though, which may be expensive for small amounts.
|-
| [[PayPal]] - regular || Most world currencies || 0 || Extremely easy to charge back. Also, since trading bitcoin is against their ToS, good luck disputing the chargeback. Do not use.
|-
| Paypal - personal || Most world currencies || 1-5 || If funded via bank, requires person to dispute the ACH, which may be more arduous. If funded via credit card, requires person to dispute the CC charge, which is pretty easy. Since there's no way to tell what the funding source was... it's a gamble. Also, if paypal account is reported stolen, paypal will probably attempt to claw back the money.
|-
| Paypal - masspay || Most world currencies || 7 || Mass pay requires funding from paypal balance. Generally much harder to reverse, but not impossible. Probably your biggest worry here is an actual stolen account.
|-
| [[Dwolla]] || USD || 3? || Since Dwolla amounts are funded via ACH, Dwolla will reverse payments if the funds were the result of fraud. Additionally, Dwolla's Terms and Conditions now state that peyments received are subject to chargebacks as the result of their internal dispute resolution processK<ref>[http://www.bitcoinmoney.com/post/8067352221 Dwolla's New Terms: "receiving party may be subject to chargebacks"]</ref>.
|-
| [[Serve]]|| USD || 0 || Extremely easy to charge back.
|-
| [[AlertPay]]|| Many currencies || 1 || Because payment may be made using a credit card a charge back is easy. Doing so however will cause the account to be closed.
|-
| [[Moneybookers]] || || 0 || Chargebacks are possible. Accounts have been terminated when this payment method was used for a Bitcoin trade.
|-
| Neteller || || ||
|-
| Western Union Money Transfer || || 9 || A money transfer can be stopped but once funds are withdrawn as cash there's little risk<ref>[http://www.ehow.com/how_8059315_stop-payment-via-western-union.html How to Stop Payment Via Western Union]</ref>.
|-
| Money Order || || 5 || A money order can be lost or stolen and there are procedures for reporting that. Losses could occur even weeks after the check has cleared<ref>[http://www.ehow.com/how_7319971_stop-payment-money-order.html How to Stop Payment on a Money Order]</ref>.
|-
| [[MoneyPak]] || USD || 10 || MoneyPaks are irrevocable.
|-
| Personal check || Any currency || 5 || At least in the USA, once a check clears, it is hard to claw back except when fraud is alleged.
|-
| Bank ACH || USD || 5 || Though not very easily, ACH can actually be clawed back if the transaction was the result of fraud.
|-
| Euro SEPA transfer || || ||
|-
| Cash in mail || Any currency || 10 || No chargebacks, obviously. Just check for counterfeit paper.
|-
| Cash at bank || Any currency || n/a || Some exchanges (e.g., [[Virtex]] and OTC traders accept cash deposited to an account at a bank.
|-
| Check at bank || Any currency || n/a || Some exchanges accept a check deposited to an account at a bank.
|-
| Credit card || Any currency || 0 || Dead easy to charge back. Do not use.
|-
| [[TransferWise]] || GBP to EUR || ||
|-
| Intra-bank transfer || || ||
|-
| [[Popmoney]] ACH || USD || 5 || Since Popmoney transfers occur via ACH, Popmoney will reverse payments if the funds were the result of fraud.
|-
| [[ING Person2Person]] || USD || 5 || Since Person2Person transfers occur via ACH, ING will reverse payments if the funds were the result of fraud.
|-
| [[Pingit]] || UK || 5 || Barclays will reverse payments if the funds were the result of fraud.
|-
| Chase QuickPay || USD || 3 || Chase has reversed legitimate transactions as the result of anti-fraud measures<ref>[http://forum.bitcoin.org/index.php?topic=11494.0 Chase QuickPay NOT RECOMMENDED]</ref> requiring the sender to be trusted to re-pay. The sender can also request a reversal after submitting an affidavit alleging that fraud occurred.
|-
| AliPay || China || n/a || Though reports of reversed AliPay payments can be found on the Internet, the operator of [[Bitcoinica]] asserts that AliPay transaction are "non-reversible"<ref>[http://bitcointalk.org/index.php?topic=65003.msg763730#msg763730 Bitcoinica now supports Alipay deposit!]</ref>.
|}

==See Also==

* [[Secure Trading]]
* [[Digital currency]]
* [[:Category:Money transmitters|Money transmitters]]

==References==
<references />

[[Category:Financial]]

Mining hardware comparison

2012-02-14T13:44:36Z

Graingert: we are not in France

Below are some statistics about the mining performance of various hardware used in a [[mining rig]].

The table shows (mostly) stock clock numbers. 10-20% performance improvement can be achieved with [[GPU overclocking tools]].

'''Notes:'''
* Mhash/s = millions hashes per second (raw speed performance ; may not be very energy efficient with some models)
* Mhash/J = millions hashes per joule (energy efficiency ; 1 joule of energy is spent for 1 watt in 1 second)
* W = watt (maximum power consumption, i.e. energy per unit of time : 1 W = 1 J/s)
* Clock (in MHz) refers to the Shader clock only with nVidia cards (not Core or Memory). With AMD card the shader clock is not separate, but is part of the GPU clock.
* SP = Stream processors (Shader Units)

==Graphics cards==
=== Popular Mining Cards ===
This information has been included to make choosing a card easier. The cards selected are generally readily available online. Once you have purchased a card or cards, use the tables below to compare different configurations and setups.
=== Card Comparison Spreadsheet ===
This spreadsheet performs several calculations and displays a visualization graph of a theoretical mining rig over time. It can be used to visualize any "what if" scenarios to better wrap your head around which card is the best choice under different conditions. Bright Yellow Boxes are editable, and affect the calculations. Dark Yellow Boxes are editable for notation, but don't affect the calculations. The Green highlighted card is the best under those conditions, the Blue highlight is second best, the Orange highlight is third best. Higher MHash/s performance can be obtained for each card through overclocking, but that drives up the wattage draw of the cards, and I did not have that complete dataset so I used the "average" MHash/s values listed here. <br />
V1.5 - 1 Jan, 2012 - by. Joseph Woodrell
[http://www.woodrell.com/joe/bitcoin/mining_sheet.zip Card Selection Spreadsheet]
<br />
==== Single Card Setups ====
{| class="wikitable sortable"
|-
! Model !! Price <ref name=amazon>Price from http://ebay.com/ on 2012-02-10 using an average of completed items, minus the top and bottom 20% to avoid spikes and give a truer average.</ref> !! Availability !! Avg. Mhash/s !! Mhash/J !! Mhash/s/$
|----
|5770
|$136
|Moderate
|212.83
|1.45
|1.56
|----
|5830
|$92
|Moderate
|302
|1.68
|3.28
|----
|5850
|$114.96
|Limited
|346.16
|1.92
|3.0
|----
|5870
|$190.16
|Limited
|393
|1.97
|2.066
|----
|5970
|$421
|Limited
|704
|2.2
|1.67
|----
|6750
|$116
|Easy
|167.59
|
|1.44
|----
|6770
|$115
|Easy
|196.67
|
|1.44
|----
|6850
|$160
|Easy
|213.7
|1.35
|1.34
|----
|6870
|$190
|Easy
|278.31
|1.73
|1.46
|----
|6950
|$230
|Easy
|369
|1.94
|1.6
|----
|6970
|$271.89
|Easy
|397
|1.89
|1.46
|----
|6990
|$622.99
|Limited
|772
|1.93
|1.23
|----
|7970
|$588.75
|Easy
|680
|
|1.67
|----
|}

==== Multi-Card Setups ====
{| class="wikitable sortable"
|-
! Model !! Price <ref name=amazon/> !! Availability !! Avg. Mhash/s !! Mhash/J !! Mhash/s/$
|----
|5830x2
|$360
|Moderate
|525
|
|1.46
|----
|5850x4
|$644
|Limited
|1360
|1.94
|2.11
|----
|5850x6
|$996
|Limited
|2130
|
|
|----
|5870x2
|$700
|Limited
|787.5
|0.84
|1.13
|----
|6770x2
|$274
|Easy
|464
|
|1.69
|----
|6950x4
|$1,000
|Easy
|1316
|1.51
|1.32
|----
|6970x2
|$700
|Easy
|769
|1.6
|1.10
|----
|6990x2
|$1,540
|Limited
|1568
|1.7
|1.02
|----
|6990x3
|$2,310
|Limited
|2094
|1.8
|0.91
|----
|}
<references>
</references>

===AMD (ATI)===
Stream SDK 2.5 seems to have resolved many of the problems with earlier versions. Everyone's setups will be unique so this should only be a guide or starting point, not an absolute.

{| class="wikitable sortable"
|-
! Model !! Mhash/s !! Mhash/J !! Mhash / $<ref name='amazon_20110625'/> !! Watts !! Clock !! SP !! SDK !! Slot !! Miner !! Notes !!Flags !!

|-
| 3410 || 0.89 || 0.074 || ? || 12(?) || 222 || 40 || 1.4 beta || PCI-E 1.1 x8 || A custom Brook+ miner || Using 16,384 length streams

|-
| 3XXX || || || || || || || || || || OpenCL Not Supported

|-
| 42XX || || || || || || || || || || OpenCL Not Supported (integrated/mobile GPU)

|-
| 4350 || 6.93 || 0.346 ||0.16 || 20 || 575 || 80 || - || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors
|-
| 4350 || 8.14 || -|| 0.19 || - || 730 || 80 || 2.4 || PCI-E 2.0 x16 || Diablo/Windows7 || -w 32. Model: Asus EAH4350 Silent. Memory at 400MHz. Runs at 60°C with ambient at 25°C.

|-
| 4550 || 7.23 || 0.289 ||0.13 || 25 || 600 || 80 || - || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors

|-
| 4550 || 7.8 || || || || || || - || PCI-E 2.0 x16 || guiminer /phoenix || worksize=64 VECTORS

|-
| 4570M || 8.02 || 0.297 || ? || 27 || 680 || 80 || - || PCI-E 2.0 x16 || Diablo/Windows7 || -w 64, SDK 2.4, Cat 11.4. Model: Sony Vaio NW

|-
| 4570M || 9.6 || 0.300|| ? || 32 || 825(OC) || 80 || - || PCI-E 2.0 x16 || Diablo/Windows7 || -w 64, SDK 2.4, Cat 11.4. Model: Sony Vaio NW. OC core 680->825. U/C memory 800->500.

|-
| 4650 || 31.33 || 0.653|| 0.44 || 48 || 650 || 320 || - || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors

|-
| 4670 || 36.14 || 0.613|| 0.34 || 59 || 750 || 320 || - || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors
|-
| 4670 || 40.11 || 0.679|| 0.38 || 59 || 800 || 320 || - || AGP x8 || poclbm/Ubuntu 10.10 w/ H == 0 mod || -w 32 -f 0, don't use vectors [http://www.bitcoin.org/smf/index.php?topic=1334.msg85236#msg85236 source]
|-
| 4670 || 50 || - || 0.47 || 60 || 800 || 320 || - || PCI-E 2.0 x16 || guiminer || 2 miners set up i7 920 (130W), CPU: Ufasoft, GPU: OpenCL; the CPU is getting about 40 Mhash/s while the GPU goes from 10-20 Mhash/s

|-
| 4730 || 72.29 || 0.657|| ? || 110 || 750 || 640 || - || PCI-E 2.0 x16 || - ||

|-
| 4770 || 72.29 || 0.904|| 0.72 || 80 || 750 || 640 || - || PCI-E 2.0 x16 || - ||

|-
| 4830 || 55.42 || 0.583|| || 95 || 575 || 640 || - || PCI-E 2.0 x16 || - ||
|-
| 4830 || 66.12 || 0.503|| || 105 || 700 || 1005 || - || PCI-E 2.0 x16 || - ||

|-
| 4830 || 61.7 || - || || - || 700 || - || 2.4 || PCI-E 2.0 x16 || poclbm-mod || Fedora 14 ||
|-
| 4830 || 64.9 || - || || - || 700 || - || 2.4 || PCI-E 2.0 x16 || poclbm-mod || Fedora 14 ||

|-
| 4850 || 75.30 || 0.685 || || 110 || 625 || 800 || - || PCI-E 2.0 x16 || - ||
|-
| 4850 || 84.3 || 0.766|| || 110 || 725 || 300 || - || PCI-E 2.0 x16 || - || -w64 fan at 70% temp 73C, stock voltage -gui miner
|-
| 4850 || 90.1 || 0.819 || || 110 || 800 || 500 || - || PCI-E 2.0 x16 || guiminer || -f 30; Tried phoenix and phatk, got same max
|-
| 4850 || 101 || 0.918 || || 110 || 817 || 500 || 2.1 || PCI-E 2.0 x16 || guiminer || -f 0, core 817mhz(default 625)@1.123v , mem downclock to 500mhz (default 993) [http://www.smpake.com/?p=6 source]
|-
| 4850x2 || 150.60 || 0.602 || || 250 || 625 || 1600 || - || PCI-E 2.0 x16 || - ||

|-
| 4860 || 67.47 || 0.519|| || 130 || 700 || 640 || - || PCI-E 2.0 x16 || - ||

|-
|style="background:#F8F8FF;"| 4870 || 92.84 || 0.6189333(?)|| || 150(?) || 830(OC) || 800 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.48 || -k poclbm AGGRESSION=5 (Windows 7 64-Bit, GPU OC 750->830MHz, VRAM UC 900->450MHz, BIOS modded)
|-
|style="background:#F8F8FF;"| 4870 || 104.2 || ?|| || ? || 830(OC) || 800 || 2.1 || PCI-E 2.0 x16 || poclbm || Windows 7 64-Bit, GPU Core OC to 830 MHz, GPU Memory UC to 200 MHz By MSI AfterBurner. Card: Gainward Golden Sample. @70%Fan we have 55 GPU temp.
|-
|style="background:#F8F8FF;"| 4870 || 104.6 || 0.872|| || 120 || 830(OC) || 800 || 2.1 || PCI-E 2.0 x16 || poclbm || -w 256 -f 1, Windows 7 64-Bit, GPU Core OC to 830 MHz, GPU Memory UC to 190 MHz (saves 30 watts at outlet)
|-
|style="background:#F8F8FF;"| 4870 || 90.36 || 0.602|| || 150 || 750 || 800 || 2.1 || PCI-E 2.0 x16 || clmine ||
|-
|style="background:#F8F8FF;"| 4870 || 78 || 0.520|| || 150 || - || - || - || PCI-E 2.0 x16 || m0mchil's OpenCL/Vista 64bit || [http://www.bitcoin.org/smf/index.php?topic=1628.msg25069#msg25069 source]
|-
|style="background:#F8F8F8;"| 4870 || 88 || || || 140 || std || 800 || 12.3.6 || PCI-E 2.0 x16 || phoenix 1.50 / 64bit OS X pyopencl / poclbm || Standard Mac Pro 3,1 with Apple HD4870 upgrade. Flags: FASTLOOP WORKSIZE=64 AGGRESSION=5 (don't use vectors, and hash rate drops to 60-70 if browser windows are visible, speeds up to 88 if you hide them!
|-
|style="background:#F8F8FF;"| 4870x2 || 180.72|| 0.632|| || 286 || 750 || 1600 || - || PCI-E 2.0 x16 || - ||
|-
|style="background:#F8F8FF;"| 4870x2 || 180.6|| 0.632|| || 286 || 800 || 1600 || - || PCI-E 2.0 x16 || - ||

|-
| 4890 || 97.1 || 0.511|| || 190 || 870(OC) || 1050 || 2.4 || PCI-E 2.0 x16 || GUIMiner v2011-01-21 Solo settings || Sapphire fab. No flags options helped. Close all browsers and do full restart of GUIMiner and then Bitcoin via GUIMiner server starter or the browsers GPU accl. will limit to 56~ ish Mhash/s - I can now start browser without slowdowns
|-
| 4890 || 102.41 || 0.539|| || 190 || 850 || 800 || - || PCI-E 2.0 x16 || - ||
|-
| 4890 || 108.3 || 0.57|| || 190 || 975 || 800 || - || PCI-E 2.0 x16 || - ||
|-
| 4890 || 121.5 || -|| || 190 || 1025 (OC) || 800 || 2.4 || PCI-E 2.0 x16 || poclbm || no flags, Vcore 1.4 ||
|-
|style="background:#FFF8EF;"| 5450 || 11.99|| 0.631|| || 19 || 650 || 80 || - || PCI-E 2.1 x16 || - ||
|-
|style="background:#FFF8EF;"| 5450 || 13.74|| || - || - || 700 || - || - || PCI-E 2.1 x16 || poclbm/Linuxcoin v0.2 || -v -w128 tried several options, seems to work best.
|-
|style="background:#FFF8EF;"| 5450 || 14.12|| || - || - || 700 || - || - || PCI-E 2.1 x16 || Phoenix/Linuxcoin v0.2 || Flags: "DEVICE=0 VECTORS AGGRESSION=4 -v FASTLOOP BFI_INT WORKSIZE=64" Kernel: "phatk"
|-
|style="background:#FFF8EF;"| 5450 || 15.36|| || - || - || 700 || - || - || PCI-E 2.1 x16 || Phoenix || Flags: "DEVICE=0 VECTORS AGRESSION=8 FASTLOOP BFI_ING WORKSIZE=128" Kernel: "phatk" - MagicSata
|-
|style="background:#FFF8EF;"| 5450 || 18.10|| || - || - || 774 || - || - || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 1 774.66MHz/300.37MHz
|-
|style="background:#FFF8EF;"| 5470 || 17.10|| || - || - || - || - || - || - || poclbm || -v -w 128 MobileGPU
|-
| 5550 || 40.59 || 1.041|| || 39 || 550 || 320 || - || PCI-E 2.1 x16 || - ||
|-
|-
| 5550 || 62.10 || - || - || - || 700 || - || - || PCI-E 2.1 x16 || Phoenix || 700MHz core 800MHz ram, phatk mod, Flags: "-k phatk worksize=128 vectors aggression=4 bfi_int"
|-
|-
|style="background:#FFFFEF;"| 5570 || 59.96 || 1.538|| || 39 || 650 || 400 || - || PCI-E 2.1 x16 || - ||
|-
|style="background:#FFFFEF;"| 5570 || 64 || 1.641|| || 39 || 650 || - || - || PCI-E 2.1 x16 || m0mchil's OpenCL/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
|style="background:#FFFFEF;"| 5570 || 62 || 1.59|| || 39 || 650 || 400 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.48 OpenCL/Linux x86_64 || -k phatk DEVICE=0 VECTORS AGGRESSION=4 -v FASTLOOP BFI_INT WORKSIZE=64
|-
|style="background:#FFFFEF;"| 5570 || 73 || 1.872|| || 39 || 700 || 400 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.48 OpenCL/Linux x86_64 || -k phatk DEVICE=0 VECTORS AGGRESSION=4 -v FASTLOOP BFI_INT WORKSIZE=64
|-
|style="background:#FFFFEF;"| 5570 || 102 || 1.46(+)|| || 75(-) || 950 || 400 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.48 OpenCL/Windows 7 x86 (no Aero) || -k phatk DEVICE=0 VECTORS AGGRESSION=7 -v FASTLOOP BFI_INT WORKSIZE=256 (Reference Sapphire card, 2 additional 120mm coolers, temperature is 79-82C)

|-
| 5650 || 48 || 1.37|| || 35(?) || - || - || - || PCI-E 2.1 x16 || m0mchil's OpenCL/Win7-64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26292#msg26292 source] [http://www.notebookcheck.net/ATI-Mobility-Radeon-HD-5650.23697.0.html source] -- not TDP but load
|-
| 5650 || 61.2 || || || 35 || || || 2.4 || PCI-E 2.1 x16 || Phoenix 1.50 OpenCL/Windows 7 x64 || -k phatk DEVICE=0 VECTORS BFI_INT WORKSIZE=128 AGGRESSION=9
|-
|style="background:#EEFFEE;"| 5670 || 71.49 || 1.117|| || 64 || 775 || 400 || - || PCI-E 2.1 x16 || - ||
|-
|style="background:#EEFFEE;"| 5670 || 72 || 1.64|| || 44 || 850 || - || - || PCI-E 2.0 x16 || poclbm-mod (Win7-64) || Sapphire 100287VGAL card is low power
|-
|style="background:#EEFFEE;"| 5670 || 85|| || - || - || 900 || 400 || - || PCI-E 2.1 x16 || poclbm || -v -f 0 -w 128
|-
|style="background:#EEFFEE;"| 5670 || 91|| || - || - || 890 || 400 || - || PCI-E 2.1 x16 || guiminer 2011-06-09 poclbm catalyst 11.2 win7 x86 || -v -f 0 -w 128
|-
|style="background:#EEFFEE;"| 5670 || 100|| || - || - || 890 || 400 || - || PCI-E 2.1 x16 || cgminer 1.5.6 || GPU/Mem 890/800 temp 72C
|-
|style="background:#EEFFEE;"| 5670 || 103 || -|| || - || 900/275 || 400 || 2.4 || PCI-E 2.1 x1 || phoenix-1.50 / phatk-mod / Ubuntu 11.04 || VECTORS BFI_INT FASTLOOP=false AGGRESSION=11 WORKSIZE=256 / small fan, under 50 deg C, no voltage tweaks... catfish
|-
| 5750 || 105 || - || - || - || - || - || - || - || poclbm || Apple iMac 27inch (Mid 2010), Mac OSX 10.7 Lion ||
|-
| 5750 || 116.24 || 1.352|| || 86 || 700 || 720 || - || PCI-E 2.1 x16 || - ||
|-
| 5750 || 137 || ||- || - || 710 || 720 || - || PCI-E 1.1 x16 || poclbm || -v -f 0 -w 128 using stock memory and GPU clocks
|-
| 5750 || 146.4 || || - || - || 775 || 720 || - || PCI-E 2.0 x16 || GUIMiner v2011-05-21 || -v -w128, AMD Catalyst overclock (775MHz GPU / 1225 MHz Memory)
|-
| 5750 || 154.56 || 1.45|| || 106 || 830 || 720 || - || PCI-E 2.1 x16 || - || -v -w128 -f20 underclocked memory clocks from 1150MHz to 300MHz
|-
| 5750 || 170 || - || || - || 870 || 720 || - || PCI-E 1.1 x16 || poclbm || -v -f 0 -w 128 patched BIOS to underclock memory to 300MHz
|-
| 5750 || 173 || - || ||- || 875 || 720 || - || PCI-E 1.1 x16 || phoenix || 875/300 w/MSI Afterburner, BFI_INT VECTORS AGGRESSION=12 FASTLOOP=FALSE -k phatk
|-
| 5750 || 177 || - || ||- || 910/575 || 720 || 2.6 || PCI-E 2.0 x8 || phoenix 1.5.6 || PowerColor GoGreen+fan, MSI Afterburner 2.2Beta, -k phatk VECTORS AGGRESSION=12 FASTLOOP=FALSE WORKSIZE=64
|-
| 5750 || 190 || - || ||- || 930/290 || - || atistream sdk || PCI-E 1.1 x16 || poclbm || 930gpu / 290mem (O.S. Ubuntu 10.10 x64, overclock gpu & underclock mem) with poclbm options -v -f 0 -w 256
|-
| 5750x2 CF || 356 || - || ||- || 870 || 720x2 || 2.4 || PCI-E 2.0 x16 || [http://forum.bitcoin.org/index.php?topic=28402.0 cgminer v1.5.1] (Win7 64bit) || 870MHz GPU / -I 8 / 2x [http://www.gigabyte.com/products/product-page.aspx?pid=3402#sp GIGABYTE GV-R575SL-1GI] cards + [http://www.gigabyte.com/products/product-page.aspx?pid=3258#sp GIGABYTE GA-790FXTA-UD5] MB + 1x [http://www.noctua.at/main.php?show=productview&products_id=9&lng=en 80mm], 1x [http://www.noctua.at/main.php?show=productview&products_id=16&lng=en 90mm] Noctua coolers
|-
|style="background:#FFFFEF;"| 5770 || 156.83 || 1.452|| || 108 || 850 || 800 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
|style="background:#FFFFEF;"| 5770 Hawk || 182 || ||- || - || 875 || 800 || 2.4 || PCI-E 2.0 x16 || poclbm/GUIMiner/Win7-64 || -v -w 128 (875MHz is stock for 5770 Hawk)
|-
|style="background:#FFFFEF;"| 5770 || 180 || 1.406(*)|| || 128(*) || 950(OC) || 800 || 2.4RC1 || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 30 (*: Overclocked wattage calculated [http://bakkap.free.fr/Misc/wCalc.html here])
|-
|style="background:#FFFFEF;"| 5770 || 185 || - || ||- || 850 || 1200 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / phatk || -k phatk VECTORS BFI_INT WORKSIZE=128 FASTLOOP AGGRESSION=7
|-
|style="background:#FFFFEF;"| 5770 || 205.58 || - || ||- || 935 || 300 || 2.1 || PCI-E 2.1 x16 || poclbm 2011-04-28 || -v -w 256
|-
|style="background:#FFFFEF;"| 5770 || 214.5 || 1.95(-)|| || 108(+) || 950 || 300 || 2.4 || PCI-E 2.1 x16 || phoenix 1.50/GUIMiner/Win7-64 || mem underclocked 300 mhz, 1.1vcore, 950mhz core, @69°C/57%FAN VECTORS BFI_INT AGGRESSION=12 -k phatk WORKSIZE=256
|-
|style="background:#FFFFEF;"| 5770 || 214.7 || 1.95(-)|| || 108(+) || 950 || 800 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / win7x86 || mem underclocked 309 mhz, -k phatk DEVICE=0 VECTORS BFI_INT FASTLOOP=false AGGRESSION=12
|-
|style="background:#FFFFEF;"| 5770 || 216.5 || -|| || - || 955 || || 2.1 || PCI-E 2.0 x16 || Phoenix 1.5 /phatk || [http://forum.bitcoin.org/index.php?topic=23067.0 Modified phatk kernel] and stock voltage for Sapphire (1.125V) VECTORS BFI_INT FASTLOOP=false AGGRESSION=12 -k phatk WORKSIZE=256
|-
|style="background:#FFFFEF;"| 5770 || 218.35 || -|| || - || 1000 || 1401 || 2.1 || PCI-E 2.0 x16 || DiabloMiner || -w 128 -v 2 (Overclocked to 1Ghz core with 1.2 voltage and Scythe Setsugen 2 cooling system)
|-
|style="background:#FFFFEF;"| 5770 || 222.60 || -|| || - || 960 || 300 || 2.1 || PCI-E 2.0 x16 || Phoenix 1.60 /phatk2 || [http://forum.bitcoin.org/index.php?topic=23067.0 Modified phatk kernel] and stock voltage for Sapphire (1.125V) VECTORS BFI_INT FASTLOOP=false AGGRESSION=9
|-
|style="background:#FFFFEF;"| 5770 || 223 || 2.23(-)|| || 100(+) || 1050 || 300 || 2.4 || PCI-E 2.1 x16 || guiminer || -v -w256 [http://www.smpake.com/?p=59 source]
|-
|style="background:#FFFFEF;"| 5770 || 227 || -|| || - || 1030 || 800 || 2.1 || PCI-E 2.0 x16 || DiabloMiner || -w 256 -v 2 (Overclocked to 1030 core/300 mem with 1.2 voltage and Scythe Setsugen 2 cooling system)
|-
|style="background:#FFFFEF;"| 5770 || 236 || -|| || - || 1033/275 || 800 || 2.4 || PCI-E 2.1 x16 || phoenix-1.50 / phatk-mod / Ubuntu 10.04 || VECTORS BFI_INT FASTLOOP=false AGGRESSION=11 WORKSIZE=256 / big fans, under 75 deg C, no voltage tweaks... catfish
|-
|style="background:#FFFFEF;"| 5770 || 233 || 2.23(-)|| || 100(+) || 1050 || 300 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 || VECTORS BFI_INT FASTLOOP=false AGGRESSION=12 -k phatk WORKSIZE=256 [http://www.smpake.com/?p=59 source]
|-
|style="background:#FFFFEF;"| 5770 || 240.61 || 2.3632(-)|| || 100(+) || 1080 || 300 || 2.4 || PCI-E 2.1 x1 || phoenix 1.48 || VECTORS BFI_INT FASTLOOP=false AGGRESSION=12 -k phatk WORKSIZE=256 (OC'd and OV'd 1080/300 1.25v)
|-
|style="background:#FFFFEF;"| 5770 || 241 || - || - || 100(+) || 1045 || 250 || 2.1 || PCI-E 2.1 x16 || phoenix 1.50 || VECTORS BFI_INT AGGRESSION=13 -k phatk WORKSIZE=256 (OC 1020/300) XFX@1.1 volts. +Kernel function improve 5%
|-
|style="background:#FFFFEF;"| 5770 || 171.12 || - || - || - || - || stock || - || PCI-E 2.1 x16 || phoenix 1.7.3/debian gnu/linux 6 squeeze || -k phatk2 DEVICE=0 VECTORS BFI_INT FASTLOOP=false AGGRESSION=12 WORKSIZE=256
|-
|style="background:#FFFFEF;"| 5770x2 || 425 || - || - || 225(+) || 960 || 800x2 || 2.1 || PCI-E 2.1 x16 || poclbm (guiminer) Win7x64 || -v -w128 (OC 960/1200)
|-
|style="background:#FFFDDD;"| 5830 || 244 || 1.36|| || 179 || 800 || 1000 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.48 OpenCL/Linux x86_64 || -k phatk DEVICE=1 VECTORS AGGRESSION=6 -v FASTLOOP WORKSIZE=128 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 267 || -|| || - || 875 || 1000 || 2.4 || PCI-E 2.1 x1 || Phoenix 1.48 OpenCL/Linux x86_64 || -k phatk DEVICE=1 VECTORS AGGRESSION=6 -v FASTLOOP WORKSIZE=128 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 245 || 1.28|| || 192 || 880 || 900 || 2.4 || PCI-E 2.1 x16 || poclbm (guiminer) || -v -w 256
|-
|style="background:#FFFDDD;"| 5830 || 248 || 1.29|| || 192 || 880 || 500 || 2.4 || PCI-E 2.1 x16 || phoenix 1.46 || -k poclbm VECTORS BFI_INT AGGRESSION=11
|-
|style="background:#FFFDDD;"| 5830 || 256 || -|| || - || 900 || 300 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 || -k poclbm VECTORS BFI_INT AGGRESSION=7
|-
|style="background:#FFFDDD;"| 5830 || 272 || 1.52|| || 179 || 875 || - || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / LinuxCoin || 275Mhz Memory clock, 1.125 V (from 1.163), VECTORS AGGRESSION=12 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 275 || 1.5714|| || 175 || 900 || 500 || 2.1 || PCI-E 2.1 x16 || poclbm (guiminer) Win7x64 || -v -w64 -f10, XFX stock w/ v2.4 SDK = 230Mh/s, v2.1 SDK = +10Mh/s, overclocking core clock by 100 = +30Mh/s, underclocking memory to 500 (ran cooler), and changing workload to -w64 = +5Mh/s.
|-
|style="background:#FFFDDD;"| 5830 || 285 || - ||1.58 || - || 960 || - || 2.4 || PCI-E 2.1 x16 || phoenix 1.47 / poclbm / Win7 64 || VECTORS BFI_INT FASTLOOP=false AGGRESSION=12
|-
|style="background:#FFFDDD;"| 5830 || 290 || -|| || - || 930 || - || 2.2 || PCI-E x16/x4/x1 || GUIMiner / phoenix 1.5 / POCLBM / Win 7 64 || POCLBM VECTORS BFI_INT WORKSIZE=256 AGGRESSION=12 FASTLOOPS=false / Memory 300Mhz, VCore standard
|-
|style="background:#FFFDDD;"| 5830 || 290 || -|| || - || 996 || - || 2.4 || PCI-E 2.1 x16 || phoenix 1.4 / poclbm / Win7 64 || VECTORS AGGRESSION=12 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 295 || -|| || - || 980 || 1120 || 2.1 || PCI-E 2.1 x16 || GUIMiner / poclbm / Win XP 32 || Extra flags -v -w 128
|-
|style="background:#FFFDDD;"| 5830 || 297 || -|| || - || 970 || 1120 || 2.4 || PCI-E 2.0 x16 || guiminer / phoenix 1.48 / phatk / Win7 64 || 300Mhz Memory clock, 44% fan-speed, -k phatk VECTORS BFI_INT AGGRESSION=8 FASTLOOP=false WORKSIZE=256
|-
|style="background:#FFFDDD;"| 5830 || 300 || -|| || - || 960|| 300 || 2.4 || PCI-E 2.1 x16 || GUIMiner / poclbm / Win 7 64 || Extra flags -v -w 256 (Sapphire Extreme 71 degrees @ 52% fan)
|-
|style="background:#FFFDDD;"| 5830 || 300 || -|| || - || 970 || - || 2.4 || PCI-E 2.0 x16 || phoenix 1.47 / pheonix 1.48 / Win7 64 || (sapphire xtreme) VECTORS BFI_INT FASTLOOP=false AGGRESSION=12
|-
|style="background:#FFFDDD;"| 5830 || 300 || -|| || - || 970 || 1120 || 2.1 || PCI-E x16 || phoenix 1.48 / phatk / Win7 64 || 300Mhz memory clock BFI_INT AGGRESSION=12 FASTLOOP=false WORKSIZE=256
|-
|style="background:#FFFDDD;"| 5830 || 305 || -|| || - || 984 || - || 2.4 || PCI-E 2.1 x16 || phoenix 1.4 / phatk / Win7 32 || 400Mhz Memory clock, VECTORS AGGRESSION=12 BFI_INT FASTLOOP=false
|-
|style="background:#FFFDDD;"| 5830 || 307 || -|| || - || 996 || - || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / Win7 64 || VECTORS AGGRESSION=12 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 307 || 2.25 || 2.55 || 125 || 965 || - || - || PCI-E 2.1 x16 || cgminer 2.0.5 / Win7 64 || Mem @ 300/Stock voltage/Entire system 200W
|-
|style="background:#FFFDDD;"| 5830 || 308 || -|| || - || 990 || 300 || 2.4 || PCI-E 2.1 x16 || phoenix 1.50 / poclbm / Xubuntu 11.04 x64 || VECTORS AGGRESSION=11 BFI_INT FASTLOOP=false WORKSIZE=256
|-
|style="background:#FFFDDD;"| 5830 || 308 || -|| || - || 990 || 375 || 2.1 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / Win7 32 || @ stock voltage VECTORS AGGRESSION=11 -v FASTLOOP=false BFI_INT
|-
|style="background:#FFFDDD;"| 5830 black || 310 || ||- || - || 990 || 300 || 2.4 || PCI-E 2.1 x8 || LinuxCoin 0.2b, phoenix/phatk || (XFX Brand) -k phatk VECTORS BFI_INT WORKSIZE=256 AGGRESSION=11 FASTLOOPS=false
|-
|style="background:#FFFDDD;"| 5830 || 311 || -|| || - || 1000 || 300 || 2.4 || PCI-E 2.1 x16 || phoenix 1.50 / phatk / Linux || VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false WORKSIZE=256
|-
|style="background:#FFFDDD;"| 5830 || 315 || -|| || - || 970 || - || 2.4 || PCI-E 2.1 x16 || phoenix 1.6.1 / phatk2 / CrunchBang Linux || memory @ 300mhz VECTORS BFI_INT AGGRESSION=9 WORKSIZE=256
|-
|style="background:#FFFDDD;"| 5830 || 316.35 || ||- || - || 1015 || 375 || 2.1 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / Win7 32 || @ stock voltage VECTORS AGGRESSION=12 -v FASTLOOP=false BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 319 || -|| 1.77 || - || 1030 || - || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / Xp 64 || 1.2v 355Mhz Memory, VECTORS AGGRESSION=12 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 321 || -|| || - || 1000 || 1120 || 2.4 || PCI-E 2.0 x16 || phoenix 1.50 / phatk-mod / Linux || 1000Mhz GPU, 350Mhz RAM, 1.15V, 90% fan, ~60c Temp, VECTORS BFI_INT FASTLOOP=false AGGRESSION=13 WORKSIZE=128; phatk kernel found [http://forum.bitcoin.org/index.php?topic=25135.0 here]
|-
|style="background:#FFFDDD;"| 5830 || 323 || || || || 900 (OC) || || 2.4 || PCI-E 2.1 x16 || phoenix 1.5 Win7x64 || (500Mhz RAM), ~61c Temp, 57% fan, BFI_INT FASTLOOP=false VECTORS AGGRESSION=12 -v WORKSIZE=64
|-
|style="background:#FFFDDD;"| 5830 || 328 || - || - || - || 1040 || - || 2.4 || PCI-E 2.1 x16 || LinuxCoin 0.2.1b / phoenix / phatk || 1.195 V, RAM @ 325 Mhz, fan @90%, no case, extra 10K RPM fan (62 deg.C in full-load); options: -k phatk DEVICE=0 VECTORS BFI_INT FASTLOOP=false AGGRESSION=11 WORKSIZE=256; brand: Sapphire Xtreme; bord is stable up to 1060 Mhz ~ 335 MHash, but produces some visual artefacts;
|-
|style="background:#FFFDDD;"| 5830 || 333 || - || - || - || 1040 || - || 2.4 || PCI-E 2.1 x16 || LinuxCoin 0.2.1b / phoenix-1.50 / phatk-[http://forum.bitcoin.org/index.php?topic=25135.0 mod] || + ~5 Mhash increase using the modified phatk from the user above. I am the same guy with 330 @ 1040 MHz Sapphire Xtreme, all other settings the same, board stable, no increase in rejected
|-
|style="background:#FFFDDD;"| 5830 || 334 || -|| || - || 1030 || - || 2.4 || PCI-E 2.1 x16 || phoenix 1.50 / phatk 2.0 / Win7 64 || Stock voltage, 385Mhz Memory, VECTORS AGGRESSION=12 WORKSIZE=256 BFI_INT -- (upped from 330 achieved with diapolo mod [http://forum.bitcoin.org/index.php?topic=25135.0 here]), now using phatk 2.0 found [http://forum.bitcoin.org/?topic=7964.0 here]
|-
|style="background:#FFFDDD;"| 5830 || 342 || - || - || - || 1045 || - || 2.4 || PCI-E 2.0 x8 || phoenix 1.48 / phatk 2.2 / WinSvr 2008 R2 64 || Stock voltage, 385Mhz Memory, VECTORS VECTORS4 FASTLOOP=false AGGRESSION=14 BFI_INT -k phatk-2.2
|-
|style="background:#FFFDDD;"| 5830x2 CF || 480 || -|| || - || 800 || - || 2.4 || PCI-E 2.1 x16 || Guiminer/ - / Win7 64bit |Guiminer -v -f70 -w128||
|-
|style="background:#FFFDDD;"| 5830x2 || 570 || -|| || - || 950 || - || 2.4 || PCI-E 2.1 x8 || Guiminer/ - / Win7 64bit poclbm || poclbm -v -w256 -f10 MEMORYCLOCK 300MHZ GPUCLOCK 950MHZ FAN 52% 72°C||
|-
|style="background:#FFFDDD;"| 5830x2 || 672 || -|| || - || 990 || - || 2.4 || PCI-E 2.1 x16 || CGMiner/ - / Win7 32bit 4way || -I 10 Mem@300, Clock@990, 336-341mhs per card. 69°C ShadesMinoco Machine||
|-
|style="background:#FFFDDD;"| 5830x6 || 1956 || -|| || - || 980 || - || 2.4 || PCI-E 2.1 x16 x1 || CGMiner/ - / Win7 32bit 4way || Gpu Engine 900-980, Target temp 76°C, -I 10, Memoryclock 300, fans at 80% ShadesMinoco Machine||
|-
|style="background:#EFEFFF;"| 5850 || 282.75 ||style="background:#EFEFFF;"| 3.06|| - || 92.25|| 666 (UC) || 1440|| 2.1 || PCI-E 2.1 x16 || Phoenix/WinXP || undervolted to 0.95V; phatk2 VECTORS BFI_INT AGGRESSION=11 WORKSIZE=256; driver 10.12; [http://bitcointalk.org/index.php?topic=9982.0 clocktweak] for setting values; [https://bitcointalk.org/index.php?topic=40056 thread]
|-
|style="background:#EFEFFF;"| 5850 || 240.77 || 1.595|| 1.49 || 151 || 725 || 1440 || - || PCI-E 2.1 x16 || - ||
|-
|style="background:#EFEFFF;"| 5850 || 250.26 || 1.657|| || 151 || 725 || 1440 || - || PCI-E 2.1 x16 || opencl client || [http://www.bitcoin.org/smf/index.php?topic=1628.msg29471#msg29471 source]
|-
|style="background:#EFEFFF;"| 5850 || 252 || 1.575|| || 160 || 765 || 1440 || 2.3 || PCI-E 2.1 x16 || poclbm 2011-01-25 ||
|-
|style="background:#EFEFFF;"| 5850x4 || 1360 || 1.94|| || 700@wall || 900 || || || || poclbm||
|-
|style="background:#EFEFFF;"| 5850 || 255.3 || 1.593|| || 160 || 765 || 1440 || 2.2 || PCI-E 2.1 x16 || poclbm 2011-01-25 ||
|-
|style="background:#EFEFFF;"| 5850 || 264 || 1.748|| || 151 || 725 || 1440 || 2.4 || PCI-E 1.0 x8 || guiminer-20110501 || -v -w128
|-
|style="background:#EFEFFF;"| 5850 || 280 || 1.75|| || 160 || 765 || 1440 || 2.2 || PCI-E 2.1 x16 || Phoenix 1.3 || with BFI_INT
|-
|style="background:#EFEFFF;"| 5850 || 280 || - || ||- || 725 || 1440 || 2.1 || PCI-E 2.1 x16 || Phoenix 1.50 / Fedora 14 || -v -k poclbm VECTORS AGGRESSION=8 WORKSIZE=128 BFI_INT FASTLOOP=true
|-
|style="background:#EFEFFF;"| 5850 || 292 || 1.825|| || 160 || 765 || 1440 || 2.1 || PCI-E 2.1 x16 || poclbm 2011-04-28 -v -f 1 ||
|-
|style="background:#EFEFFF;"| 5850 || 298 || 1.8620|| || 160 || 765 || 1440 || 2.1 || PCI-E 2.1 x16 || poclbm 2011-04-28 -v -f 1 -w 64 ||
|-
|style="background:#EFEFFF;"| 5850 || 300 || 1.5460|| || 194 || 925(OC) || 1440 || - || PCI-E 2.1 x16 || m0mchil's OpenCL || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
|style="background:#EFEFFF;"| 5850 || 304 || - || || - || 725 (stock) || 1440 || 2.1 || PCI-E 2.1 x16 || cgminer.exe -v 2 -I 8 -w 256 --gpu-memclock 275 ||
|-
|style="background:#EFEFFF;"| 5850 || 314 || 1.8362|| || 171 || 820(OC) || 1440 || 2.4 || PCI-E 1.0 x8 || poclbm || -v -w128
|-
|style="background:#EFEFFF;"| 5850 || 328 || TBD|| || TBD || 875 @ Stock voltage || 1440 || 2.4 || PCI-E 2.1 x16 || phoenix || 70C @42% fan, mem @ 500mhz; -v -k phatk VECTORS BFI_INT AGGRESSION=8 FASTLOOP=false WORKSIZE=128 ||
|-
|style="background:#EFEFFF;"| 5850 || 330 || - || ||- || 850 @ Stock voltage || 1440 || 2.1 || PCI-E 2.0 x16 || phoenix || EAH5850, miner arguments: -k poclbm DEVICE=1 VECTORS AGGRESSION=8 WORKSIZE=128 BFI_INT FASTLOOP=false
|-
|style="background:#EFEFFF;"| 5850 || 331 || - || ||- || 725 (Stock) || || 2.4 || PCI-E 2.0 x16 || Diablo Win7 64bits|| Sapphire 5850 Xtreme, Arguments: -v 2 -w 192 (by Swapper 2011-07-05)
|-
|style="background:#EFEFFF;"| 5850 || 335 || 1.8611|| || 180 || 890(OC) || 1440 || 2.4 || PCI-E 2.0 x8 || poclbm || -v -w128, Memory downclocked to 300Mhz
|-
|style="background:#EFEFFF;"| 5850 || 344 || 1.8594|| || 185 || 890(OC) || 1440 || - || PCI-E 2.0 x16 || phoenix ||
|-
|style="background:#EFEFFF;"| 5850 || 347 || -|| || - || 876 || 1440 || 2.4 || PCI-E 2.0 x16 || guiminer / phoenix 1.48 / phatk / Win7 64 || 300Mhz Memory clock, 50% fan-speed, -k phatk VECTORS BFI_INT AGGRESSION=11 FASTLOOP=false WORKSIZE=256
|-
|style="background:#EFEFFF;"| 5850 || 354 || -|| || - || 900(OC) || 1440 || 2.1 || PCI-E 2.0 x16 || diablo -v 2 -w 128 || Ubuntu 11.04 64-bit [http://forum.bitcoin.org/index.php?topic=9239.0 Headless], catalyst 11.5, memory downclocked to 300mhz, stock voltage. flashed with atiflash [http://www.youtube.com/watch?v=U9AxNmOy6_0 video]
|-
|style="background:#EFEFFF;"| 5850 || 355 || -|| || - || 900(OC) || 1440 || 2.1 || PCI-E 2.0 x16 || phoenix 1.48 / phatk || Ubuntu 11.04 64-bit, Memory downclocked to 200MHz, VECTORS BFI_INT FASTLOOP=false AGGRESSION=11 WORKSIZE=128
|-
|style="background:#EFEFFF;"| 5850 || 355 || -|| || - || 900 || 1440 || 2.1 || PCI-E 2.0 x16 || phoenix 1.48 / phatk / Ubuntu 11.04 x64 || 300Mhz Memory clock, 60% fan-speed, -k phatk VECTORS BFI_INT AGGRESSION=11 FASTLOOP=false WORKSIZE=256
|-
|style="background:#EFEFFF;"| 5850 || 359 || -|| || - || 900 || 1440 || 2.4 || PCI-E 2.0 x16 || phoenix 1.50 / phatk / Ubuntu 11.04 x64 || 300Mhz Memory clock, 66% fan-speed, -k phatk VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false WORKSIZE=256
|-
|style="background:#EFEFFF;"| 5850 || 365 || -|| || - || 920 || 1440 || 2.1 || PCI-E x16 || phoenix 1.48 / phatk / Win7 64 || 300Mhz memory clock VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false WORKSIZE=256
|-
|style="background:#EFEFFF;"| 5850 || 367.5 || -|| || - || 900(OC) || 1440 || 2.1 || PCI-E 1.0 x16 || diablo with bitless's hack, -v 2 -w 128 || RHEL 5U5 x86_64, catalyst 11.5, Sapphire HD 5850 Xtreme, Memory downclocked to 300MHz, core voltage 1.145V, BIOS modded with RBE
|-
|style="background:#EFEFFF;"| 5850 || 369.4 || -|| || - || 930 || 1440 || 2.4 || PCI-E 1.0 x16 || guiminer / phoenix / phatk / Win7 32 || Catalyst 11.5, XFX HD5850, Memory downclocked to 322MHz, -k phatk VECTORS BFI_INT AGGRESSION=13 WORKSIZE=256
|-
|style="background:#EFEFFF;"| 5850 || 375 || -|| || - || 940 || 1440 || 2.4 || PCI-E 2.0 x16 || phoenix 1.50 / phatk / Ubuntu 10.04 || 300Mhz memory clock VECTORS AGGRESSION=13 WORKSIZE=256 BFI_INT FASTLOOP=false
|-
|style="background:#EFEFFF;"| 5850 || 381 || -|| || - || 940 || 1440 || 2.5 || PCI-E 1.0 x16 || phoenix / phatk / Win7 x64 / Catalyst 11.6 || MSI Afterburner 500MHz memory clock,-k phatk VECTORS BFI_INT WORKSIZE=256 AGGRESSION=13
|-
|style="background:#EFEFFF;"| 5850 || 382 || 1.8454|| || 207 || 995(OC) || 1440 || - || PCI-E 2.0 x8 || phoenix || OC 1.177v on core
|-
|style="background:#EFEFFF;"| 5850 || 391 || -|| || - || 1000 || 1440 || 2.1 || PCI-E 2.0 x16(@x8) || phoenix 1.5 / phatk / Win7 64 || Mem @ 280, fan @ 100%, Temp @ 71, 1.163 V core, -v -k phatk VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false WORKSIZE=256, The name is Mautobu
|-
|style="background:#EFEFFF;"| 5850 || 392 || -||2.43 || - || 990 || 1440 || 2.4 || PCI-E 2.1 x16 || phoenix-svn (AUR) / phatk / Arch Linux || Memory: 180MHz, -v -q 1 -k phatk WORKSIZE=128 VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false
|-
|style="background:#EFEFFF;"| 5850 || 397 || -|| || - || 950 || 1440 || 2.5 || PCI-E 2.1 16x || phoenix 1.5 / phatk 2.2 / Win7 64, catalyst 11.6 || Mem speed 350Mhz, Fan 85%, 70C, 1.083 Vcore, -k phatk VECTORS BFI_INT AGGRESSION=12 FASTLOOP=false WORKSIZE=256
|-
|style="background:#EFEFFF;"| 5850 || 400 || -|| || - || 1000 || 1440 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.5 Win7 x64 || Memory 600MHz, Vcore 1.225, 73C, -k phatk WORKSIZE=128 VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false, 3% phatk mod
|-
|style="background:#EFEFFF;"| 5850 || 404|| -|| || - || 965 || 1440 || 2.5 || PCI-E 2.0 x16(@x8) || phoenixsvn / phatk2 / Ubuntu 11.04 / catalyst 11.8 || 5870 bios flash, Mem @322, fan@55%, Temp@83oC, 1.163Vcore, -k phatk2 VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false WORKSIZE=256
|-
|style="background:#EFEFFF;"| 5850 || 408 || -|| - || - || 999/275 || 1440 || 2.4 || PCI-E 2.1 x16 || phoenix 1.50 / phatk-mod / Ubuntu 10.04 || Fan 70%, temp < 60 deg C, Sapphire 5 heatpipe card, same flags as above/below (edit1- oops, no voltage tweaks... edit2- wow, phatk-mod makes a difference... catfish)
|-
|style="background:#EFEFFF;"| 5850 || 412 || -|| || - || 1010 || 1440 || 2.4 || PCI-E 2.0 1x>16x || phoenix 1.5 / phatk 3% mod / Win7 64 11.5 || VECTORS BFI_INT AGGRESSION=12 -k phatk
|-
|style="background:#EFEFFF;"| 5850 || 414.8 || -|| || - || 1018 || 450 || 2.4 || PCI-E 2.0 16x || GUIMiner / Win7 64 11.7 || I use Sapphire HD5850 Toxic 2GB and for OC TRIXX Sapphire Tweak Utility v4.0.2. 72 deg C, fan 100%, core 1018mhz, mem 450Mhz, stock voltage (1.163). proof: http://img23.imageshack.us/img23/2367/414upload.png GUIMiner parameters: -v -w256 -f1
|-
|style="background:#EFEFFF;"| 5850 || 420 || -|| || - || 1055 || 300 || 2.5 || PCI-E 2.0 1x>16x || phoenix 1.5 / phatk 3% mod / Win7 64 11.6 || Fan 80%, 66C, 1.250 Vcore, -k phatk PLATFORM=0 DEVICE=0 VECTORS BFI_INT AGGRESSION=8 And proof: http://i.imgur.com/s9hqs.png
|-
|style="background:#EFEFFF;"| 5850 || 431 || -|| || - || 1040 || 1440 || 2.4 || PCI-E 2.0 4x>16x || phoenix-svn / phatk kernel / Debian Wheezy AMD64 + fglrx 11.6 || fan 100%, vcore 1.1750 V, 72C, VECTORS BFI_INT AGGRESSION=15 FASTLOOP=false -k phatk, proof: http://imageshack.us/photo/my-images/199/431u.png/
|-
|style="background:#EFEFFF;"| 5850x3 || 1,010 || -|| || - || 850 || - || 2.4 || PCI-E 2.0 (x3) || GUIMiner || -v -w128 | MSI Afterburner settings: 850MHz core clock and 500MHz memory clock ||
|-
|style="background:#EFEFFF;"| 5850x6 || 2,135 || -|| || - || 900 || - || 2.5 || PCI-E 2.0 (6 total, 4 full length, 2 @ PCIE1x with risers || GUIMiner 24/8/2011 - poclbm || -v -f1 -w128 | Win 7 64Bit, Gigabyte GA-890FXA-UD5 motherboard, 4gb ram, AM3 cpu, Kingston SSD, Catalyst 11.8 drivers, guiminer switches: -v -f1 -w128, MSI Afterburner settings: 900MHz core clock and 1000MHz memory clock, cable risers required to fit all 6 cards, fans 100% Proof: http://i.imgur.com/6s7zv.jpg ||
|-
|style="background:#EFFFEF;"| 5870M || 152.5 || -|| || - || 750(OC) || 1000 || 2.1 || PCI-E 2.1 x16 || gui-miner (win-7) ||||
|-
|style="background:#EFFFEF;"| 5870M || 189.2 || -|| || - || 850(OC) || 1000 || 2.5 || PCI-E 2.1 x16 || Wins 7 64/gui-miner (win-7) || -v -w128 -f0 Graphics Overdrive setting 700->850 core clock & 900->1030memory clock . +35mhs over stock settings||
|-
|-
|style="background:#EFFFEF;"| 5870 || 313.65 || 1.668||1.65 || 188 || 850 || 1600 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
|style="background:#EFFFEF;"| 5870 || 313 || 1.665|| || 188 || 900? || 1600 || 2.3 || PCI-E 2.1 x16 || Diablo/Linux ||
|-
|style="background:#EFFFEF;"| 5870 || 343 || 1.824|| || 188 || 900? || 1600 || 2.1 || PCI-E 2.1 x16 || Diablo/Linux ||
|-
|style="background:#EFFFEF;"| 5870 || 355 || 1.888|| || 188 || 900? || 1600 || 2.1 || PCI-E 2.1 x16 || poclbm/Linux ||
|-
|style="background:#EFFFEF;"| 5870 || 340 || 1.809|| || 188 || 850 || 1600 || - || PCI-E 2.1 x16 || m0mchil's OpenCL || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26363#msg26363 source]
|-
|style="background:#EFFFEF;"| 5870 || 360 || 1.6822|| || 214 || 970 || 700 || - || PCI-E 2.0 x16 || m0mchil's OpenCL w7-64 || -f 0 -v -w 128 [http://www.bitcoin.org/smf/index.php?topic=6144.msg91959#msg91959 source]
|-
|style="background:#EFFFEF;"| 5870 || 379 || 2.015|| || 188 || 850 || 1600 || - || PCI-E 2.0 x16 || hashkill-0.2.5 alpha || -D -G2
|-
|style="background:#EFFFEF;"| 5870 || 397 || -|| || - || 930 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.48 || -k phatk VECTORS BFI_INT AGGRESSION=10 WORKSIZE=128
|-
|style="background:#EFFFEF;"| 5870 || 408 || 1.8888|| || 216 || 980 || 1600 || 2.1 || PCI-E 2.0 x16 || poclbm/Win7x64 || -f 20 -v -w 128, BIT_ALIGN, BFI_INT
|-
|style="background:#EFFFEF;"| 5870 || 400 || 1.9047|| || 210 || 950 || 1600 || 2.4 || PCI-E 2.0 x8 || Phoenix 1.3 || -k poclbm VECTORS AGGRESSION=7 FASTLOOP BFI_INT
|-
|style="background:#EFFFEF;"| 5870 || 421.5 || 2.007|| || 201 || 950 || 1600 || - || PCI-E 2.0 x16 || hashkill-0.2.5 alpha || -D -G2 (GPU OC to 900, memory downclocked to 900)
|-
|style="background:#EFFFEF;"| 5870 || 414 || 1.9255|| || 215 || 975 || 1600 || 2.4 || PCI-E 2.0 x16 || guiminer/w7x64 || -k poclbm -v -w 256 -f 1 VECTORS BITALIGN BFI_INT -- Memory Clock 300
|-
|style="background:#EFFFEF;"| 5870 || 420 || 2.0000|| || 210 || 950 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.48 || -k phatk VECTORS BFI_INT AGGRESSION=14 WORKSIZE=256 -- Memory Clock 300Mhz
|-
|style="background:#EFFFEF;"| 5870 || 421 || 1.9581|| || 215 || 975 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.47 || VECTORS BFI_INT AGGRESSION=13 -k phatk
|-
|style="background:#EFFFEF;"| 5870 || 440 || 2.0000|| || 220 || 995 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix ||
|-
|style="background:#EFFFEF;"| 5870 || 438 || 1.9819|| || 221 || 1000(OC) || 1600 || 2.1 || PCI-E 2.0 x16 || poclbm/Linux || -v -w 64 -f 1
|-
|style="background:#EFFFEF;"| 5870 || 458 || -|| || - || 1040 || 1600 || 2.1 || PCI-E 2.0 x16 || poclbm/Windows 7 64 || -v -w 256 -f 1 Crossfired, Water cooled, 916 Mhash/s total. Best dual gpu setup me thinks? The name is Mautobu.
|-
|style="background:#EFFFEF;"| 5870 || 435 || -|| || - || 990 || 300 || 2.4 || PCI-E 2.0 x8 || LinuxCoin v0.2b phoenix/phatk || (Powercolor brand) -k phatk VECTORS BFI_INT WORKSIZE=256 AGGRESSION=11 FASTLOOPS=false
|-
|style="background:#EFFFEF;"| 5870 || 445 || 2.28||2.34 || 195 || 1005 || 335 || 2.4 || PCI-E 2.0 x4 || Ubuntu 11.04 phoenix/phatk || (Asus brand, volts = 1'072) -k phatk VECTORS BFI_INT WORKSIZE=256 AGGRESSION=12 FASTLOOPS=false -a 7 (-a 10)
|-
|style="background:#EFFFEF;"| 5870 || 430 || || || || 980 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.48/Windows 7 64 || -k phatk VECTORS BFI_INT AGGRESSION=14 WORKSIZE=256 -- Memory Clock 300Mhz
|-
|style="background:#EFFFEF;"| 5870 || 432 || || || || 985 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.73/Windows 7 64 || -k phatk VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128 Memory Clock=900Mhz Asus 76C Fan=60% 65F ambient
|-
| 5870 || 437 || || 1.90|| || 960 || - || 2.1 || PCI-E 2.0 x1 || phoenix 1.50 + phatk || Card is clocked with BIOS flash @ 960Mhz Core and 300Mhz Memory. More information and pictures: http://forum.bitcoin.org/index.php?topic=7216.msg324521#msg324521
|-
|style="background:#EFFFEF;"| 5870 || 453 || || || || 980 || 1600 || 2.5 || PCI-E 2.1 x16 || Phoenix 1.50/Windows 7 64 catalyst 11.6 phatk 2.2 || -k phatk VECTORS BFI_INT AGGRESSION=12 WORKSIZE=256 FASTLOOPS=false -- Memory Clock 350Mhz Vcore 1.163v
|-
|style="background:#EFFFEF;"| 5870 || 460 || || || || 1050 || 1600 || 2.4 || PCI-E 2.0 x16 || Guiminer || -k phatk VECTORS BFI_INT AGGRESSION=14 WORKSIZE=256 -- Memory Clock 300Mhz vcore @ 1225mV
|-
|style="background:#EFFFEF;"| 5870 || 460 || || || || 1020 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.50/Windows 7 64 || VECTORS BFI_INT AGGRESSION=12 WORKSIZE=256 -k phatk -- Memory Clock 300Mhz vcore @ 1225mV, 3% phatk mod
|-
|style="background:#EFFFEF;"| 5870x2 (CF) || 864 || -|| || - || 900 || 3200 || 2.1 || PCI-E 2.1 x16 || guiminer || -k phatk VECTORS FASTLOOP=false AGGRESSION=7 BFI_INT WORKSIZE=128 (Same flags per GPU)
|-
|style="background:#EFFFEF;"| 5870x2 (Ares) || 620 || -|| || - || 850 || 3200 || 2.1 || PCI-E 2.1 x16 || guiminer || -v -w 128
|-
|style="background:#EFFFEF;"| 5870x2 (Ares) || 826 || 0.751|| || 1100 || 950 || 3200 || 2.1 || PCI-E 2.1 x16 || phoenix 1.4 w/ Phtak || AGGRESSION=13 WORKSIZE=128 VECTORS BFI_INT Memory @ 300MHz
|-
|style="background:#EFFFEF;"| 5870x2 (Ares) || 826 || 1.18|| || 700 || 935 || 3200 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 w/ Phatk || AGGRESSION=13 WORKSIZE=256 VECTORS BFI_INT FASTLOOP=false, memory @ 319 MHz, Windows 7 32-bit
|-
|style="background:#EFFFEF;"| 5870x2 (Ares) || 878 || 0.585|| || 1500 || 1000 || 3200 || 2.1 || PCI-E 2.1 x16 || phoenix 1.7 w/ Phtak || AGGRESSION=13 WORKSIZE=128 VECTORS BFI_INT Memory @ 300MHz
|-
| 5870x4 || 1784 || || 1.29|| || 960 || - || 2.1 || PCI-E 2.0 x1 || phoenix 1.50 + phatk + [https://bitcointalk.org/index.php?topic=7964.0 Version 2.2 Improvement] || Cards are clocked with BIOS flash @ 960Mhz Core and 300Mhz Memory. More information and pictures: http://forum.bitcoin.org/index.php?topic=7216.msg324521#msg324521
|-
|style="background:#EFFFEF;"| 5870x6 || 2568 || -|| || 1200 || 970 || -|| 2.4 || PCI-E 2.1 x16 || poclbm/debian32bit || -v -w128, voltage default, Mem downclocked to 300 MHz, Fan 80-90% (+ 4x12cm fun 1900rpm), Temp 6x 70-75C. Whole computer comsumpts 1280Watt. Using PCI-E risers 16x-16x to use 6 GPU cards
|-
|style="background:#FFEFEF;"| 5970 || 530 || 1.803||0.53 ? || 294 || 725 || 3200 || 2.4.595.10 || PCI-E 2.1 x16 || poclbm/201103.beta3/Windows || -v -w128 -f60
|-
|style="background:#FFEFEF;"| 5970 || 535.06 || 1.820|| || 294 || 725 || 3200 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
|style="background:#FFEFEF;"| 5970 || 560 || 1.905|| || 294 || 725 || 3200 || - || PCI-E 2.1 x16 || Diablo ||
|-
|style="background:#FFEFEF;"| 5970 || 565 || 1.922|| || 294 || 725 || 3200 || 2.1 || PCI-E 2.1 x16 || clmine2 ||
|-
|style="background:#FFEFEF;"| 5970 || 604 || 2.054|| || 294 || 725 || 3200 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
|style="background:#FFEFEF;"| 5970 || 645 || 1.875|| || 344 || 850 || 3200 || 2.1 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || -f1, Debian 6, fglrx-driver 10.9.3
|-
|style="background:#FFEFEF;"| 5970 || 740 || 2.1511|| || 344 || 850 || 3200 || 2.1 || PCI-E 2.1 x16 || phoenix/1.3 || AGGRESSION=12 WORKSIZE=128 VECTORS BFI_INT, memory clock @ 300MHz
|-
|style="background:#FFEFEF;"| 5970 || 755 || 2.2076|| || 342 || 848 || 3200 || 2.1 || PCI-E 2.1 x16 || poclbm 28-04-11 || -f 1 -w 256 -v, Ubuntu 10.10, fglrx 11.4, memory clock @ 300MHz
|-
|style="background:#FFEFEF;"| 5970 || 802 || 2.31|| || 347 || 850 || 3200 || 2.4 || PCI-E 2.1 x16 || phoenix poclbm Ubuntu 11.04 || -q 6 -k AGGRESSION=19 WORKSIZE=128 BFI_INT VECTORS, fglrx 11.4, mem clock @ 1000MHz
|-
|style="background:#FFEFEF;"| 5970 || 820 || ??? || || ??? || 910 || 3200 || 2.4 || PCI-E 2.1 x1 || Phoenix 1.5 Win7 || AGGRESSION=12 WORKSIZE=256 BFI_INT VECTORS -k phatk, 11.5, Mem @ 300MHz, 1.110v, 3% phatk mod
|-
|style="background:#FFEFEF;"| 5970 || 822.2 || -|| || - || 950 || 3200 || 2.4 || PCI-E 2.1 x16 || phoenix win7 || -k phatk -q 6 AGGRESSION=20 WORKSIZE=128 BFI_INT VECTORS, but with this increasing difficulty mining becomes pretty pointless
|-
|style="background:#FFEFEF;"| 5970 || 833 || -|| || - || 930 || 3200 || 2.4 || PCI-E 2.1 x16 || phoenix 1.7.5, win7 x64, catalyst 11.7 || -k phatk AGGRESSION=13 WORKSIZE=256 BFI_INT VECTORS fastloops=false. memory@300mhz, 1.125v, fan 100%, 73C core temp, 95c voltage controllers. it will clock higher but not stable without a voltage increase and i fear for the VRMs
|-
|style="background:#FFEFEF;"| 5970 || 863.4 || -|| || - || 955 || 3200 || 2.4 || PCI-E 2.1 x16 || Diablo - Debian || -v 2 -w 256 (XFX Radeon HD 5970 Black Edition)
|-
| 6310M || 9.821 || 0.545|| || 18 || 500 || 80 || 2.4 || Integrated/APU || poclbm-gui -v -w128 || HP DM1z 18W TDP is shared with the CPU
|-
| 6450 || 27.0 || 1.5 || - || 18 || 625 || 160 || 2.4 || PCI-E 2.0 x16 || guiminer/poclbm 2011-06-14 || -v -w128 Sapphire HD6450 1gb ddr3 Ubuntu 11.04 64bit
|-
| 6470M || 24.1 || - || ||- || - || - || 2.1 || Integrated/APU || guiminer ||
|-
| 6470M || 31.0 || - || ||- || - || - || 2.1 || Integrated/APU || phoenix 1.48 ||
|-
| 6490M || 17.18 || - || ||- || - || - || - || PCI-E 2.1 x16 || phoneix 1.50 with poclbm, Mac OS X 10.6.7 || MacBook Pro 2,8 VRAM: 256MB. phoenix -k poclbm VECTORS BFI_INT FASTLOOP
|-
| 6490M || 16.289 || 0.708|| || 23 || - || - || - || PCI-E 2.1 x16 || poclbm-mod (Mac OS X 10.6.7) || MacBook Pro early 2011
|-
| 6490M || 15.21 || - || ||- || - || - || - || - || [http://forum.bitcoin.org/index.php?topic=8994.0 DiabloMiner GUI] v2011-05-22 / Mac OS X 10.6.7 || Model: MacBookPro8,2 VRAM: 256MB
|-
| 6490M || 32.1 || - || ||- || - || - || - || - || guiminer 2011-07-01 with poclbm (Win7-x64) ||MacBookPro8,2 (WinX64) -v -w128 -f0
|-
| style="background:#FFDD00;"| 6520G || 33.8 || - || || - || 400 || 320 || - || Integrated/APU || guiminer 2011-07-01 with OpenCL (Win7-64bit) || -v -w128 on Toshiba L775D-S7222
|-
|style="background:#FFDD00;"| 6550D || 67.6 || -|| || - || 600 || 400 || 2.5 || FM-1 || guiminer 2011-07-01 with OpenCL (Win7-64bit) || -v -w128 -f2
|-
|style="background:#FFDD00;"| 6570 || 68.0 || 1.133|| || 60 || 650 || 480 || 2.4 || PCI-E x16 || guiminer 2011-05-21 with poclbm (Win7-32bit) || no extra option for miner . Sapphire 6570 gddr5 512mb
|-
|style="background:#FFDD00;"| 6570 || 82.1 || 1.368|| || 60 || 650 || 480 || 2.4 || PCI-E x16 || guiminer 2011-05-21 with poclbm (Win7-32bit) || -v -w128 . Sapphire 6570 gddr5 512mb
|-
|style="background:#FFDD00;"| 6570 || 86.0 || 1.95 || - || 44 || 650 || 480 || 2.4 || PCI-E x16 || guiminer/poclbm 2011-06-14 || -v -w128 Sapphire Ultimate HD6570 1gb ddr3 Ubuntu 11.04 64bit
|-
| 6630M || 48.80 || -|| || - || - || - || - || - || [http://forum.bitcoin.org/index.php?topic=8994.0 DiabloMiner GUI] v2011-06-18 / Mac OS X 10.7 || Mac Mini 2011 MC816D/A
|-
| 6630M || 63.00 || -|| || - || 600 || 480 || 2.5 || PCI-E 2.0 x16 || DiabloMiner Windows || Lenovo ThinkPad Edge E320 (card overclocked using Sapphire TRIXX)
|-
| 6670 || 102.20 || -|| || - || 800 || - || - || PCI-E 2.1 x16 || poclbm/Debian sid || -v -f 0 -w 128
|-
| 6670 || 104.00 || - || 1.0 || - || 820 || - || - || PCI-E 2.1 x16 || guiminer(poclbm)/Win 7|| -v -a4 -f15 -d0 -w64
|-
| 6670 || 110.00 || - || 1.0 || - || 850 || - || - || PCI-E 2.1 x16 || guiminer(poclbm)/Win 7|| -v -f 0 -w 128 -q 6
|-
| 6750 || 167.59 || -|| || - || 870 || - || - || PCI-E 2.1 x16 || guiminer || -v -f30 -w128
|-
| 6750 || 142 || -|| || 150 || 700 || - || - || PCI-E 2.1 x16 || poclbm || -v -w128, Gigabyte SL (passive cooler), watts is TDP, card runs very hot (>90°C)
|-
| 6750M || 41.48 || -|| || - || 870 || - || - || PCI-E 2.1 x16 || diablominer ||
|-
| 6750M || 60 || -|| || - || - || - || - || - || diablominer OSX 10.7 WorkSize=128||
|-
| 6770 || 180 || -|| || - || 850 || 1200 || - || - || guiminer || -v -w128 , this was an XFX (OEM) model, GPU @ 850 MHz, mem @ 1200 MHz; I pushed it up to 190 Mhash/s briefly by overclocking, but it crashed the system above that
|-
| 6770 || 202 || -|| || - || 960 || 800 || - || PCI-E 2.1 x1,x4,x8,x16 || phoenix 1.48 || Sapphire 6770 (standard) -q2 -k poclbm DEVICE=0 AGGRESSION=10 VECTORS WORKSIZE=128 BFI_INT FASTLOOP (The PCI-E speed does not affect the mining speed)

|-
| 6770 || 217 || -|| || - || 960 || 800 || - || PCI-E x16 || Guiminer with phoenix || Sapphire 6770 -k phatk VECTORS BFI_INT WORKSIZE=128 FASTLOOP=false AGGRESSION=12 with https://forum.bitcoin.org/index.php?topic=22965.0 modification
|-
| 6770 || 235 || -|| || - || 1010 || 300 || 2.4 || PCI-E 2.0 x8 || Phoenix 1.50 || Sapphire 6770 -k phatk PLATFORM=0 DEVICE=0 VECTORS BFI_INT WORKSIZE=256 FASTLOOP=false AGGRESSION=13 3% mod https://forum.bitcoin.org/index.php?topic=22965.0 and AS5 paste on core w/ external 12" fan 50C full load. Stock voltage.
|-
| 6770x2 || 470 || -|| || - || 1010 || 300 || 2.4 || PCI-E 2.0 x8 || Phoenix 1.50 || Sapphire 6770 -k phatk PLATFORM=0 DEVICE=0 VECTORS BFI_INT WORKSIZE=256 FASTLOOP=false AGGRESSION=13 3% mod https://forum.bitcoin.org/index.php?topic=22965.0 and AS5 paste on core w/ external 12" fan 50C full load. Stock voltage.
|-
| 6790 || 220 || 1.467|| || 150 || 800 || - || - || PCI-E 2.1 x16 || Phoenix 1.48 || -k phatk BFI_INT FASTLOOP AGGRESSION=12 VECTORS OC'd to 1ghz, underclocked mem to 300, voltage at 1175
|-
| 6790 || 219 || 1.467|| || 150 || 960 || - || - || PCI-E 2.1 x16 || guiminer || -v -f0 -w128 / GPU OC to 960MHz under Windows7 64bit
|-
|style="background:#EFEFFF;"| 6850 || 171.59 || 1.351||1.07 || 127 || 775 || 960 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
|style="background:#EFEFFF;"| 6850 || 196 || -|| || - || 850 || 960 || - || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 0
|-
|style="background:#EFEFFF;"| 6850 || 220 || 1.236(*)|| || 178(*) || 1000(OC) || 960 || 2.4RC1 || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 30 (*: Overclocked wattage calculated [http://bakkap.free.fr/Misc/wCalc.html here] )
|-
|style="background:#EFEFFF;"| 6850 || 234.8 || ||- || - || 940 || 960 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.3 || AGGRESSION=8 WORKSIZE=128 VECTORS BFI_INT
|-
|style="background:#EFEFFF;"| 6850 || 236.0 || ||- || - || 940 || 960 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.4 || -k phatk AGGRESSION=12 WORKSIZE=128 VECTORS BFI_INT, Core @ 900MHz, Memory @ 300MHz
|-
|style="background:#EFEFFF;"| 6850 || 244.2 || ||- || - || 960 || 960 || 2.1 || PCI-E 2.0 x16 || poclbm june-2011 || -v -w 128
|-
|style="background:#EFEFFF;"| 6850 || 245.1 || ||- || 200 || 940 || 960 || 2.4 || PCI-E 2.0 x16 || guiminer (Phoenix) || Sapphire 6850 (Memory @1000MHz); Win7 64bit; flags: -k phatk VECTORS BFI_INT FASTLOOP=false AGGRESSION=14 WORKSIZE=128
|-
|style="background:#EFEFFF;"| 6850 || 250 || 1.612(*) ||- || 155(*) || 940 (OC) || 960 || 2.4 || PCI-E 2.0 x16 || AOCLBF 1.74 (Phoenix 1.5**) @Win7/x64 || XFX 6850 (Memory @840MHz; Vdcc @1.148V; Fan @74%; Temp @70C; System @39C); flags: -k phatk BFI_INT FASTLOOP VECTORS AGGRESSION=11 WORKSIZE=128 (*: Overclocked wattage calculated [http://bakkap.free.fr/Misc/wCalc.html here] / **: [http://forum.bitcoin.org/index.php?topic=22965.0 Tainted Kernel])
|-
|style="background:#EFEFFF;"| 6850 || 262.5 || || - || - || 965 || 525 || 2.4 || PCI-E 2.0 x16 || guiminer / poclbm || -v -f 0 -w 128 (HIS 6850 flashed to HIS 6870 BIOS)
|-
|style="background:#EFEFFF;"| 6850 || 267.2 || ||1.67 || - || 1010(OC) || 960 || 2.4 || PCI-E 2.0 x16 || guiminer / phoenix 1.50 || -k phatk VECTORS BFI_INT AGGRESSION=11 worksize=128 FASTLOOP=false
|-
|style="background:#EFEFFF;"| 6850 || 301.4 || ||1.67 || - || || || 2.4 || PCI-E 2.0 x16 || guiminer / poclbm || -v -f 2 -w 128 clock @ 985 mem @ 890
|-
|style="background:#FFFF00;"| 6870 || 232.47 || 1.540||1.22 || 151 || 900 || 1120 || - || PCI-E 2.1 x16 || poclbm -v -w 128 ||
|-
|style="background:#FFFF00;"| 6870 || 277.47 || -|| || - || 940 || 1120 || - || PCI-E 2.1 x16 || Phoenix 1.3 || AGGRESSION=8 WORKSIZE=128 VECTORS BFI_INT
|-
|style="background:#FFFF00;"| 6870 || 271 || 1.807|| || 150 || 940 || 1120|| 2.4 || PCI-E 2.0 x16 || poclbm -v -w 128 || Debian 6.0.1 x86_64
|-
|style="background:#FFFF00;"| 6870 || 279 || 1.847(?)|| || 151(?) || 900 || 1120 || 2.4 || PCI-E 2.1 x16 || hashkill-0.2.5 alpha cat 11.4 sdk 2.4 || -G2 -D stock clocks, debian linux 64bit
|-
|style="background:#FFFF00;"| 6870 || 281.7 || 1.172 (stock)|| || - || 980 || 1120|| 2.4 || PCI-E 2.1 x16 || guiminer-v2011-06-09 || xfx6870, flags: -v 19 -w 128, win7 32-bit
|-
|style="background:#FFFF00;"| 6870 || 293.13 || || ||- || 945 || 1050|| 2.5 || PCI-E 2.1 x16 || Phoenix 1.5 Phatk || xfx6870, Catalyst 11.6, 1.5 Phoenix flags: -k phatk FASTLOOP=false DEVICE=0 VECTORS BFI_INT AGGRESSION=13 WORKSIZE=128; http://forum.bitcoin.org/index.php?topic=25860.0 Kernel Patch; http://forum.bitcoin.org/index.php?topic=6458.0 Cmd; http://developer.amd.com/tools/gDEBugger/Pages/default.aspx No Crossfire Required; runs faster without crossfire 1% + additional 3% from update
|-
|style="background:#FFFF00;"| 6870 || 294 || || ||- || 980 || 1120|| 2.4 || PCI-E 2.1 x16 || phoenix phatk || xfx6870, 340MHz memory clock, Catalyst 11.6, flags: BFI_INT VECTORS AGGRESSION=9 WORKSIZE=256
|-
|style="background:#FFFF00;"| 6870 || 300 || - || || - || 940 || 1120 || 2.5 || PCI-E 2.1 x16 || Phoenix 1.6.2 phatk2 || xfx6870 Black Edition, 340MHz Memory Clock, Catalyst 11.6, VECTORS BFI_INT AGGRESSION=13 WORKSIZE=128, Debian Linux 64-Bit, Fan @ 50%, Temp @ 75C
|-
|style="background:#FFFF00;"| 6870 || 302 || - || || - || 940 || 1120 || 2.5 || PCI-E 2.1 x16 || cgminer 2.1.2 || xfx6870 Black Edition, 340MHz Memory Clock, Catalyst 11.6, -w 256 -I 9, Debian Linux 64-Bit, Fan @ 50%, Temp @ 75C
|-
|style="background:#FFFF00;"| 6870 || 300.06 || 1.830|| || 164 || 1020 || 1120 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.4 cat 11.4 || VECTORS BFI_INT AGGRESSION=8 fastloop mem clock 344
|-
|style="background:#FFFF00;"| 6870 || 300 || 1.72|| || 174 || 1038 || 1120 || 2.4 || PCI-E 2.1 x16 || poclbm windows7x86 cat 11.4 || -v -w128 -f1 mem clock 360, fan 100% temp 73C
|-
|style="background:#CCFF00;"| 6870 || 307 || 1.72|| || 174 || 1001/\1001 || 1120 || 2.4 || PCI-E 2.1 x16 || poclbm windows7x86 cat11.8 || -v -w128 -f5,85°C
|-
|style="background:#FFFF00;"| 6870 || 310 || -|| || - || 1035 || 1120 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 phatk 11.5 sdk 2.4 || BFI_INT VECTORS FASTLOOP=false AGGRESSION=12 WORKSIZE=128, mem clock @ 300MHz, voltage @ 1.300
|-
|style="background:#FFFF00;"| 6870 || 310 || -|| || - || 975 || 1120 || 2.4 || PCI-E 2.1 x16 || phoenix phatk linuxcoin || BFI_INT VECTORS FASTLOOP=false AGGRESSION=13 WORKSIZE=128, mem clock @ 340MHz, core clock @ 970MHz, flashed bios, 72 degrees w/ fan @ 68%, GIGABYTE SOC
|-
|style="background:#CCFF00;"| 6870 || 312 || -|| || - || 975 || 300|| 2.4 || PCI-E 2.1 x16 || phoenix 1.50 / phatk / Windows 7 x64 SP1 || VECTORS BFI_INT AGGRESSION=11 FASTLOOP=false WORKSIZE=256, mem clock @ 300MHz, voltage @ 1.300, Fan @ 45%, Temp @ 62C, MSI 6870 HAWK.
|-
|style="background:#FFFF00;"| 6870 || 314 || -|| || - || 1030 || 1120|| 2.4 || PCI-E 2.1 x16 || phoenix 1.50 / phatk / Linux || VECTORS BFI_INT AGGRESSION=11 FASTLOOP=false WORKSIZE=256
|-
|style="background:#FFFF00;"| 6870 || 316 || -|| || - || 1030 || 1120 || 2.4 || PCI-E 2.1 x16 || guiminer 2011-06-09 using phoenix (Win7-32bit) || -k phatk platform=0 device=0 VECTORS BFI_INT AGGRESSION=11 worksize=128 FASTLOOP=false, mem clock @ 228MHz, voltage @ 1.25, Fan @ 40%, Temp @ 73C
|-
|style="background:#FFFF00;"| 6870 || 322 || 1.882|| || 170 || 1050 || 1120 || 2.4 || PCI-E 2.1 x16 || phoenix 1.47 phatk 11.5 sdk 2.4 || BFI_INT VECTORS FASTLOOP=false AGGRESSION=12 WORKSIZE=256, mem clock @ 400MHz
|-
|style="background:#FFFF00;"| 6870 || 329 || -|| || - || 1075 || 1120|| 2.4 || PCI-E 2.1 x16 || phoenix 1.48 phatk 11.5 sdk 2.4 || BFI_INT VECTORS FASTLOOP=false AGGRESSION=11 WORKSIZE=256
|-
|style="background:#FFFF00;"| 6870 || 245|| -|| || - || 900|| 1120 || 2.4 || PCI-E 2.0 x16 || ph rising 1.45 phoenix 1.50 phatk 11.5 sdk 2.4 || HD5xxx+ Fastloop phatk AGGRESSION=10
|-
|style="background:#FFFF00;"| 6870 || 297|| -|| || - || 1000|| 1120 || 2.4 || PCI-E 2.0 x16 || ph rising 1.62 phoenix 1.50 phatk 11.5 sdk 2.4 || Vectors HD5xxx+ Fastloop phatk AGGRESSION=11 WORKSIZE=128
|-
|style="background:#FFFF00;"| 6870 || 321|| -|| || - || 1050|| 1120 || 2.4 || PCI-E 2.1 x8 ||aoclbf 1.7 phoenix 1.50 11.6|| Vectors HD5xxx+ phatk AGGRESSION=13 WORKSIZE=256, Memory=325MHz, Volts=1.3V, Fan~55%, Temps~70C
|-
|style="background:#FFFF00;"| 6870 || 332 || -||1.74 || - || 1050 || 1120 || 2.4 || PCI-E 2.1 x16 || guiminer 2011-06-14 using phoenix (Win7-32bit) || -k phatk platform=0 device=0 VECTORS BFI_INT AGGRESSION=13 worksize=128 FASTLOOP=false, mem clock @ 228MHz, voltage @ 1.3, Fan @ 60%, Temp @ 74C, flash and browser hardware acceleration disabled, aero enabled.
|-
|style="background:#FFFF00;"| 6870 || 295 || 2.02||1.64 || 146 || 950 || 1120 || 2.4 || PCI-E 2.1 x16 || hashkill latest as of 7/6/11 (ubuntu 11.4) || hashkill-gpu -p bitcoin user:pass:server -D, mem clock 850, voltage @ 1.175, Fan @ 70%, Temp @ 71C.
|-
|style="background:#FFFF00;"| 6870 || 339.25 || - || - || - || 1090 || 1120 || 2.6 || PCI-E 2.1 x16 || Phoenix 1.7.3 cat 12.1 || Mem @ 350Mhz Clock @ 1090 Voltage 1.337 fan @ 100 Temp @ 75 diapolo's modified phatk kernel -k phatk_dia platform=0 device=0 VECTORS2 AGGRESSION=11 worksize=64 FASTLOOP=false BFI_INT
|-
|style="background:#FFFF00;"| 6870 || 264.5 || - || - || - || 980 || 1050 || ??? || PCI-E 2.1 x16 || GUIMiner v2011-05-01 || Stays around 66*C if I keep the side panel off and the room well ventilated. Card is PowerColor branded. Windows 7 Ultimate SP1 with Classic theme. Fan is at 100%.||-v -w128
|-
|style="background:#FFFF00;"| 6870x4 || 1150|| -|| 1.2 || - || 900|| 1050 || 2.4 || PCI-E 2.0 x16 || phoenix 1.7 (Win7-64bit) || -k phatk platform=0 device=0-3 VECTORS BFI_INT AGGRESSION=11 worksize=128 FASTLOOP=false
|-
|style="background:#FFFF00;"| 6870x4 || 1180 || -|| - || 145 || 950 || 1120 || 2.4 || PCI-E 2.1 x16 || poclbm/debian32bit || -v -w128, Gigabyte SOC. voltage 1.175 (default), GPU default 950 MHz, Mem downclocked to 300 MHz, Fan 4x100% (+ 2x12cm fun 1300rpm), Temp 4x75C (in summer).
|-
|style="background:#FFFF00;"| 6870x4 || 1200 || -|| - || 150 || 970 || 1120 || 2.4 || PCI-E 2.1 x16 || poclbm/debian32bit || -v -w128, Gigabyte SOC. voltage 1.175 (default), GPU overclocked from 950 to 970 MHz, Mem downclocked to 300 MHz, Fan 4x100% (+ 2x12cm fun 1300rpm), Temp 4x75C (in summer). Unstable with GPU@975 MHz.
|-
| 6950 || 272 || -||0.90 || - || 900 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1150 mV, AGGRESSION = 7, BFI_INT, MSI 6950
|-
| 6950 || 291 || -|| || - || 920 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1200mV, AGGRESSION = 7, BFI_INT, MSI 6950
|-
| 6950 || 295 || -|| || - || 930 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1275mV, AGGRESSION = 7, BFI_INT, MSI 6950
|-
| 6950 || 300 || -|| || - || 940 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1300mV, AGGRESSION = 7, BFI_INT, MSI 6950
|-
| 6950 || 295 || 1.844(?)|| || 160(?) || 810 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || unlocked shaders, default mem 1250
|-
| 6950 || 314 || -|| || - || 800 || 1408 || 2.4.595.0 || PCI-E 2.1 x16 || guiminer/poclbm 05-01-11 || -v -f30 -w128 default mem 1250 Stock Sapphire 6950 1gb
|-
| 6950 || 325 || 1.635(?)|| || 200(?) || 885 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || unlocked shaders, default mem 1250
|-
| 6950 || 332 || ~1.95 || ~1.2 || ~170 || 840 || 1408 || 2.5.684.212 || PCI-E 2.1 x16 || guiminer/poclbm 2011-06-14 || -v -w 128 -f 0, WinXP x86, Cat11.6b, desktop on IGP, Sapphire 1GB w/ HW locked BIOS, +40MHz GPU OC, 160W ACP + 5% OC = 170W new estimated ACP
|-
| 6950 || 333 || ~1.95 || ~1.2 || ~170 || 840 || 1408 || 2.4.650.9 || PCI-E 2.1 x16 || guiminer/poclbm 2011-06-14 || -v -w 128 -f 0, WinXP x86, Cat11.6, desktop on IGP, Sapphire 1GB w/ HW locked BIOS, +40MHz GPU OC, 160W ACP + 5% OC = 170W new estimated ACP
|-
| 6950 || 338 || ~1.84 || - || ~184 || 860 || 1408 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.50/poclbm kernel || Sapphire 2GB card w/ HW locked BIOS; Cat 11.6, Win7 x64; core @ 860MHz & 1087mV (OC + undervolt), mem @ 860MHz; cmd line args: VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128; power and MH/J calculated using Power = C*f*v^2 w/ assumption of 175 W at stock settings w/ 100% GPU util. (not measured)
|-
| 6950 || 340 || - || ||- || 895 || 1408 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm 05-21-11 || -v -w 128, mem @ 500, 1200 mV, MSI 6950
|-
| 6950 || 340 || - || ||- || 800 || 1536 ||(?) || PCI-E 2.1 x16 || guiminer/poclbm 05-21-11 || -v -f30 -w128 default mem 1250,Sapphire 6950 1gb, unlocked shaders
|-
| 6950 || 343 || 2.14 || - || 160 || 840 || 1536 || 2.4 || PCI-E 2.1 x16 || phoenix 06-27-11 || VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128 FASTLOOP=false, HIS H695FN2G2M 2GB, mem @ 720, Kill-a-Watt measured
|-
| 6950 || 344 || ~2.02 || ~1.27 || ~170 || 840 || 1408 || 2.5.684.212 || PCI-E 2.1 x16 || poclbm/20110709 || -v -w 128 -f 0, WinXP x86, Cat11.6b, desktop on IGP, Sapphire 1GB w/ HW locked BIOS, +40MHz GPU OC, 160W ACP + 5% OC = 170W new estimated ACP
|-
| 6950 || 349 || 1.745(?)|| || 200(?) || 800 || 1408 || - || PCI-E 2.1 x16 || guiminer/poclbm 05-21-11 || -v -f30 -w128, xfx 6950 xxx 1gb, locked shaders, core 900, mem 650, 79° C
|-
| 6950 || 351 || ~1.91 || - || ~184 || 860 || 1408 || 2.4 || PCI-E 2.1 x16 || GUIminer/poclbm v2011-07-01 || Sapphire 2GB card w/ HW locked BIOS; Cat 11.6, Win7 x64; core @ 860MHz & 1087mV (OC + undervolt), mem @ 860MHz; cmd line args: -v -w 128 -f 0; (same system as the 338 MH/s result above using Phoenix)
|-
| 6950 || 360 || 1.8(?)|| || 200(?) || 970 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || unlocked shaders, default mem 1250
|-
| 6950 || 360 || -|| || - || 870 || 1375 || - || PCI-E 2.1 x16 || guiminer/poclbm || flashed with 6970 BIOS, -v -f30 -w128
|-
| 6950 || 365 || -|| || - || 925 || 1408 || - || PCI-E 2.1 x16 || guiminer/poclbm || stock bios, -v -f0 -w128, MSI twinfrozr III 2GB
|-
| 6950 || 344.4 || -|| || - || 800 || 1536 || - || PCI-E 2.1 x16 || guiminer/poclbm || Powercolor 6950 @ shadermod on original Bios 6950 / 1000mV 850/730, +20% powertune, Fan @ 60%, -v -w128 -f1.
|-
| 6950 || 352.8 || -|| || - || 820 || 1536 || - || PCI-E 2.1 x16 || guiminer/poclbm || Powercolor 6950 @ shadermod on original Bios 6950 / 1000mV 850/730, +20% powertune, Fan @ 60%, -v -w128 -f1.
|-
| 6950 || 366.4 || -|| || - || 850 || 1536 || - || PCI-E 2.1 x16 || guiminer/poclbm || Powercolor 6950 @ shadermod on original Bios 6950 / 1000mV 850/730, +20% powertune, Fan @ 60%, -v -w128 -f1.
|-
| 6950 || 383 || -|| || - || 975 || 1408 || - || PCI-E 2.1 x16 || guiminer/poclbm || stock bios, -v -f0 -w128, voltage 1.274 @72c MSI twinfrozr III 2GB
|-
| 6950 || 388.4 || -|| || - || 900 || 1536 || - || PCI-E 2.1 x16 || guiminer/poclbm || Powercolor 6950 @ shadermod on original Bios 6950 / 1000mV 850/730, +20% powertune, Fan @ 60%, -v -w128 -f1.
|-
| 6950 || ~400 || -|| || - || 895 || 320 || 1536|| PCI-E 2.1 x16 || GUIMiner 24th Aug 2011 || Sapphire HD6950 Shader unlock mod 1408>1536 / +20% Power control, Fan @ 55%, Flags:-v -f2 -w64 -r5.Note this keeps temps under 80oC which is needed for this to be stable.Moderate fan noise.Power use is ~200W.
|-
| 6950 || 403 || -|| || - || 939 || 685 || - || PCI-E 2.1 x16 || phoenix-1.50/phatk || ASUS EAH6950 ([http://www.techpowerup.com/vgabios/90661/Asus.HD6970.2048.101124.html (Ref. 6950 Flashed -> 6970)]) / +10% overdrive volt., Fan @ 90%, VECTORS BFI_INT WORKSIZE=128 AGGRESSION=13. Overclocked from 880 -> 939 with MSI Aferburner
|-

| 6950 || 408.8 || -|| || - || 925 || 1536 || - || PCI-E 2.0 x16 || cgminer 2.12 || GIGABYTE GV-R695D5-2GD-B @ shadermod on original Bios 6950, mem@625, V=1100mv Fan @ 60%. Windows 7x64, Catalyst 11.9
|-

| 6950 || 410.4 || -|| || - || 950 || 1536 || - || PCI-E 2.1 x16 || guiminer/poclbm || Powercolor 6950 @ shadermod on original Bios 6950 / 1000mV 850/730, +20% powertune, Fan @ 60%, -v -w128 -f1.
|-
| 6950 || 418.8 || -|| || - || 940|| 1536 || - || PCI-E 2.1 x16 || guiminer/poclbm || Gigabyte OC 1GB, shadermod, voltage locked 1.175, mem 450, -w128 -v -f0, ATI Tray Tool
|-
| 6950 || 425.3 || -|| || - || 950/850 || 1536 || - || PCI-E 2.1 x16 || phoenix-1.50/phatk2 (Ubuntu natty) || Asus 1GB DirectCU, shadermod on OEM BIOS, OEM 1.1v, AMDOverdriveCtrl for 950 core 850 mem, 20% overdrive, flags VECTORS2 BFI_INT FASTLOOP=false AGGRESSION=13 WORKSIZE=128
|-
| 6950 || 432.4 || -|| || - || 1000 || 1536 || - || PCI-E 2.1 x16 || guiminer/poclbm || Powercolor 6950 @ shadermod on original Bios 6950 / 1000mV 850/730, +20% powertune, Fan @ 60%, -v -w128 -f1.
|-
| 6950 || 454.4 || -|| || - || 1050 || 1536 || - || PCI-E 2.1 x16 || guiminer/poclbm || Powercolor 6950 @ shadermod on original Bios 6950 / 1000mV 850/730, +20% powertune, Fan @ 60%, -v -w128 -f1.
|-
| 6950 || 417 || 2.085(?)|| || 200(?) || 975 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || guiminer/poclbm || unlocked shaders, +20% overdrive, mem @ 1250, fan @ 77%, temp 64C, -v -w128, gpu core @ 1145mV
|-
| 6950 || 428 || 2.14(?)|| || 200(?) || 1000 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || guiminer/poclbm || unlocked shaders, +20% overdrive, mem @ 1250, fan @ 80%, temp 64C, -v -w128, gpu core @ 1160mV
|-
| 6950 || 440 || || || || 990 || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/phatk || unlocked shaders, mem @ 1375, VGPU 1.21v, Watercooled (MCW60), temp 54C, VECTORS BFI_INT AGGRESSION=11 -k phatk
|-
| 6950 || 432 || 2.16(?)||1.44 || 200(?) || 1000 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || guiminer/poclbm || unlocked shaders, +20% overdrive, mem @ 520, fan @ 80%, temp 76C, -v -w128 -f 2, gpu core @ 1275mV
|-
|style="background:#FFAFAF;"| 6950x2 CF || 720 || - || - || ~400 || 900 || 1408 || 2.4.595.0 || PCI-E 2.1 x16 || GUIMiner v2011-07-01 || MSI Afterburner - gpu @ 900 (870 stock), mem @ 900 (1250 stock), temp 69-71C(bottom vga) fan@94% / 77-81C(top vga) fan@99% - 31C enviornment, -v -f 1 -w 128 BFI_INT
|-
|style="background:#FFAFAF;"| 6950x2 CF || 731 || - || - || ~400 || 900 || 1408 || 2.4.595.0 || PCI-E 2.1 x16 || GUIMiner v2011-07-01 || MSI Afterburner - gpu @ 900 (870 stock), mem @ 900 (1250 stock), temp 68C(bottom vga) fan@90% / 73C(top vga) fan@99% - 28C enviornment, -v -f 1 -w 128 BFI_INT AGGRESSION=13
|-
| 6950x3 || 1081 || -|| || - || 860 || 1408 || 2.4(?) || PCI-E 2.1 x8 || guiminer/poclbm 07-01 || Sapphire 2GB stock bios, stock voltage, locked shaders: +20% overdrive, mem@650, fan@95%, temp 94C, -v -f0 -w128, 93c
|-
| 6950x4 || 1316 || 1.513|| || 870 || 840 || 1408 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || locked shaders, default mem 1250, dual fan 75C typical
|-
|style="background:#F0FF0F;"| 6970 || 323 || 1.468||0.92 || 220 || 880 || 1536 || 2.3 || PCI-E 2.1 x16 || poclbm || -w 64, SDK 2.1 not supported on 69xx.
|-
|style="background:#F0FF0F;"| 6970 || 365 || 2.04|| || 180 || 840 || 1536 || 2.5 || PCI-E 2.1 x16 || guiminer/poclbm || -v -w128, fan @ 50%/temp 61C, 1.0 V, 150 MHz mem, TX650w (84%), reference card
|-
|style="background:#F0FF0F;"| 6970 || 370 || -|| || - || 880 || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm || -v -w128, fan @ 50%/temp 72C, stock card
|-
|style="background:#F0FF0F;"| 6970 || 372 || 1.691(?)|| || 220(?) || 900 || 1536 || 2.4 || PCI-E 2.1 x16 || phoenix (svn trunk 05.14.2011) || clock 900/1375, VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128, fan 45% (auto) / temp 90C
|-
|style="background:#F0FF0F;"| 6970 || 388 || -|| || - || 900 || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm || -v -w128, fan @ 50%/temp 72C, stock voltage of 1.175v
|-
|style="background:#F0FF0F;"| 6970 || 385 || 1.964|| || 196 || 900 || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm || -v -w128, memory downclocked to 684Mhz, fan @ 70%/temp 81C
|-
|style="background:#F0FF0F;"| 6970 || 380 || -|| || - || - || - || 2.4 || PCI-E 2.1 x16 || poclbm || -v -w128<br>export GPU_USE_SYNC_OBJECTS=1 # to reduce poclbm CPU from 100% to 2%
|-
|style="background:#F0FF0F;"| 6970 || 403 || -|| || - || MAX || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm || clock Max/50%+stock, -v -w128, fan= 100%/temp 72C (Note: Overclocked using CCC utility under Windows 7, Clock set to Max value w/ 50% increase to memory and 5% increase to voltage)
|-
|style="background:#F0FF0F;"| 6970 || 406 || -|| || - || 950 || 1536 || 2.4 || PCI-E 2.1 x16 || phoenix 1.50/phatk || GPU Overclocked to Max (950MHz) using aticonfig, Memory Underclocked using AMDOverdriveCtrl (850MHz). Temp ~ 82C. VECTORS BFI_INT FASTLOOP=false AGGRESSION=11 WORKSIZE=128
|-
|style="background:#F0FF0F;"| 6970 || 407 || -|| || - || 955 || 1536 || 2.4 || PCI-E 2.1 x16 || poclbm || -v -w128, fan 75%/temp 75C, voltage +10%
|-
|style="background:#F0FF0F;"| 6970 || 414 || -|| || - || 960 || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm || -v -w128, fan @ 53%/temp 73C, stock voltage of 1.175v, high air flow case
|-
|style="background:#F0FF0F;"| 6970 || 420 || -|| || - || 975 || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm || -v -w128 -f0, clocks 975MHz/685MHz MSI Lightning
|-
|style="background:#F0FF0F;"| 6970 || 423 || -||1.20 || - || 995 || 1536 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || ATI Tray Tools, Clocks=995/331.25, WORKSIZE=128 BFI_INT AGGRESSION=11 VECTORS ,68C @ 65% Fan, HAF932 Case
|-
|style="background:#F0FF0F;"| 6970 || 431 || -|| - || - || 976 || 1536 || 2.4 || PCI-E 2.1 x16 || phoenix 1.7/phatk2 || MSI AFTERBURNER, Clocks[976/1000], -k parameters[VECTORS BFI_INT AGGRESSION=11], Temperatures{CARD}[86C@100% Fan]{ROOM}[27C/81F],
|-
|style="background:#F0FF0F;"| 6970 || 433 || -|| - || - || 975 || 1536 || 2.6 || PCI-E 2.1 x16 || phoenix 1.6.2/phatk || MSI Afterburner 2.2Beta, -k phatk AGGRESSION=11 WORKSIZE=128 VECTORS, GPU 65C@100% Fan, Room 21C
|-
|style="background:#F0FF0F;"| 6970x2 || 710 || -|| || - || 900/880 || 1536 || 2.2 || PCI-E 2.1 x16 || poclbm || -w 256
|-
|style="background:#F0FF0F;"| 6970x2 || 828|| -|| || - || 940 || 1536 || 2.4 || PCI-E 2.1 x16 || poclbm || -v -w128, fans 74%/82%, temp 74C/82C, powertune +20% (via CCC), memory underclock 825MHz (via MSI Afterburner), with 'Maj' fix
|-
|style="background:#F0FF0F;"| 6970x3 || 1243|| -|| || 1000+ || 910 || 1536 || 2.5 || 2x16, 1x8 || phoenix 1.7.0 || fans 100%, temp 88C/84C/69C, GPU 920/ memory 795/ powertune 20%, ATI 11.11, -k phatk2 VECTORS BFI_INT FASTLOOP=false WORKSIZE=128 AGGRESSION=13
|-
| 6990 || 670 || 1.94||0.89 || 346 || 830 || 3072 || 2.4 || PCI-E 2.1 x16 || poclbm || Catalyst 11.4 [http://forum.bitcoin.org/index.php?topic=2949.msg106238#msg106238 source].
|-
| 6990 || 704 || || || || 830 || 3072 || 2.4 || PCI-E 2.1 x16 || Diablo Win7 64bits || Catalyst 11.4, Arguments: -v 2 -w 128 (by Swapper 2011-07-07)
|-
| 6990 || 708 || 2.05|| || 346 || 830 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || BIOS switch at "default" position 2, see [http://www.bitcoin.org/smf/index.php?topic=2949 source]
|-
| 6990 || 744 || || || || 830 || 3072 || 2.5 || PCI-E 2.1 x16 || Diablo Win7 64bits || Catalyst 11.6b, Arguments: -v 2 -w 128 (by Swapper 2011-07-14)
|-
| 6990 || 746 || 1.82|| || 410 || 880 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || BIOS switch at "overclocked" position 1, see [http://www.bitcoin.org/smf/index.php?topic=2949 source]
|-
| 6990 || 758 || -|| || - || 880 || - || 2.4 || - || Phoenix with Poclbm || Catalyst 11.4, OC switch ON, VECTORS AGGRESSION=12 BFI_INT WORKSIZE=128 FASTLOOP=false
|-
| 6990 || 771 || 1.8804|| || 410 || 880 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || SDK 2.1 not supported on 69xx. Memory clock @ 1280Mhz.
|-
| 6990 || 772 || 1.8380|| || 420 || 900 || 3072 || 2.3 || PCI-E 2.1 x16 || Phoenix & Poclbm || OC switch ON + overclocked to 900 mhz, VECTORS AGGRESSION=12 BFI_INT WORKSIZE=128
|-
| 6990 || 790 || -|| || - || 900 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || BIOS switch at "overclocked" position 1; with "aticonfig --odsc=900,1260" to further overclock the GPU to 900 MHz and mem to 1260 MHz, see [http://www.bitcoin.org/smf/index.php?topic=2949 source]
|-
| 6990 || 795 || -|| || - || - || - || 2.4 || || Diablo's miner || BIOS switch at "overclocked" position 1; On Windows Vista, Clocks set at 955,1250. Power control at 20.
Diablo's args: -w 128 -g 5 -v 2 -f 0
|-
| 6990 || 802 || -|| || - || 915 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || BIOS switch at "overclocked" position 1; with "aticonfig --odsc=915,1260" to further overclock the GPU to 915 MHz and mem to 1260 MHz, see [http://www.bitcoin.org/smf/index.php?topic=2949 source]
|-
| 6990 || 835 || -||1.11 || - || 890/860 || 3072 || 2.4 || PCI-E 2.1 x16 || phoenix || BIOS switch at "overclocked" position 1; with "aticonfig --adapter=1 --odsc=990,890 and aticonfig --adapter=0 --odsc=960,860" (GPU 0 runs hot). Currently, aticonfig can only underclock RAM to 100mhz below core speed. Command line: phoenix.py -k poclbm VECTORS AGGRESSION=13 WORKSIZE=128 BFI_INT
|-
| 6990 || 865 || -||1.11 || - || 890/860 || 3072 || 2.4 || PCI-E 2.1 x16 || cgminer || BIOS switch at "overclocked" position 1; with core 0 at 990/890 engine/mem, core 1 at 960/860 (runs hot). Watercooled at 65-68C.
|-
| 6990x2 || 1436 || 1.848|| || 777 || 880 || 6144 || 2.4 || PCI-E 2.0 x16 x2 || guiminer 2011.05.11 || AUSUM switch set to 1 on both cards; Core left at 880MHz, memory left at 1250MHz; VECTORS AGGRESSION=12 BFI_INT WORKSIZE=128
|-
| 6990x2 || 1640 || 1.416|| || 1200 || 1010 || 3072 || 2.1 || PCI-E 2.0 x16 x16 || phoenix 1.7.0 || GPU 910MHz, Memory 785MHz, Powertune 20%; VECTORS AGGRESSION=12 BFI_INT WORKSIZE=128 FASTLOOP=false
|-
| 6990x2 || 1700 || 1.416|| || 1200 || 1010 || 3072 || 2.1 || PCI-E 2.0 x16 x16 || guiminer 2011.06.14 || GPU 1010MHz, Memory 900MHz; -k phatk2 VECTORS BFI_INT FASTLOOP=false WORKSIZE=128 AGGRESSION=13
|-
| 6990x2 || 1740 || 2.11 || || 825 || 940 || 3072 || 2.1 || PCI-E 2.0 x16 x16 || cgminer 2.0.8 || GPU0+3 930MHz core/805MHz memory, GPU1+2 940MHz core/815MHz memory; BIOS switch factory setting; Cooled with 7C air from outside; -g4 -I9 -k phatk
|-
| 6990x3 || 2094 || -|| || - || 900 || - || 2.4 || PCI-E 2.0 x16 x8 x4 || poclbm || GPU 900MHz, Memory 1250MHz; poclbm.py -f 0 -w 256
|-
| 7970 || 650 || -|| || - || 1100 || - || 2.4 || PCI-E 2.0 x16 x8 x4 || Diablo|| GPU 1100MHz, Memory 600MHz;
|-
| 7970 || 710 || -|| || - || 1200 || - || 2.4 || PCI-E 2.0 x16 || DiabloMiner|| GPU 1200MHz, Memory 600MHz; -v 1 -w 256
|-
| FirePro V4800 || 79.7 || -|| || - || 775 || 400 || 2.4 || PCI-E 2.1 x16 || GUIMiner v2011-05-01 ||
|-
| FirePro V8700 || 84.8 || -|| || - || 750 || 800 || - || - || poclbm-mod.03.24.2011 ||

|-
| FirePro M5800 || 61.4 || -|| || - || 650 || - || - || - || poclbm-mod.03.24.2011 || Ubuntu
|-
| FirePro M5800 || 69.3 || -|| || - || 650 || 400 || 2.1 || - || GUIMiner v2011-04-26 || -v -w128, Windows 7 32bit
|-
| FirePro V5800 || 119 || -|| || - || 690 || 800 || - || PCI-E 2.0 x16 || GUIMiner v2011-05-01 || Windows 7 32bit
|-
| FirePro V5800 || 144 || -|| || - || 690 || 800 || - || PCI-E 2.0 x16 || GUIMiner v2011-05-01 || -v -w128 (Windows 7 32bit)
|-
| FirePro V5800 || 161 || -|| || - || 780 || 800 || - || PCI-E 2.0 x16 || GUIMiner v2011-05-01 || -v -w128 (Windows 7 32bit)
|-
| FirePro V7750 || 35.7 || -|| || - || - || 320 || 2.4 || PCI-E 2.0 x16 || GUIMiner v2011-05-21 || Windows 7 64bit
|-
| FirePro V7800 || 254.85 || -|| || - || - || 1440 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.48 with poclbm || Debian Squeeze
|-
| FirePro M7740 (M97 GL) [DELL] || 63.0 || -|| || - || 650 || - || 2.1 || PCIe v2.0 x16 || GUIMiner v2011-06-14 || Windows 7 64bit / only SDK2.1 works
|-
| FirePro M7820 || 150.0 || -|| || - || 700 || 800 || 2.1 || PCI-E 2.1 x16 || GUIMiner v2011-06-09 / poclbm || Memory downclocked to 500 from 1000MHz, 169MH/s@800MHz, 181MH/s@860Mhz (max.), only SDK2.1 works, Windows 7 x86
|}

<references>
<ref name='amazon_20110625'>$ Prices from http://www.amazon.com on 2011-06-25</ref>
</references>

===Nvidia===

{| class="wikitable sortable"
|-
! Model !! Mhash/s !! Mhash/J !! Watts !! Clock !! SP !! Comment
|-
| ION || 1.8 || 0.067 || 27 || || 16 || poclbm; power consumption incl. CPU
|-
| 8200 mGPU || 1.2 || || || 1200 || 16 || 128 MB shared memory, "poclbm -w 128 -f 0"
|-
| 8400 GS || 2.3 || || || || || "poclbm -w 128"
|-
| 8400 GS || 1.6 || 0.013 || 128 || 1238 || || DiabloMiner -w 128 -f 1 [https://en.bitcoin.it/wiki/User:Knightmb source]
|-
| 8400M GS || 2.0 || || || || ||
|-
| 8500GT || 2.4 || || || 918 || 16 || poclbm under GUIMiner
|-
| 8600M GT || 4.93 || || || || 32 ||
|-
| 8600M GT || 3.8 || || || || || Macbook Pro running Diablo
|-
| 8600GT || 5.66 || || || 1188 || 32 ||
|-
| 8600GT OC || 7.3 || || || 1602 || 32 || [http://www.bitcoin.org/smf/index.php?topic=1334.0 poclbm] -w 128 [http://www.bitcoin.org/smf/index.php?topic=4967.msg72833#msg72833 source]
|-
| 8800GT || 25 || 0.24 || 105 || 1300 || ||
|-
| 8800GT || 24.5 || 0.23 || 105 || 1300 || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source]
|-
| 8800GT || 31.1 || 0.296 || 105 || 1855 || || Overclocked 715 GPU / 1030 Memory / 1855 Shader; GuiMiner v2011-05-21
|-
| 8800GT || 31.8 || 0.303 || 105 || 1836 || 112 || 713 gpu, 1026 memory. win7x86, phoenix 1.48, -k poclbm WORKSIZE=64 AGGRESSION=5
|-
| 8800GT || 34.0 || || 105 || 1998 || || gpu 756M, mem 1123M, shader 1998M, temp 65C. winXP, phoenix 1.50, -k poclbm WORKSIZE=64 AGGRESSION=6 -- same settings get 32.7 MH/s with aggression 2
|-
| 8800GTS || 16.8 || 0.109 || 154 || || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg25069#msg25069 source] [http://www.techspot.com/review/79-geforce-8800-gts-512/page11.html source]
|-
| 8800 GTS || 18.7 || 0.124 || 150 || 1200 || || poclbm -w 64 no vectors
|-
| 8800 GTS || 33.5 || || 150 || OC || || CUDA mining via GUIminer. Win7 64bit. poclbm -v -w128 -f0. OC'd Core@799MHz, Mem@1080MHz, Shader@1905MHz. Fan 70%, GPU temp @ 66C in comfortable room temp.
|-
| 8800 GTX || 27.5 || || || 1404 || || phoenix 1.48, poclbm, no vectors, 83C with 50C ambient
|-
| 8800m GTX || 16.3 || || || || || rpcminer-cuda Win7-64
|-
| 9300GE || 1.57 || || || 1300 || 8 ||
|-
| 9300GS || 1.69 || || || 1400 || 8 ||
|-
| 9300/nForce 730i || 2.15 || || || 1200 || 16 ||
|-
| 9400GT || 3.37 || 0.067 || 50 || 1400 || 16 ||
|-
| 9400M (MacBook) || 1.90 || 0.32 || 6 || 700 || || poclbm -f 8 no vectors
|-
| 9500M GS || 3.2 || || || 950 || 32 || rpcminer-cuda
|-
| 9500GT || 6.75 || 0.135 || 50 || 1400 || 32 ||
|-
| 9500GT || 7.10 || 0.135 || 50 || 1767 || 32 || rpcminer-cuda, Overclocked 707 GPU / 500 Memory / fan 100% 73C steady
|-
| 9600GSO || 19.88 || 0.237 || 84 || 1375 || 96 ||
|-
| 9600GSO512 || 11.75 || 0.131 || 90 || 1625 || 48 ||
|-
| 9600GT || 15.66 || 0.165 || 95 || 1625 || 64 ||
|-
| 9600GT Zotac || 15 || || || 1650 || 64 ||
|-
| 9600GT OC || 18.8 || <0.198 || >95 || 1981 || 64 || [http://www.bitcoin.org/smf/index.php?topic=1334.0 poclbm] -w 128 -f 10 [http://www.bitcoin.org/smf/index.php?topic=4967.msg74610#msg74610 source] [http://www.bitcoin.org/smf/index.php?topic=4967.msg73353#msg73353 source]
|-
| 9600M GS || 4.0 || || || 1075 || 32 || rpcminer-cuda
|-
| 9800GT || 30.36 || 0.289 || 105 || 1800 || 112 ||
|-
| 9800GT EE || 19.7 || 0.263 || 75 || 1375 || 112 || rpcminer-cuda
|-
| 9800GT OC || 29.5 || 0.283 || 105 || 1836 || 112 || poclbm.py, no options. Memory underclocked to 850Mhz, GPU overclocked to 733Mhz
|-
| 9800GTX || 32.54 || 0.232 || 140 || 1688 || 128 ||
|-
| 9800GTX+ || 32.6 || 0.232 || 140 || 1688 || 128 || win7x64 275.33 Overclocked to 756/1890/1102 using a CUDA-specific miner (instead of phoenix, yay for ZERO stales!)
|-
| 9800GTX+ || 35.39 || 0.251 || 141 || 1836 || 128 ||
|-
| 9800GTX+ || 36 || || || || || factory OC ubuntu polclbm.py -w 128 -f 10 -a 10 (DO NOT USE -v)
|-
| 9800GTX+ || 37.23 || 0.266 || 140 || 1890 || 128 || win7x64 275.27 phoenix(1.48) -k poclbm AGGRESSION=3 WORKSIZE=64 (may cause 75%+ stale count, in which case use a CUDA-specific miner instead)
|-
| 9800GTX+ || 40.20 || 0.287 || 140 || 835 || 128 || lowered memory clock higher core, unstable if going higher
|-
|style="background-color:#FFEFEF"| 9800GX2 || 57.83 || 0.294 || 197 || || 2x128 ||
|-
|style="background-color:#FFEFEF"| 9800GX2 || 28 || 0.142 || 197 || || 2x128 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37620#msg37620 source]
|-
| G210 || 3.38 || 0.111 || 30.5 || 1402 || 16 ||
|-
| G210 || 3.79 || 0.124 || 30.5 || 1402 || 16 || poclbm -f 1
|-
| GT220 || 10.8 || 0.084 || 128 || 1360 || || DiabloMiner -w 128 -f 1000 [https://en.bitcoin.it/wiki/User:Knightmb source]
|-
| GT230 || 15.5 || 0.161 || 96 || 650 || 64 || (9600GT rebranded one from in a medion pc)
|-
| GT240 || 19.37 || 0.281 || 69 || 1340 || 96 ||
|-
| GT240 || 21.24 || || || || 96 || [http://www.bitcoin.org/smf/index.php?topic=4291.0 poclbm-mod] -f 0 -v [http://www.bitcoin.org/smf/index.php?topic=4967.msg73383#msg73383 source]
|-
| GT240 || 28.1 || || || || 96 || poclbm -f0 -v (Gainward GT240 1024DDR5 OC core@670/stockmem@1700/shader@1700 - stable; max.temp=73)
|-
| GT240M || 9.8 || 0.426 || 23 || 550 || 48 || poclbm -f 0 -w 256
|-
| GTS250 || 35.39 || 0.244 || 145 || 1836 || 128 ||
|-
| GTS250 || 35.2 || 0.243 || 145 || 1836 || 128 ||
|-
| GTS250 OC || 37 || 0.255 || 145 || 2047 || 128 ||
|-
| GTX260M || 22.5 || || || 500 || 112 || poclbm 4/28/2011 Asus G71GX runs ~90c without cooling pad
|-
| GTX260 || 35.91 || 0.178 || 202 || 1242 || 192 ||
|-
| GTX260 || 44 || 0.242 || 182 || 1242 || 216 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
| GTX260c216 || 40.40 || 0.236 || 171 || 1242 || 216 ||
|-
| GTX260c216 || 47.4 || 0.260 || 182 || 1348 || 216 || poclbm -w 256
|-
| GTX260c216 || 50.00 || || || 1050 || 216 || m0mchil GPU client, Windows 7 64-bit, x6 @ 3.5ghz
|-
| GTX260c216 OC || 52.0 || || || 1461 || 216 || "poclbm -w 256 -f 1"
|-
| GTX260c216 OC || 58.9 || || || 756/400 || 216 || Core overclocked, Memory underclocked, Ubuntu 11.04 Classic Session(No Effects) "poclbm -w 256 -f 1"
|-
| GTX260c216 OC || 60.1 || || || 1706 || 216 || Core: 364 MHz, Shaders: 1706 MHz, Memory: 594 MHz, VDDC: 1.1800V. "poclbm-mod -w 256 -f 1"
|-
| GTX275 || 50.75 || 0.232 || 219 || 1404 || 240 ||
|-
| GTX275 || 58 || || || 729/1458 || 240 || poclbm -f 0 -w 256
|-
| GTX280 || 46.84 || 0.198 || 236 || 1296 || 240 ||
|-
| GTX280 || 64.34 || 0.289 || 245 || 1296 || 240 || phoenix.exe -k poclbm AGGRESSION=6 WORKSIZE=128 (61*C with Accelero XTREME GTX280)
|-
| GTX285 || 64.8 || || || 1607 || 240 || GuiMiner - Not sure about wattage yet. Still testing. Card runs around 74 C
|-
|-
| GTX285 || 53.35 || 0.262 || 204 || 1476 || 240 ||
|-
| GTX295 || 89.78 || 0.311 || 289 || 1242 || 480 ||
|-
| GTX295 || 120.70 || 0.418 || 289 || 1242 || 480 || GUIMiner no oc.
|-
| GTX295 || 117.30 || 0.406 || 289 || 1476 || 490 ||
|-
| GT 320M (MacBook Air) || 6.12 || || || 1212 || 48 ||
|-
| 320M (Mac mini 2010) || 7.0 || 0.35 || 20 || 450 || 32 || poclbm no extra options, windows 7 x64
|-
| GT 325M || 7.5 || || || 990 || 48 || rpcminer-cuda
|-
| GT 325M || 10.5 || || || 325/650(mem)/1300(shaders) || || rpcminer-cuda, 71 degrees
|-
| GT 325M || 7.99 || || || || || poclbm -f 0 -w 256
|-
| GT330 || 21.65 || || || || || poclbm -f 0 -w 256
|-
| GT 330M || 7.97 || || || || || Model: MacBookPro6,2 VRAM: 512MB Software: [http://forum.bitcoin.org/index.php?topic=8994.0 DiabloMiner GUI] v2011-05-22 / Mac OS X 10.6.7
|-
| GT 330M || 10.8 || || ||650MHZ core||6|| Model: MacBookPro6,2 VRAM: 512MB Software: GUIMiner running in Bootcamp] v2011-08-24 / Mac OS X 10.6.8.The GPU was OC'd to 650MHZ core clock,mem clock was the lowest it would go in MSI Afterburner.The Bootcamp OS was Windows 7 x64.MBP Mid 2010.
|-
| GT 330M (Sony Vaio Z) || 7.8 || 0.71 ( 0.3 total) || 11 (26w total) || 1045 || 48 ||
|-
| GTS 350M (Toshiba A665-3DV) || 17.0 || 1.214 || 14 || 1080 || || DiabloMiner-Windows.exe
|-
| GTS 350M (Toshiba A665-3DV5) || 20.8 || || || 1350 || || DiabloMiner-Windows.exe, OC'd 550/850/1350 73C stable
|-
| GTS 360M || 25.0 || || || || || [toshiba qosmio laptop, ~150-165*F stock fans]
|-
| GTS 360M (ASUS G60jx) || 20.0 || || || || || everythins is stock, it cannot sustain. it reaches 90 degrees and freezes.
|-
| GTS 360M (ASUS G60jx) || 27.2 || || || Shader @ 1720, Memory @ 900 || || stock hardware (clean exhaust fan), Afterburner, 72 deg C Stable
|-
| GT430 || 20.24 || 0.413 || 49 || 1400 || 96 ||
|-
| GT440 || 20.4 || || || 1645 || 96 || rpcminer-cuda -aggression=8; winxp x64 driver 275.33
|-
| GT540M || 16.0 || || || || || rpcminer-cuda
|-
| GT550M || 17.08 || || || || || rpcminer-cuda -aggression=8
|-
| GTS450 || 45.28 || 0.427 || 106 || 1566 || 192 ||
|-
| GTX460SE || 56.39 || 0.376 || 150 || 1300 || 288 ||
|-
| GTX460 || 66.32 || || || 814 || 336 || rpcminer-cuda 20110605, Graphics Clock @ 814MHz, Memory @ 1555MHz
|-
| GTX460 || 68.31 || 0.427 || 160 || 1350 || 336 ||
|-
| GTX460 768MB || 57.8 || || ? || 1350 || 336 || rpcminer-cuda -gputhreads=320 -gpugrid=336
|-
| GTX460 768MB (MSI Cyclone 768D5/OC) || 75.1 || || ? || 930 || 336 || rpcminer-cuda on Win7 x64 with ForceWare 275.33. [http://event.msi.com/vga/afterburner/download.htm MSI Afterburner] set to core: 930MHz, shader: 1850MHz, core voltage: 1.087V, memory: 1600MHz. Runs at 58°C with fan at 75% (ambient 25°C).
|-
| GTX460 1GB DirectCU || 72.3 || ? || ? || 1672 || 336 || rpcminer-cuda -gputhreads=320 -gpugrid=336
|-
| GTX460 (2 cards) || 102 || 0.319? || 320? || 1350 || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26363#msg26363 source]
|-
| GTX460 (2 cards) OC || 127 || 0.374 || 340 || 1620 || 2x 336 || [http://www.bitcoin.org/smf/index.php?topic=2444.0 rpcminer-cuda] -gpugrid=128 -gputhreads=128 ver.20110227
|-
| GTX465 || 64.41 || 0.322 || 200 || 1215 || 352 ||
|-
| GTX470 || 81.98 || 0.381 || 215 || 1215 || 448 ||
|-
| GTX470 || 94.7 || || || 1414 || ||
|-
| GTX470 || 103.7 || || || 1520 || || memory @ 418MHz, stable @ 72 deg fan @ 90%, puddinpop rpcminer-cuda -gpugrid=96 -gputhread=128 AGGRESSION=14 GIGABYTE brand card BIOS 70.00.21.00.03
|-
| GTX470 || 111.9 || 0.520 || 215 || 1650 || 448 ||
|-
| GTX470 || 115 || || || 1616 || || phoenix 1.46 poclbm VECTORS BFI_INT FASTLOOP AGGRESSION=6
|-
| GTX470x2 || 121 ea. (130 burst ea.) || || || 1700 ||448|| PuddinPop rpcminer-cuda -gpugrid=96 -gputhreads=128 AGGRESSION=14 (memory 856 Max Temp. 71 deg. F on Water 1.085v+, Stable on Beast 2.0>3 days, no i7 CPU OC, driver 280.26, bios 70.00.21.00.03)
|-
| GTX480 || 101.28 || 0.405 || 250 || 1401 || 480 ||
|-
| GTX480 || 140.43 || || || 1700 || 480 || rpcminer-cuda -gpugrid=512 -gputhreads=480
|-
| GTX480 AMP!Zotac|| 140.1 || || || 1700|| 480 || rpcminer-cuda -gpugrid=480 -gputhreads=480 (vCore-1050,Core Clock-851, Shader Clock-1702, Memory Clock-2033, t-79°c, Water 43°c, stable temperature and work)
|-
| GTX560 Ti || 67.7 || 0.39 || 170 || 1700 || 384 || standard EVGA 560, no overclock
|-
| GTX560 Ti || 74 || 0.41 || 170 || 822 || 384 || MSI 560Ti HAWK; core 822 Mhz clock (no overclock); rpcminer-cuda.exe -aggression=4 -gpugrid=64 -gputhreads=384; temp - 71°C; Win 7 x64
|-
| GTX560 Ti || 74.8 || 0.41 || 180 || 1700 || 384 || gigabyte 900Mhz clock; -w 512 -v
|-
| GTX560 Ti || 81 || ? || ? || 835 || 384 || Gainward GTX560TI Phantom, default clock, rpcminer-cuda
|-
| GTX560 OC || 86.7 || <0.51 || >170 || 1800 || 384 || [http://www.bitcoin.org/smf/index.php?topic=2444.0 rpcminer-cuda] [http://www.bitcoin.org/smf/index.php?topic=4967.msg72816#msg72816 source]
|-
| GTX570 || 105.83 || 0.483 || 219 || 1464 || 480 ||
|-
| GTX570 || 140 || 0.639 || 219 || 750 || 480 || rpcminer-cuda.exe -aggression=10 -gpugrid=480 -gputhreads=960; display driver stops working with aggression=11 under win7 x64 driver 270.61
|-
| GTX570 || 157 || 0.717 || 219 || 850 || 480 || rpcminer-cuda.exe -aggression=11 -gpugrid=120 -gputhreads=960
|-
| GTX580 || 140.05 || 0.574 || 244 || 1544 || 512 ||
|-
| GTX580x2 || 2x 146 || 0.598 || 244 || 1544 || 512 || rpcminer-cuda.exe -gpugrid=128 -gputhreads=1024
(aggression levels above the default of 6 not recommended; only a gain of ~3MH/s per card, and '''heavy''' lag, GUIMiner v2011-08-24, win7 64bit nVidia 290.36 beta driver)
|-
| GTX590 || 193.1 || --- || --- || 1215 || 2x 512 || poclbm -v -w 256, Win
|-
| GTX590 || 2x 121.48 || --- || --- || 750 || 2x 512 ||
|-
| Quadro FX 580 || 5.7 || 0.14 || 40 || 1125 || 4 ||rpcminer-cuda, Win, -gpugrid=128 -gputhreads=512
|-
| Quadro FX 770M || 5.75 || || || 500 || 32 || DiabloMiner-Windows.exe BFI_INT FASTLOOP AGGRESSION=6, Win
|-
|Quadro FX 770M || 6.39 || || || 500 || 32 || DiabloMiner-Windows.exe BFI_INT FASTLOOP AGGRESSION=6 w 64, Win 7x64
|-
|Quadro FX 880M || 9.6 || || || || || poclbm/guiminer
|-
| Quadro FX 1600M || 6 || 0.12 || 50 || 625 || 32 ||rpcminer-cuda, Win
|-
| Quadro FX 2000M || 23 || 0.397 || 58 || || || phoenix 1.48, -k poclbm, VECTORS, AGGRESION=6, Lenovo W520 platform
|-
| Quadro FX 2800M || 22 || 0.293 || 75 || 600 || 96 ||DiabloMiner, win
|-
| Quadro FX 3600M || 36 || 0.514 || 70 || 500 || 96 ||
|-
| Quadro FX 3800 || 33.3 || || || || || poclbm/guiminer -f0 -w128
|-
| Quadro NVS 135M || 1.05 || 0.1 || 10 || 800 || 1 ||
|-
| Quadro NVS 295 || 1.7 || 0.07 || 23 || 567 || 8 || phoenix
|-
| Quadro NVS 3100M || 3.6 || 0.257 || 14 || 600 || 16 || rpcminer-cuda, Win, CUDA 3.1.1
|-
| Quadro NVS 4200M || 10.0 || || || 810 || || guiminer, Win7-64
|-
| Quadro 5000 || 67.7 || 0.445 || 152 || 513 || 352 || rpcminer-cuda.exe -aggression=7 gpugrid=352 gputhreads=704;
|-
| Tesla C1060 || 52.5 || || || 1296 || 240 || poclbm, Win7x64
|-
| Tesla M2050 || 79.8 || || || 1550 || 448 || DiabloMiner
|-
| Tesla S1070 || 155.2 || || || || || rpcminer-cuda, Linux, CUDA 3.2, 4 instances (-gpu=0 through -gpu=3)
|-
| Tesla S2070 || 749.23 || || || || || rpcminer-cuda, Linux, CUDA 4.0, 8 instances (-gpu=0 through -gpu=7)
|-
| GTX280x2 || 102.7 || || || || ||
|-
|}

==CPUs/APUs==

A lot of nice data can be pulled from [http://www.bitcoin.org/smf/index.php?topic=1628.0 this thread] to seed this section.

Might you wish to throttle CPU load a bit, so it doesn't reach 100°C, it can be done with Battle Encoder Shirase to a margin, like, -15% of available CPU cycles.

Often, the best combination to be is to throttle CPU miner to -5% '''AND''' set it to least of priority levels, so as not to choke GPU miner up.

===AMD===
{| class="wikitable sortable"
|-
! Model !! nprocs !! Mhash/s !! Mhash/J !! TDP [W] !! CPU Clock !! Mhash/s CPU !! Mhash/s GPU !! GPU !! GPU Clock !! SP !! Software !! Notes
|-
| 4x Opteron 6174 || 48 || 115 || 0.36 || 320W || 2.2 GHz || 2.4
|colspan=4|
| cpuminer v0.8.1 || --alg 4way --threads 48
|-
| 2x Opteron 6128 || 16 || 32.4 || 0.141 || 230W || 2 GHz || 32.4
|colspan=4|
| 0.3.19 || -4way
|-
| Athlon XP 2000+ || 2 || 0.62 || 0.009 || 70W || 1.67 GHz || 0.62
|colspan=4|
| 0.3.18/Ubuntu || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source] [http://www.pcstats.com/articleview.cfm?articleid=914&page=4 source]
|-
| Athlon 64 3500+ || 1 || 1.18 || 0.013 || 89W || 2.54 GHz || 1.18
|colspan=4|
| ufasoft v0.4 || overclocked (originally 2.2 GHz)
|-
| Athlon 64 X2 3800+ || 2 || 1.73 || 0.03 || 65 W || 2.00 GHz || 1.73
|colspan=4|
| cpuminer (v0.8.1-1-g69529c3) || -algo=4way
|-
| Athlon 64 X2 4000+ || 2 || 1.9 || 0.02 || 65W || 2.1 GHz || 1.9
|colspan=4|
| rpc-miner ||
|-
| Athlon 64 X2 4400+ || || 2.09 || 0.032 || 65W || 2.3GHz || 2.09
|colspan=4|
| 0.3.19/Win x64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source]
|-
| Athlon 64 X2 6000+ || 2 || 2.81 || 0.02 || 125W || 3 GHz || 2.81
|colspan=4|
| || [http://www.bitcoin.org/smf/index.php?topic=1628.msg22881#msg22881 source]
|-
| Athlon 64 X2 6400+ Black Edition || 2 || 2.9 || 0.023 || 125W || 3.2 GHz || 2.9
|colspan=4|
| 0.3.20.2 BETA/Win 7 x64 || -4way
|-
| Athlon II X2 240e || 2 || 2.71 || 0.06 || 45W || 2.81 GHz || 2.71
|colspan=4|
| bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Athlon II X2 250 || 2 || 5.6 || 0.09 || 65W || 3.01GHz || 5.6
|colspan=4|
| bitcoin-miner 0.11 ||
|-
| Athlon II X4 630 || 4 || 10.7 || 0.11 || 95W || 2.8 GHz || 10.7
|colspan=4|
| bitcoin-miner 0.4 ||
|-
| Opteron 8220 x16 || 16 || 25 || || || 2.8Ghz || 1.5
|colspan=4|
| ufasoft / OpenSuse 64bit || running default, but had to copy 32bit binaries over to get curl and ufasoft running. might be better when using native 32bit system w/o other users on the machine ||
|-
| Phenom II X3 720 || 3 || 3.8 || 0.04 || 95W || 2.8 GHz || 3.8
|colspan=4|
| 0.3.1x/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
| Phenom X4 9950 BE || 4 || 9.3 || 0.07 || 126W || 2.6 GHz || 2.32
|colspan=4|
| bitcoin-miner 0.13/WinXP || No GPU
|-
| Phenom II X3 720 || 3 || 7.2 || 0.08 || 95W || 2.8 GHz || 7.2
|colspan=4|
| cpu-miner 0.2.1/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
| Phenom II X4 810 || 4 || 5.0 || || 95W || 2.8 GHz ||
|colspan=4|
| rpcminer-cpu ||
|-
| Phenom II X4 810 || 4 || 9.5 || || 95W || 2.8 GHz ||
|colspan=4|
| rpcminer-4way ||
|-
| Phenom II X4 810 || 4 || 10.5 || || 95W || 2.8 GHz ||
|colspan=4|
| ufasoft v0.10 ||
|-
| Phenom II X4 810 || 4 || 11.5 || || 95W || 2.8 GHz ||
|colspan=4|
| cgminer 1.5.3 || "cgminer 1.5.3 --algo 4way" on Ubuntu 11.10 alpha 2 (64 bit), built by GCC 4.6.1 with "-O3 -Wall -march=native"
|-
| Phenom II X4 955 || 4 || 11 || 0.09 || 125W || 3.2 GHz || 11
|colspan=4|
| rpcminer-4way ||
|-
| Phenom II X4 965 || 4 || 12 || 0.09 || 140W || 3.4 GHz || 11
|colspan=4|
| rpcminer-4way ||
|-
| Phenom II X6 1055T || 6 || 15.84 || 0.13 || 125W || 2.82 GHz || 15.84
|colspan=4|
| bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Phenom II X6 1075T || 6 || 21.3 || || 125W|| ||
|colspan=4|
| minerd || Ubuntu 11.04 amd64 runlevel=1 -algo=4way -threads=6
|-
| Phenom II X6 1090T || 6 || 18|| || 141W|| 3.50 GHz || 3
|colspan=4|
| minerd ||
|-
| Phenom II X6 1100T || 6 || 22 || 0.176 || 125W || 3.82 GHz || 22
|colspan=4|
| bitcoin-miner || Aciid#bitcoin-dev
|-
| Sempron 3000+ || 2 || 0.8 || || 62W || 1.6 GHz || 0.8
|colspan=4|
| cpuminer || --alg 4way
|-
| Turion X2 RM-70 || 2 || 1.9 || || 65W || 2.1 GHz || 1.9
|colspan=4|
| cpuminer || --alg 4way
|-
| Zacate E-350 || 2 || 11 || 0.615 || 18W || 1.6 Ghz || 1.231 || 9.831 || HD6310M || 492 Mhz || 80 || poclbm -v -w128 + Ufasoft 0.7 || stock speeds
|-
| Zacate E-350 || 2 || 12
|colspan=2|
| 1.648 Ghz || 1.252 || 10.87 || HD6310M || 492 Mhz || 80 || poclbm -v -w 256 -f 1 || "autotune" speed with ASUS EFI BIOS
|-
| Ontario C-50 || 2 || 6.2 || 0.68 || 9W || 1.0 Ghz || 1.200 || 6.2 || HD6250M || 277 Mhz || 80 || poclbm -v -w128 -f5 -r5 ||
|-
| A8-3850 || 1 || 60 || || 100W || Stock || || 60 || HD6550D || Stock || 400 || poclbm.exe, Win7-32, 4GB RAM || All running at stock speeds, and set to auto in BIOS.
|}

===ARM===
{| class="wikitable sortable"
|-
! Model !! p/t !! Mhash/s !! Mhash/J !! Mhash/s/$ /€ !! ACP [W] !! Clock !! Version !! Comment
|-
| ARM1136EJ-S || 1 || 0.11 || ? || ? || ? || 0.528 GHz || cpuminer git || T-Mobile Pulse, inside Debian chroot, 'c' algo
|-
| Cortex-A8 || 1 || 0.125 || 0.36 || <0.01 || 0.35 W || 0.6 GHz || cpuminer git (2011-03-26) || Nokia N900: 'cryptopp'
|-
| Cortex-A8 || 1 || 0.2 || 0.57 || <0.01 || 0.35 W || 0.6 GHz || cpuminer git (2011-03-26) || Nokia N900: 'c' algo
|-
| 2x Cortex-A9 || 2 || 0.57|| 1.14 ||<0.01 || 0.5 W || 1.0 GHz || cpuminer git (2011-03-24) || Toshiba AC100, ubuntu, 'c' algo
|-
| Marvel Feroceon (88FR131) || 1 || 0.195 || 0.224 ||<0.01|| 0.87 W || 1.2 GHz || cpuminer git (2011-06-15) || Marvell SheevaPlug, Debian, 'c' algo
|}

===Intel===
{| class="wikitable sortable"
|-
! Model !! p/t !! Mhash/s !! Mhash/J !! Mhash / $<ref name='amazon_20110625'/>/€<ref name='geizhals_20110625'/> !! ACP [W] !! Clock [GHz] !! Version !! Comment
|-
| Pentium III mobile ? || 1 || 0.3 || 0.014 |||| 21 || 1.07 || 0.3.1x/Win2K || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source] [http://ark.intel.com/Product.aspx?id=27380 source]
|-
| Pentium M 1.6ghz || 1 || 0.4 || || || || 1.6 || minerd (jgarzik's 1.0) || cryppto, Windows 7
|-
| Pentium M 1.6ghz || 1 || 0.62 || || || || 1.6 || Ufasoft 0.20 || Windows XP Professional
|-
| Pentium M 1.73ghz || 1 || 0.5 || || || || 1.73 || minerd (jgarzik's 1.0) || cryppto, Windows 7
|-
| Old Xeon 512k (Dual) || 2x1/2 || 2.0 || || || || 3.0 || cpuminer (v0.8.1-1-g69529c3) || HT disabled, algo=4way (twice as fast as the 2nd best algo)
|-
| Pentium 4 2.0A || 1 || 0.85 || || || || 2.0 || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft-0.4]/WinXP || -g no -t 2
|-
| Pentium 4 630 || 1/2 || 1.29 || || || || 3.0 || ufasoft 0.23 || Windows XP
|-
| Pentium Dual-Core E2180 || 2/2 || 1.75 || || || || 2.0 || rpcminer-cpu || Win7-64
|-
| Pentium Dual-Core E2180 || 2/2 || 4.1 || || || || 2.0 || cpuminer || sse2_64
|-
| Pentium Dual-Core E2180 || 2/2 || 4.5 || || || || 2.0 || ufasoft v0.11 || Win7-64
|-
| Pentium Dual-Core E5400 || 2/2 || 2.27 || 0.03 || || 65 || 2.7 || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Celeron E330 || 2/2 || 2.2 || 0.03 || || 65 || 2.5 || 0.3.19/Ubuntu10.04 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37620#msg37620 source]
|-
|-
| Celeron E3400 || 2/2 || 5.9 || - || - || - || 2.6 || Ufasoft v0.13 / GUIMiner v2011-06-14 || WinXP 32 bit, SSE2, Flags "-g no"
|-
| Core 2 Quad Q6600 || 4/4 || 11.0 || || 0.02/0.06 || 105 || 2.40 || bitcoin-miner 0.10 || -a 60 -g no -t 4
|-
| Core 2 Quad Q8200 || 4/4 || 10.9 || || 0.06/0.10 || || 2.33 || Ufasoft 0.14 || -g no -l yes -t 4
|-
| Core 2 Quad Q9400 || 4/4 || 11 || 0.046 || 0.06/0.07 || 95 || 2.66 || bitcoin-miner 0.10 || -a 60 -g no -t 4
|-
| Core 2 Quad Q9650 || 4/4 || 18.67 || || 0.05/0.06 || 95 || 4.00 || bitcoin-miner 0.10 || -a 60 -g no -t 4
|-
| Core i3 530 || 2/4 || 8.31 || 0.10 || 0.06/0.10 || 80 || 3.66 || Ufasoft 0.7 || -v -a5 -g no -t 4
|-
| Core i3 M350 || 2/4 || 1.48 || 0.04 || || 35 || 2.27 || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Core i3-2100 || 2/4 || 8.28 || || || || 3.1 || ufasoft v0.20 ||
|-
| Core i5 M450 || 2/4 || 1.8 || 0.05 || || 35 || 1.2 || 0.3.17/Win7-54 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26292#msg26292 source]
|-
| Core i5-650 || 2/4 || 5.1 || 0.04 ? || 0.02/0.03 || || 3.2 || cpuminer-0.7 || -4way
|-
| Core i5-750 || 4/4 || 14 || || 0.06/0.10 || || 3.2 || bitcoin-miner 0.11 || -a 5 -g no -t 4
|-
| Core i5 ? || 4/? || 6.5 || || || || || client from svn || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37621#msg37621 source]
|-
| Core i5-2400 || 4/4 || 4.5 || 0.05 || 0.02/0.03 || 95 || 3.1 || cpuminer git (2011-01-22) || cryptopp_asm32
|-
| Core i5-2400 || 4/4 || 14 || 0.15 || 0.07/0.09 || 95 || 3.1 || cpuminer git (2011-03-26) || sse2_64
|-
| Core i5 2500K || 4/4 || 20.6 || ||0.10/0.12 || || 4.2 || bitcoin-miner || -g no
|-
| Core i5 2600K || 4/8 || 17.3 || || || 75 || 3.4 || bitcoin-miner || -g no. 75W for the whole System without monitor (MSI Board). CPU underclocked to 3,4Ghz and undervolted to 1,012Vcore. Passive Cooling! 3.6ghz results in 18,4 Mhash/s
|-
| Core i7 2600K || 4/8 || 18.6 || || || 95 W max. || 3.4 || Ufasoft bitcoin-miner 0.20 || -g no -t 8 CPU @ 3.511Ghz 1.176V
|-
| Core i7 620M || 2/4 || 1.888 || || || || 2.66 || [http://forum.bitcoin.org/index.php?topic=8994.0 RPCMiner GUI] v2011-05-22 / Mac OS X 10.6.7 || Model: MacBookPro6,2 RAM: 4GB
|-
| Core i7 720QM || 4/8 || 7.9 || ?|| || 45 || 2.8 || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] || stream processors overclocked from 1.6 GHz; Dell Precision M6500, Win7-64, 8GB DDR3
|-
| Core i7 820 || 4/8 || 13.8 || || || || 2.8 || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] || -t 8
|-
| Core i7 920 || 4/8 || 19.2 || 0.10 || || 195 || 4.0 (x21) || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] || -a 5
|-
| Core i7 950 || 4/8 || 5.88 || 0.039 || || 150 || 3.83 (x23) || bitcoin-0.3.20.2 Win7-64 ||
|-
| Core i7 950 || 4/8 || 18.9 || 0.126 || || 150 || 3.83 (x23) || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] v0.4 ||
|-
| Core i7 980x || 6/12 || 19.2 || 0.15 || || 130 || 4.4 (x33) || cpuminer/Win7-64 ||
|-
| Core i7 980x || 6/12 || 8.7 || || || || 3.9 (x27) || 0.3.17/Win7-64 ||
|-
| Core i7 990x || 6/12 || 33.3 || || || || 4.5 (x32) || ufasoft/Win2008 R2-64 || Ram - 12Gb, Rampage III BlackEdition, Water cooling
|-
| Core i7 2635QM || 4/8 || 2.93 || || || || 2.00 || [http://forum.bitcoin.org/index.php?topic=8994.0 RPCMiner GUI] v2011-05-22 / Mac OS X 10.6.7 || Model: MacBookPro8,2 RAM: 4GB
|-
| Core i7 620M || 2/4 || 6.3 || 0.18 || || 35 || 2.66 || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] v0.4 ||
|-
| Core i7 2600k || 4/4 || 6.7 || || || || 4.00 || phoenix 0.48 ||
|-
| Core 2 Duo U7600 || 1 || 1.1 || || || || 1.2 || minerd (jgarzik's 1.0) || cryppto, Windows 7
|-
| Core 2 Duo E5200 || 2/2 || 6.2 || 0.086 || || 72 || 2.76 || Ufasoft/Win7-64 || TDP is 65W + 7W overclock
|-
| Core 2 Duo E6550 || 1/2 || 2.45 || || || || 2.33 || cpuminer 0.7.1 (Linux) || --algo=sse2_64
|-
| Core 2 Duo E6850 || 2/2 || 6.75 || 0.10 || || 65 || 3.0 || ufasoft-0.3 ||
|-
| Core 2 Duo E7300 || 2/2 || 7.76 || 0.11 || || 70 || 3.33 || ufasoft-0.3 || uncertain of overclock; miner optimized for Intel Core
|-
| Core 2 Duo E7300 || 2/2 || 2.52 || 0.04 || || 65 || 2.66 || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Core 2 Duo E8200 || 2/2 || 2.3 || 0.035 || || 65 || 2.66 || rpcminer-cpu ||
|-
| Core 2 Duo E8400 || 2/2 || 6.9 || 0.106 || || 65 || 3.0 || ufasoft v0.10 || windows 7/64bit (-t 2)
|-
| Core 2 Duo E8500 || 1/2 || 3.6 || || || || 3.16 || guiminer v2011-06-14 || windows vista 32bit
|-
| Core 2 Duo E8500 || 2/2 || 7.2 || || || || 3.16 || guiminer v2011-06-14 || windows vista 32bit
|-
| Core 2 Duo P8700 || 2/2 || 5.9 || || || || 2.53 || ufasoft v0.21 || windows 7/64bit
|-
| Core 2 Duo T5450 || 2/2 || 2.5 || 0.07 || || 35 || 1.63 || bitcoin-miner 0.10 || Ubuntu 11.04
|-
| Core 2 Duo T6400 || 2/2 || 4.2 || 0.12 || || 35 || 2.00 || cpuminer git (Linux) || --algo=sse2_64
|-
| Core 2 Duo T7250 || 2/2 || 4.5 || 0.13 || || 35 || 2.00 || bitcoin-miner 0.13/WinXP || No GPU
|-
| Core 2 Duo T7450 || 2/2 || 3.7 || 0.10 || || 35 || 2.13 || bitcoin-miner 0.10 || Ubuntu 11.04
|-
| Core 2 Duo T9400 || 2/2 || 4.2 || || || || 2.53 || ufasoft v0.13 || Win7-64
|-
| Core 2 Extreme X9000 || 2/2 || 2.37 || || || || 2.8 || rpcminer-cpu || Win7-64
|-
| Core 2 Extreme X9000 || 2/2 || 6.2 || || || || 2.8 || ufasoft v0.11 || Win7-64
|-
| Core 2 Extreme X9000 || 2/2 || 7.2 || || || || 3.2 || ufasoft v0.11 || Win7-64 Overclocked from 2.8 GHz to 3.2 GHz
|-
| Xeon 2.8 || 2/2 || 0.8 || || || || 2.8 || cpuminer || cryptopp_asm32
|-
| Xeon 3060 || 1/2 || 2.03 || 0.03 || || 65 || 2. || cpuminer 0.8.1 (Linux) || --algo=cryptopp_asm32
|-
| Xeon Prestonia 2.4 (dual) || 2x1/2 || 2.16 || 0.017 || || 130 || 2.4 || ufasoft v0.4 ||
|-
| Xeon X5355 (dual) || 2x4/4 || 10.13 || 0.16 || || 120 || 2.6 || bitcoind || Roughly the same speed as the "c" algo in cpuminer
|-
| Xeon X5355 (dual) || 2x4/4 || 22.76 || 0.09 || || 120 || 2.6 || cpuminer (v0.8.1-1-g69529c3) || -O2 -march=core2, algo=sse2_64
|-
| Xeon X5365 (dual) || 2x4/4 || 26.00 || ? || || ? || 3.0 || cpuminer git (2011-06-15) || algo=sse2_64
|-
| Xeon X5650 || 2x6/24 || 28.6 || ? || ? || ? || 2.67 || cpuminer 1.0.2 || --algo 4way
|-
| Xeon E5335 || 4/4 || 9.35 || 0.12 || || 80 || 2.00 || ufasoft v0.11 || Vista-32
|-
| Xeon E5410 || 4/4 || 9.8 || ? || || 80 || 2.33|| ufasoft v0.10 || CentOS 5.5 x64
|-
| Xeon E5440 || 4/8 || 7.3 || ? || || 80 || 2.66|| Kiv's poclbm-gui || FIXME: Either wrong model # or wrong threads/speed info
|-
| Xeon E5506 || 4/4 || 9.6 || ? || || 80 || 2.13|| ufasoft v0.10 || CentOS 5.5 x64
|-
| Xeon E5520 || 4/8 || 6.5 || 0.08 || || 80 || 2.27 || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Xeon E5530 || 4/8 || 7.14 || 0.09 || || 80 || 2.4 || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Xeon E5620 || 4/8 || 11.2 || ? || || 80 || 2.4 || ufasoft v0.10 -t 4 || CentOS 5.5 x64 Hyper-Threading is off
|-
| Xeon E5630 (dual) || 2x4/8 || 8 || 0.1 || || 80 || 2.53 || 0.3.17/Win7-64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg29471#msg29471 source]
|-
| Xeon E6520 (dual) || 2x4/8 || 24.7 || || || || 2.53 || ufasoft v0.10 || windows 2008 R2 64bit (-t 16)
|-
| Xeon E7220 || 2/2 || 6.3 || ? || || 80 || 2.93|| ufasoft v0.10 || CentOS 5.5 x64
|-
| Xeon E7320 (dual) || 2x2 || 1.5 || || || || 2.8 || cgminer v1.2.8 || 2x2.8ghz dual core running Ubuntu 11.04 x86 (individual cores get 0.4 MH/s)
|-
| Xeon E7450 (quad) || 4x6/24 || 60 || || || || 2.40 || ufasoft v0.13 || -t 24
|-
| Xeon E7520 (dual) || 2x4/16 || 18 || || || 95 || 1.87 || ufasoft v0.10 || windows 2008 R2 64bit (-t 16)
|-
| Xeon W3680 || 6/12 || 18 || || || 130 || 3.33 || cpuminer v1.0.2 --algo=4way || Ubuntu 11.04 64bit
|-
| Atom Z520 || 1/2 || 1.20 || || || 2 || 1.7 || ufasoft 1.18 || Asus Eee 1101HA with overclocking capabilities
|-
| Atom N230 || 1/2 || 0.375 || || || 4 || 1.6 || rpcminer-cpu ||
|-
| Atom N230 || 1/2 || 0.245 || || || 4 || 1.6 || rpcminer-4way ||
|-
| Atom N230 || 1/2 || 0.97 || || || 4 || 1.6 || ufasoft v0.10 ||
|-
| Atom N270 || 1/2 || 1.19 || 0.24 || || 5 || 1.6 || ufasoft v0.10 ||
|-
| Atom N450 || 1/2 || 1.60 || 0.31 || || 6.5 || 2.06 || ufasoft v0.10 ||
|-
| Atom N550 || 2/4 || 1.97 || || || || 1.5 || ufasoft v0.21 || Windows 7/64 bit
|-
| Atom 330 || 2/4 || 1.80 || || || 8 || 1.6 || ufasoft v0.13 || -t 4
|-
| Atom D510 || 2/4 || 1.00 || || || || 1.6 || cpuminer w cryptopp_asm32 || debian linux 6.0, headless system, 2 GB RAM, running from usb-flash
|-
| Atom D510 || 4/4 || 2.3 || 0.07 || || 30 || 1.6 || bitcoin-miner 0.10 || Ubuntu 11.04 Server
|}

<references>
<ref name='amazon_20110625'>$ Prices from http://www.amazon.com on 2011-06-25</ref>
<ref name='geizhals_20110625'>€ Prices from http://geizhals.at/eu on 2011-06-25</ref>
</references>

===Other===
{| class="wikitable sortable"
|-
! Model !! p/t !! Mhash/s !! Mhash/J !! Mhash/s/$ !! ACP [W] !! Clock !! Version !! Comment
|-
| Cell || 6 || 21 || 0.35 || 0.07 || 60W || 3.2 GHz || Cellminer || Sony Playstation 3 (FAT): Needs custom firmware. [https://github.com/verement/cellminer source] [http://www.bitcoin.org/smf/index.php?topic=4704.20 source] Total power usage of PS3 fat is 120W but only the Cell cpu is active.
|-
| Cell || 7 || 26.6 || ? || ? || 60W || 3.2 GHz || Cellminer || Sony Playstation 3 (FAT): Needs custom firmware. [https://github.com/verement/cellminer source] [http://www.bitcoin.org/smf/index.php?topic=4704.20 source] Running with 7th spu enabled and both ppe cores.
|-
| Cell || 6 || 21 || 0.7 || 0.07 || 35W || 3.2 GHz || cellminer || Sony Playstation 3 (SLIM): Total power usage of PS3 slim is 70W but only the Cell cpu is active.
|-
| ARM || 1 || 0.187 || ? || ? || ? || 1200 MHz || cpuminer || Seagate Dockstar [http://archlinuxarm.org/platforms/armv5/seagate-dockstar ArchLinux]
|-
| MIPS || 1 || 0.026 || ? || ? || ? || 200 MHz || cpuminer || ASUS WL-500G Deluxe Router Running [http://openwrt.org/ OpenWrt]
|-
| VIA Eden || 1 || 1.3 || 0.17 || || 8W || 1600 MHz || cpuminer || VIA Eden w/ padlock
|-
| PowerPC 7447A || 1 || 0.53 || || || || 1420 MHz || cpuminer ||
|-
| PowerPC 7450 (G4e) || 1 || 1.29 || || || || 1670 MHz || cgminer 2.0.7 || PowerBook5,6; Mac OS X 10.5.8; Altivec
|-
| PowerPC 750 (G3) || 1 || 0.140 || || || || 600 MHz || cpuminer || iBook G3 600 w/ Cryptopp
|-
| IBM Power7 (PowerPC) || || 7.6 || || || || 3.5 Ghz || cgminer || IBM Power7 770, SuSE Linux 11.1, 4 cores, OpenCL, YASM, Altivec
|}

===FPGA Devices===

{| class="wikitable sortable"
|-
! Board !! Cores !! Mhash/s !! Mhash/J !! Mhash/s/$ !! Power [W] !! Board price !! Clock !! Version !! FPGA Model !! Comment
|-
| Terasic DE2-115 || 1 || 80 || 18.18 || 0.13 || 4.4 || $595 ($299 academic) <ref>price from http://www.terasic.com.tw/cgi-bin/page/archive.pl?No=502 on 2011-06-26</ref> || 80 MHz || fpgaminer 0.03 || Altera EP4CE115C7 || Unoptimized Pipelined Version
|-
| Terasic DE2-115 || 1 || 109 || || 0.18 || || $595 ($299 academic) <ref>Price from http://www.terasic.com.tw/cgi-bin/page/archive.pl?No=502 on 2011-06-26</ref> || 109 MHz || fpgaminer 0.03-makomk || Altera EP4CE115C7 || Makomk's Improvements
|-
| XUPV5-LX110T || 1 || 120 || || 0.06 || || $1999 ($750 academic) <ref>Price from http://www.digilentinc.com/Products/Detail.cfm?NavPath=2,400,795&Prod=XUPV5 on 2011-06-26</ref> || 120 MHz || fpgaminer virtex5 || Xilinx XC5VLX110T-1FF1136 || Original non-configurable fully-unrolled Xilinx VHDL Design
|-
| Digilent Nexys 2 500K || 1 || 3.125 || 4.0 || 0.02 || 0.78 || $149 ($99 academic) <ref>Price from http://www.digilentinc.com/Products/Detail.cfm?Prod=NEXYS2 on 2011-06-26</ref> || 100 MHz || fpgaminer Verilog Xilinx port || Xilinx XC3S500E-FG320-5 ||
|-
| Avnet Spartan-6 LX150T Development Kit || 1 || 100 || ~25 || || ~4.0 || $995 <ref>Price from http://www.xilinx.com/products/boards-and-kits/AES-S6DEV-LX150T-G.htm on 2011-07-26</ref> || 100 MHz || fpgaminer makomk Xilinx port || Xilinx XC6SLX150T-3FGG676 || -3N 484-pin chip is ~$150, 0.67Mhash/s/$
|-
| Terasic DE0-Nano || 1 || 6.25 || ?? || 0.08 || ?? || 79$ || 50 MHz || Makomk-partial-unroll-speed, LOG2_LOOP=3 || Altera EP4CE22F17C6 || 16k LEs from 22k used
|-
| Xilinx ML605 development kit || 3 || 375 || 23 || 0.21 || 16 || $1795 <ref>Price from Avnet on Aug 11, 2011</ref> || 125MHz || Modified verilog xilinx fpga miner port (modified for 3 cores, a PCIe interface and use of DSP48s)|| Xilinx XC6VLX240T-1FFG1156 || Uses PCIe interface instead of serial interface. ML605 power manager must have its current limit increased to meet power demands. DSP48s used to reduce logic resources.
|-
| Bitcoin Dominator X5000 || 1 || 100 || 14.7 || 0.23 || 6.8 || $440 <ref>Price from https://bitcointalk.org/index.php?topic=37904.0</ref> || 100 MHz || || Xilinx XC6SLX150-3FG484 ||
|-
| X6500 FPGA Miner || 1 || 400 || 16.6 || 0.71 || 20 || $560 <ref>Price from https://bitcointalk.org/index.php?topic=40058.0</ref> || 200 MHz || X5000_ztexmerge || Xilinx XC6SLX150-2FG484 x2 || See <ref>http://fpgamining.com/bitstreams/</ref> for bitstreams and frequencies
|-
| [http://en.qi-hardware.com/wiki/Icarus Icarus] || 1 || 380 || 19 || 0.66 || 20 || $569 <ref>Price from https://bitcointalk.org/index.php?topic=51371.0</ref> || 190 MHz || Bitstream V3 || Xilinx XC6SLX150-2FGG484I ||
|-
| [http://www.ztex.de/usb-fpga-1/usb-fpga-1.15.e.html ZTEX USB-FPGA Module 1.15b] || 1 || 90 || 18.0 || 0.25 || 5.0 || $364 <ref>http://shop.ztex.de</ref> || 184 MHz || [http://www.ztex.de/btcminer BTCMiner]-120208 || Xilinx XC6SLX75-3 || single unit price including Experimental Board 1.3 as baseboard ||
|-
| [http://www.ztex.de/usb-fpga-1/usb-fpga-1.15x.e.html ZTEX USB-FPGA Module 1.15x] || 1 || 210 || 22.3 || 0.82-0.5 || 9.4 || $255-$420 <ref>https://bitcointalk.org/index.php?topic=49180.0</ref> || 210 MHz || [http://www.ztex.de/btcminer BTCMiner]-120208 || Xilinx XC6SLX150-3/-N3 || See <ref>https://bitcointalk.org/index.php?topic=49180.0</ref> for prices ||
|}

<references>
</references>

==See Also==

* [[Mining rig]]
* [[ZTEX FPGA Boards for Bitcoin Mining]]
* [[Generation Calculator]]
* [[Power Calc]]
* [[OpenCL miner]]
* [http://www.pcper.com/article.php?aid=745 ATI Stream vs. NVIDIA CUDA - GPGPU computing battle royale]
* [http://bitminer.info/ Bitminer.info]
* [http://www.pcper.com/reviews/Graphics-Cards/Bitcoin-Currency-and-GPU-Mining-Performance-Comparison Bitcoin Mining Performance Compared]
** [http://www.pcper.com/reviews/Graphics-Cards/Bitcoin-Mining-Update-Power-Usage-Costs-Across-United-States Bitcoin Mining Power Costs Compared]

[[Category:Mining]]

Myths

2011-12-28T00:20:27Z

Graingert: That site no longer operates and probably should not be linked to

Let's clear up some common Bitcoin misconceptions.

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

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

Being decentralized, Bitcoin solves all of these problems.

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

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

Unlike fiat currencies, bitcoins are:
* predictable and limited in [[Controlled_Currency_Supply|supply]]
* not controlled by a central authority (such as [http://en.wikipedia.org/wiki/Federal_Reserve The Fed])

Unlike electronic fiat currency systems, bitcoins are:
* potentially anonymous
* freeze-proof
* faster to transfer
* cheaper to transfer

== Bitcoin is backed by processing power ==

It is not correct to say that Bitcoin is backed by processing power. A currency being "backed" by something means that it is pegged to something else via a central party at a certain exchange rate. You cannot exchange bitcoins for the computing power that was used to create them. Bitcoin is in this sense not backed by anything. It is a currency in its own right. Similar to gold - is gold backed by anything? No! It's just gold. The same applies with Bitcoin.

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

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

Gold isn't backed by anything either. Bitcoins have properties inherent to its design that are subjectively valued by individuals. This valuation is demonstrated when individuals freely exchange for or with bitcoins. Please refer to the [http://en.wikipedia.org/wiki/Subjective_theory_of_value Subjective Theory of Value]. See also myth [[#Bitcoin_is_backed_by_processing_power|Bitcoin is backed by processing power]].

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

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

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

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

It is true that bitcoins have no intrinsic value, in the [http://en.wikipedia.org/wiki/Intrinsic_value_%28numismatics%29 numismatic sense], in other words, value in any realm outside of being used as a medium of exchange.

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

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

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

== Bitcoins are illegal because they're not legal tender ==

Short answer: chickens aren't legal tender either, but bartering with chickens is not illegal.

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

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

http://en.wikipedia.org/wiki/Definitions_of_terrorism#United_States according to this, you need to do violent activities to be considered a terrorist for legal purposes. This has no bearing on politicians and idiotic US attorney's public remarks.

Also, Bitcoin isn't domestic. It's a worldwide community. See this map of Bitcoin nodes
http://forum.bitcoin.org/?topic=2346.0

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

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

While it may be easy to transfer bitcoins anonymously, ''spending'' them anonymously on tangibles is just as hard as spending any other kind of money anonymously. Tax evaders are often caught because of suspicious purchases, or undeclared assets, not because government is able to follow their money.

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

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

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

SHA256 and ECDSA which are used in Bitcoin are well-known industry standard algorithms. If you believe that these algorithms are untrustworthy then you should not trust Bitcoin, credit card transactions or any type of electronic bank transfer.

== Early adopters are unfairly rewarded ==

Early adopters are rewarded for taking the higher risk with their time and money.

In more pragmatic terms, "fairness" is an arbitrary concept that is improbable to be agreed upon by a large population. Establishing "fairness" is no goal of Bitcoin, as this would be impossible.

The vast majority of the 21 million Bitcoins still have not been distributed. By starting to mine or acquire bitcoins today, you too can become an early adopter.

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

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

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

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

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

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

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

Bitcoins are divisible to 0.00000001, so this is not a problem. If you lose your coins, all other coins will go up in value a little. Consider it a donation to all other bitcoin users.

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

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

A ponzi scheme is a zero sum game. Early adopters can only profit at the expense of late adopters. Bitcoin has possible win-win outcomes. Early adopters profit from the rise in value. Late adopters profit from the usefulness of a stable and widely accepted p2p currency.

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

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

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

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

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

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

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

The members of the community vary in their ideological stances.

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

CONFIRMED, see [[Weaknesses]].

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

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

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

== Bitcoin violates governmental regulations ==

Name them if you can.

See also the [[Myths#Bitcoins_are_illegal_because_it_s_not_legal_tender|legal tender]] question.

== Fractional reserve banking is not possible ==

Please see the main article, [[Fractional Reserve Banking and Bitcoin]]

== Point of sale with bitcoins isn't possible because of the 10 minute wait for confirmation ==

Transactions [[FAQ#Why_do_I_have_to_wait_10_minutes_before_I_can_spend_money_I_received.3F|can]] take tens of minutes to become ''confirmed'', and this won't change for the foreseeable future. Even after the computing power of the network is orders of magnitude larger than today, the difficulty of generating a block will self-adjust to maintain a target of 6 blocks per hour. Three potential solutions to allow POS transactions are:

'''1.''' For small transactions, simply assume the customer isn't ripping you off. Give the customer his latte immediately after the transaction posts to the network. The transaction should propagate through the network almost instantly, allowing the seller to see the transaction within seconds (albeit with zero confirmations.) The cost of a double-spend attack should make small-scale fraud not worthwhile.

'''2.''' Utilize a [https://bitcointalk.org/index.php?topic=423.msg3819#msg3819 'listening' period] prior to rendering the service or good. This has yet to be formally implemented in the standard Bitcoin client, but would allow a vendor to receive the transaction and then monitor the Bitcoin network for a certain period of time (maybe 10 seconds) for possible double spends. Vendors might utilize specialized payment processors with multiple well-connected nodes for this purpose. As explained by Satoshi, the network nodes only accept the first version of a transaction they receive to incorporate into the block they're trying to generate. When you broadcast a transaction, if someone else broadcasts a double-spend at the same time, it is a race to propagate them to the most nodes first. If one has a slight head start, it will geometrically spread through the network and get many times more nodes. Additionally, a payment "processing" company could blast out the transaction to thousands of nodes instantly and listen for double spend attempts. The probability of the attacker thwarting such a system would be so low that a payment processor could ''guarantee'' payments and eat the cost if a double-spend attempt actually succeeds. If a double-spend attempt is detected, the vendor is notified: no latte, and a call to the police should be put in immediately.

'''3.''' Create a network of transaction hubs. These entities would communicate using a common API. They would float short-term loans between each other to facilitate instant transactions.

Imagine that Alice uses Carol's Clearinghouse as her hub, and Bob uses Dave's Anonymous Exchange. Both Alice and Bob have accounts with their respective hubs, and have already deposited some bitcoins in their accounts. When Alice wants to buy a latte from Bob at a point of sale, Alice tells Carol "I want to send Bob ''x'' bitcoins. He uses Dave's Anonymous Exchange." After checking that Alice's account does contain at least ''x'' bitcoins, Carol sends a message to Dave, saying "Credit Bob's account with ''x'' bitcoins immediately; I'll send you the real bitcoins in the next block." Bob instantly sees his balance increase, and gives Alice her latte.

Optionally, option 3 allows all parties to circumvent use of the block-chain and its associated fees altogether. If Alice and Bob have accounts with Carol and Dave, then Carol and Dave are effectively functioning as banks. Carol and Dave can credit and debit millions of accounts millions of times daily and only "re-balance" money owed at the end of each business day through a single transaction in the Bitcoin block-chain.

Option 3 requires trust. Alice has to trust Carol's Clearinghouse, and the hubs have to trust each other. Due to competition, various hubs could develop with vastly different fee structures, membership requirements, trustability, etc. The advantage of option 3 is that it is instant. The disadvantage of option 3 is that trust is required. If trust is not established, option 2 can be used.

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

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

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

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

'''Why it's actually a good thing''': Bitcoin is designed such that your money is yours and yours alone. Allowing chargebacks implies that it is possible for another entity to take your money from you. You can have either total ownership rights of your money, or fraud protection, but not both. That said, nothing prevents the creation of services overlayed on top of Bitcoin that provide fraud protection services.

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

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

Yes, but quantum computers don't yet exist and probably won't for a while. Bitcoin's security can be [http://en.wikipedia.org/wiki/Post-quantum_cryptography upgraded] if this were considered an imminent threat.

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

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

== [[Mining|Bitcoin mining]] is a waste of energy and harmful for ecology ==

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

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

'''Economic Argument 1'''

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

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

Market forces could even push mining into innovative solutions that have a ''net'' electricity consumption of ''zero''. For example, electric heaters could come equipped with a cheap CPU instead of a resistance coil.

'''Economic Argument 2'''

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

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

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

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

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

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

* Hopefully Bitcoin will grow to the point where no single organization can disrupt the network, or would be better served by helping it.
* Terrorists fly aircraft into buildings, but the governments have not yet abolished consumer air travel. Obviously the public good outweighs the possible bad in their opinion.
* Criminal law differs between jurisdictions.

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

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

Bitcoins are not coins at all, nor are they banknotes. They do not resemble US currency in any way, shape, or form. The word "dollar" is not attached to them in any way. The "$" symbol is not used in any way.

Bitcoins have no representational similarity whatsoever to US dollars.

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

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

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

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

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

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

[[de:Mythen]]

Bitcoin randomizer

2011-12-28T00:19:30Z

Graingert:

The '''Bitcoin Randomizer''' is a self-labeled Ponzi-style scheme that rewards those who have contributed earlier to gain proportionally more than those who have contributed later.

The site is no longer accepting or releasing funds
==External Links==

* [http://fxnet.bitlex.org Bitcoin Randomizer web site]

[[Category:Gambling]]

User talk:Graingert

2011-11-28T00:57:26Z

Graingert: Blanked the page

Zero Knowledge Contingent Payment

2011-11-28T00:34:55Z

Graingert: /* Zero knowledge contingent payments */

Its possible to make a transaction in bitcoin that requires the spender to provide a "secret" which hashes to a specified value. And example is the 0.01 output here with the SHA256 opcode: https://blockexplorer.com/tx/9969603dca74d14d29d1d5f56b94c7872551607f8c2d6837ab9715c60721b50e

Used directly, like in this example, this is insecure. Once you've published the spending transaction a trouble making miner could just drop your transaction and use the password in a new transaction that pays him instead.

So— the advice is that you shouldn't use a password alone, you should require a signature and a password. But then what is the use of that?

There are a couple uses but I'll give an example here of one of the more impressive uses:

==Zero knowledge contingent payments==

Let H() be a complicated computer program. For some H(X)=Y you want to know some X that gives you a particular Y.

Perhaps H() is a password hashing algorithm and you're looking for the password that gives you a particular hash in order to crack it. Or perhaps H() is a complicated program that decides if a image is one you would find beautiful. We'll use password cracking here, but this works for all programs.

Say I happen to _know_ some X that answers your question... and I'd like to sell it to you. But we don't trust each other at all, and because we're computer geeks we have no friends who can act as trusted mediators. Can we make this exchange using bitcoin with zero trust? Yes.

A [[w:zero-knowledge proof]] lets someone prove a mathematical fact to another person without teaching them anything about the fact itself. It has been proven that you can convert any computer program into a proof. So, using a zero-knowledge proof I could prove to you that I know some X such that H(X)=Y ... which is helpful but it's not enough because you could pay me and I could not tell you the answer (or I could tell you and then you don't pay). Here is where the password locked transactions come in.

First I encrypt X with random key K, Ex=AES(X,K).
then I construct the program:

Ex=AES(X,K);Hk=SHA256(K);H(UNAES(Ex,K))+Ex+Hk==Y+Ex+Hk

and I convert that program into a zero knowledge proof. Externally to bitcoin I tell you Ex,Hk and then prove the above statement to be true.

You then form a bitcoin payment which requires both my public key and password K. In order to redeem this transaction I must disclose K, the key you need to decrypt Ex and give you your solution. So neither of us can cheat, so no trust is required.

The reason this isn't something people are using yet is because while the academics have proven it to be possible actually converting complicated programs like compositions of ciphers and hash-functions into zero-knowledge proofs is apparently not something anyone has figured out how to do practically.

Myths

2011-11-09T11:27:13Z

Graingert:

Let's clear up some common Bitcoin misconceptions.

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

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

Being decentralized, Bitcoin solves all of these problems.

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

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

Unlike fiat currencies, bitcoins are:
* predictable and limited in [[Controlled_Currency_Supply|supply]]
* not controlled by a central authority(Ex. Fed)

Unlike electronic fiat currency systems, bitcoins are:
* potentially anonymous
* freeze proof
* faster to transfer
* cheaper to transfer

== Bitcoin is backed by processing power ==

It is not correct to say that Bitcoin is backed by processing power. A currency being "backed" by something means that it is pegged to something else via a central party at a certain exchange rate. You cannot exchange bitcoins for the computing power that was used to create them. Bitcoin is in this sense not backed by anything. It is a currency in its own right. Similar to gold - is gold backed by anything? No! It's just gold. The same applies with Bitcoin.

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

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

Gold isn't backed by anything either. Bitcoins have properties inherent to its design that are subjectively valued by individuals. This valuation is demonstrated when individuals freely exchange for or with bitcoins. Please refer to the [http://en.wikipedia.org/wiki/Subjective_theory_of_value Subjective Theory of Value]. See also myth [[#Bitcoin_is_backed_by_processing_power|Bitcoin is backed by processing power]].

== Bitcoins value is based on how much electricity and computing power it takes to mine them ==

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

In fact the causality is the reverse of that (this applies to the labor theory of value in general). The cost to mine Bitcoins is based on how much they are worth. If Bitcoins go up in value, more people will mine (because mining is profitable), thus [[difficulty]] will go up, thus the cost of mining will go up. The inverse happens if bitcoins go down in value. These effects balance out to cause mining to always cost the amount of bitcoins it produces.

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

It is true that bitcoins have no intrinsic value, in the [http://en.wikipedia.org/wiki/Intrinsic_value_%28numismatics%29 numismatic sense], in other words, value in any realm outside of being used as a medium of exchange.

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

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

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

== Bitcoins are illegal because they're not legal tender ==

Short answer: chickens aren't legal tender either, but bartering with chickens is not illegal.

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

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

http://en.wikipedia.org/wiki/Definitions_of_terrorism#United_States according to this, you need to do violent activities to be considered a terrorist for legal purposes. This has no bearing on politicians and idiotic US attorney's public remarks.

Also, Bitcoin isn't domestic. It's a worldwide community. See this map of Bitcoin nodes
http://forum.bitcoin.org/?topic=2346.0

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

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

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

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

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

SHA256 and ECDSA which are used in Bitcoin are well-known industry standard algorithms. If you believe that these algorithms are untrustworthy then you should not trust Bitcoin, credit card transactions or any type of electronic bank transfer.

== Early adopters are unfairly rewarded ==

Early adopters are rewarded for taking the higher risk with their time and money.

In more pragmatic terms, "fairness" is an arbitrary concept that is improbable to be agreed upon by a large population. Establishing "fairness" is no goal of Bitcoin, as this would be impossible.

The vast majority of the 21 million Bitcoins have been distributed. By starting to mine or acquire bitcoins today, you too can become an early adopter.

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

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

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

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

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

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

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

Bitcoins are divisible to 0.00000001, so this is not a problem. If you lose your coins, all other coins will go up in value a little. Consider it a donation to all other bitcoin users.

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

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

A ponzi scheme is a zero sum game. Early adopters can only profit at the expense of late adopters. Bitcoin has possible win-win outcomes. Early adopters profit from the rise in value. Late adopters profit from the usefulness of a stable and widely accepted p2p currency.

Not to be confused with the [[Bitcoin randomizer|Bitcoin Randomizer]] which is a game that really is self-described as a Ponzi scheme.

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

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

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

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

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

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

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

The members of the community vary in their ideological stances.

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

CONFIRMED, see [[Weaknesses]].

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

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

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

== Bitcoin violates governmental regulations ==

Name them if you can.

See also the [[Myths#Bitcoins_are_illegal_because_it_s_not_legal_tender|legal tender]] question.

== Fractional reserve banking is not possible ==

Fractional reserve banking arises when issuers of money substitutes create more substitutes than the reserves they have. The process is described in more detail in [http://en.wikipedia.org/wiki/Fractional-reserve_banking Wikipedia article on Fractional reserve banking]:
<blockquote>As most bank deposits are treated as money in their own right, fractional reserve banking increases the money supply, and banks are said to create money.</blockquote>
Practicing fractional reserve banking without issuing money substitutes is not logically possible.

With fiat money, the base money are the reserves commercial banks have with the central banks, and the substitutes are the account balances of the customers of commercial banks. With gold, the base money is the gold bullion/coins stored at the bank, and the substitutes are bank notes, cheques, account balances or other instruments the commercial banks provide to the depositors.

The reason why substitutes are accepted as if they were the base money is that the base money has in some circumstances high transaction costs (for example, gold might be too heavy to carry around, or the buyer and seller are not at the same location and want to perform the exchange electronically), or are not legally permitted (normal people are not allowed to obtain central bank reserves). This creates a demand for forms of money which have lower transaction costs. With gold/fiat, this requires the creation of money substitutes.

The situation with Bitcoin is different, because other forms can be created without substitutes, for example [[Casascius physical bitcoins]] or [[BitBills]]. Bitcoin in its "classical" form is the equivalent of a bank deposit. An issuer of a Bitcoin substitute, before they even think about practicing FRB, would need to find a way of creating demand for these substitutes. This is problematic, because such substitutes are incompatible with the Bitcoin network, and need to compete against not only Bitcoin, but against other currencies, payment methods and services. Currently, the only examples of such substitutes are account balances on exchanges, and most e-wallets ([[Strongcoin]] being an exception, using client-side encryption, the balances of their deposits are just another way of storing a Bitcoin wallet, so they are not substitutes). Even in these examples, Bitcoin substitutes do not circulate outside of centralised systems, so performing FRB with them has a limited impact on the money supply and is very risky.

If in the future, P2P exchanges and distributed wallets are available (both have been suggested already at bitcointalk.org forums), this would decrease the demand for Bitcoin substitutes even further.

Historically, in all the situations where fractional reserve Bitcoin substitutes were produced, this resulted either in a voluntary elimination of the excess substitutes (Mt. Gox hack from June 2011), bankruptcy (the demise of mybitcoin) or a new investor bailout (the demise of bitomat.pl and subsequent takeover by Mt. Gox). Here we have empirical evidence that FRB with Bitcoin is possible.

In face of the lack of demand for Bitcoin-substitutes, it is doubful whether FRB with Bitcoin can be conducted in a profitable manner and have a similar impact and scale than with fiat/gold.

== Point of sale with bitcoins isn't possible because of the 10 minute wait for confirmation ==

Transactions [[FAQ#Why_do_I_have_to_wait_10_minutes_before_I_can_spend_money_I_received.3F|can]] take tens of minutes to become ''confirmed'', and this won't change for the foreseeable future. Even after the computing power of the network is orders of magnitude larger than today, the difficulty of generating a block will self-adjust to maintain a target of 6 blocks per hour. Three potential solutions to allow POS transactions are:

'''1.''' For small transactions, simply assume the customer isn't ripping you off. Give the customer his latte immediately after the transaction posts to the network. The transaction should propagate through the network almost instantly, allowing the seller to see the transaction within seconds (albeit with zero confirmations.) The cost of a double-spend attack should make small-scale fraud not worthwhile.

'''2.''' Utilize a [https://bitcointalk.org/index.php?topic=423.msg3819#msg3819 'listening' period] prior to rendering the service or good. This has yet to be formally implemented in the standard Bitcoin client, but would allow a vendor to receive the transaction and then monitor the Bitcoin network for a certain period of time (maybe 10 seconds) for possible double spends. Vendors might utilize specialized payment processors with multiple well-connected nodes for this purpose. As explained by Satoshi, the network nodes only accept the first version of a transaction they receive to incorporate into the block they're trying to generate. When you broadcast a transaction, if someone else broadcasts a double-spend at the same time, it is a race to propagate them to the most nodes first. If one has a slight head start, it will geometrically spread through the network and get many times more nodes. Additionally, a payment "processing" company could blast out the transaction to thousands of nodes instantly and listen for double spend attempts. The probability of the attacker thwarting such a system would be so low that a payment processor could ''guarantee'' payments and eat the cost if a double-spend attempt actually succeeds. If a double-spend attempt is detected, the vendor is notified: no latte, and a call to the police should be put in immediately.

'''3.''' Create a network of transaction hubs. These entities would communicate using a common API. They would float short-term loans between each other to facilitate instant transactions.

Imagine that Alice uses Carol's Clearinghouse as her hub, and Bob uses Dave's Anonymous Exchange. Both Alice and Bob have accounts with their respective hubs, and have already deposited some bitcoins in their accounts. When Alice wants to buy a latte from Bob at a point of sale, Alice tells Carol "I want to send Bob ''x'' bitcoins. He uses Dave's Anonymous Exchange." After checking that Alice's account does contain at least ''x'' bitcoins, Carol sends a message to Dave, saying "Credit Bob's account with ''x'' bitcoins immediately; I'll send you the real bitcoins in the next block." Bob instantly sees his balance increase, and gives Alice her latte.

Optionally, option 3 allows all parties to circumvent use of the block-chain and its associated fees altogether. If Alice and Bob have accounts with Carol and Dave, then Carol and Dave are effectively functioning as banks. Carol and Dave can credit and debit millions of accounts millions of times daily and only "re-balance" money owed at the end of each business day through a single transaction in the Bitcoin block-chain.

Option 3 requires trust. Alice has to trust Carol's Clearinghouse, and the hubs have to trust each other. Due to competition, various hubs could develop with vastly different fee structures, membership requirements, trustability, etc. The advantage of option 3 is that it is instant. The disadvantage of option 3 is that trust is required. If trust is not established, option 2 can be used.

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

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

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

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

'''Why it's actually a good thing''': Bitcoin is designed such that your money is yours and yours alone. Allowing chargebacks implies that it is possible for another entity to take your money from you. You can have either total ownership rights of your money, or fraud protection, but not both. That said, nothing prevents the creation of services overlayed on top of Bitcoin that provide fraud protection services.

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

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

Yes, but quantum computers don't yet exist and probably won't for a while. Bitcoin's security can be [http://en.wikipedia.org/wiki/Post-quantum_cryptography upgraded] if this were considered an imminent threat.

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

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

== Bitcoin mining is a waste of energy and harmful for ecology ==

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

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

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

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

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

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

* Hopefully Bitcoin will grow to the point where no single organization can disrupt the network, or would be better served by helping it.
* Terrorists fly aircraft into buildings, but the governments have not yet abolished consumer air travel. Obviously the public good outweighs the possible bad in their opinion.
* Criminal law differs between jurisdictions.

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

Liberty Dollars started as a commercial venture to establish alternative US currency, including physical banknotes and coins, backed by precious metals. This, in and of itself, is not illegal. They were later shut down for counterfeiting and intent to fraud after the coins, which contained less than $1 worth of silver, were put into circulation with the general money supply, supposedly having a value of 1 USD. These actions were encouraged by the makers of Liberty Dollars.

Bitcoins are not necessarily equal in value to dollars or any other currency and no one is saying they are. No member of the public will be tricked into accepting a bitcoin instead of a dollar.

Of course, actually 'shutting down' the decentralized Bitcoin network is rife with its own set of difficult considerations.

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

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

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

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

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

[[de:Mythen]]

Myths

2011-11-09T11:26:59Z

Graingert:

Let's clear up some common Bitcoin misconceptions.

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

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

Being decentralized, Bitcoin solves all of these problems.

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

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

Unlike fiat currencies, bitcoins are:
* predictable and limited in [[Controlled_Currency_Supply|supply]]
* not controlled by a central authority(Ex. Fed)

Unlike electronic fiat currency systems, bitcoins are:
* potentially anonymous
* freeze proof
* faster to transfer
* cheaper to transfer

== Bitcoin is backed by processing power ==

It is not correct to say that Bitcoin is backed by processing power. A currency being "backed" by something means that it is pegged to something else via a central party at a certain exchange rate. You cannot exchange bitcoins for the computing power that was used to create them. Bitcoin is in this sense not backed by anything. It is a currency in its own right. Similar to gold - is gold backed by anything? No! It's just gold. The same applies with Bitcoin.

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

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

Gold isn't backed by anything either. Bitcoins have properties inherent to its design that are subjectively valued by individuals. This valuation is demonstrated when individuals freely exchange for or with bitcoins. Please refer to the [http://en.wikipedia.org/wiki/Subjective_theory_of_value Subjective Theory of Value]. See also myth [[#Bitcoin_is_backed_by_processing_power|Bitcoin is backed by processing power]].

== Bitcoins value is based on how much electricity and computing power it takes to mine them ==

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

In fact the causality is the reverse of that (this applies to the labor theory of value in general). The cost to mine Bitcoins is based on how much they are worth. If Bitcoins go up in value, more people will mine (because mining is profitable), thus [[difficulty]] will go up, thus the cost of mining will go up. The inverse happens if bitcoins go down in value. These effects balance out to cause mining to always cost the amount of bitcoins it produces.

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

It is true that bitcoins have no intrinsic value, in the [http://en.wikipedia.org/wiki/Intrinsic_value_%28numismatics%29 numismatic sense], in other words, value in any realm outside of being used as a medium of exchange.

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

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

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

== Bitcoins are illegal because they're not legal tender ==

Short answer: chickens aren't legal tender either, but bartering with chickens is not illegal.

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

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

http://en.wikipedia.org/wiki/Definitions_of_terrorism#United_States according to this, you need to do violent activities to be considered a terrorist for legal purposes. This has no bearing on politicians and idiotic US attorney's public remarks.

Also, Bitcoin isn't domestic. It's a worldwide community. See this map of Bitcoin nodes
http://forum.bitcoin.org/?topic=2346.0

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

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

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

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

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

SHA256 and ECDSA which are used in Bitcoin are well-known industry standard algorithms. If you believe that these algorithms are untrustworthy then you should not trust Bitcoin, credit card transactions or any type of electronic bank transfer.

== Early adopters are unfairly rewarded ==

Early adopters are rewarded for taking the higher risk with their time and money.

In more pragmatic terms, "fairness" is an arbitrary concept that is improbable to be agreed upon by a large population. Establishing "fairness" is no goal of Bitcoin, as this would be impossible.

The vast majority of the 21 million Bitcoins still have been distributed. By starting to mine or acquire bitcoins today, you too can become an early adopter.

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

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

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

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

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

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

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

Bitcoins are divisible to 0.00000001, so this is not a problem. If you lose your coins, all other coins will go up in value a little. Consider it a donation to all other bitcoin users.

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

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

A ponzi scheme is a zero sum game. Early adopters can only profit at the expense of late adopters. Bitcoin has possible win-win outcomes. Early adopters profit from the rise in value. Late adopters profit from the usefulness of a stable and widely accepted p2p currency.

Not to be confused with the [[Bitcoin randomizer|Bitcoin Randomizer]] which is a game that really is self-described as a Ponzi scheme.

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

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

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

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

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

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

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

The members of the community vary in their ideological stances.

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

CONFIRMED, see [[Weaknesses]].

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

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

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

== Bitcoin violates governmental regulations ==

Name them if you can.

See also the [[Myths#Bitcoins_are_illegal_because_it_s_not_legal_tender|legal tender]] question.

== Fractional reserve banking is not possible ==

Fractional reserve banking arises when issuers of money substitutes create more substitutes than the reserves they have. The process is described in more detail in [http://en.wikipedia.org/wiki/Fractional-reserve_banking Wikipedia article on Fractional reserve banking]:
<blockquote>As most bank deposits are treated as money in their own right, fractional reserve banking increases the money supply, and banks are said to create money.</blockquote>
Practicing fractional reserve banking without issuing money substitutes is not logically possible.

With fiat money, the base money are the reserves commercial banks have with the central banks, and the substitutes are the account balances of the customers of commercial banks. With gold, the base money is the gold bullion/coins stored at the bank, and the substitutes are bank notes, cheques, account balances or other instruments the commercial banks provide to the depositors.

The reason why substitutes are accepted as if they were the base money is that the base money has in some circumstances high transaction costs (for example, gold might be too heavy to carry around, or the buyer and seller are not at the same location and want to perform the exchange electronically), or are not legally permitted (normal people are not allowed to obtain central bank reserves). This creates a demand for forms of money which have lower transaction costs. With gold/fiat, this requires the creation of money substitutes.

The situation with Bitcoin is different, because other forms can be created without substitutes, for example [[Casascius physical bitcoins]] or [[BitBills]]. Bitcoin in its "classical" form is the equivalent of a bank deposit. An issuer of a Bitcoin substitute, before they even think about practicing FRB, would need to find a way of creating demand for these substitutes. This is problematic, because such substitutes are incompatible with the Bitcoin network, and need to compete against not only Bitcoin, but against other currencies, payment methods and services. Currently, the only examples of such substitutes are account balances on exchanges, and most e-wallets ([[Strongcoin]] being an exception, using client-side encryption, the balances of their deposits are just another way of storing a Bitcoin wallet, so they are not substitutes). Even in these examples, Bitcoin substitutes do not circulate outside of centralised systems, so performing FRB with them has a limited impact on the money supply and is very risky.

If in the future, P2P exchanges and distributed wallets are available (both have been suggested already at bitcointalk.org forums), this would decrease the demand for Bitcoin substitutes even further.

Historically, in all the situations where fractional reserve Bitcoin substitutes were produced, this resulted either in a voluntary elimination of the excess substitutes (Mt. Gox hack from June 2011), bankruptcy (the demise of mybitcoin) or a new investor bailout (the demise of bitomat.pl and subsequent takeover by Mt. Gox). Here we have empirical evidence that FRB with Bitcoin is possible.

In face of the lack of demand for Bitcoin-substitutes, it is doubful whether FRB with Bitcoin can be conducted in a profitable manner and have a similar impact and scale than with fiat/gold.

== Point of sale with bitcoins isn't possible because of the 10 minute wait for confirmation ==

Transactions [[FAQ#Why_do_I_have_to_wait_10_minutes_before_I_can_spend_money_I_received.3F|can]] take tens of minutes to become ''confirmed'', and this won't change for the foreseeable future. Even after the computing power of the network is orders of magnitude larger than today, the difficulty of generating a block will self-adjust to maintain a target of 6 blocks per hour. Three potential solutions to allow POS transactions are:

'''1.''' For small transactions, simply assume the customer isn't ripping you off. Give the customer his latte immediately after the transaction posts to the network. The transaction should propagate through the network almost instantly, allowing the seller to see the transaction within seconds (albeit with zero confirmations.) The cost of a double-spend attack should make small-scale fraud not worthwhile.

'''2.''' Utilize a [https://bitcointalk.org/index.php?topic=423.msg3819#msg3819 'listening' period] prior to rendering the service or good. This has yet to be formally implemented in the standard Bitcoin client, but would allow a vendor to receive the transaction and then monitor the Bitcoin network for a certain period of time (maybe 10 seconds) for possible double spends. Vendors might utilize specialized payment processors with multiple well-connected nodes for this purpose. As explained by Satoshi, the network nodes only accept the first version of a transaction they receive to incorporate into the block they're trying to generate. When you broadcast a transaction, if someone else broadcasts a double-spend at the same time, it is a race to propagate them to the most nodes first. If one has a slight head start, it will geometrically spread through the network and get many times more nodes. Additionally, a payment "processing" company could blast out the transaction to thousands of nodes instantly and listen for double spend attempts. The probability of the attacker thwarting such a system would be so low that a payment processor could ''guarantee'' payments and eat the cost if a double-spend attempt actually succeeds. If a double-spend attempt is detected, the vendor is notified: no latte, and a call to the police should be put in immediately.

'''3.''' Create a network of transaction hubs. These entities would communicate using a common API. They would float short-term loans between each other to facilitate instant transactions.

Imagine that Alice uses Carol's Clearinghouse as her hub, and Bob uses Dave's Anonymous Exchange. Both Alice and Bob have accounts with their respective hubs, and have already deposited some bitcoins in their accounts. When Alice wants to buy a latte from Bob at a point of sale, Alice tells Carol "I want to send Bob ''x'' bitcoins. He uses Dave's Anonymous Exchange." After checking that Alice's account does contain at least ''x'' bitcoins, Carol sends a message to Dave, saying "Credit Bob's account with ''x'' bitcoins immediately; I'll send you the real bitcoins in the next block." Bob instantly sees his balance increase, and gives Alice her latte.

Optionally, option 3 allows all parties to circumvent use of the block-chain and its associated fees altogether. If Alice and Bob have accounts with Carol and Dave, then Carol and Dave are effectively functioning as banks. Carol and Dave can credit and debit millions of accounts millions of times daily and only "re-balance" money owed at the end of each business day through a single transaction in the Bitcoin block-chain.

Option 3 requires trust. Alice has to trust Carol's Clearinghouse, and the hubs have to trust each other. Due to competition, various hubs could develop with vastly different fee structures, membership requirements, trustability, etc. The advantage of option 3 is that it is instant. The disadvantage of option 3 is that trust is required. If trust is not established, option 2 can be used.

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

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

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

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

'''Why it's actually a good thing''': Bitcoin is designed such that your money is yours and yours alone. Allowing chargebacks implies that it is possible for another entity to take your money from you. You can have either total ownership rights of your money, or fraud protection, but not both. That said, nothing prevents the creation of services overlayed on top of Bitcoin that provide fraud protection services.

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

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

Yes, but quantum computers don't yet exist and probably won't for a while. Bitcoin's security can be [http://en.wikipedia.org/wiki/Post-quantum_cryptography upgraded] if this were considered an imminent threat.

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

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

== Bitcoin mining is a waste of energy and harmful for ecology ==

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

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

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

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

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

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

* Hopefully Bitcoin will grow to the point where no single organization can disrupt the network, or would be better served by helping it.
* Terrorists fly aircraft into buildings, but the governments have not yet abolished consumer air travel. Obviously the public good outweighs the possible bad in their opinion.
* Criminal law differs between jurisdictions.

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

Liberty Dollars started as a commercial venture to establish alternative US currency, including physical banknotes and coins, backed by precious metals. This, in and of itself, is not illegal. They were later shut down for counterfeiting and intent to fraud after the coins, which contained less than $1 worth of silver, were put into circulation with the general money supply, supposedly having a value of 1 USD. These actions were encouraged by the makers of Liberty Dollars.

Bitcoins are not necessarily equal in value to dollars or any other currency and no one is saying they are. No member of the public will be tricked into accepting a bitcoin instead of a dollar.

Of course, actually 'shutting down' the decentralized Bitcoin network is rife with its own set of difficult considerations.

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

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

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

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

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

[[de:Mythen]]

Casascius Bitcoin POS system

2011-10-01T15:01:45Z

Graingert:

[[Image:VeriFone Vx570.jpg|thumb|right|200px|The Bitcoin POS system is based on the VeriFone Vx510 or Vx570 (pictured here) model of point-of-sale bankcard machines.]]
The '''Casascius Bitcoin POS system''' is a desktop retail point-of-sale acceptance system for Bitcoin "in a box". The system is based on a VeriFone Vx510 or Vx570 payment terminal, and allows merchants to easily accept Bitcoin payments from customers. It can optionally allow merchants to dispense (sell) Bitcoins.

The POS system features an Ethernet network connection, a 128x64 pixel backlit monochrome display, a receipt printer, and a 24-key keypad, all in a compact terminal. The Vx570 terminal also includes a USB port, to which a QR barcode scanner can be attached.

The POS system is a client-server application with the client application run on the payment terminal, and the server application run on any machine that is available to the shop. Known herein as Somebody, Inc.

The POS system acts as a client for a central server run by Somebody, Inc. It does not maintain a Bitcoin block chain, but rather, sends SSL-encrypted queries to servers belonging to Somebody, Inc. in order to retrieve rate quotes and perform transactions. Consequently, it requires a constant Internet connection in order to function. Transactions cannot take place and rates cannot be quoted without a functional connection to the Internet.

The POS system and its server are an open source project that is mainly in the planning stage. The POS system is not fully functional.

See also:
* [[Casascius Bitcoin POS system/Protocol]]
* https://www.github.com/casascius/vfbitcoin

==Functionality==
[[Image:Vx570_QR_code.jpg|thumb|right|200px|Smartphones can scan QR codes straight off the screen or receipt paper.]]
The POS system offers the following functionality for retail merchants:

* Instant notification of received Bitcoin payments on the network - audible (beeps), and a receipt ticket printed
* Real-time quote of exchange rates, automatically updated continuously from the source of the merchant's choice, and optionally computed with a merchant-definable spread.
* Exchange-rate calculator, converts between local currency and BTC, prints rate quotes.
* Printing of unique Bitcoin receiving addresses for accepting customer payments (receipt prints address both in text and QR code)
* Ability to accept payments by scanning a QR-coded private key presented by the customer (requires USB barcode scanner)
* Security from hackers and thieves: POS system doesn't store bitcoins or private keys, and cannot send or dispense the bitcoins it receives.

The POS system also offers the following functionality for merchants who wish to use the system to sell or dispense bitcoins.

* Complete isolation from the receiving functionality. Dispensed bitcoins always come from a separate account dedicated to this feature.
* Two-factor authentication: a PIN number and a fingerprint verification are required to dispense bitcoins. (Serial fingerprint module sold separately)
* Two admin-configurable ways to dispense bitcoins:
*# As a new private key printed on a receipt
*# To load a Bitcoin stored-value or "gift" card, upon which a private key is printed under a scratchoff. Simply swipe the magstripe on the card. The bitcoin address is on the magstripe.
* No bitcoins are stored on the terminal. Bitcoin purchases are executed on a remote server in real time.
* Anti-theft tamper-resistance. The built-in tamper-resistance features of the Vx510/Vx570 terminals are used to safeguard a single private key that is checked by the server. If the terminal is opened or tampered with, this key is erased.

==Usage==
To use the Bitcoin POS system, simply power it up. After the boot screen, you will receive the main screen.

On the main screen, the following is shown:
* Menu choices for F1 thru F4: (F1-New Address F2-Alerts F3-Scan Payment F4-Utils)
* Time and date, and network status
* Current exchange rate (use Setup to choose sources and to choose optional spreads)
* Number of alerts (including new incoming transactions)
* Number of transactions awaiting 6 confirmations

==Initial setup==
Initial setup is simple. Just take it out of the box, load the paper roll, and plug the unit into power and an Ethernet network. If you are using a barcode scanner, this connects to the USB port. If you are using a fingerprint reader (to dispense Bitcoins), this connects to the port with a calculator icon (this is normally considered the "PIN Pad" port in debit card processing environments). Please note that the Ethernet port and the PIN pad port look identical, and the plugs may fit interchangeably, but '''they are not compatible'''.

The Bitcoin POS system requires an Ethernet connection to the Internet to perform any functions. Without a good Internet connection, the network status will show "No network available", the exchange rate will be missing, and transactions will not be possible.

The POS system will automatically acquire an IP address from your network via DHCP, but if you need to set a static IP, press the * key twice, and enter the network configuration password (default: "2663") to access the network setup menu. When you change the IP settings, the terminal will reboot.

The clock is set automatically from the Somebody, Inc. servers. Use the web interface to set your local time zone. Daylight Saving Time is automatically adjusted where appropriate.

==Accepting payments==

===From a smartphone user===
To accept a payment from someone who intends to transfer Bitcoins using a smartphone, press F1. If you are expecting a certain amount of Bitcoins or local currency, enter the amount now, otherwise press Enter. Use the purple softkeys to select the appropriate currency units. A new bitcoin address and the expected amount will be generated and printed in text and as a QR code on the receipt printer. Hand this to the customer so they may initiate their payment.

:''Note: The same information will be displayed on-screen. If the paper roll is empty, the customer can scan the QR code or type the Bitcoin address directly from the screen.''

When the customer makes their payment, this will show up as an alert on the terminal, and the terminal will beep three times. In addition, it will beep once every minute until the alert is viewed.

To view the alert, press F2. When you view the alert, you can see the actual amount that the customer paid, along with the equivalent in local currency. Note that when you print the bitcoin address, the local conversion rate used is locked for five minutes, and will be used if the payment initially arrived within five minutes of printing the address. Otherwise, the conversion rate in effect at the time the payment was received is used.

===From someone presenting bearer items===
To accept a payment from someone who is presenting bitcoins in the form of a typeable private key or a QR code, press F3. Then:
* If the customer presented a QR code, scan it now.
* If the customer presented a printed private key, or you do not have a QR code scanner, you may type it now. Enter each character on the numeric pad, pressing the keys repeatedly where you need a letter in place of a number. Private keys are case sensitive. Use the appropriate purple softkey to switch between upper and lower case.
* If you are using the Vx570, you can optionally connect a full-size PC keyboard to its USB port.

After you scan a code, the total for all code(s) the customer has scanned is shown on screen. If there are more codes to scan, scan them now. Otherwise, press Enter.

Once you press Enter, the total Bitcoin value of all the scanned codes will be displayed. You will be asked what amount you want to capture. If you want to capture the entire amount, press Enter. If you only want to capture some of the amount and give change back to the customer, enter the amount now. If you enter an amount and have scanned more than one private key, you will be asked which of those keys the change should be returned.

Review and commit (accept) the transaction at the next step. Once you have accepted the transaction, it will be initiated on the Bitcoin network and will appear as "unconfirmed".

Notes:
*Pay special attention to the confirmation status when customers present their own private key codes for scanning. The balance isn't swept from the private key until you actually accept the transaction.
*It is possible that the funds on the private key can be spent by another person between the time you scan the code and the time you commit (accept) it. The Bitcoin POS system will show a zero balance upon the initial scan if the funds have already been spent, but it is possible, for example, that another person could spend the funds ''after'' they are scanned but ''before'' the transaction is committed. In most cases, you'll be notified within a minute or two (via the Alerts screen) that a payment was rejected by the network. Also note that if a payment consisted of multiple scans, ''all'' of them must be accepted for the transaction to go through. If a single scan gets rejected due to a double-spend attempt, the entire transaction gets rejected.
*The Bitcoin network may charge a transaction fee under various circumstances. If you sweep ''all'' the funds from the keys present, the transaction fee will be deducted from the balance you receive. If you sweep ''some'' but not ''all'' of the funds, the fee will either be deducted from the balance you receive (default), or the change returned to the customer. This can be changed on the setup screen. Transaction fees charged by Somebody, Inc. are billed separately and are never deducted from transactions directly.

===Ensuring transactions confirm===
The Bitcoin POS system automatically notifies when transactions arrive. However, the moment they arrive, they are considered "unconfirmed". There is always a possibility that a transaction may be rejected, such as if someone attempts to spend the same funds somewhere else at the same time. This possibility decreases exponentially each time a payment receives a "confirmation" (which you can see by going to F4-Utils, then choosing Recent Incoming Payments). The Alerts screen is used for notifying you of rejected payments.

If a recently received payment is rejected, the terminal will repeatedly beep four times every minute until you view the rejection alert. In addition, the beeps will be in a lower pitch than usual.

Payment rejections are rare, and this is particularly true for low-value transactions. It's even rarer to have a payment be rejected after its first confirmation. The definition of a payment rejection is the receipt of another confirmed transaction on the Bitcoin network that purports to spend the same funds to a different payee, invalidating the original transaction paying you.

Due to the decentralized way Bitcoin works, it is possible (but very difficult and resource-intensive) for people to orchestrate payment rejections. It is believed that the cost of orchestrating a rejection are high enough to preclude it from being cost-effective to attempt on low-value transactions, but becomes a potential concern as transaction size increases. The risk of rejection on higher-value transactions becomes lower each time a confirmation is received. Particularly for valuable purchases, you may consider requiring a wait of several confirmations to ensure that the payment is unlikely to be rejected. It is common for Bitcoin merchants to wait for six (6) confirmations in low-trust environments.

==Dispensing Bitcoins==
If your account is set up for dispensing Bitcoins, access the Dispense menu by pressing the # key twice at the main menu, and then entering your Dispensing password. Note that there is no visual indication or menu option for dispensing bitcoins - you must memorize the # # sequence.

:''Note: If you have not yet set up a dispensing password, you may set one up at this point. Before that password can be used for dispensing, you must log on to the Somebody, Inc. website and confirm that password online.''

If you have set up fingerprint authentication, touch your finger to the reader to authenticate.

At the Dispense menu, press a softkey. (Note that any or all of these options may be disabled in the setup menu).
*F1 - Dispense to Printer - to dispense Bitcoins in the form of a private key printed on the printer
*F2 - Dispense to Card - to add Bitcoins to a stored-value card.
*F3 - Transfer to Address - to send Bitcoins to a scanned or typed address.
*F4 - Exit Dispense Mode. Note that the terminal will automatically exit Dispense Mode if you don't make a selection within 15 seconds.

Note that the rate for dispensing is the admin-configurable "sell" rate and may differ from the exchange rate shown on the main screen. If you enter a BTC amount, the exact amount will be dispensed.

===Dispensing to Printer===
* Press '''F1 - Dispense to Printer''' to dispense to the printer. Enter the amount to dispense (either in BTC or local currency, choosing the currency via the purple softkeys if allowed), and press Enter.
* The first half of the receipt will print, displaying only the private key in text and QR formats.
* Visually confirm that the private key is legible. A four-digit code will appear in the upper right corner of the printed code - type this on the keypad, then press Enter. (This helps confirm the code printed properly, because once dispensed, without the private key, the funds are permanently gone).
* The remainder of the receipt, showing the amount, will print. Hand it to the customer.
* The Dispensing mode will immediately exit.

===Dispensing to Stored Value Card===
* Press '''F2 - Dispense to Card''' to dispense to a stored value card.
* Visually ensure you are using an undamaged, unscratched stored value card, and swipe the card through the magstripe reader.
* Enter the amount to dispense (either in BTC or local currency, choosing the currency via the purple softkeys if allowed), and press Enter.
* Enter the 10-digit code printed on the upper-right corner of the card.
* Confirm that the amount entered is correct, and then press Enter.
* A confirmation receipt will print, and the Dispensing mode will immediately exit.

:'''''Warning:''' Always ensure that empty stored value cards are kept securely and were received from a trusted supply channel, and do not load cards that have been handled by a customer. Don't transfer bitcoins to a stored value you cannot be sure is genuine. It is possible for a fraudster to create stored value cards - or to re-encode real ones - to cause the bitcoins to be sent to his address instead of your customer. When you receive a shipment of empty stored value cards from Somebody, Inc., you must go online and confirm receipt of the shipment before you can send bitcoins to these cards.''

===Dispensing to a Bitcoin address===
:''Note: This option is disabled by default, and will not appear on the menu if not enabled. Use the admin menu to enable it.''
* Press '''F3 - Transfer to Address'''.
* Scan the address with the barcode scanner, or enter it on the keypad or with a USB keyboard.
* Enter the amount to dispense (either in BTC or local currency, choosing the currency via the purple softkeys if allowed), and press Enter. The amount can only be entered on the terminal keypad, not through the USB keyboard or barcode scanner.
* Confirm that the amount entered is correct, and then press Enter.
* A confirmation receipt will print, and the Dispensing mode will immediately exit.

===Admin Tools===
You can access admin tools to perform functions like fingerprint setup and viewing the amount of BTC available in your dispensing account by pressing the first purple softkey at the Dispense menu.

In the Admin Tools menu, you may do the following:
* Enable/disable dispensing to printer
* Enable/disable dispensing to stored value cards
* Enable/disable transfer to Bitcoin addresses
* Enable/disable dispensing in BTC denominated amounts
* Enable/disable dispensing in local currency-denominated amounts
* Enable/disable display of BTC balance of dispenser account on Dispense menu
* Fingerprint Functions
** Activate and initialize a fingerprint reader accessory
** Enroll a fingerprint and set access rights
** Delete an enrolled fingerprint

Running Bitcoin

2011-08-15T22:49:09Z

Graingert: /* Start automatically */

There are two variations of the official bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called [[bitcoind]]). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).

__TOC__
==Command-line arguments==

Give Bitcoin (or bitcoind) the -? or –help argument and it will print out a list of the most commonly used command-line arguments and then exit:

Usage:
bitcoin [options]
bitcoin [options] <command> [params] Send command to -server or bitcoind
bitcoin [options] help List commands
bitcoin [options] help <command> Get help for a command
Options:
-conf=<file> Specify configuration file (default: bitcoin.conf)
-gen Generate coins
-gen=0 Don't generate coins
-min Start minimized
-datadir=<dir> Specify data directory
-proxy=<ip:port> Connect through socks4 proxy
-addnode=<ip> Add a node to connect to
-connect=<ip> Connect only to the specified node
-nolisten Don't accept connections from outside
-noupnp Don't attempt to use UPnP to map the listening port
-upnp Attempt to use UPnP to map the listening port
-paytxfee=<amt> Fee per KB added to transactions you send
-server Accept command line and JSON-RPC commands
-daemon Run in the background as a daemon and accept commands
-testnet Use the test network
-port=<port> Connect to the Network from <port> (default: 8333; 18333 for testnet)
-rpcuser=<user> Username for JSON-RPC connections
-rpcpassword=<pw> Password for JSON-RPC connections
-rpcport=<port> Listen for JSON-RPC connections on <port> (default: 8332)
-rpcallowip=<ip> Allow JSON-RPC connections from specified IP address
-rpcconnect=<ip> Send commands to node running on <ip> (default: 127.0.0.1)
-keypool=<n> Set key pool size to <n> (default: 100)
-rescan Rescan the block chain for missing wallet transactions
-rpcssl Use OpenSSL (https) for JSON-RPC connections
-? This help message

==Bitcoin.conf Configuration File==
All command-line options (except for -datadir and -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.

The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin [[data directory]], but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.
{|
! Operating System
! Default bitcoin datadir
! Typical path to configuration file
|-
| Windows
| %APPDATA%\Bitcoin\
| (XP) C:\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf
(Vista, 7) C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf
|-
| Linux
| $HOME/.bitcoin/
| /home/username/.bitcoin/bitcoin.conf
|-
| Mac OSX
| $HOME/Library/Application Support/Bitcoin/
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf
|}

==Sample Bitcoin.conf==
Here is a sample bitcoin.conf file, containing every option set to its default value.

# bitcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=1

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
# find other peers.
#noirc=1

# Maximum number of inbound+outbound connections.
#maxconnections=

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin to accept JSON-RPC commands.
#server=1

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
#rpcuser=Ulysseys
#rpcpassword=YourSuperGreatPasswordNumber_385593

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.*

# Listen for RPC connections on this TCP port:
rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem

# Miscellaneous options

# Set gen=1 to attempt to generate bitcoins
gen=0

# Use SSE instructions to try to generate bitcoins faster.
#4way=1

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
keypool=100

# Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
paytxfee=0.00

# Allow direct connections for the 'pay via IP address' feature.
#allowreceivebyip=1

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

==Platforms==
===Windows===

====Start automatically====
To configure the Bitcoin client to start automatically:

Settings -> Options

then mark the checkbox titled:
[X] Start Bitcoin on system startup

[[{{ns:file}}:Client_Settings_Options_windows.png]]

===Mac===

===Linux===
[[{{ns:file}}:Client_Settings_Options.png]]
[[Category:Technical]][[Category:Developer]]

Running Bitcoin

2011-08-15T22:48:38Z

Graingert: /* Generate on startup */ removed bitcoin generation as mining with the cpu client is discouraged

There are two variations of the official bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called [[bitcoind]]). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).

__TOC__
==Command-line arguments==

Give Bitcoin (or bitcoind) the -? or –help argument and it will print out a list of the most commonly used command-line arguments and then exit:

Usage:
bitcoin [options]
bitcoin [options] <command> [params] Send command to -server or bitcoind
bitcoin [options] help List commands
bitcoin [options] help <command> Get help for a command
Options:
-conf=<file> Specify configuration file (default: bitcoin.conf)
-gen Generate coins
-gen=0 Don't generate coins
-min Start minimized
-datadir=<dir> Specify data directory
-proxy=<ip:port> Connect through socks4 proxy
-addnode=<ip> Add a node to connect to
-connect=<ip> Connect only to the specified node
-nolisten Don't accept connections from outside
-noupnp Don't attempt to use UPnP to map the listening port
-upnp Attempt to use UPnP to map the listening port
-paytxfee=<amt> Fee per KB added to transactions you send
-server Accept command line and JSON-RPC commands
-daemon Run in the background as a daemon and accept commands
-testnet Use the test network
-port=<port> Connect to the Network from <port> (default: 8333; 18333 for testnet)
-rpcuser=<user> Username for JSON-RPC connections
-rpcpassword=<pw> Password for JSON-RPC connections
-rpcport=<port> Listen for JSON-RPC connections on <port> (default: 8332)
-rpcallowip=<ip> Allow JSON-RPC connections from specified IP address
-rpcconnect=<ip> Send commands to node running on <ip> (default: 127.0.0.1)
-keypool=<n> Set key pool size to <n> (default: 100)
-rescan Rescan the block chain for missing wallet transactions
-rpcssl Use OpenSSL (https) for JSON-RPC connections
-? This help message

==Bitcoin.conf Configuration File==
All command-line options (except for -datadir and -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.

The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin [[data directory]], but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.
{|
! Operating System
! Default bitcoin datadir
! Typical path to configuration file
|-
| Windows
| %APPDATA%\Bitcoin\
| (XP) C:\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf
(Vista, 7) C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf
|-
| Linux
| $HOME/.bitcoin/
| /home/username/.bitcoin/bitcoin.conf
|-
| Mac OSX
| $HOME/Library/Application Support/Bitcoin/
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf
|}

==Sample Bitcoin.conf==
Here is a sample bitcoin.conf file, containing every option set to its default value.

# bitcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=1

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
# find other peers.
#noirc=1

# Maximum number of inbound+outbound connections.
#maxconnections=

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin to accept JSON-RPC commands.
#server=1

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
#rpcuser=Ulysseys
#rpcpassword=YourSuperGreatPasswordNumber_385593

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.*

# Listen for RPC connections on this TCP port:
rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem

# Miscellaneous options

# Set gen=1 to attempt to generate bitcoins
gen=0

# Use SSE instructions to try to generate bitcoins faster.
#4way=1

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
keypool=100

# Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
paytxfee=0.00

# Allow direct connections for the 'pay via IP address' feature.
#allowreceivebyip=1

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

==Platforms==
===Windows===

====Start automatically====
To configure the Bitcoin client to start automatically:

Settings -> Options

then mark the checkbox titled:
[X] Start Bitcoin on window system startup

[[{{ns:file}}:Client_Settings_Options_windows.png]]

===Mac===

===Linux===
[[{{ns:file}}:Client_Settings_Options.png]]
[[Category:Technical]][[Category:Developer]]

Running Bitcoin

2011-08-15T22:47:54Z

Graingert:

There are two variations of the official bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called [[bitcoind]]). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).

__TOC__
==Command-line arguments==

Give Bitcoin (or bitcoind) the -? or –help argument and it will print out a list of the most commonly used command-line arguments and then exit:

Usage:
bitcoin [options]
bitcoin [options] <command> [params] Send command to -server or bitcoind
bitcoin [options] help List commands
bitcoin [options] help <command> Get help for a command
Options:
-conf=<file> Specify configuration file (default: bitcoin.conf)
-gen Generate coins
-gen=0 Don't generate coins
-min Start minimized
-datadir=<dir> Specify data directory
-proxy=<ip:port> Connect through socks4 proxy
-addnode=<ip> Add a node to connect to
-connect=<ip> Connect only to the specified node
-nolisten Don't accept connections from outside
-noupnp Don't attempt to use UPnP to map the listening port
-upnp Attempt to use UPnP to map the listening port
-paytxfee=<amt> Fee per KB added to transactions you send
-server Accept command line and JSON-RPC commands
-daemon Run in the background as a daemon and accept commands
-testnet Use the test network
-port=<port> Connect to the Network from <port> (default: 8333; 18333 for testnet)
-rpcuser=<user> Username for JSON-RPC connections
-rpcpassword=<pw> Password for JSON-RPC connections
-rpcport=<port> Listen for JSON-RPC connections on <port> (default: 8332)
-rpcallowip=<ip> Allow JSON-RPC connections from specified IP address
-rpcconnect=<ip> Send commands to node running on <ip> (default: 127.0.0.1)
-keypool=<n> Set key pool size to <n> (default: 100)
-rescan Rescan the block chain for missing wallet transactions
-rpcssl Use OpenSSL (https) for JSON-RPC connections
-? This help message

==Bitcoin.conf Configuration File==
All command-line options (except for -datadir and -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.

The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin [[data directory]], but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.
{|
! Operating System
! Default bitcoin datadir
! Typical path to configuration file
|-
| Windows
| %APPDATA%\Bitcoin\
| (XP) C:\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf
(Vista, 7) C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf
|-
| Linux
| $HOME/.bitcoin/
| /home/username/.bitcoin/bitcoin.conf
|-
| Mac OSX
| $HOME/Library/Application Support/Bitcoin/
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf
|}

==Sample Bitcoin.conf==
Here is a sample bitcoin.conf file, containing every option set to its default value.

# bitcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=1

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
# find other peers.
#noirc=1

# Maximum number of inbound+outbound connections.
#maxconnections=

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin to accept JSON-RPC commands.
#server=1

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
#rpcuser=Ulysseys
#rpcpassword=YourSuperGreatPasswordNumber_385593

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.*

# Listen for RPC connections on this TCP port:
rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem

# Miscellaneous options

# Set gen=1 to attempt to generate bitcoins
gen=0

# Use SSE instructions to try to generate bitcoins faster.
#4way=1

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
keypool=100

# Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
paytxfee=0.00

# Allow direct connections for the 'pay via IP address' feature.
#allowreceivebyip=1

# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
#minimizetotray=1

==Platforms==
===Windows===

====Start automatically====
To configure the Bitcoin client to start automatically:

Settings -> Options

then mark the checkbox titled:
[X] Start Bitcoin on window system startup

[[{{ns:file}}:Client_Settings_Options_windows.png]]

====Generate on startup====
To configure the Bitcoin client so that mining on startup is automatic:
Configure bitcoin.conf as follows:
gen=1

===Mac===

===Linux===
[[{{ns:file}}:Client_Settings_Options.png]]
[[Category:Technical]][[Category:Developer]]

File:Client Settings Options windows.png

2011-08-15T22:46:49Z

Graingert: Bitcoin client's Settings -> Options dialog window. For windows

== Summary ==
Bitcoin client's Settings -> Options dialog window. For windows
== Licensing ==
{{PD-ineligible}}

Petition against illegal use

2011-08-12T18:13:29Z

Graingert:

'''Please note''': This is still a draft, and signatures are subject to removal if the signer no longer agrees with the petition text. If the text has changed since someone signed their name, assume the signature's validity to be dubious at best.

== Definitions ==

"Illegal activity" is defined as infringement of civil or criminal law in the jurisdiction of the person acting. For example, if it is legal to use/abuse marijuana in JurisdictionX, then it is NOT considered to be illegal activity for someone in JurisdictionX. On the other hand, if it is illegal in JurisdictionY, it IS considered illegal activity to anyone under that jurisdiction.

== Text ==
<pre>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We, the undersigned, are opposed to the use of Bitcoin for any kind of illegal activity.
We encourage Bitcoin users to follow the laws in their jurisdiction and pay any applicable taxes.
</pre>
==See Also==

* [[Tax compliance]]
* [[Bitcoin Court]]
* [[Bitcoin Police]]

=== Signatures ===
* Luke Dashjr, Florida

Talk:Promotional graphics

2011-05-08T21:50:17Z

Graingert: Created page with "These graphics should be under some sort of license. CC-BY? or WTFPL like tango? Maybe a custom license ala firefox/chrome logos"

These graphics should be under some sort of license.

CC-BY? or WTFPL like tango?

Maybe a custom license ala firefox/chrome logos