Bitcoin Wiki - User contributions [en]

Metonymous:Transactions

2011-07-25T19:29:09Z

Metonymous: Created page with "=Abstract= Transactions could be treated as non atomic entities. =Influences= This page proposes a command line interface based to transactions based on the "Object" lifecyc..."

=Abstract=
Transactions could be treated as non atomic entities.

=Influences=
This page proposes a command line interface based to transactions based on the "Object" lifecycle from ObjectOriented programming. It also borrows from RESTful architecture design (get, put, update, delete, resources via URI). The "Functional design" influences are inspired by [[Da2ce7:New_Transaction]] and Erlang.

=New Concepts=
Transactions can be represented as a list containing

=Interface=
* [transaction_id] create_transaction {params}
** atomic "new", "save","broadcast" operation
** if the transaction created by new_transaction {params} would be invalid, create_transaction will throw an error
**
* {transaction} new_transaction
* {transaction} get_transaction {transaction_id}
** returns comma seperated ...

Securing your wallet

2011-05-15T13:10:03Z

Metonymous: /* Storage of Archive */ that's obfuscation, not encryption

==Introduction==

Wallet security can be broken down into two independent goals:
# Protecting your wallet against loss.
# Protecting your wallet against theft.

In the case that your current wallet hasn't been protected adequately (e.g. put online with a weaker password):
# Making a new secure wallet, using appropriate long-term protection.

==Technical Background==

Bitcoin transactions send Bitcoins to a specific public key. A Bitcoin address is an encoded hash of a public key. In order to use received Bitcoins, you need to have the private key matching the public key you received with. This is sort of like a super long password associated with an account (public key). Your Bitcoin wallet contains all of the private keys necessary for spending your received transactions. If you delete your wallet without a backup, then you no longer have the authorization information necessary to claim your coins, and the coins associated with those keys are lost forever.

The wallet contains a pool of queued keys. By default there are 100 keys in the [[key pool]]. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.

Creating a new address generates a new pair of public and private keys, which are added to your wallet. Each keypair is mostly random numbers, so they cannot be known prior to generation. If you backup your wallet and then create more than 100 new addresses, the keypair associated with the newest addresses will not be in the old wallet because the new keypairs are only known after creating them. Any coins received at these addresses will be lost if you restore from the backup.

The situation is made somewhat more confusing because the receiving addresses shown in the UI are not the only keys in your wallet. Each Bitcoin generation is given a new public key, and, more importantly, each sent transaction also sends some number of Bitcoins back to yourself at a new key. When sending Bitcoins to anyone, you generate a new keypair for yourself and simultaneously send Bitcoins to your new public key and the actual recipient's public key. This is an anonymity feature – it makes tracking Bitcoin transactions much more difficult.

So if you create a backup, do more than 100 things that cause a new key to be used, and then restore from the backup, some Bitcoins will be lost. Bitcoin has not deleted any keys (keys are never deleted) – it has created a new key that is not in your old backup and then sent Bitcoins to it.

== Making a new wallet ==

In the case that a wallet has been distributed, or stored, in a (real or potential) compromised state, it is wise to create a new wallet and transfer the full balance of Bitcoins to an address contained only in the newly created wallet.

For example, this will be necessary if one created a wallet with a password of 12 characters, as suggested. However a few years have passed and the wallet is now more easily compromised. Just re-encrypting isn't secure. One needs to make a new wallet and make the old wallet worthless (spending the funds to the new wallet).

==Making a secure workspace==

===Linux===

The first step is to make a [http://www.howtogeek.com/howto/ubuntu/add-a-user-on-ubuntu-server/ new user,] so type:

sudo adduser new_user_name

when you get to the prompt 'Enter the new value, or press ENTER for the default', just keep hitting ENTER.

Then switch user to the new user. To get to the new user you can use the switch user icon for your system, which on Ubuntu is in the 'System/Quit' screen, or if there is no switch icon on your system you can log out and log back in as the new user. Then click on a folder in the new user to display the file browser, then keep going up folders until you see the new user home directory, then right click to bring up the Properties dialog, then click on the Permissions tab, then in the Others section, set the folder access to None.

For secure browsing, open Firefox, and then go into the Edit menu and click Preferences. Starting from the left, click on the General tab, and in the 'Startup/When Firefox starts' pop up menu, choose 'Show a Blank Page'. Then click on the Content tab, and deselect 'Load images automatically' and deselect 'Enable Javascript'. Then click on the Privacy tab, and in the 'History/Firefox will' pop up menu, choose 'Never remember history'. Then click on the Security tab, and in the Passwords section, deselect 'Remember passwords for sites' and deselect 'Use a master password'. Then click on the Advanced tab, then click on the Update tab, and then in the 'Automatically check for updates to' section, deselect 'Add-ons' and 'Search Engines'.

When javascript is disabled, the [http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.19/bitcoin-0.3.19-linux.tar.gz/download linux download page] will not download automatically, so you'll have to click on the 'direct link' part of the "Problems with the download? Please use this 'direct link' or try another mirror." line.

After you've made your secure new user, to maintain security you should use it only for bitcoin.

== Locating BitCoin's data directory ==

The [[data directory]] is the location where Bitcoin's data files are stored, including the wallet data file.

=== Windows ===

Go to Start -> Run (or press WinKey+R) and run this:

explorer %APPDATA%\BitCoin

BitCoin's data folder will open. For most users, this is the following locations:

C:\Documents and Settings\YourUserName\Application data\BitCoin (XP)

C:\Users\YourUserName\Appdata\Roaming\BitCoin (Vista and 7)

"AppData" and "Application data" are hidden by default.

=== Linux ===

By default BitCoin will put its data here:

~/.bitcoin/

You need to do a "ls -a" to see directories that start with a dot.

If that's not it, you can do a search like this:

find / -name wallet.dat -print 2>/dev/null

=== Mac ===

By default BitCoin will put its data here:

~/Library/Application Support/Bitcoin/

==Backup==

The only file you need to back up is "wallet.dat". Ensure that BitCoin is closed, copy this file somewhere else, encrypt it, and put it somewhere safe. Ideally, you would put this file in two places: one nearby, and one 100+ miles away.

You can use the [[api|backupwallet]] JSON-RPC command to back up without shutting down Bitcoin.

=== General Solutions ===

Your wallet.dat file is not encrypted by BitCoin. Anyone who can access it can easily steal all of your coins. Use one of these encryption programs if there is any chance someone might stumble upon your wallet.
* [http://www.7-zip.org/ 7-zip] - Supports strongly-encrypted archives.
* [http://www.axantum.com/axcrypt/ AxCrypt]
* [http://www.truecrypt.org/ TrueCrypt] - Volume-based on-the-fly encryption (for advanced users)
* [http://www.rarlab.com/ WinRar] - Commonly used archive software that supports verification records and encryption.

There is also a list of [[OpenSourceEncryptionSoftware|open source encryption software.]]

==== Password Strength ====
Brute-force password cracking has come a long distance, a previously thought secure password of random [a-Z] [0-9] [!-~] of 8 characters long can be trivially solved now (using appropriate hardware)... The recommended length is '''at least''' 12 characters long.

If you use keyfiles in addition to a password, it is unlikely that your encrypted file can ever be cracked using brute force methods, even 10 years from now when even a 12 character password might be too short.

Assume that any encrypted files you store online (eg. gmail, Dropbox) will be stored somewhere forever and can never be erased.

==== Storage of Archive ====
One of the most simple methods for storing a appropriately '''encrypted''' archive of your wallet.dat file is to send the archive as an email attachment to your own e-mail address. Services like gmail.com use very comprehensive distributed networks that make the loss of data very unlikely. One can even obfuscate the name of the files within the archive, and name the archive something less inviting, such as: 'personal notes' or 'car insurance'.

Another solution is to use a file storage service like [http://www.wuala.com/bitcoin Wuala] ( encrypted, [http://www.bitcoin.org/smf/index.php?topic=5817.0 instructions]), [http://www.dropbox.com Dropbox] and [http://en.wikipedia.org/wiki/Comparison_of_online_backup_services others], including the more secure [http://www.spideroak.com SpiderOak].

=== Linux solution ===

Linux users can setup cron by running 'crontab -e' and adding this line:

01 */1 * * * /usr/local/bin/backupwallet.sh

This cron line runs backupwallet.sh at the 01 minute of every hour. Remember to add a newline after the last line of the crontab file, or else the last line won't run.

backupwallet.sh:

#!/bin/bash

TS=$(date "+%Y%m%d-%H-%M")
WALLET=/tmp/wallet${TS}
WALLET_E=/tmp/wallet${TS}.crypt

if
echo -n making backup...
bitcoind backupwallet $WALLET
[[ ! -s "$WALLET" ]]
then echo failed
elif
echo done
echo -n encrypting....
! gpg -r myusername --output $WALLET_E --encrypt $WALLET
then echo failed
elif
echo done
echo -n copying to distant server...
! scp $WALLET_E user@myserver.org:~/wallets/
then echo failed
else echo done
fi

rm -f $WALLET $WALLET_E

The shell script:

* Calls bitcoind backupwallet to create a time/date-stamped wallet.
* GPG encrypts the wallet with your public key.
* Copies the result to a backup location.

[[Category:Technical]]

==Restore==

Assuming your backup is recent enough that you haven't used up all of your key pool... restoring a wallet to a new (or old) location and rescanning the block chain should leave you with all your coins. Just follow these steps:
* Quit bitcoin(d).
* Copy your backed up wallet.dat into your bitcoin profile directory.
* If copying into existing profile, delete file ''blkindex.dat'', to make the client rescan the block chain.
And you'll be good as new.

==Erasing Plain Text Wallets==

A good practice is to keep at least two wallets, one as a "current account" for everyday transactions and one as a "savings account" where you store the majority of your Bitcoins.

The "savings account" wallet should be backed up in encrypted form only and all plaintext copies of this wallet should be erased. In case someone gains unauthorised access to your computer (either by physically stealing it or by exploiting a system vulnerability via the internet), they will only be able to spend the coins in your "current account" wallet.

In most operating systems, including Windows, Linux, and Mac OS X, simply deleting a wallet.dat file will ''not'' generally destroy it. It is likely that advanced tools can still be used to recover the wallet.dat file, even after it has been deleted.

The Linux '''shred''' command can be used to overwrite the wallet file with random data prior to deleting; this particular copy of the file will then be practically impossible to recover. Using shred (and similar tools on Windows) however does not guarantee that still other copies don't exist somewhere hidden on your HD. That will depend on your system configuration and what packages you have installed. Some system restore and backup tools, for instance, create periodic snapshots of your filesystem, duplicating your wallet.dat.

For Windows, the built-in command ''cipher /w'' will shred all previously-deleted files. [http://www.cylog.org/utilities/cybershredder.jsp CyberShredder] can securely deleted individual files.

==eWallet==

Storing bitcoins with an [[eWallet]] provider incurs risks as well.

==See Also==

* [[Data directory]]

Mining hardware comparison

2011-05-11T09:36:01Z

Metonymous: /* Nvidia */ AWS Tesla stats

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 via overclocking.

'''Note:''' Clock 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.

==Graphics cards==

===AMD===
To get the maximum performance use the 2.1 release of the ATI Stream SDK. 2.2 wastes CPU time, and 2.3/2.4 drop mining performance by 5-10%.

{| class="wikitable sortable"
|-
! Model !! Mhash/s !! Mhash/J !! W !! Clock !! SP !! SDK !! Slot !! Miner !! Notes
|-
| 3XXX || || || || || || || || OpenCL Not Supported
|-
| 42XX || || || || || || || PCI-E 2.0 x16 || || OpenCL Not Supported (intergrated/mobile GPU)
|-
| 4350 || 6.93 || 0.346 || 20 || 575 || 80 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors
|-
| 4550 || 7.23 || 0.289 || 25 || 600 || 80 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors
|-
| 4650 || 31.33 || 0.653 || 48 || 650 || 320 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors
|-
| 4670 || 36.14 || 0.613 || 59 || 750 || 320 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors
|-
| 4670 || 40.11 || || 59 || 800 || 320 || || AGP x8 || poclbm/Ubuntu 10.10 w/ H == 0 mod [http://www.bitcoin.org/smf/index.php?topic=1334.msg85236#msg85236 source] || -w 32 -f 0, don't use vectors
|-
| 4730 || 72.29 || 0.657 || 110 || 750 || 640 || || PCI-E 2.0 x16 || ||
|-
| 4770 || 72.29 || 0.904 || 80 || 750 || 640 || || PCI-E 2.0 x16 || ||
|-
| 4830 || 55.42 || 0.583 || 95 || 575 || 640 || || PCI-E 2.0 x16 || ||
|-
| 4850 || 75.30 || 0.685 || 110 || 625 || 800 || || PCI-E 2.0 x16 || ||
|-
| 4850 || 100 || || || 811 || 500 || 2.1 || PCI-E 2.0 x16 || guiminer || -f 0, core 811mhz(default 625) , mem downclock to 500mhz (default 993)
|-
| 4860 || 67.47 || 0.519 || 130 || 700 || 640 || || PCI-E 2.0 x16 || ||
|-
| 4870 || 90.36 || 0.602 || 150 || 750 || 800 || 2.1 || PCI-E 2.0 x16 || clmine ||
|-
| 4870 || 78 || || || || || || PCI-E 2.0 x16 || m0mchil's OpenCL/Vista 64bit || [http://www.bitcoin.org/smf/index.php?topic=1628.msg25069#msg25069 source]
|-
| 4890 || 102.41 || 0.539 || 190 || 850 || 800 || || PCI-E 2.0 x16 || ||
|-
| 4890 || 108.3 || || 190 || 975 || 800 || || PCI-E 2.0 x16 || ||
|-
| 4850X2 || 150.60 || 0.602 || 250 || 625 || 1600 || || PCI-E 2.0 x16 || ||
|-
| 4870X2 || 180.72 || 0.632 || 286 || 750 || 1600 || || PCI-E 2.0 x16 || ||
|-
| 4870X2 || 180.6 || || 286 || 800 || 1600 || || PCI-E 2.0 x16 || ||
|-
| 5450 || 11.99 || 0.631 || 19 || 650 || 80 || || PCI-E 2.1 x16 || ||
|-
| 5550 || 40.59 || 1.041 || 39 || 550 || 320 || || PCI-E 2.1 x16 || ||
|-
|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]
|-
| 5650 || 48 || 2.5-3.2 ? || 15-19 ? || || || || 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]
|-
| 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
|-
| 5670 || 85 || || || 900 || 400 || || PCI-E 2.1 x16 || poclbm || -v -f 0 -w 128
|-

| 5750 || 116.24 || 1.352 || 86 || 700 || 720 || || PCI-E 2.1 x16 || ||
|-
| 5750 || 154.56 || 1.45 || 106 || 830 || 720 || || PCI-E 2.1 x16 || ||-v -w128 -f20 underclocked memory clocks from 1150MHz to 300MHz
|-
| 5770 || 156.83 || 1.452 || 108 || 850 || 800 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
|style="background:#FFFFEF;"| 5770 || 180 || 1.406 || 128[*] || 950 || 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 || 205.58 || || || 935 || 300 || 2.1 || PCI-E 2.1 x16 || poclbm 2011-04-28 || -v -w 256
|-
|style="background:#FFFFFF;"| 5830 || 206.64 || 1.181 || 175 || 800 || 1120 || || PCI-E 2.1 x16 || ||
|-
|style="background:#FFFFFF;"| 5830 || 241 || 1.377 || 175 || 1006 || || 2.3 || PCI-E 2.1 x16 || poclbm 2011-03-11 / Win7 64 ||
|-
|| 5830 || 245 || 1.4 || 175 || 880 || 900 || 2.4 || PCI-E 2.1 x16 || poclbm (guiminer) || -v -w 256
|-
|style="background:#FFFFFF;"| 5830 || 290 || || || 996 || || 2.4 || PCI-E 2.1 x16 || phoenix 1.4 / poclbm / Win7 64 || vectors, aggr 12, BFI_INT
|-
|style="background:#EFEFFF;"| 5850 || 240.77 || 1.595 || 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;"| 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 || 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.862|| 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.546 || 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 || 344 || 1.8594 || 185 || 890 (OC) || 1440 || || PCI-E 2.0 x16 || phoenix ||
|-
| 5870M || 116.5 || ? || ? || ? || ? || 2.1 || PCI-E 2.1 x16 || gui-miner (win-7) ||
|-
|style="background:#EFFFEF;"| 5870 || 313.65 || 1.668 || 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 || || || 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 || 385 || || || 980 || 1600 || || PCI-E 2.0 x16 || poclbm-mod/Win7-64 || -f 0 -v -w 128
|-
|style="background:#EFFFEF;"| 5870 || 400 || || || 950 || 1600 || 2.4 || PCI-E 2.0 x8 || Phoenix 1.3 || -k poclbm VECTORS AGGRESSION=7 FASTLOOP BFI_INT
|-
|style="background:#FFEFEF;"| 5970 || 530 || 1.803 || 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 || || || PCI-E 2.1 x16 || Diablo ||
|-
|style="background:#FFEFEF;"| 5970 || 565 || 1.922 || 294 || || || 2.1 || PCI-E 2.1 x16 || clmine2 ||
|-
|style="background:#FFEFEF;"| 5970 || 604 || 2.054 || 294 || || || 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 || -q 6 -k poclbm AGGRESSION=19 WORKSIZE=128 BFI_INT VECTORS, Ubuntu 11.04, fglrx 11.4, memory clock @ 1000MHz
|-
|style="background:#FFEFEF;"| 5870x2 || 620 || || || 850 || 3200 || 2.1 || PCI-E 2.1 x16 || guiminer || -v -w 128
|-
|style="background:#FFEFEF;"| 5870x2 || 820 || || || 975 || 3200 || 2.1 || PCI-E 2.1 x16 || phoenix/1.3 || AGGRESSION=13 WORKSIZE=128 VECTORS BFI_INT Memory @ 300MHz
|-
| 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
|-
| 6490M || 16.289 || 0.708 || 23 || || || || PCI-E 2.1 x16 || poclbm-mod (Mac OS X 10.6.7) || MacBook Pro early 2011
|-
| 6850 || 171.59 || 1.351 || 127 || 775 || 960 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
| 6850 || 196 || || || 850 || 960 || || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 0
|-
| 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 || 220 || 1.236 || 178[*] || 1000 || 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] )
|-
| 6870 || 232.47 || 1.540 || 151 || 900 || 1120 || || PCI-E 2.1 x16 || poclbm -v -w 128 ||
|-
| 6870 || 277.47 || || || 940 || 1120 || || PCI-E 2.1 x16 || Phoenix 1.3 AGGRESSION=8 WORKSIZE=128 VECTORS BFI_INT ||
|-
| 6870 || 260.1 || 1.611 || 175 || 1001 || 1150 || 2.2 || PCI-E 2.1 x16 || poclbm-gui windows7x86 cat 11.3 || -v -w 128 -f 1
|-
| 6870 || 272 || 1.802 (?) || 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 [http://img690.imageshack.us/img690/853/gpumine1.png source]
|-
| 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
|-
| 6870 || 302 || 1.726 (?) || 175 (?) || 1000 || 1120 || 2.4 || PCI-E 2.1 x16 || hashkill-0.2.5 alpha cat 11.4 sdk 2.4 || -G2 -D overclocked to 1000, debian linux 64bit [http://img814.imageshack.us/img814/6646/gpumine2.png source]
|-
|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
|-
| 6950 || 295 || || 160 (?) || 810 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || unlocked shaders, default mem 1250
|-
| 6950 || 325 || || 200 (?) || 885 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || unlocked shaders, default mem 1250
|-
| 6950 || 360 || || 200 (?) || 970 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || unlocked shaders, default mem 1250
|-
| 6970 || 323 || 1.468 || 220 || 880 || 1536 || 2.3 || PCI-E 2.1 x16 || poclbm || -w 64, SDK 2.1 not supported on 69xx.
|-
| 6990 || 708 || 2.05 || 346 || 830 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || [http://www.bitcoin.org/smf/index.php?topic=2949 source]. SDK 2.1 not supported on 69xx.
|-
| 6990 || 746 || 1.82 || 410 || 880 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || [http://www.bitcoin.org/smf/index.php?topic=2949 source]. SDK 2.1 not supported on 69xx.
|-
| 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 || Overclock switch ON + overclocked to 900 mhz, VECTORS AGGRESSION=12 BFI_INT WORKSIZE=128
|-
|FirePro V8700 || 84.8 || || || 750 || 800 || || || poclbm-mod.03.24.2011 ||
|-
|FirePro M5800 || 61.4 || || || 650 || || || || poclbm-mod.03.24.2011 || Ubuntu ||
|-
|}

===Nvidia===

{| class="wikitable sortable"
|-
! Model !! Mhash/s !! Mhash/J !! W !! Clock !! SP !! Comment
|-
| 8200 mGPU || 1.2 || || || 1200 || 16 || 128 MB shared memory, "poclbm -w 128 -f 0"
|-
| 8400 GS || 2.3 || || || || || "poclbm -w 128"
|-
| 8600M GT || 4.93 || || || || 32 ||
|-
| 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]
|-
| 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
|-
| 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
|-
| 9500GT || 6.75 || 0.135 || 50 || 1400 || 32 ||
|-
| 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]
|-
| 9800GT || 30.36 || 0.289 || 105 || 1800 || 112 ||
|-
| 9800GTX || 32.54 || 0.232 || 140 || 1688 || 128 ||
|-
| 9800GTX+ || 35.39 || 0.251 || 141 || 1836 || 128 ||
|-
|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 || 9.83 || 0.170 || 58 || 1360 || 48 ||
|-
| 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]
|-
| GTS250 || 35.39 || 0.244 || 145 || 1836 || 128 ||
|-
| GTS250 || 35.2 || 0.243 || 145 || 1836 || 128 ||
|-
| GTS250 OC || 37 || 0.255 || 145 || 2047 || 128 ||
|-
| 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 OC || 52.0 || || || 1461 || 216 || "poclbm -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 ||
|-
| GTX285 || 53.35 || 0.262 || 204 || 1476 || 240 ||
|-
| GTX295 || 89.78 || 0.311 || 289 || 1242 || 480 ||
|-
| GT 320M (MacBook Air) || 6.12 || || || 1212 || 48 ||
|-
| GT 330M (Sony Vaio Z) || 7.8 || 0.71 ( 0.3 total) || 11 (26w total) || 1045 || 48 ||
|-
| GT430 || 20.24 || 0.413 || 49 || 1400 || 96 ||
|-
| GTS450 || 45.28 || 0.427 || 106 || 1566 || 192 ||
|-
| GTX460SE || 56.39 || 0.376 || 150 || 1300 || 288 ||
|-
| GTX460 || 68.31 || 0.427 || 160 || 1350 || 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 || 111.9 || || 215 || 1650 || 448 ||
|-
| GTX480 || 101.28 || 0.405 || 250 || 1401 || 480 ||
|-
| GTX560 Ti || 67.7 || 0.39 || 170 || 1700 || 384 || standard EVGA 560, no overclock
|-
| 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 ||
|-
| GTX580 || 140.05 || --- || 244 || 1544 || 512 ||
|-
| Quadro FX 580 || 5.7 || 0.14 || 40 || 1125 || 4 ||rpcminer-cuda, Win, -gpugrid=128 -gputhreads=512
|-
| Quadro FX 1600M || 6 || 0.12 || 50 || 625 || 32 ||rpcminer-cuda, Win
|-
| Quadro NVS 135M || 1.05 || 0.1 || 10 || 800 || 1 ||
|-
| Quadro NVS 3100M || 3.6 || 0.257 || 14 || 600 || 16 || rpcminer-cuda, Win, CUDA 3.1.1
|-
| Tesla M2050 || 79.8 || || || || || DiabloMiner
|-
| Tesla M2050 || [http://glennfrancismurray.com/cost-defective-mining-with-gpu-clusters-amazo 100] || 0 || 0 || - || 512 || Amazon AWS [http://glennfrancismurray.com/cost-defective-mining-with-gpu-clusters-amazo CUDA RPC Miner & CUDA 2.0]
|-
|}

==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. Also from [https://www.bitcoin.org/wiki/doku.php?id=bitcoin_miners this page on the old wiki].

===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 X4 630 || 4 || 10.7 || 0.11 || 95W || 2.8 GHz || 10.7
|colspan=4|
| bitcoin-miner 0.4 ||
|-
| 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 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 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 1100T || 6 || 22 || 0.176 || 125W || 3.82 GHz || 22
|colspan=4|
| bitcoin-miner || Aciid#bitcoin-dev
|-
| 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
|}

===ARM===
{| class="wikitable sortable"
|-
! Model !! p/t !! Mhash/s !! Mhash/J !! ACP [W] !! Clock !! Version !! Comment
|-
| Cortex A8 || 1 || 0.125 || 0.36 || 0.35 W || 0.6 GHz || cpuminer git (2011-03-26) || Nokia N900: 'cryptopp'
|-
| Cortex A8 || 1 || 0.2 || 0.57 || 0.35 W || 0.6 GHz || cpuminer git (2011-03-26) || Nokia N900: 'c' algo
|-
| Tegra 250 (2xCortex-A9) || 2 || 0.57 || 1.14 || 0.5 W || 1.0 GHz || cpuminer git (2011-03-24) || Toshiba AC100, ubuntu, 'c' algo
|-
| ARM 11 || 1 || 0.11 || ? || ? || 0.528 GHz || cpuminer git || T-Mobile Pulse, inside Debian chroot, 'c' algo
|}

===Intel===
{| class="wikitable sortable"
|-
! Model !! p/t !! Mhash/s !! Mhash/J !! ACP [W] !! Clock !! Version !! Comment
|-
| Pentium III mobile ? || 1 || 0.3 || 0.014 || 21W || 1.07 GHz || 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]
|-
| Old Xeon 512k (Dual) || 2x1/2 || 2.0 || ? || ? || 3.06GHz || 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 GHz || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft-0.4]/WinXP || -g no -t 2
|-
| Pentium Dual-Core E5400 || 2/2 || 2.27 || 0.03 || 65W || 2.7 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Celeron E330 || 2/2 || 2.2 || 0.03 || 65W || 2.5 GHz || 0.3.19/Ubuntu10.04 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37620#msg37620 source]
|-
| Core 2 Quad Q9400 || 4/4 || 4.35 || 0.046 || 95W || 2.66 GHz || ||
|-
| Core i3 530 || 2/4 || 8.31 || 0.10 || 80W || 3.66 GHz || Ufasoft 0.7 || -v -a5 -g no -t 4
|-
| Core i3 M350 || 2/4 || 1.48 || 0.04 || 35W || 2.27 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Core i5 M450 || 2/4 || 1.8 || 0.05 || 35W || 1.2 GHz || 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 ? || || 3.2 GHz || cpuminer-0.7 || -4way
|-
| 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 || 95W || 3.1 GHz || cpuminer git (2011-01-22) || cryptopp_asm32
|-
| Core i5-2400 || 4/4 || 14 || 0.15 || 95W || 3.1 GHz || cpuminer git (2011-03-26) || sse2_64
|-
| Core i7 920 || 4/8 || 19.2 || 0.10 || 195 || 4.0 GHz (x21) || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] || -a 5
|-
| Core i7 950 || 4/8 || 5.88 || 0.039 || 150W || 3.83 GHz (x23) || bitcoin-0.3.20.2 Win7-64 ||
|-
| Core i7 950 || 4/8 || 18.9 || 0.126 || 150W || 3.83 GHz (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 GHz (x33) || cpuminer/Win7-64 ||
|-
| Core i7 980x || 6/12 || 8.7 || || || 3.9 GHz (x27) || 0.3.17/Win7-64 ||
|-
| Core i7 620M || 2/4 || 6.3 || 0.18 || 35 || 2.66 GHz || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] v0.4 ||
|-
| Core 2 Duo E6550 || 1/2 || 2.45 || ? || ? || 2.33 GHz || cpuminer 0.7.1 (Linux) || --algo=sse2_64
|-
| Core 2 Duo E6850 || 2/2 || 6.75 || 0.10 || 65W || 3.0 Ghz || ufasoft-0.3 ||
|-
| Core 2 Duo E7300 || 2/2 || 7.76 || 0.11 || 70W || 3.33 GHz (o/c?) || ufasoft-0.3 || miner optimized for Intel Core
|-
| Core 2 Duo E7300 || 2/2 || 2.52 || 0.04 || 65W || 2.66 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Core 2 Duo T6400 || 2/2 || 4.2 || 0.12 || 35 W || 2.00 GHz || cpuminer git (Linux) || --algo=sse2_64
|-
| Xeon 3060 || 1/2 || 2.03 || 0.03 || 65W || 2.4GHz || cpuminer 0.8.1 (Linux) || --algo=cryptopp_asm32
|-
| Xeon Prestonia 2.4 (dual) || 2x1/2 || 2.16 || 0.017 || 130W || 2.4 GHz || ufasoft v0.4 ||
|-
| Xeon X5355 (dual) || 2x4/4 || 10.13 || 0.16 || 120W || 2.66GHz || bitcoind || Roughly the same speed as the "c" algo in cpuminer
|-
| Xeon X5355 (dual) || 2x4/4 || 22.76 || 0.09 || 120W || 2.66GHz || cpuminer (v0.8.1-1-g69529c3) || -O2 -march=core2, algo=sse2_64
|-
| Xeon E5440 || 4/8 || 7.3 || ? || 80W || 2.66 GHz|| Kiv's poclbm-gui || FIXME: Either wrong model # or wrong threads/speed info
|-
| Xeon E5520 || 4/8 || 6.5 || 0.08 || 80W || 2.27 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Xeon E5530 || 4/8 || 7.14 || 0.09 || 80W || 2.4 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Xeon E5630 (dual) || 2x4/8 || 8 || 0.1 || 80W || 2.53 GHz || 0.3.17/Win7-64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg29471#msg29471 source]
|-
| Atom N270 || 1 || 0.42 || '''0.17''' || 2.5W || 1.6 GHz || 0.3.1x/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|}

===Other===
{| class="wikitable sortable"
|-
! Model !! p/t !! Mhash/s !! Mhash/J !! ACP [W] !! Clock !! Version !! Comment
|-
| Cell || 6 || 21 || 0.35 || 60W || 3.2 GHz || cellminer || Sony Playstation 3 (FAT): Needs custom firmware (no links to it, potential issues with Sony assholes.) [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 || 6 || 21 || 0.7 || 35W || 3.2 GHz || cellminer || Sony Playstation 3 (SLIM): Total power usage of PS3 slim is 70W but only the Cell cpu is active.
|}

==See Also==

* [[Mining rig]]
* [[Generation Calculator]]
* [[Power Calc]]
* [[OpenCL miner]]
* [http://www.pcper.com/article.php?aid=745 ATI Stream vs. NVIDIA CUDA - GPGPU computing battle royale]

[[Category:Mining]]