https://en.bitcoin.it/w/api.php?action=feedcontributions&user=Nanotube&feedformat=atomBitcoin Wiki - User contributions [en]2024-03-19T04:11:00ZUser contributionsMediaWiki 1.30.0https://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Editing_privileges&diff=68787Bitcoin Wiki:Editing privileges2021-07-15T22:44:14Z<p>Nanotube: point to both libera and freenode</p>
<hr />
<div>Before you can begin editing, you must '''read the rules''' and '''activate your wiki account'''.<br />
<br />
Rules: [[Bitcoin_Wiki_talk:Editing_privileges#Rules]]<br />
<br />
To activate your account, you can pick one of these methods:<br />
<br />
*Join {{Libera IRC|bitcoin-pricetalk}} on Libera or {{Freenode IRC|bitcoin-pricetalk}} on Freenode and ask directly<br />
*Post your wiki username on [https://bitcointalk.org/index.php?topic=1025908.0 this] BitcoinTalk thread<br />
<br />
We ask that new registrants do this to verify that they are not disruptive robots.<br />
{{p-full}}<br />
{{DISPLAYTITLE:<span style="font-size:0px;">Bitcoin Wiki:</span><span style="color:purple;">Editing privileges</span>}}</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=User:Nanotube&diff=68728User:Nanotube2021-07-07T03:35:12Z<p>Nanotube: update my user page</p>
<hr />
<div>Greetings to all.<br />
<br />
Ways to reach me:<br />
* [[Special:EmailUser/Nanotube|email]]<br />
* Talk to user 'nanotube' on Libera.Chat IRC<br />
* Leave a message on [[User_talk:Nanotube]] (best to combine it with an email, for extra noticeability)<br />
* Leave a message on bitcointalk.org forum for user 'nanotube'<br />
<br />
==My projects==<br />
<br />
* http://bitcoin-otc.com - an over-the-counter IRC-based trading marketplace<br />
* [[gribble]] irc bot, provides up to date bitcoin information on IRC, also does streaming market quotes on #bitcoin-market.<br />
<br />
==Helpful links==<br />
<br />
[https://en.bitcoin.it/w/index.php?namespace=2&invert=1&title=Special%3ARecentChanges Recent changes excluding User namespace] (ignore all the spam user creations).</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=IRC_channels&diff=68727IRC channels2021-07-06T20:36:10Z<p>Nanotube: remove space before internal link name, otherwise it rendered with a space</p>
<hr />
<div>This page lists IRC channels for discussing Bitcoin-related topics. Please read: [[Bitcoin IRC Channel Guidelines]] before joining.<br />
<br />
Most of the channels are either on [https://libera.chat Libera.chat] or on [http://www.freenode.net Freenode] IRC networks.<br />
<br />
==Bitcoin Project==<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|bitcoin}} (on Freenode) || General Bitcoin-related discussion and support. ([[Bitcoin_IRC_Channel_Guidelines |guidelines]]).<br />
|-<br />
| {{Libera IRC|bitcoin}} (on Libera) || General Bitcoin-related discussion and support. ([[Bitcoin_IRC_Channel_Guidelines |guidelines]]).<br />
|-<br />
| {{Libera IRC|bitcoin-core-builds}} || Discussion of the Bitcoin Core build system.<br />
|-<br />
| {{Freenode IRC|bitcoin-commits}} || Real-time notification of commits to Bitcoin projects.<br />
|-<br />
| {{Libera IRC|bitcoin-core-dev}} || For development of Bitcoin Core. Log sources; [http://www.erisian.com.au/bitcoin-core-dev/ 1], [http://gnusha.org/bitcoin-core-dev/ 2]<br />
|-<br />
| {{Libera IRC|bitcoin-core-gui}} || For development of Bitcoin Core's GUI.<br />
|-<br />
| {{Libera IRC|bitcoin-core-pr-reviews}} || Weekly PR review club for discussing Bitcoin Core Pull Requests.<br />
|-<br />
| {{Freenode IRC|bitcoin-gaming}} || Bitcoin gamers hangout.<br />
|-<br />
| {{Freenode IRC|bitcoin-gentoo}} || Gentoo community.<br />
|-<br />
| {{Freenode IRC|bitcoin-marketing}} || Marketing and promotion of bitcoin<br />
|-<br />
| {{Libera IRC|bitcoin-news}} || RSS News related to Bitcoin.<br />
|-<br />
| {{Freenode IRC|bitcoin-politics}} || Discuss politics with other Bitcoin users.<br />
|-<br />
| {{Libera IRC|bitcoin-pricetalk}} || ALL Discussion Remotely Related to Bitcoin Price or other offtopic goes here<br />
|-<br />
| {{Freenode IRC|bitcoin-watch|text=[[Bitcoin-Watch|#bitcoin-watch]]}} || Streaming Bitcoin transactions, including market data.<br />
|-<br />
| {{Libera IRC|bitcoin-wiki}} || Bitcoin Wiki support<br />
|-<br />
| {{Freenode IRC|bitcoin-wizards}} (on Freenode) || Bitcoin experts and futurists ([http://gnusha.org/bitcoin-wizards/ history])<br />
|-<br />
| {{Libera IRC|bitcoin-wizards}} (on Libera) || Bitcoin experts and futurists ([http://gnusha.org/bitcoin-wizards/ history])<br />
|-<br />
| {{Libera IRC|lightning-dev}} || Lightning protocol development ([http://gnusha.org/lightning-dev/ history])<br />
|-<br />
| {{Freenode IRC|lnd}} || Lightning only version of #bitcoin-commits<br />
|-<br />
| {{Freenode IRC|sidechains-dev}} || Sidechains development<br />
|}<br />
<br />
===Local communities===<br />
<br />
{| class="wikitable"<br />
| {{Freenode IRC|bitcoin-aus}} || Aussie bitcoin community.<br />
|-<br />
| {{Freenode IRC|AustinBitcoin}} || Austin, TX bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-bra}} || Brazilian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-cad}} || Canadian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-cn}} || Chinese bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-dk}} || Danish bitcoin community.<br />
|-<br />
| {{Libera IRC|bitcoin-de}} || German bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-eastcoastusa}} || East Coast USA bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-il}} || Israeli bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-nl}} || Dutch bitcoin community. <br />
|-<br />
| {{Freenode IRC|bitcoin-pl}} || Polish bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-romania}} || Romanian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-ve}} || Venezuelan bitcoin community.<br />
|-<br />
| {{Freenode IRC|btc.chat}} || Russian bitcoin community.<br />
|-<br />
| #bitcoins.fi @ IRCNet || Finnish bitcoin community.<br />
|-<br />
| {{Libera IRC|bitcoin-hr}} || Croatian language bitcoin community.<br />
|-<br />
| {{Libera IRC|bitcoin-fr}} || French language bitcoin community.<br />
<br />
|}<br />
<br />
==Mining Related Communities==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|avalon}} || Discussion and support specific to [[Avalon]] mining machine<br />
|-<br />
| {{Freenode IRC|bitcoin-mining}} || Discussion and support related to mining.<br />
|-<br />
| {{Freenode IRC|bitcoin-fpga}} || Discussion and support specific to FPGA mining.<br />
|-<br />
| {{Freenode IRC|btcguild}} || [[BTCGuild]] mining pool community<br />
|-<br />
| {{Freenode IRC|butterflylabs}} || [[Butterfly Labs]] chat<br />
|-<br />
| {{Freenode IRC|cgminer}} || Discussion and support specific to [[CGMiner]].<br />
|-<br />
| {{Freenode IRC|eligius}} || [[Eligius]] mining pool community (also support for [[BFGMiner]] and [[Eloipool]])<br />
|-<br />
| {{Freenode IRC|mining.bitcoin.cz}} || Slush's mining pool community<br />
|-<br />
| {{Freenode IRC|ozcoin}} || [[Ozco.in]] mining pool community<br />
|-<br />
| <small>[irc://irc.foonetic.net/xkcd-bitcoin IRC] [http://irc.lc/foonetic/xkcd-bitcoin/Miner@@@ Web]</small> #xkcd-bitcoin || [https://en.bitcoin.it/wiki/XKCD_Pool XKCD Pool]<br />
|-<br />
| <small>[irc://irc.quakenet.org/bitcoins.lc IRC] [http://irc.lc/quakenet/bitcoins.lc/Miner@@@ Web]</small> #bitcoins.lc @ Quakenet || [http://www.bitcoins.lc Bitcoins.lc Pool] <br />
|-<br />
| {{Freenode IRC|p2pool}} || [[P2Pool]] decentralized mining pool<br />
|-<br />
| {{Freenode IRC|bitminter}} || [[BitMinter]] Mining Pool Community<br />
|-<br />
| {{Freenode IRC|kncminer}} || [[KNCMiner]] ASIC Mining Hardware Vendor Discussion<br />
|}<br />
<br />
==Communities for Exchanges and Trading==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|bitcoin-assets}} || Discussion of securities and other asset investments. [http://bitcoin-assets.com bitcoin-assets.com].<br />
|-<br />
| {{Freenode IRC|bitcoin-assets-trades}} || Streaming assets market data (only), no chat.<br />
|-<br />
| {{Freenode IRC|bitcoin-auction}} || Live auctions over IRC.<br />
|-<br />
| {{Libera IRC|bitcoin-market}} || Streaming market data (only), no chat.<br />
|-<br />
| {{Libera IRC|bitcoin-otc|text=[[bitcoin-otc|#bitcoin-otc]]}} || Over-the-counter trading marketplace and discussion. ([http://bitcoinstats.com/irc/bitcoin-otc/logs/ history])<br />
|-<br />
| {{Freenode IRC|bitcoin-escrow}} || Third party escrow agents.<br />
|-<br />
| {{Libera IRC|bitcoin-otc-ticker}} || Streaming market data form the [[#bitcoin-otc]] order book.<br />
|-<br />
| {{Libera IRC|bitcoin-otc-ratings|bitcoin-otc-ratings}} || Updates to ratings on the [[#bitcoin-otc]] Web of Trust.<br />
|-<br />
| {{Libera IRC|bitcoin-pit}} || Only over-the-counter trading.<br />
|-<br />
| {{Freenode IRC|btc.chat.traders}} || Russian community discussion about trades/exchanges.<br />
|-<br />
| {{Freenode IRC|coinbase}} || [[Coinbase]] chat<br />
|-<br />
| {{Freenode IRC|bitcoin-rt}} || Real-time tape (executed trades).<br />
|-<br />
| {{Freenode IRC|localbitcoins-chat}} || [[LocalBitcoins.com]] exchange support<br />
|}<br />
<br />
==Related Communities==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|opentransactions}} || [[Open Transactions]] project.<br />
|-<br />
| {{Freenode IRC|namecoin}} || [[Namecoin]] and the [[Dot-bit]] project.<br />
|-<br />
| {{Freenode IRC|twister}} || [[Twister]], P2P microblogging discussion.<br />
|-<br />
| {{Libera IRC|joinmarket}} || [[JoinMarket]], A [[CoinJoin]] implementation<br />
|-<br />
| {{Freenode IRC|darkwallet}} || [[DarkWallet]] and libbitcoin/Obelisk discussion & development channel.<br />
|-<br />
| {{Freenode IRC|electrum}} || [[Electrum]], lightweight bitcoin client.<br />
|-<br />
| {{Freenode IRC|copay}} || [[Copay]], lightweight bitcoin client.<br />
|-<br />
| {{Freenode IRC|bitcoin-stackexchange}} || Discussion complementing [http://bitcoin.stackexchange.com Bitcoin StackExchange].<br />
<br />
|}<br />
<br />
==See Also==<br />
<br />
* [[Bitcoin_Wiki:Community_portal]]<br />
<br />
[[fr:Canaux IRC]]<br />
[[pl:Kanały IRC]]<br />
[[ro:Canale]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=IRC_channels&diff=68726IRC channels2021-07-06T20:17:06Z<p>Nanotube: update channel list, remove some dead chans, point to libera where i know channel has moved.</p>
<hr />
<div>This page lists IRC channels for discussing Bitcoin-related topics. Please read: [[Bitcoin IRC Channel Guidelines]] before joining.<br />
<br />
Most of the channels are either on [https://libera.chat Libera.chat] or on [http://www.freenode.net Freenode] IRC networks.<br />
<br />
==Bitcoin Project==<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|bitcoin}} (on Freenode) || General Bitcoin-related discussion and support. ([[Bitcoin_IRC_Channel_Guidelines | guidelines]]).<br />
|-<br />
| {{Libera IRC|bitcoin}} (on Libera) || General Bitcoin-related discussion and support. ([[Bitcoin_IRC_Channel_Guidelines | guidelines]]).<br />
|-<br />
| {{Libera IRC|bitcoin-core-builds}} || Discussion of the Bitcoin Core build system.<br />
|-<br />
| {{Freenode IRC|bitcoin-commits}} || Real-time notification of commits to Bitcoin projects.<br />
|-<br />
| {{Libera IRC|bitcoin-core-dev}} || For development of Bitcoin Core. Log sources; [http://www.erisian.com.au/bitcoin-core-dev/ 1], [http://gnusha.org/bitcoin-core-dev/ 2]<br />
|-<br />
| {{Libera IRC|bitcoin-core-gui}} || For development of Bitcoin Core's GUI.<br />
|-<br />
| {{Libera IRC|bitcoin-core-pr-reviews}} || Weekly PR review club for discussing Bitcoin Core Pull Requests.<br />
|-<br />
| {{Freenode IRC|bitcoin-gaming}} || Bitcoin gamers hangout.<br />
|-<br />
| {{Freenode IRC|bitcoin-gentoo}} || Gentoo community.<br />
|-<br />
| {{Freenode IRC|bitcoin-marketing}} || Marketing and promotion of bitcoin<br />
|-<br />
| {{Libera IRC|bitcoin-news}} || RSS News related to Bitcoin.<br />
|-<br />
| {{Freenode IRC|bitcoin-politics}} || Discuss politics with other Bitcoin users.<br />
|-<br />
| {{Libera IRC|bitcoin-pricetalk}} || ALL Discussion Remotely Related to Bitcoin Price or other offtopic goes here<br />
|-<br />
| {{Freenode IRC|bitcoin-watch|text=[[Bitcoin-Watch|#bitcoin-watch]]}} || Streaming Bitcoin transactions, including market data.<br />
|-<br />
| {{Libera IRC|bitcoin-wiki}} || Bitcoin Wiki support<br />
|-<br />
| {{Freenode IRC|bitcoin-wizards}} (on Freenode) || Bitcoin experts and futurists ([http://gnusha.org/bitcoin-wizards/ history])<br />
|-<br />
| {{Libera IRC|bitcoin-wizards}} (on Libera) || Bitcoin experts and futurists ([http://gnusha.org/bitcoin-wizards/ history])<br />
|-<br />
| {{Libera IRC|lightning-dev}} || Lightning protocol development ([http://gnusha.org/lightning-dev/ history])<br />
|-<br />
| {{Freenode IRC|lnd}} || Lightning only version of #bitcoin-commits<br />
|-<br />
| {{Freenode IRC|sidechains-dev}} || Sidechains development<br />
|}<br />
<br />
===Local communities===<br />
<br />
{| class="wikitable"<br />
| {{Freenode IRC|bitcoin-aus}} || Aussie bitcoin community.<br />
|-<br />
| {{Freenode IRC|AustinBitcoin}} || Austin, TX bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-bra}} || Brazilian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-cad}} || Canadian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-cn}} || Chinese bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-dk}} || Danish bitcoin community.<br />
|-<br />
| {{Libera IRC|bitcoin-de}} || German bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-eastcoastusa}} || East Coast USA bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-il}} || Israeli bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-nl}} || Dutch bitcoin community. <br />
|-<br />
| {{Freenode IRC|bitcoin-pl}} || Polish bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-romania}} || Romanian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-ve}} || Venezuelan bitcoin community.<br />
|-<br />
| {{Freenode IRC|btc.chat}} || Russian bitcoin community.<br />
|-<br />
| #bitcoins.fi @ IRCNet || Finnish bitcoin community.<br />
|-<br />
| {{Libera IRC|bitcoin-hr}} || Croatian language bitcoin community.<br />
|-<br />
| {{Libera IRC|bitcoin-fr}} || French language bitcoin community.<br />
<br />
|}<br />
<br />
==Mining Related Communities==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|avalon}} || Discussion and support specific to [[Avalon]] mining machine<br />
|-<br />
| {{Freenode IRC|bitcoin-mining}} || Discussion and support related to mining.<br />
|-<br />
| {{Freenode IRC|bitcoin-fpga}} || Discussion and support specific to FPGA mining.<br />
|-<br />
| {{Freenode IRC|btcguild}} || [[BTCGuild]] mining pool community<br />
|-<br />
| {{Freenode IRC|butterflylabs}} || [[Butterfly Labs]] chat<br />
|-<br />
| {{Freenode IRC|cgminer}} || Discussion and support specific to [[CGMiner]].<br />
|-<br />
| {{Freenode IRC|eligius}} || [[Eligius]] mining pool community (also support for [[BFGMiner]] and [[Eloipool]])<br />
|-<br />
| {{Freenode IRC|mining.bitcoin.cz}} || Slush's mining pool community<br />
|-<br />
| {{Freenode IRC|ozcoin}} || [[Ozco.in]] mining pool community<br />
|-<br />
| <small>[irc://irc.foonetic.net/xkcd-bitcoin IRC] [http://irc.lc/foonetic/xkcd-bitcoin/Miner@@@ Web]</small> #xkcd-bitcoin || [https://en.bitcoin.it/wiki/XKCD_Pool XKCD Pool]<br />
|-<br />
| <small>[irc://irc.quakenet.org/bitcoins.lc IRC] [http://irc.lc/quakenet/bitcoins.lc/Miner@@@ Web]</small> #bitcoins.lc @ Quakenet || [http://www.bitcoins.lc Bitcoins.lc Pool] <br />
|-<br />
| {{Freenode IRC|p2pool}} || [[P2Pool]] decentralized mining pool<br />
|-<br />
| {{Freenode IRC|bitminter}} || [[BitMinter]] Mining Pool Community<br />
|-<br />
| {{Freenode IRC|kncminer}} || [[KNCMiner]] ASIC Mining Hardware Vendor Discussion<br />
|}<br />
<br />
==Communities for Exchanges and Trading==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|bitcoin-assets}} || Discussion of securities and other asset investments. [http://bitcoin-assets.com bitcoin-assets.com].<br />
|-<br />
| {{Freenode IRC|bitcoin-assets-trades}} || Streaming assets market data (only), no chat.<br />
|-<br />
| {{Freenode IRC|bitcoin-auction}} || Live auctions over IRC.<br />
|-<br />
| {{Libera IRC|bitcoin-market}} || Streaming market data (only), no chat.<br />
|-<br />
| {{Libera IRC|bitcoin-otc|text=[[bitcoin-otc|#bitcoin-otc]]}} || Over-the-counter trading marketplace and discussion. ([http://bitcoinstats.com/irc/bitcoin-otc/logs/ history])<br />
|-<br />
| {{Freenode IRC|bitcoin-escrow}} || Third party escrow agents.<br />
|-<br />
| {{Libera IRC|bitcoin-otc-ticker}} || Streaming market data form the [[#bitcoin-otc]] order book.<br />
|-<br />
| {{Libera IRC|bitcoin-otc-ratings|bitcoin-otc-ratings}} || Updates to ratings on the [[#bitcoin-otc]] Web of Trust.<br />
|-<br />
| {{Libera IRC|bitcoin-pit}} || Only over-the-counter trading.<br />
|-<br />
| {{Freenode IRC|btc.chat.traders}} || Russian community discussion about trades/exchanges.<br />
|-<br />
| {{Freenode IRC|coinbase}} || [[Coinbase]] chat<br />
|-<br />
| {{Freenode IRC|bitcoin-rt}} || Real-time tape (executed trades).<br />
|-<br />
| {{Freenode IRC|localbitcoins-chat}} || [[LocalBitcoins.com]] exchange support<br />
|}<br />
<br />
==Related Communities==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|opentransactions}} || [[Open Transactions]] project.<br />
|-<br />
| {{Freenode IRC|namecoin}} || [[Namecoin]] and the [[Dot-bit]] project.<br />
|-<br />
| {{Freenode IRC|twister}} || [[Twister]], P2P microblogging discussion.<br />
|-<br />
| {{Libera IRC|joinmarket}} || [[JoinMarket]], A [[CoinJoin]] implementation<br />
|-<br />
| {{Freenode IRC|darkwallet}} || [[DarkWallet]] and libbitcoin/Obelisk discussion & development channel.<br />
|-<br />
| {{Freenode IRC|electrum}} || [[Electrum]], lightweight bitcoin client.<br />
|-<br />
| {{Freenode IRC|copay}} || [[Copay]], lightweight bitcoin client.<br />
|-<br />
| {{Freenode IRC|bitcoin-stackexchange}} || Discussion complementing [http://bitcoin.stackexchange.com Bitcoin StackExchange].<br />
<br />
|}<br />
<br />
==See Also==<br />
<br />
* [[Bitcoin_Wiki:Community_portal]]<br />
<br />
[[fr:Canaux IRC]]<br />
[[pl:Kanały IRC]]<br />
[[ro:Canale]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin-OTC&diff=68725Bitcoin-OTC2021-07-06T20:04:43Z<p>Nanotube: update irc</p>
<hr />
<div>The '''Bitcoin-OTC''' project is a marketplace for people to conduct [http://en.wikipedia.org/wiki/Over-the-counter_(finance) over-the-counter] trading in bitcoin. It is located on {{Libera IRC|bitcoin-otc}} IRC channel on Libera.Chat IRC network.<br />
<br />
Trading in the market is facilitated by the [[gribble]] bot, which takes care of maintaining the outstanding [http://bitcoin-otc.com/vieworderbook.php order book], as well as a web of trust user [http://bitcoin-otc.com/trust.php rating system]. All trades are conducted between users directly, without any intermediation by the marketplace.<br />
<br />
The source code for all the related software, including bot plugins and the website, is open, and hosted on [https://github.com/nanotube/supybot-bitcoin-marketmonitor this github repository].<br />
<br />
==Orders==<br />
<br />
The order book holds offers not just for buying and selling bitcoins but for physical goods and services as well.<br />
<br />
==Web of trust network==<br />
<br />
The OTC Rating System is an irc-based web of trust network. Users can give each other ratings between -10 and +10. User must be [http://wiki.bitcoin-otc.com/wiki/GPG_authentication identified via a PGP key] to enter ratings.<br />
<br />
Only one rating can exist between two people. The 'rate' command updates the existing rating if it is used multiple times. So as the trust increases or decreases, user can update the trust value for a particular user.<br />
<br />
Only users with positive ratings in the system can rate other users. <br />
<br />
The system calculates the cumulative trust received by a user from all ratings. Through the web interface, users can explore the trust ratings and interconnections between users.<br />
<br />
==Rating guidelines==<br />
Users are suggested to take the size of transactions, the nature of your relationship and interaction, length of history, etc, into consideration with giving out rating.<br />
<br />
The basic guidelines on what ratings to hand out to people.<br />
<br />
{| style="border: 1px solid #c6c9ff; border-collapse: collapse;" cellspacing="0" cellpadding="10" border="1"<br />
|- style="text-align: center; background-color: #f0f0ff;"<br />
! Rating !! Guideline<br />
|-<br />
! 10 <br />
| You trust this person as you trust yourself. Reserve this for close friends and associates you know in person.<br />
|-<br />
! 8 <br />
| Large number of high-value transactions, long period of association, very trustworthy.<br />
|-<br />
! 5 <br />
| You've had a number of good transactions with this person.<br />
|-<br />
! 1 <br />
| One or two good transactions with this person<br />
|-<br />
! -1 <br />
| Person strikes you as a bit flaky. Unreasonable/unexpected delays in payment, etc.<br />
|-<br />
! -10 <br />
| Person failed to hold up his end of the bargain, took payment and ran, fraudster.<br />
|}<br />
<br />
==Relying on the rating==<br />
<br />
Users have several ways to check if the identity of the person is genuine. Once you check that the user is [http://wiki.bitcoin-otc.com/wiki/GPG_authentication identified via PGP key], you can query his rating with the 'getrating' command (sum of all ratings) or the 'gettrust' command (total of ratings by people you trust). You can also explore the [http://bitcoin-otc.com/viewratings.php trust network] and make sure that the person is well connected to a number of trusted users.<br />
<br />
==See also==<br />
<br />
* [[Buying bitcoins]]<br />
* [[:Category:Local|Local]]<br />
<br />
==External Links==<br />
<br />
* [http://www.bitcoin-otc.com Bitcoin-OTC website]<br />
* [http://bitcoin-otc.com/vieworderbook.php Market order book]<br />
* [http://bitcoin-otc.com/viewratings.php Bitcoin-OTC web of trust]<br />
* [http://wiki.bitcoin-otc.com/ Bitcoin-OTC wiki]<br />
* [http://margintradingbitcoin.com/bitcoin-otc-trading-buy-sell-btc-over-the-counter/ Bitcoin OTC Trading Desk] Trusted Over-The-Counter Marketplace<br />
* [https://github.com/lachesis/bitcoinotcauth BitcoinOTCAuth] XChat auth script on GitHub<br />
<br />
[[Category:Exchanges]]<br />
[[Category:Futures Exchanges]]<br />
[[ru:Bitcoin-OTC]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin_IRC_Channel_Guidelines&diff=68724Bitcoin IRC Channel Guidelines2021-07-06T20:04:02Z<p>Nanotube: update irc template to libera</p>
<hr />
<div>The {{Libera IRC|bitcoin}} channel on Libera.Chat serves as the de-facto "front door" for newcomers on bitcoin.<br />
<br />
The purpose for this channel is general discussion of everything related to bitcoin. We try to discuss and help people with everything regarding the protocol, clients, custom implementations and the philosophy behind bitcoin.<br />
<br />
Our purpose is to help anyone with relevant discussions:<br />
<br />
* The channel's language is english<br />
<br />
* Please try to remain on topic, the channel is about everything related to bitcoin. This means that the following topics are off-topic: all alt-coins, issues about how the channel is moderated, begging, spamming, referral sites or any other form of advertising. This includes anything else that is of no interest for the majority of the users.<br />
<br />
* Please refrain from any insults, flamewars or trolling. <br />
<br />
* It is strictly forbidden to discuss unlawful activity, pursuant to [https://libera.chat/policies Libera.Chat network policies];<br />
<br />
* Generally, anything that would make a newcomer feel unwelcome or would reflect badly on the bitcoin community should be avoided.<br />
<br />
* There are many side channels that allow discussions on various topics. A complete list can be found on [[IRC_channels]]. The major sidechannels are: [[Bitcoin-otc]] for any trading, {{Libera IRC|bitcoin-mining}} for anything bitcoin mining related and {{Libera IRC|bitcoin-pricetalk}} for price related discussions. Please use these channels.<br />
<br />
* We strive to maintain a professional, friendly, and helpful atmosphere on the channel at all times. Any deviation to this might get you a warning, or booted off the channel. Feel free to discuss this with an operator in private, but do not discuss this in the main channel. Operators always have the last say in any discussion.<br />
<br />
* Do not trust any website link given on the channel. There are many people out there trying to trick you into visiting a malicious site, or to trick you into executing viruses that are designed to search for bitcoin wallets and send the coins to the attacker. Do not click on any link unless you fully know what you are doing.<br />
<br />
* Any url might be a scam site. Therefore we do not allow url's in general. All url shorteners are strictly forbidden as they are hiding the final url. Other sites might be allowed by the goodwill of the operators, but this is more an exception to the rule, and can be decided on case by case by the operators. Google docs in particular are currently banned automatically by one of the bots, as they have been the source of criminal activity in the past.<br />
<br />
* We strive to provide high-quality information. Therefore we do not allow any advice on bad practices. For example: web wallets are insecure by design. Therefore, we will not recommend them as they are not as secure, and we will not allow other people to recommend them to anyone else. If in doubt ask an operator.</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Template:Libera_IRC&diff=68723Template:Libera IRC2021-07-06T20:02:26Z<p>Nanotube: update to new libera.chat webchat, and insert the required # in webchat arg.</p>
<hr />
<div><small>[ircs://irc.libera.chat:6697/{{{1}}} IRC] [https://web.libera.chat/?channels=#{{{1}}} Web]</small> {{#if: {{{text|}}} | {{{text}}} | <nowiki>#</nowiki>{{{1}}}}}</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Template:Freenode_IRC&diff=68722Template:Freenode IRC2021-07-06T19:59:52Z<p>Nanotube: Reverted edits by Nanotube (talk) to last revision by Luke-jr</p>
<hr />
<div><small>[irc://irc.freenode.net/{{{1}}} IRC] [https://webchat.freenode.net/?channels={{{1}}}&uio=d4 Web]</small> {{#if: {{{text|}}} | {{{text}}} | <nowiki>#</nowiki>{{{1}}}}}</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin-OTC&diff=68721Bitcoin-OTC2021-07-06T19:55:39Z<p>Nanotube: update to s/freenode/libera.chat/</p>
<hr />
<div>The '''Bitcoin-OTC''' project is a marketplace for people to conduct [http://en.wikipedia.org/wiki/Over-the-counter_(finance) over-the-counter] trading in bitcoin. It is located on {{Freenode IRC|bitcoin-otc}} IRC channel on Libera.Chat IRC network.<br />
<br />
Trading in the market is facilitated by the [[gribble]] bot, which takes care of maintaining the outstanding [http://bitcoin-otc.com/vieworderbook.php order book], as well as a web of trust user [http://bitcoin-otc.com/trust.php rating system]. All trades are conducted between users directly, without any intermediation by the marketplace.<br />
<br />
The source code for all the related software, including bot plugins and the website, is open, and hosted on [https://github.com/nanotube/supybot-bitcoin-marketmonitor this github repository].<br />
<br />
==Orders==<br />
<br />
The order book holds offers not just for buying and selling bitcoins but for physical goods and services as well.<br />
<br />
==Web of trust network==<br />
<br />
The OTC Rating System is an irc-based web of trust network. Users can give each other ratings between -10 and +10. User must be [http://wiki.bitcoin-otc.com/wiki/GPG_authentication identified via a PGP key] to enter ratings.<br />
<br />
Only one rating can exist between two people. The 'rate' command updates the existing rating if it is used multiple times. So as the trust increases or decreases, user can update the trust value for a particular user.<br />
<br />
Only users with positive ratings in the system can rate other users. <br />
<br />
The system calculates the cumulative trust received by a user from all ratings. Through the web interface, users can explore the trust ratings and interconnections between users.<br />
<br />
==Rating guidelines==<br />
Users are suggested to take the size of transactions, the nature of your relationship and interaction, length of history, etc, into consideration with giving out rating.<br />
<br />
The basic guidelines on what ratings to hand out to people.<br />
<br />
{| style="border: 1px solid #c6c9ff; border-collapse: collapse;" cellspacing="0" cellpadding="10" border="1"<br />
|- style="text-align: center; background-color: #f0f0ff;"<br />
! Rating !! Guideline<br />
|-<br />
! 10 <br />
| You trust this person as you trust yourself. Reserve this for close friends and associates you know in person.<br />
|-<br />
! 8 <br />
| Large number of high-value transactions, long period of association, very trustworthy.<br />
|-<br />
! 5 <br />
| You've had a number of good transactions with this person.<br />
|-<br />
! 1 <br />
| One or two good transactions with this person<br />
|-<br />
! -1 <br />
| Person strikes you as a bit flaky. Unreasonable/unexpected delays in payment, etc.<br />
|-<br />
! -10 <br />
| Person failed to hold up his end of the bargain, took payment and ran, fraudster.<br />
|}<br />
<br />
==Relying on the rating==<br />
<br />
Users have several ways to check if the identity of the person is genuine. Once you check that the user is [http://wiki.bitcoin-otc.com/wiki/GPG_authentication identified via PGP key], you can query his rating with the 'getrating' command (sum of all ratings) or the 'gettrust' command (total of ratings by people you trust). You can also explore the [http://bitcoin-otc.com/viewratings.php trust network] and make sure that the person is well connected to a number of trusted users.<br />
<br />
==See also==<br />
<br />
* [[Buying bitcoins]]<br />
* [[:Category:Local|Local]]<br />
<br />
==External Links==<br />
<br />
* [http://www.bitcoin-otc.com Bitcoin-OTC website]<br />
* [http://bitcoin-otc.com/vieworderbook.php Market order book]<br />
* [http://bitcoin-otc.com/viewratings.php Bitcoin-OTC web of trust]<br />
* [http://wiki.bitcoin-otc.com/ Bitcoin-OTC wiki]<br />
* [http://margintradingbitcoin.com/bitcoin-otc-trading-buy-sell-btc-over-the-counter/ Bitcoin OTC Trading Desk] Trusted Over-The-Counter Marketplace<br />
* [https://github.com/lachesis/bitcoinotcauth BitcoinOTCAuth] XChat auth script on GitHub<br />
<br />
[[Category:Exchanges]]<br />
[[Category:Futures Exchanges]]<br />
[[ru:Bitcoin-OTC]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin_IRC_Channel_Guidelines&diff=68720Bitcoin IRC Channel Guidelines2021-07-06T19:51:50Z<p>Nanotube: update page for libera.chat</p>
<hr />
<div>The {{Freenode IRC|bitcoin}} channel on Libera.Chat serves as the de-facto "front door" for newcomers on bitcoin.<br />
<br />
The purpose for this channel is general discussion of everything related to bitcoin. We try to discuss and help people with everything regarding the protocol, clients, custom implementations and the philosophy behind bitcoin.<br />
<br />
Our purpose is to help anyone with relevant discussions:<br />
<br />
* The channel's language is english<br />
<br />
* Please try to remain on topic, the channel is about everything related to bitcoin. This means that the following topics are off-topic: all alt-coins, issues about how the channel is moderated, begging, spamming, referral sites or any other form of advertising. This includes anything else that is of no interest for the majority of the users.<br />
<br />
* Please refrain from any insults, flamewars or trolling. <br />
<br />
* It is strictly forbidden to discuss unlawful activity, pursuant to [https://libera.chat/policies Libera.Chat network policies];<br />
<br />
* Generally, anything that would make a newcomer feel unwelcome or would reflect badly on the bitcoin community should be avoided.<br />
<br />
* There are many side channels that allow discussions on various topics. A complete list can be found on [[IRC_channels]]. The major sidechannels are: [[Bitcoin-otc]] for any trading, {{Freenode IRC|bitcoin-mining}} for anything bitcoin mining related and {{Freenode IRC|bitcoin-pricetalk}} for price related discussions. Please use these channels.<br />
<br />
* We strive to maintain a professional, friendly, and helpful atmosphere on the channel at all times. Any deviation to this might get you a warning, or booted off the channel. Feel free to discuss this with an operator in private, but do not discuss this in the main channel. Operators always have the last say in any discussion.<br />
<br />
* Do not trust any website link given on the channel. There are many people out there trying to trick you into visiting a malicious site, or to trick you into executing viruses that are designed to search for bitcoin wallets and send the coins to the attacker. Do not click on any link unless you fully know what you are doing.<br />
<br />
* Any url might be a scam site. Therefore we do not allow url's in general. All url shorteners are strictly forbidden as they are hiding the final url. Other sites might be allowed by the goodwill of the operators, but this is more an exception to the rule, and can be decided on case by case by the operators. Google docs in particular are currently banned automatically by one of the bots, as they have been the source of criminal activity in the past.<br />
<br />
* We strive to provide high-quality information. Therefore we do not allow any advice on bad practices. For example: web wallets are insecure by design. Therefore, we will not recommend them as they are not as secure, and we will not allow other people to recommend them to anyone else. If in doubt ask an operator.</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Template:Freenode_IRC&diff=68719Template:Freenode IRC2021-07-06T19:46:45Z<p>Nanotube: </p>
<hr />
<div><small>[ircs://irc.libera.chat:6697/{{{1}}} IRC] [https://web.libera.chat/?channels=#{{{1}}} Web]</small> {{#if: {{{text|}}} | {{{text}}} | <nowiki>#</nowiki>{{{1}}}}}</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Template:Freenode_IRC&diff=68718Template:Freenode IRC2021-07-06T19:41:21Z<p>Nanotube: update links to libera</p>
<hr />
<div><small>[ircs://irc.libera.chat:6697/{{{1}}} IRC] [https://web.libera.chat/?channels={{{1}}}&uio=d4 Web]</small> {{#if: {{{text|}}} | {{{text}}} | <nowiki>#</nowiki>{{{1}}}}}</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Gribble&diff=53132Gribble2014-11-18T20:53:35Z<p>Nanotube: /* Examples */ add market convert</p>
<hr />
<div>[http://gribble.sourceforge.net/ gribble] is a modified Supybot IRC bot, carrying some useful bitcoin-related commands and factoids. The bot's command sequence is ';;', to issue any command just start a line with two semicolons. You can also issue inline commands with two commas. <br />
<br />
It is present on #bitcoin (general discussion), #bitcoin-dev (bitcoin information queries), #bitcoin-otc (facilitate over-the-counter trading, with the OTC order book and OTC web of trust), and a number of other channels. You can also PM commands to gribble and it will PM back.<br />
<br />
==Source code==<br />
<br />
The core of gribble is a modified supybot. Code lives [http://gribble.sourceforge.net/ here].<br />
<br />
The code for bitcoin-related plugins lives [https://github.com/nanotube/supybot-bitcoin-marketmonitor/ here].<br />
<br />
==General Info==<br />
<br />
To get help on any command, try 'help <command>', to get a list of bitcoin-related aliases, run 'apropos bc', and to get a list of factoids, run command 'facts', and click on the link supplied.<br />
<br />
==List of commands==<br />
<br />
===Mining/network/hashrate stats===<br />
<br />
* '''hextarget''' - show the current [[difficulty]] target in hex. if optional [[block]] number argument is specified, show target for that block.<br />
* '''bcstats''' - show some statistics about the block chain - number of blocks, difficulty, estimated next difficulty target, time to next difficulty<br />
* '''blocks''' - show the current number of blocks in the bitcoin block chain<br />
* '''blockdiff''' - show difficulty for a specified past block.<br />
* '''bounty''' - show current block reward bounty, in BTC.<br />
* '''diff''' - show the current generation difficulty<br />
* '''diffchange''' - show estimated percent change in difficulty<br />
* '''estimate''' - show the estimate of the next difficulty, based on data since last change<ref>[https://bitcointalk.org/index.php?topic=3247.0 Estimate is usually wildly inaccurate for 100-200 blocks after a difficulty change due to insufficient sample size.]</ref>, and for last three days.<br />
* '''genprob''' - show the probability of getting at least one block at given hashrate, in a given time period, at given difficulty. uses current difficulty by default.<br />
* '''genrate''' - given the hash rate, and optional difficulty, calculate expected BTC generation per day and per hour. uses current difficulty by default.<br />
* '''gentime''' - given a hash rate, and optional difficulty level, calculate the expected average time to generate a block. uses current difficulty by default.<br />
* '''halfreward''' - show estimated time of next block reward halving.<br />
* '''interval''' - show the average time between blocks, over the past 1000 blocks. If given optional integer argument, use that many blocks for the estimate.<br />
* '''nethash''' - current 3-day estimate of network hash power, in Ghps.<br />
* '''nextretarget''' - show the block at which the next difficulty change will take place<br />
* '''prevdiff''' - show previous difficulty level<br />
* '''prevdiffchange''' - show previous difficulty percent change.<br />
* '''timetonext''' - show estimated time to reach the next difficulty target<br />
* '''totalbc''' - show total number of bitcoins in existence.<br />
* '''tblb''' -- given an interval in seconds, calculate the expected time between blocks which take at least <interval> seconds to create.<br />
* '''tslb''' - show time elapsed since last generated block.<br />
<br />
Big kudos goes out to theymos for providing a web interface to [http://blockexplorer.com/q/ real time statistics about the bitcoin block chain], and to http://blockchain.info for a similar service.<br />
<br />
===Markets and exchange rates===<br />
<br />
* '''avgprc''' - show average 24h, 7d, and 30d trading prices of BTC in various currencies.<br />
* '''bc,convert''' - convert bitcoin price, based on Mt.Gox last, to currency you specify. e.g., try 'bc,convert eur' for euros.<br />
* '''bc,fx''' - show various currency exchange rates<br />
* '''bc,xag''' - show price of silver in BTC<br />
* '''bc,xau''' - show price of gold in BTC<br />
* '''ticker''' - show pretty-printed ticker. takes a number of optional arguments to customize output.<br />
* '''bids''' - given a numeric argument, shows how many total btc are being demanded on MtGox at or over the given price. If optional '--under' argument given, looks under the price.<br />
* '''asks''' - given a numeric argument, shows how many total btc are being offered on MtGox at or below given price. If optional '--over' argument given, looks over the price.<br />
* '''market buy''' - supply number of btc to buy (or with --usd option, number of dollars to spend buying), to see the results of such a market order.<br />
* '''market sell''' - supply number of btc to sell (or with --usd option, number of dollars receive from selling), to see the results of such a market order.<br />
* '''obip''' - order book implied price. finds the weighted average price of BTC by averaging over the order book N coins away from the spread in both directions.<br />
* '''baratio''' - shows total USD volume of bids, total BTC volume of asks, and ratio of the two.<br />
<br />
===Mining pool statistics===<br />
<br />
Current hash rates are shown in Mhps.<br />
<br />
* '''bc,slushpool'''<br />
* '''bc,eligius'''<br />
* '''bc,p2pool'''<br />
* '''bc,btcguild'''<br />
* '''bc,deepbit'''<br />
* '''bc,ozcoin'''<br />
* '''bc,bitpenny'''<br />
<br />
===Other===<br />
<br />
* '''bc,help''' - show list of 'bc,' commands - same as 'apropos bc'.<br />
* '''bc,wiki''' - fetch a link to a page in this wiki, based on a search string. For example, to see a link to this page, try 'bc,wiki gribble'. <br />
<br />
===bitcoin-otc related info===<br />
<br />
* See [http://wiki.bitcoin-otc.com/wiki/Using_bitcoin-otc OTC guide] about using the order book<br />
* See [http://wiki.bitcoin-otc.com/wiki/GPG_authentication OTC GPG guide] about using the gpg authentication system<br />
* See [http://wiki.bitcoin-otc.com/wiki/OTC_Rating_System Web of Trust guide] about using the rating system/web of trust<br />
<br />
===General commands===<br />
<br />
The above list is specifically for bitcoin-related commands. See [http://sourceforge.net/apps/mediawiki/gribble/index.php?title=Using_Gribble_on_Sourceforge this page] for list and help of most commonly used non-bitcoin-related gribble commands. You can find more helpful info on the [http://gribble.sourceforge.net/ gribble] project page, or by exploring the bot with 'list' and 'help' commands.<br />
<br />
==Examples==<br />
<br />
<me> ;;bc,blocks<br />
<gribble> 167418<br />
<br />
<me> Check out the current difficulty! ,,bc,diff<br />
<gribble> 1376302.2678864<br />
<br />
<me> Here is a list of all gribble bitcoin commands: ,,(apropos bc)<br />
<gribble> Alias bc,24hprc, Alias bc,altprofit, Alias bc,avgprc, Alias bc,bcm, Alias bc,bitpenny, Alias bc,blockdiff, Alias bc,blocks, Alias bc,bounty, Alias bc,btceur, Alias bc,btcgbp, Alias bc,btcguild, Alias bc,btcrub, Alias bc,btcto, Alias bc,calc, Alias bc,calcd, Alias bc,channels, Alias bc,convert, Alias bc,deepbit, Alias bc,diff, Alias bc,diffchange, Alias bc,eligius, Alias bc,estimate, Alias (2 more messages)<br />
<me> ;;more<br />
<gribble> bc,exchb, Alias bc,fx, Alias bc,gen, Alias bc,gend, Alias bc,halfreward, Alias bc,help, Alias bc,hextarget, Alias bc,intersango, Alias bc,interval, Alias bc,mtgox, Alias bc,mtgoxask, Alias bc,mtgoxbid, Alias bc,mtgoxlast, Alias bc,nethash, Alias bc,nexttarget, Alias bc,ozcoin, Alias bc,p2pool, Alias bc,p2poolalt, Alias bc,p2pooldiff, Alias bc,prevdiff, Alias bc,price, Alias bc,prob, Alias (1 more message)<br />
<someoneelse> ;;more me<br />
<gribble> bc,probd, Alias bc,sectohalve, Alias bc,silkroad, Alias bc,sincelastblock, Alias bc,slushpool, Alias bc,spotestimate, Alias bc,stats, Alias bc,swepool, Alias bc,timetonext, Alias bc,totalbc, Alias bc,tradehill, Alias bc,tslb, Alias bc,wiki, Alias bc,xag, and Alias bc,xau<br />
<br />
<me> ;;list<br />
<gribble> Admin, Alias, Anonymous, AutoMode, Channel, ChannelLogger, ChannelStats, Conditional, Config, Debug, Dict, Dunno, Factoids, Filter, Format, GPG, GPGExt, Games, Gatekeeper, Google, Herald, Internet, Later, Market, Math, MessageParser, Misc, Network, OTCOrderBook, Owner, Plugin, RSS, RatingSystem, Relay, Reply, Scheduler, Seen, Services, Status, String, Time, Topic, Unix, User, Utilities, (1 more message)<br />
<br />
<me> ;;list Alias<br />
<gribble> ?, about, add, bashorg, bc,24hprc, bc,altprofit, bc,avgprc, bc,bcm, bc,bitpenny, bc,blockdiff, bc,blocks, bc,bounty, bc,btceur, bc,btcgbp, bc,btcguild, bc,btcrub, bc,btcto, bc,calc, bc,calcd, bc,channels, bc,convert, bc,deepbit, bc,diff, bc,diffchange, bc,eligius, bc,estimate, bc,exchb, bc,fx, bc,gen, bc,gend, bc,halfreward, bc,help, bc,hextarget, bc,intersango, bc,interval, bc,mtgox, (3 more messages)<br />
<br />
<me> ;;sl bitcoin<br />
<gribble> http://bitcoin.org/ | Official site offering documentation, forums and the open source client software which permits to send and receive bitcoins.<br />
<br />
<me> Some commands have more than one argument. Surround with parens. <br />
<me> e.g., Is your wallet safe? ,,(bc,wiki secure wallet)<br />
<gribble> https://en.bitcoin.it/wiki/Securing_your_wallet | Introduction. Wallet security can be broken down into two independent goals: ... Making a new secure wallet, using appropriate long-term protection. For a brief ...<br />
<br />
<me> ;;market convert 9000 usd to eur<br />
<gribble> 7178.4<br />
<br />
<me> ;;later tell nanotube Hey, I need to talk to you. Let me know when you're online.<br />
<gribble> The operation succeeded.<br />
<br />
<me> ;;auth me<br />
<gribble> Request successful for user me, hostmask me!~me@freenode/me. Your challenge string is: freenode:#bitcoin-otc:69a5920b6c5aa77a8f9c34da066ad95b70985da197bd3d917277929ca8fc52e2<br />
<me> ;;verify http://pastebin.com/raw.php?i=your-pgp-signed-challenge-string-in-pasted<br />
<gribble> You are now authenticated for user 'me' with key ABCDEFGH12345678<br />
<br />
===List of commands===<br />
<br />
8ball, ?, about, action, add, alert, alias, announce, announce add, announce list, announce remove, any, aol, apply, apropos, asks, at, auth, author, avgprc, azn, balance, ban add, ban list, ban remove, base, bashorg, bc,24hprc, bc,avgprc, bc,bear, bc,bitpenny, bc,blockdiff, bc,blocks, bc,bounty, bc,btcguild, bc,calc, bc,calcd, bc,convert, bc,deepbit, bc,diff, bc,diffchange, bc,eligius, bc,estimate, bc,fx, bc,gen, bc,gend, bc,help, bc,hextarget, bc,intersango, bc,interval, bc,mktcap, bc,nethash, bc,nexttarget, bc,ozcoin, bc,p2pool, bc,p2poolalt, bc,p2pooldiff, bc,prevdiff, bc,prevdiffchange, bc,price, bc,prob, bc,probd, bc,silkroad, bc,sincelastblock, bc,slushpool, bc,spotestimate, bc,stats, bc,tblb, bc,timetonext, bc,totalbc, bc,tslb, bc,wiki, bc,xag, bc,xau, bcauth, bcregister, bcstats, bcverify, bids, binary, bitcoinrss, blockdiff, blocks, bold, book, bot, botsnack, boturl, botweb, bounty, bsx, btcauth, btcregister, btcverify, buy, cache, calc, call, cand, capabilities, capability add, capability list, capability remove, capability set, capability setdefault, capability unset, capitalize, ceq, change, changeaddress, changekey, changename, channel, channeldb, channels, channelstats, cheer, chr, cif, clearq, cmd, coin, collect, color, colorize, command, commands, concat, config, configure, connect, contributors, convert, copumpkinprice, cor, countargs, cpu, crypt, ctell, ctime, cut, cxor, cycle, decode, default, defaultcapability, defaultplugin, dehalfop, deleteuser, deop, devoice, dice, dict, dictionaries, diff, diffchange, direct, disable, disconnect, dns, do, doctype, driver, drmath, drmathcheck, ea, eauth, ebay, echangekey, echo, ed, eightball, elapsed, enable, encode, environ, eregister, errno, estimate, ev, eval, events, everify, exec, exn, export, factlist, facts, feed, fetch, field, fight, fit, flush, forget, format, fortune, gangnam, ge, genprob, genrate, gentime, get, getprefix, getrating, gettrust, ghost, give, giveme, giveout, gnu, google, goxlag, goxvol, gribble, gt, h, halfop, halfreward, headers, hebrew, help, hexip, hexlify, hextarget, histsearch, hostmask, hostmask add, hostmask list, hostmask remove, hug, icalc, ident, identify, ignore, ignore add, ignore list, ignore remove, info, infographic, insert, interval, invite, ircquote, isitdown, jeffk, join, kban, key, kick, last, latency, le, learn, leet, len, letmein, levenshtein, limit, list, lithp, lmgtfy, load, lobotomy add, lobotomy list, lobotomy remove, lock, logmark, lower, ls, lt, ltcbtc, lucky, match, md5, mode, moderate, monologue, more, morse, mp, names, nceq, ne, net, netcraft, nethash, networks, nextretarget, nge, ngt, nick, nicks, nle, nlt, nmc,last, nne, notes, notice, obip, oobhresponse, op, ord, otc, outfilter, part, password, pet, petuser, pgp, phonebook, pid, ping, pl0x, plugin, plugins, pong, preferredsupportlink, prefsup, prevdiff, prevdiffchange, private, processes, progstats, quit, rainbow, random, randomize, rank, rate, rated, re, reconnect, redo, refresh, register, reload, remove, rename, reorder, repeat, replace, replies, reply, repr, restore, reverse, ripple, roar, rot13, roulette, rpn, rss, sample, say, scramble, search, seconds, seen, sell, sendquote, separator, server, set, set password, set secure, settrace, sfideasearch, sflaconica, sfticketsearch, sftwitter, sfuserpage, sfwikisearch, sha, show, shrink, shuffle, simpleeval, since, size, sl, slap, slogan, smack, soundex, source, spell, spellit, squish, stats, status, stripcolor, success, sudo, suicide, supa1337, swap, synonym, t, targetproject, tell, templatelink, texthelp, threads, ticker, tickeruk, time, timetonext, title, tmp, tn,blocks, tn,diff, topic, totalbc, translate, trustinfo, tslb, tz, ud, unauth, unban, unbinary, underline, undo, undup, unhexlify, unidentify, units, uniud, unload, unlock, unmoderate, unmorse, unrate, unregister, unrename, unsettrace, until, upkeep, upper, uptime, urlquote, urlunquote, user, username, utime, vacuum, verify, version, view, voice, voiceme, whatis, whoami, whois, wk, wotgraph, wp, wq, wrongulate, wtf, xagusd, xauusd, xor, and yt<br />
<br />
==Factoids==<br />
<br />
* [http://gribble.dreamhosters.com/viewfactoids.php?db=%23bitcoin-dev factoids for #bitcoin-dev channel]<br />
* [http://gribble.dreamhosters.com/viewfactoids.php?db=%23bitcoin-otc factoids for #bitcoin-otc channel]<br />
<br />
==References==<br />
<references /></div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Talk:Tonal_Bitcoin&diff=50496Talk:Tonal Bitcoin2014-08-24T16:31:57Z<p>Nanotube: /* Proposal for deletion */</p>
<hr />
<div>This is for discussion, '''not trolling'''. Note that this is not an encyclopedia, and does not have any "notability" requirements. If you don't want to use Tonal, don't. Trolling is not acceptable and will be deleted. Reasoned criticism is welcome in the "Criticism" section of the page.<br />
<br />
<br />
I have no legitimate stake in the matter, I made a few edits that I hope remove POV and still embrace the idea of Tonal Bitcoin. This is Raize, I am sorry I am not familiar enough with wiki editing to provide my signature. --[[User:Raize|Raize]]<br />
<br />
<br />
==Proposal for deletion==<br />
<br />
I propose to delete this article on the following grounds.<br />
<br />
# "Tonal bitcoin" ''is'' Bitcoin. Tonal Bitcoin only refers to the choice of the bitcoin user to employ a different representation of standard bitcoin balances. Instead of using decimal, the originator proposes using tonal units. If we follow this approach to the extreme, we could also use any base X system. It comes down to this: If you have a bitcoin balance of X in decimal notation, you can convert this to a balance Y in tonal units.<br />
# There is almost no information about tonal bitcoin available on the web attesting to its insignificance. All information that is available seems to come from a single source. To make matters worse, the information that is available is extremely confusing and poorly written.<br />
# No one, with the possible exception of one person, use "tonal bitcoin" units.<br />
# Not one exchange or business uses Tonal bitcoin units (to my knowledge).<br />
<br />
[[User:Lunokhod|Lunokhod]] ([[User talk:Lunokhod|talk]]) 14:59, 21 August 2014 (UTC)<br />
<br />
: '''1)''' Exactly why it is on-topic to the wiki, and should ''not'' be deleted; '''2)''' This wiki is just as relevant to the web as any random altcoin website, and this wiki explicitly permits and encourages original content and original research, unlike Wikipedia which is merely an encyclopedia; '''3)''' I know multiple people who use TBC (though I won't do so publicly so they can be trolled) - and in any case, significance and/or notability is not a concern of this wiki (see [[:Bitcoin:About|the wiki about/policy page]]); '''4)''' Again, irrelevant. --[[User:Luke-jr|Luke-jr]] ([[User talk:Luke-jr|talk]]) 16:10, 24 August 2014 (UTC)<br />
<br />
:: I agree that this should not be deleted. This is not Wikipedia, we don't have a notability policy, and explicitly allow technical or niche material relating to bitcoin. [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 16:31, 24 August 2014 (UTC)</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=User_talk:Lunokhod&diff=50494User talk:Lunokhod2014-08-24T16:25:52Z<p>Nanotube: respond on tonal</p>
<hr />
<div>Your trolling on [[Tonal Bitcoin]] is not appreciated. I suggest you review the wiki's [[:Bitcoin:About|about/policy]]; particularly make note that:<br />
* ''"Tonal bitcoin" ''is'' Bitcoin, but...'' - Which is why it is on-topic for the wiki, unlike other altcoins.<br />
* ''These is almost no information about tonal bitcoin available on the web.'' - This wiki is just as relevant to the web as any random altcoin website, and this wiki explicitly permits and encourages original content and original research, unlike Wikipedia which is merely an encyclopedia.<br />
If you dislike that the [[list of alternative cryptocurrencies]] page is listed in order of market cap, please note that I did explicitly raise my concern that this ordering may not be ideal for the very reason of giving undue sort order to TBC. Feel free to resort the list by some better metric. --[[User:Luke-jr|Luke-jr]] ([[User talk:Luke-jr|talk]]) 14:06, 21 August 2014 (UTC)<br />
* My comments on [[Tonal Bitcoin]] are not "trolling". They are my opinions, and you can discuss it on the talk page based on the merits. If you delete my comments again from a discuss page, I will ask the administrators to ban your account. That is not acceptable wikipedia behavior [[User:Lunokhod|Lunokhod]] ([[User talk:Lunokhod|talk]])<br />
** The talk page is for discussion, not trolling, which your comments are. I take your deletion of the warning against trolling on the talk page as implicit admission you recognise that to be true, even if you will explicitly deny it. This behaviour is not acceptable. P.S. This is not Wikipedia. --[[User:Luke-jr|Luke-jr]] ([[User talk:Luke-jr|talk]]) 16:32, 21 August 2014 (UTC)<br />
<br />
Hi, I got your message on my talk page. I don't think Tonal bitcoin should be deleted - bitcoin is many things to different people, some more niche than others. It is an interesting extension of the historic tonal system to bitcoin, and if some people care enough about it to make it and use it, what's wrong with that? I did talk to Luke about his management of the talk page for tonal, and he has agreed to be less deletion-happy. additionally luke does many helpful things on the wiki, i do not think this issue is cause to get his user account banned. we're all attached to our favorite pet projects, so it is understandable that he might be a little too defensive about it. we can just discuss things like sane adults, sometimes with the help of a mediator if necessary, and keep working together. [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 16:25, 24 August 2014 (UTC)</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Talk:Comparison_of_VPS_providers&diff=50320Talk:Comparison of VPS providers2014-08-19T20:34:22Z<p>Nanotube: /* Reorganizing the list */</p>
<hr />
<div>==Reorganizing the list==<br />
The fight to be on top of the list on this page is disappointing. I think the page is already in need of reorganization; perhaps we can sort it by actual popularity. Suggestions? --[[User:Taras|Taras]] ([[User talk:Taras|talk]]) 00:58, 17 August 2014 (UTC)<br />
<br />
: just keep it alphabetized and ban anyone who tries to jump the line :) [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 20:34, 19 August 2014 (UTC)<br />
<br />
== Adding IPv6 ==<br />
Support for IPv6 is a very important transition, both for TOR, and for general internet connectivity.<br />
* In Oct 2012, support for TOR clients connecting to relays as well as relays publishing IPv6 addresses and accepting clients connecting over IPv6 had been implemented.<br />
* By Jan 2013, support for exiting to IPv6 destinations had been implemented.<br />
<br />
Please see the [[https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/IPv6 TOR on IPv6 roadmap]] for additional details regarding TOR and IPv6.<br />
<br />
Using [http://ipv6-test.com IPv6-test.com], I've tested for accessibility to each provider's homepage via IPv6. The following is proposed for satisfying a '''yes''' listing critera:<br />
* [http://ipv6-test.com/validate.php IPv6-test.com] must report a valid AAAA record for provider's homepage.<br />
* [http://ipv6-test.com/validate.php IPv6-test.com] must be able to load the provider's homepage via IPv6.<br />
[[User:Erth64net|Erth64net]] ([[User talk:Erth64net|talk]]) 20:31, 16 July 2013 (GMT)</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=User_talk:Taras&diff=49891User talk:Taras2014-08-14T02:41:42Z<p>Nanotube: /* admin rights */ new section</p>
<hr />
<div>Here I am hello [[User:Taras|Taras]] ([[User talk:Taras|talk]]) 21:49, 5 April 2014 (UTC)<br />
:Love you {{unsigned|Taras}}<br />
<br />
== admin rights ==<br />
<br />
you have admin rights on the english wiki. that means you can move/delete pages when you deem it appropriate.</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Safewallet&diff=48038Safewallet2014-06-09T16:16:33Z<p>Nanotube: redirect dupe page</p>
<hr />
<div>#REDIRECT [[Safewallet.in]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Issue_Tracker&diff=48006Bitcoin Wiki:Issue Tracker2014-06-08T12:20:09Z<p>Nanotube: /* Require a fee for new user registration */ add workaround</p>
<hr />
<div>This page serves as the Wiki issue tracker. <br />
<br />
To file a new issue, add a second-level heading (==), and describe your issue in detail.<br />
<br />
Issue discussion should happen on the Talk page.<br />
<br />
Do not delete resolved issues unless you are a wiki administrator, or the creator of the issue.<br />
<br />
== Presented with SSL cert from another site ==<br />
<br />
A few times on 2014-03-27, non-deterministically across a few pages, I got the typical "wrong SSL cert" warning from Firefox, saying I'd been delivered the cert for '''kitchensurfing.com''', issued the same day.<br />
<br />
== Backup site broken ==<br />
<br />
dump.bitcoin.it just goes to the Main Page<br />
<br />
== Bitc<b></b>oin:* namespace interwiki links broken ==<br />
<br />
Links to [[Bit<b></b>coin:Community portal]] (for example) get turned into broken bitcoin: URI links.<br />
<br />
== Make the anti-spam payment system more discoverable ==<br />
I understand that [[Cryptopay]] is [being replaced](http://www.reddit.com/r/Bitcoin/comments/27lofu/dear_bitcoin_foundation_please_take_ownership_of/ci20i6t). Can you give us more details on that? The new system should be more discoverable by new users - I suggest a notification for every new user on how to edit. (people still ask me how to edit the damn thing).<br />
<br />
== Require a fee for new user registration ==<br />
There is still a big spam problem in the [https://en.bitcoin.it/w/index.php?title=Special:RecentChanges&limit=500 Recent Changes page]. As a workaround, can use [https://en.bitcoin.it/w/index.php?namespace=2&invert=1&title=Special%3ARecentChanges this link] to view recent changes excluding the user namespace.<br />
<br />
== Use a proper issue tracker ==<br />
I know you like wikis ... but can't we use something like Zendesk to track issue?<br />
Wikis weren't designed to be issue trackers...</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=List_of_address_prefixes&diff=47958List of address prefixes2014-06-08T04:05:23Z<p>Nanotube: cut out altcoin stuff as per policy.</p>
<hr />
<div>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.<br />
<br />
{| class="wikitable" <br />
|-<br />
!Decimal version<br />
!Leading symbol<br />
!Use<br />
!Example<br />
|-<br />
|0<br />
|1<br />
|Bitcoin pubkey hash<br />
|<tt>17VZNX1SN5NtKa8UQFxwQbFeFc3iqRYhem</tt><br />
|-<br />
|5<br />
|3<br />
|Bitcoin script hash<br />
| <tt>3EktnHQD7RiAE6uzMj2ZifT9YgRrkSgzQX</tt><br />
|-<br />
|111<br />
|m or n<br />
|Bitcoin testnet pubkey hash<br />
|<tt>mipcBbFg9gMiCh81Kj8tqqdgoZub1ZJRfn</tt><br />
|-<br />
|128<br />
|5<br />
|Bitcoin Private key<br />
|<tt>5Hwgr3u458GLafKBgxtssHSPqJnYoGrSzgQsPwLFhLNYskDPyyA</tt><br />
|-<br />
|196<br />
|2<br />
|Testnet script hash<br />
|<br />
|-<br />
|239<br />
|9<br />
|Testnet Private key<br />
|<tt>92Pg46rUhgTT7romnV7iGW6W1gbGdeezqdbJCzShkCsYNzyyNcc</tt><br />
|}<br />
<br />
The following table shows the leading symbol(s) and address length(s) for 160 bit hashes for each of the possible decimal version values:<br />
<br />
{| class="wikitable"<br />
|-<br />
!Decimal version<br />
!Leading symbol<br />
!Address length<br />
|-<br />
|0<br />
|1<br />
|up to 34<br />
|-<br />
|1<br />
|Q-Z, a-k, m-o<br />
|33<br />
|-<br />
|2<br />
|o-z, 2<br />
|33 or 34<br />
|-<br />
|3<br />
|2<br />
|34<br />
|-<br />
|4<br />
|2 or 3<br />
|34<br />
|-<br />
|5-6<br />
|3<br />
|34<br />
|-<br />
|7<br />
|3 or 4<br />
|34<br />
|-<br />
|8<br />
|4<br />
|34<br />
|-<br />
|9<br />
|4 or 5<br />
|34<br />
|-<br />
|10-11<br />
|5<br />
|34<br />
|-<br />
|12<br />
|5 or 6<br />
|34<br />
|-<br />
|13<br />
|6<br />
|34<br />
|-<br />
|14<br />
|6 or 7<br />
|34<br />
|-<br />
|15-16<br />
|7<br />
|34<br />
|-<br />
|17<br />
|7 or 8<br />
|34<br />
|-<br />
|18<br />
|8<br />
|34<br />
|-<br />
|19<br />
|8 or 9<br />
|34<br />
|-<br />
|20-21<br />
|9<br />
|34<br />
|-<br />
|22<br />
|9 or A<br />
|34<br />
|-<br />
|23<br />
|A<br />
|34<br />
|-<br />
|24<br />
|A or B<br />
|34<br />
|-<br />
|25-26<br />
|B<br />
|34<br />
|-<br />
|27<br />
|B or C<br />
|34<br />
|-<br />
|28<br />
|C<br />
|34<br />
|-<br />
|29<br />
|C or D<br />
|34<br />
|-<br />
|30-31<br />
|D<br />
|34<br />
|-<br />
|32<br />
|D or E<br />
|34<br />
|-<br />
|33<br />
|E<br />
|34<br />
|-<br />
|34<br />
|E or F<br />
|34<br />
|-<br />
|35-36<br />
|F<br />
|34<br />
|-<br />
|37<br />
|F or G<br />
|34<br />
|-<br />
|38<br />
|G<br />
|34<br />
|-<br />
|39<br />
|G or H<br />
|34<br />
|-<br />
|40-41<br />
|H<br />
|34<br />
|-<br />
|42<br />
|H or J<br />
|34<br />
|-<br />
|43<br />
|J<br />
|34<br />
|-<br />
|44<br />
|J or K<br />
|34<br />
|-<br />
|45-46<br />
|K<br />
|34<br />
|-<br />
|47<br />
|K or L<br />
|34<br />
|-<br />
|48<br />
|L<br />
|34<br />
|-<br />
|49<br />
|L or M<br />
|34<br />
|-<br />
|50-51<br />
|M<br />
|34<br />
|-<br />
|52<br />
|M or N<br />
|34<br />
|-<br />
|53<br />
|N<br />
|34<br />
|-<br />
|54<br />
|N or P<br />
|34<br />
|-<br />
|55-56<br />
|P<br />
|34<br />
|-<br />
|57<br />
|P or Q<br />
|34<br />
|-<br />
|58<br />
|Q<br />
|34<br />
|-<br />
|59<br />
|Q or R<br />
|34<br />
|-<br />
|60-61<br />
|R<br />
|34<br />
|-<br />
|62<br />
|R or S<br />
|34<br />
|-<br />
|63<br />
|S<br />
|34<br />
|-<br />
|64<br />
|S or T<br />
|34<br />
|-<br />
|65-66<br />
|T<br />
|34<br />
|-<br />
|67<br />
|T or U<br />
|34<br />
|-<br />
|68<br />
|U<br />
|34<br />
|-<br />
|69<br />
|U or V<br />
|34<br />
|-<br />
|70-71<br />
|V<br />
|34<br />
|-<br />
|72<br />
|V or W<br />
|34<br />
|-<br />
|73<br />
|W<br />
|34<br />
|-<br />
|74<br />
|W or X<br />
|34<br />
|-<br />
|75-76<br />
|X<br />
|34<br />
|-<br />
|77<br />
|X or Y<br />
|34<br />
|-<br />
|78<br />
|Y<br />
|34<br />
|-<br />
|79<br />
|Y or Z<br />
|34<br />
|-<br />
|80-81<br />
|Z<br />
|34<br />
|-<br />
|82<br />
|Z or a<br />
|34<br />
|-<br />
|83<br />
|a<br />
|34<br />
|-<br />
|84<br />
|a or b<br />
|34<br />
|-<br />
|85<br />
|b<br />
|34<br />
|-<br />
|86<br />
|b or c<br />
|34<br />
|-<br />
|87-88<br />
|c<br />
|34<br />
|-<br />
|89<br />
|c or d<br />
|34<br />
|-<br />
|90<br />
|d<br />
|34<br />
|-<br />
|91<br />
|d or e<br />
|34<br />
|-<br />
|92-93<br />
|e<br />
|34<br />
|-<br />
|94<br />
|e or f<br />
|34<br />
|-<br />
|95<br />
|f<br />
|34<br />
|-<br />
|96<br />
|f or g<br />
|34<br />
|-<br />
|97-98<br />
|g<br />
|34<br />
|-<br />
|99<br />
|g or h<br />
|34<br />
|-<br />
|100<br />
|h<br />
|34<br />
|-<br />
|101<br />
|h or i<br />
|34<br />
|-<br />
|102-103<br />
|i<br />
|34<br />
|-<br />
|104<br />
|i or j<br />
|34<br />
|-<br />
|105<br />
|j<br />
|34<br />
|-<br />
|106<br />
|j or k<br />
|34<br />
|-<br />
|107-108<br />
|k<br />
|34<br />
|-<br />
|109<br />
|k or m<br />
|34<br />
|-<br />
|110<br />
|m<br />
|34<br />
|-<br />
|111<br />
|m or n<br />
|34<br />
|-<br />
|112-113<br />
|n<br />
|34<br />
|-<br />
|114<br />
|n or o<br />
|34<br />
|-<br />
|115<br />
|o<br />
|34<br />
|-<br />
|116<br />
|o or p<br />
|34<br />
|-<br />
|117-118<br />
|p<br />
|34<br />
|-<br />
|119<br />
|p or q<br />
|34<br />
|-<br />
|120<br />
|q<br />
|34<br />
|-<br />
|121<br />
|q or r<br />
|34<br />
|-<br />
|122-123<br />
|r<br />
|34<br />
|-<br />
|124<br />
|r or s<br />
|34<br />
|-<br />
|125<br />
|s<br />
|34<br />
|-<br />
|126<br />
|s or t<br />
|34<br />
|-<br />
|127-128<br />
|t<br />
|34<br />
|-<br />
|129<br />
|t or u<br />
|34<br />
|-<br />
|130<br />
|u<br />
|34<br />
|-<br />
|131<br />
|u or v<br />
|34<br />
|-<br />
|132-133<br />
|v<br />
|34<br />
|-<br />
|134<br />
|v or w<br />
|34<br />
|-<br />
|135<br />
|w<br />
|34<br />
|-<br />
|136<br />
|w or x<br />
|34<br />
|-<br />
|137-138<br />
|x<br />
|34<br />
|-<br />
|139<br />
|x or y<br />
|34<br />
|-<br />
|140<br />
|y<br />
|34<br />
|-<br />
|141<br />
|y or z<br />
|34<br />
|-<br />
|142-143<br />
|z<br />
|34<br />
|-<br />
|144<br />
|z or 2<br />
|34 or 35<br />
|-<br />
|145-255<br />
|2<br />
|35<br />
|}</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Template:Altcoin&diff=47951Template:Altcoin2014-06-08T04:00:49Z<p>Nanotube: update date</p>
<hr />
<div><noinclude><br />
{{template}}<br />
</noinclude><br />
{{mbox<br />
|title=This page is about an altcoin, and therefore pending deletion as off-topic per [[:Bitcoin:About#Alternative cryptocurrencies|wiki policy]].<br />
|content=If there is any technical information in this article not covered elsewhere, please copy it before 2014-08-01.<br />
|bgcol=ff8888<br />
|bordercol=880000<br />
}}<br />
<includeonly>[[Category:Candidates for deletion|{{PAGENAME}}]]</includeonly></div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:About&diff=47947Bitcoin Wiki:About2014-06-08T03:39:55Z<p>Nanotube: /* Acceptable Use */ update basic rules</p>
<hr />
<div>This wiki is a public resource for the community of Bitcoin users, developers, and businesses as well as anyone interested in Bitcoin.<br />
<br />
Unlike Wikipedia, the Bitcoin Wiki is not an encyclopedia, and includes things like non-encyclopedia details (e.g., exact specifications on service fees, product performance, etc), how-to manuals, protocol specifications, original research, etc. There are also no notability requirements beyond the requirement that the material be of general interest to some segment of the Bitcoin community or the Bitcoin-curious general public.<br />
<br />
Because this resource is open to editing by the general public, readers should be aware that the material presented here often does not reflect the views of the entire Bitcoin community and may be outdated, incorrect, or outright malicious at times.<br />
<br />
== Policies and Rules ==<br />
<br />
Content on the Wiki should generally be factual in nature where possible, but because Bitcoin is relatively new, many important subjects are not yet completely understood and are sometimes best described by opinion. When there is controversy, the Bitcoin wiki should teach it and explain all the major views. Editors should refrain from asserting ownership over an article and seek compromise where possible. Opinion pieces that are of general community interest can be posted under the user's personal namespace. Generally, if you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.<br />
<br />
While the Wiki doesn't exist to promote any particular businesses or commercial activity, such things are important parts of the Bitcoin ecosystem and get discussed here, but biased editing with a strong pecuniary interest is frowned upon and spamming up the wiki with referral links is prohibited. Non-Bitcoin alternatives may, at times, be discussed here, especially for comparison purposes or to illustrate a point but this wiki is a Bitcoin community resource and edits which promote competing systems may be frowned on by the community.<br />
<br />
To prevent unnecessary drama, editors should refrain from adding material which they believe may be unlawful for them or other editors to post. Bitcoin Wiki respects your freedom to communicate but since this is a shared resource you should respect other people's right to be free from the association with your views and their consequences. <br />
<br />
As a small community resource, the Bitcoin Wiki is often less formal than generic references like Wikipedia and because it addresses a broad community of interests, not all pages will be suitable for all readers: Some pages are written for a technical audience about a technical subject and wouldn't serve their intended audience if simplified for the layman. In cases where audience goals conflict and can't be resolved, we should ExpandSpace and create new pages to cover the subject from different angles if we need to. Editors should be mindful, however, of the work it takes to maintain pages and try to avoid an excessive proliferation of pages which will not be well maintained.<br />
<br />
== Internationalization ==<br />
This wiki uses a multi-lingual scheme similar to Wikipedia's, which means a translated article get links to its translation in the menu (in the left column from the [[Main Page]]). <br />
<br />
If you feel one language is missing and are ready to start translating a lot of pages, you can request the creation of the language of your choice.<br />
<br />
* [[Main Page|English]]<br />
* French: [http://fr.bitcoin.it Français]<br />
* Chinese: [http://zh-cn.bitcoin.it 中文(中国大陆)]<br />
* German: [http://de.bitcoin.it Deutsch]<br />
* Hebrew: [http://he.bitcoin.it עברית]<br />
* Russian: [http://ru.bitcoin.it Русский]<br />
* Spanish: [http://es.bitcoin.it Español]<br />
* Italian: [http://it.bitcoin.it Italiano] <br />
* Polish: [http://pl.bitcoin.it/wiki/Strona_g%C5%82%C3%B3wna Język Polski]<br />
* Lithuanian: [[Talk:Bitcoin.it Wiki#Lithuanian|Lietuvių kalba (preparation)]]<br />
<br />
== Backups ==<br />
<br />
'''Note: This is temporarily offline.'''<br />
<br />
Backups are generated daily at 00:00 GMT, and can be downloaded from [https://dump.bitcoin.it/ the backup repository]. Setting up a mirror is easy enough, as many websites explain how to restore a MediaWiki xml dump into a fresh installation.<br />
<br />
== Contact ==<br />
<br />
Staff and some other editors can be contacted in [irc://irc.freenode.net/bitcoin-wiki the #bitcoin-wiki freenode IRC channel].<br />
Please avoid contacting us to ask questions already answered on this wiki.<br />
<br />
== License ==<br />
<br />
When Bitcoin.it wiki was opened (on December 16th 2010), the initial license was [[wikipedia:WTFPL|WTFPL]]. It has been brought up that CC-by would be more appropriate as content from the previous wiki is under CC-by.<br />
<br />
== Acceptable Use ==<br />
<br />
===Links===<br />
No affiliate/referral code links.<br />
<br />
=== Alternative cryptocurrencies ===<br />
<br />
Alternative cryptocurrencies (ie, besides Bitcoin) are, as a rule, considered off-topic.<br />
Technical topics, including changes that may never be made to Bitcoin, are allowed, provided they stick to the technical topic only.<br />
A single [[list of alternative cryptocurrencies]] is exempted from this policy.<br />
<br />
== See Also ==<br />
* [[:Bitcoin:Community_portal|Community portal]]<br />
<br />
[[Category:Introduction]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=IRC_channels&diff=47760IRC channels2014-05-30T15:33:24Z<p>Nanotube: /* Bitcoin Project */ bc-news no longer works</p>
<hr />
<div>Most of the following Bitcoin-related IRC channels are available on [http://www.freenode.net Freenode]:<br />
<br />
==Bitcoin Project==<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|bitcoin}} || General Bitcoin-related discussion ([[Bitcoin_IRC_Channel_Guidelines | guidelines]]).<br />
|-<br />
| {{Freenode IRC|bitcoin-court}} || [[Bitcoin Court]] Settles disputes between parties.<br />
|-<br />
| {{Freenode IRC|bitcoin-dev}} || Bitcoin software development. ([http://bitcoinstats.com/irc/bitcoin-dev/logs/ history]. [[Bitcoin-dev | guidelines]])<br />
|-<br />
| {{Freenode IRC|bitcoin-gaming}} || Bitcoin gamers hangout.<br />
|-<br />
| {{Freenode IRC|bitcoin-gentoo}} || Gentoo community.<br />
|-<br />
| {{Freenode IRC|bitcoin-marketing}} || Marketing and promotion of bitcoin<br />
|-<br />
| {{Freenode IRC|bitcoin-news}} || RSS News related to Bitcoin.<br />
|-<br />
| {{Freenode IRC|bitcoin-police}} || [[Bitcoin Police]] Investigates incidents related to Bitcoin.<br />
|-<br />
| {{Freenode IRC|bitcoin-politics}} || Discuss politics with other Bitcoin users.<br />
|-<br />
| {{Freenode IRC|bitcoin-pricetalk}} || ALL Discussion Remotely Related to Bitcoin Price goes here<br />
|-<br />
| {{Freenode IRC|bitcoin-tweets}} || Automated announce of bitcoin-related tweets.<br />
|-<br />
| {{Freenode IRC|bitcoin-watch|text=[[Bitcoin-Watch|#bitcoin-watch]]}} || Streaming Bitcoin transactions, including market data.<br />
|-<br />
| {{Freenode IRC|bitcoin-wiki}} || Bitcoin Wiki support<br />
|}<br />
<br />
===Local communities===<br />
<br />
{| class="wikitable"<br />
| {{Freenode IRC|bitcoin-otc-eu}} || European OTC trading marketplace.<br />
|-<br />
| {{Freenode IRC|bitcoin-otc-ru}} || Russian OTC trading marketplace.<br />
|-<br />
| {{Freenode IRC|bitcoin-otc-uk}} ||United kingdom OTC Trading Marketplace.Founder Angus Bates.<br />
|-<br />
| {{Freenode IRC|bitcoin-aus}} || Aussie bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-br}} || Brazilian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-cad}} || Canadian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-cn}} || Chinese bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-dk}} || Danish bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-de}} || German bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-eastcoastusa}} || East Coast USA bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-il}} || Israeli bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-nl}} || Dutch bitcoin community. <br />
|-<br />
| {{Freenode IRC|bitcoin-pl}} || Polish bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-romania}} || Romanian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-ve}} || Venezuelan bitcoin community.<br />
|-<br />
| {{Freenode IRC|btc.chat}} || Russian bitcoin community.<br />
<br />
|}<br />
<br />
==Mining Related Communities==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|avalon}} || Discussion and support specific to [[Avalon]] mining machine<br />
|-<br />
| {{Freenode IRC|bitcoin-mining}} || Discussion and support related to mining.<br />
|-<br />
| {{Freenode IRC|bitcoin-fpga}} || Discussion and support specific to FPGA mining.<br />
|-<br />
| {{Freenode IRC|btcguild}} || [[BTCGuild]] mining pool community<br />
|-<br />
| {{Freenode IRC|butterflylabs}} || [[Butterfly Labs]] chat<br />
|-<br />
| {{Freenode IRC|cgminer}} || Discussion and support specific to [[CGMiner]].<br />
|-<br />
| {{Freenode IRC|eligius}} || [[Eligius]] mining pool community (also support for [[BFGMiner]] and [[Eloipool]])<br />
|-<br />
| {{Freenode IRC|give-me-coins}} || [[Give Me COINS]] mining pool community<br />
|-<br />
| {{Freenode IRC|mining.bitcoin.cz}} || Slush's mining pool community<br />
|-<br />
| {{Freenode IRC|ozcoin}} || [[Ozco.in]] mining pool community<br />
|-<br />
| <small>[irc://irc.foonetic.net/xkcd-bitcoin IRC] [http://irc.lc/foonetic/xkcd-bitcoin/Miner@@@ Web]</small> #xkcd-bitcoin || [https://en.bitcoin.it/wiki/XKCD_Pool XKCD Pool]<br />
|-<br />
| <small>[irc://irc.quakenet.org/bitcoins.lc IRC] [http://irc.lc/quakenet/bitcoins.lc/Miner@@@ Web]</small> #bitcoins.lc @ Quakenet || [http://www.bitcoins.lc Bitcoins.lc Pool] <br />
|-<br />
| {{Freenode IRC|p2pool}} || [[P2Pool]] decentralized mining pool<br />
|-<br />
| {{Freenode IRC|bitminter}} || [[BitMinter]] Mining Pool Community<br />
|-<br />
| {{Freenode IRC|kncminer}} || [[KNCMiner]] ASIC Mining Hardware Vendor Discussion<br />
|-<br />
| {{Freenode IRC|triplemining}} || [[TripleMining]] mining pool community<br />
|}<br />
<br />
==Communities for Exchanges and Trading==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|bitcoin-assets}} || Discussion of securities and other asset investments. [http://bitcoin-assets.com bitcoin-assets.com].<br />
|-<br />
| {{Freenode IRC|bitcoin-assets-trades}} || Streaming assets market data (only), no chat.<br />
|-<br />
| {{Freenode IRC|bitcoin-auction}} || Live auctions over IRC.<br />
|-<br />
| {{Freenode IRC|bitcoin-market}} || Streaming market data (only), no chat.<br />
|-<br />
| {{Freenode IRC|bitcoin-otc|text=[[bitcoin-otc|#bitcoin-otc]]}} || Over-the-counter trading marketplace and discussion. ([http://bitcoinstats.com/irc/bitcoin-otc/logs/ history])<br />
|-<br />
| {{Freenode IRC|bitcoin-escrow}} || Third party escrow agents.<br />
|-<br />
| {{Freenode IRC|bitcoin-otc-ticker|bitcoin-otc-ticker}} || Streaming market data form the [[#bitcoin-otc]] order book.<br />
|-<br />
| {{Freenode IRC|bitcoin-otc-ratings|bitcoin-otc-ratings}} || Updates to ratings on the [[#bitcoin-otc]] Web of Trust.<br />
|-<br />
| {{Freenode IRC|bitcoin-pit}} || Only over-the-counter trading.<br />
|-<br />
| {{Freenode IRC|bitcoin-wot|bitcoin-wot}} || Distributed Web of Trust (WoT) system for [[#bitcoin-otc]].<br />
|-<br />
| {{Freenode IRC|btc.chat.traders}} || Russian community discussion about trades/exchanges.<br />
|-<br />
| {{Freenode IRC|coinbase}} || [[Coinbase]] chat<br />
|-<br />
| {{Freenode IRC|#mtgox-chat}} || [[#MtGox]] chat (Note the extra pound sign (#) is part of the channel name)<br />
|-<br />
| {{Freenode IRC|mtgox}} || [[MtGox]] support<br />
|-<br />
| {{Freenode IRC|mtgoxlive}} || [[MtGox Live]] real-time view of trading<br />
|-<br />
| {{Freenode IRC|mtgox-news}} || Mt. Gox topics from Twitter.<br />
|-<br />
| {{Freenode IRC|mtgox-rt}} || Mt. Gox real-time tape (executed trades).<br />
|-<br />
| {{Freenode IRC|bitcoin-rt}} || Real-time tape (executed trades).<br />
|-<br />
| {{Freenode IRC|localbitcoins-chat}} || [[LocalBitcoins.com]] exchange support<br />
|-<br />
| {{Freenode IRC|Coinabul}} || [http://Coinabul.com Coinabul]'s customer support and news channel. Selling gold and silver for Bitcoin.<br />
|}<br />
<br />
==Related Communities==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|opentransactions}} || [[Open Transactions]] project.<br />
|-<br />
| {{Freenode IRC|namecoin}} || [[Namecoin]] and the [[Dot-bit]] project.<br />
|-<br />
| {{Freenode IRC|twister}} || [[Twister]], P2P microblogging discussion.<br />
|-<br />
| {{Freenode IRC|darkwallet}} || [[DarkWallet]] and libbitcoin/Obelisk discussion & development channel.<br />
|-<br />
| {{Freenode IRC|electrum}} || [[Electrum]], lightweight bitcoin client.<br />
|-<br />
| {{Freenode IRC|bitcoin-stackexchange}} || Discussion complementing [http://bitcoin.stackexchange.com Bitcoin StackExchange].<br />
<br />
|}<br />
<br />
[[fr:Canaux IRC]]<br />
[[pl:Kanały IRC]]<br />
[[ro:Canale]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=IRC_channels&diff=47759IRC channels2014-05-30T15:19:49Z<p>Nanotube: /* Communities for Exchanges and Trading */ cut out -markets* and -tickers* since they're all dead.</p>
<hr />
<div>Most of the following Bitcoin-related IRC channels are available on [http://www.freenode.net Freenode]:<br />
<br />
==Bitcoin Project==<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|bc-news}} || RSS News related to Bitcoin.<br />
|-<br />
| {{Freenode IRC|bitcoin}} || General Bitcoin-related discussion ([[Bitcoin_IRC_Channel_Guidelines | guidelines]]).<br />
|-<br />
| {{Freenode IRC|bitcoin-court}} || [[Bitcoin Court]] Settles disputes between parties.<br />
|-<br />
| {{Freenode IRC|bitcoin-dev}} || Bitcoin software development. ([http://bitcoinstats.com/irc/bitcoin-dev/logs/ history]. [[Bitcoin-dev | guidelines]])<br />
|-<br />
| {{Freenode IRC|bitcoin-gaming}} || Bitcoin gamers hangout.<br />
|-<br />
| {{Freenode IRC|bitcoin-gentoo}} || Gentoo community.<br />
|-<br />
| {{Freenode IRC|bitcoin-marketing}} || Marketing and promotion of bitcoin<br />
|-<br />
| {{Freenode IRC|bitcoin-police}} || [[Bitcoin Police]] Investigates incidents related to Bitcoin.<br />
|-<br />
| {{Freenode IRC|bitcoin-politics}} || Discuss politics with other Bitcoin users.<br />
|-<br />
| {{Freenode IRC|bitcoin-pricetalk}} || ALL Discussion Remotely Related to Bitcoin Price goes here<br />
|-<br />
| {{Freenode IRC|bitcoin-tweets}} || Automated announce of bitcoin-related tweets.<br />
|-<br />
| {{Freenode IRC|bitcoin-watch|text=[[Bitcoin-Watch|#bitcoin-watch]]}} || Streaming Bitcoin transactions, including market data.<br />
|-<br />
| {{Freenode IRC|bitcoin-wiki}} || Bitcoin Wiki support<br />
|}<br />
<br />
===Local communities===<br />
<br />
{| class="wikitable"<br />
| {{Freenode IRC|bitcoin-otc-eu}} || European OTC trading marketplace.<br />
|-<br />
| {{Freenode IRC|bitcoin-otc-ru}} || Russian OTC trading marketplace.<br />
|-<br />
| {{Freenode IRC|bitcoin-otc-uk}} ||United kingdom OTC Trading Marketplace.Founder Angus Bates.<br />
|-<br />
| {{Freenode IRC|bitcoin-aus}} || Aussie bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-br}} || Brazilian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-cad}} || Canadian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-cn}} || Chinese bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-dk}} || Danish bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-de}} || German bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-eastcoastusa}} || East Coast USA bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-il}} || Israeli bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-nl}} || Dutch bitcoin community. <br />
|-<br />
| {{Freenode IRC|bitcoin-pl}} || Polish bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-romania}} || Romanian bitcoin community.<br />
|-<br />
| {{Freenode IRC|bitcoin-ve}} || Venezuelan bitcoin community.<br />
|-<br />
| {{Freenode IRC|btc.chat}} || Russian bitcoin community.<br />
<br />
|}<br />
<br />
==Mining Related Communities==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|avalon}} || Discussion and support specific to [[Avalon]] mining machine<br />
|-<br />
| {{Freenode IRC|bitcoin-mining}} || Discussion and support related to mining.<br />
|-<br />
| {{Freenode IRC|bitcoin-fpga}} || Discussion and support specific to FPGA mining.<br />
|-<br />
| {{Freenode IRC|btcguild}} || [[BTCGuild]] mining pool community<br />
|-<br />
| {{Freenode IRC|butterflylabs}} || [[Butterfly Labs]] chat<br />
|-<br />
| {{Freenode IRC|cgminer}} || Discussion and support specific to [[CGMiner]].<br />
|-<br />
| {{Freenode IRC|eligius}} || [[Eligius]] mining pool community (also support for [[BFGMiner]] and [[Eloipool]])<br />
|-<br />
| {{Freenode IRC|give-me-coins}} || [[Give Me COINS]] mining pool community<br />
|-<br />
| {{Freenode IRC|mining.bitcoin.cz}} || Slush's mining pool community<br />
|-<br />
| {{Freenode IRC|ozcoin}} || [[Ozco.in]] mining pool community<br />
|-<br />
| <small>[irc://irc.foonetic.net/xkcd-bitcoin IRC] [http://irc.lc/foonetic/xkcd-bitcoin/Miner@@@ Web]</small> #xkcd-bitcoin || [https://en.bitcoin.it/wiki/XKCD_Pool XKCD Pool]<br />
|-<br />
| <small>[irc://irc.quakenet.org/bitcoins.lc IRC] [http://irc.lc/quakenet/bitcoins.lc/Miner@@@ Web]</small> #bitcoins.lc @ Quakenet || [http://www.bitcoins.lc Bitcoins.lc Pool] <br />
|-<br />
| {{Freenode IRC|p2pool}} || [[P2Pool]] decentralized mining pool<br />
|-<br />
| {{Freenode IRC|bitminter}} || [[BitMinter]] Mining Pool Community<br />
|-<br />
| {{Freenode IRC|kncminer}} || [[KNCMiner]] ASIC Mining Hardware Vendor Discussion<br />
|-<br />
| {{Freenode IRC|triplemining}} || [[TripleMining]] mining pool community<br />
|}<br />
<br />
==Communities for Exchanges and Trading==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|bitcoin-assets}} || Discussion of securities and other asset investments. [http://bitcoin-assets.com bitcoin-assets.com].<br />
|-<br />
| {{Freenode IRC|bitcoin-assets-trades}} || Streaming assets market data (only), no chat.<br />
|-<br />
| {{Freenode IRC|bitcoin-auction}} || Live auctions over IRC.<br />
|-<br />
| {{Freenode IRC|bitcoin-market}} || Streaming market data (only), no chat.<br />
|-<br />
| {{Freenode IRC|bitcoin-otc|text=[[bitcoin-otc|#bitcoin-otc]]}} || Over-the-counter trading marketplace and discussion. ([http://bitcoinstats.com/irc/bitcoin-otc/logs/ history])<br />
|-<br />
| {{Freenode IRC|bitcoin-escrow}} || Third party escrow agents.<br />
|-<br />
| {{Freenode IRC|bitcoin-otc-ticker|bitcoin-otc-ticker}} || Streaming market data form the [[#bitcoin-otc]] order book.<br />
|-<br />
| {{Freenode IRC|bitcoin-otc-ratings|bitcoin-otc-ratings}} || Updates to ratings on the [[#bitcoin-otc]] Web of Trust.<br />
|-<br />
| {{Freenode IRC|bitcoin-pit}} || Only over-the-counter trading.<br />
|-<br />
| {{Freenode IRC|bitcoin-wot|bitcoin-wot}} || Distributed Web of Trust (WoT) system for [[#bitcoin-otc]].<br />
|-<br />
| {{Freenode IRC|btc.chat.traders}} || Russian community discussion about trades/exchanges.<br />
|-<br />
| {{Freenode IRC|coinbase}} || [[Coinbase]] chat<br />
|-<br />
| {{Freenode IRC|#mtgox-chat}} || [[#MtGox]] chat (Note the extra pound sign (#) is part of the channel name)<br />
|-<br />
| {{Freenode IRC|mtgox}} || [[MtGox]] support<br />
|-<br />
| {{Freenode IRC|mtgoxlive}} || [[MtGox Live]] real-time view of trading<br />
|-<br />
| {{Freenode IRC|mtgox-news}} || Mt. Gox topics from Twitter.<br />
|-<br />
| {{Freenode IRC|mtgox-rt}} || Mt. Gox real-time tape (executed trades).<br />
|-<br />
| {{Freenode IRC|bitcoin-rt}} || Real-time tape (executed trades).<br />
|-<br />
| {{Freenode IRC|localbitcoins-chat}} || [[LocalBitcoins.com]] exchange support<br />
|-<br />
| {{Freenode IRC|Coinabul}} || [http://Coinabul.com Coinabul]'s customer support and news channel. Selling gold and silver for Bitcoin.<br />
|}<br />
<br />
==Related Communities==<br />
<br />
{| class="wikitable"<br />
! Channel !! Description<br />
|-<br />
| {{Freenode IRC|opentransactions}} || [[Open Transactions]] project.<br />
|-<br />
| {{Freenode IRC|namecoin}} || [[Namecoin]] and the [[Dot-bit]] project.<br />
|-<br />
| {{Freenode IRC|twister}} || [[Twister]], P2P microblogging discussion.<br />
|-<br />
| {{Freenode IRC|darkwallet}} || [[DarkWallet]] and libbitcoin/Obelisk discussion & development channel.<br />
|-<br />
| {{Freenode IRC|electrum}} || [[Electrum]], lightweight bitcoin client.<br />
|-<br />
| {{Freenode IRC|bitcoin-stackexchange}} || Discussion complementing [http://bitcoin.stackexchange.com Bitcoin StackExchange].<br />
<br />
|}<br />
<br />
[[fr:Canaux IRC]]<br />
[[pl:Kanały IRC]]<br />
[[ro:Canale]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin_IRC_Channel_Guidelines&diff=47098Bitcoin IRC Channel Guidelines2014-05-07T21:34:44Z<p>Nanotube: Removed protection from "Bitcoin IRC Channel Guidelines": let's see how it goes</p>
<hr />
<div>The {{Freenode IRC|bitcoin}} channel on freenode serves as the de-facto "front door" for newcomers on IRC. Therefore, we strive to maintain a professional, friendly, and helpful atmosphere on the channel at all times. To this effect, the following behaviors are expressly prohibited: <br />
* Insults, flamewars, trolling;<br />
* Discussion of unlawful activity, pursuant to [http://freenode.net/policy.shtml#unlawful freenode's guidelines];<br />
* Generally, anything that would make a newcomer feel unwelcome or would reflect badly on the bitcoin community is to be avoided.<br />
Private chat and alternative channels are always available, make good use of them.</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Contract&diff=46251Contract2014-04-09T01:27:47Z<p>Nanotube: Reverted edits by Ragnar (talk) to last revision by Mike</p>
<hr />
<div>A '''distributed contract''' is a method of using Bitcoin to form agreements with people via the block chain. Contracts don't make anything possible that was previously impossible, but rather, they allow you to solve common problems in a way that minimizes trust. Minimal trust often makes things more convenient by allowing human judgements to be taken out of the loop, thus allowing complete automation.<br />
<br />
By building low trust protocols that interact with Bitcoin, entirely new products can be created:<br />
<br />
* [[Smart Property|Smart property]] is property that can be atomically traded and loaned via the block chain.<br />
* [[Transferable virtual property]] are digital items that can be traded but not duplicated.<br />
* [[Agents]] are autonomous programs that maintain their own wallet, which they use to buy server time. Money is obtained by the agent selling services. If demand exceeds supply the agents can spawn children that either survive or die depending on whether they can get enough business.<br />
* [[Distributed markets]] are a way to implement peer to peer bond and stock trading, allowing Bitcoin to be evolve into a full competitor to the international financial system.<br />
* The [[Ripple currency exchange]] is a way to implement a distributed currency exchange based on social networks.<br />
<br />
This page also lists some smaller examples.<br />
<br />
Many of the ideas underlying Bitcoin contracts were first described by Nick Szabó in his seminal paper, <br />
[http://szabo.best.vwh.net/formalize.html Formalizing and Securing Relationships on Public Networks]. These pages were written by [mailto:mike@plan99.net Mike Hearn]. Contact him if you have an idea for a new type of contract. You can watch '''[https://www.youtube.com/watch?feature=player_embedded&v=mD4L7xDNCmA a video of a talk on contracts]''' that was presented at the Bitcoin 2012 conference in London.<br />
<br />
<br />
==A warning about the mempool transaction replacement mechanism==<br />
<br />
In places this page refers to the ability to use the nSequence field for transaction mempool replacement. This mechanism was disabled in [https://github.com/bitcoin/bitcoin/commit/401926283a200994ecd7df8eae8ced8e0b067c46 2010], and more recently the code has been [https://github.com/bitcoin/bitcoin/commit/98c7c8fd1d3712e02be0e9f2eeca7e02aa54d197 removed completely], due to concerns over people using it to perform DoS attacks. Implementors should take this into account and try to create contract mechanisms that do not rely on mempool replacement if they wish to have their implementations work with current implementations. If Bitcoin changes in future to allow mempool replacement once again, this page will be updated.<br />
<br />
==Theory==<br />
<br />
Every [[transaction]] in Bitcoin has one or more inputs and outputs. Each input/output has a small, pure function associated with it called a [[script]]. Scripts can contain signatures over simplified forms of the transaction itself.<br />
<br />
Every transaction can have a lock time associated with it. This allows the transaction to be pending and replaceable until an agreed-upon future time, specified either as a block index or as a timestamp (the same field is used for both, but values less than 500 million are interpreted as a block index). If a transaction's lock time has been reached, we say it is final.<br />
<br />
Each transaction input has a sequence number. In a normal transaction that just moves value around, the sequence numbers are all UINT_MAX and the lock time is zero. If the lock time has not yet been reached, but all the sequence numbers are UINT_MAX, the transaction is also considered final. Sequence numbers can be used to issue new versions of a transaction without invalidating other inputs signatures, e.g., in the case where each input on a transaction comes from a different party, each input may start with a sequence number of zero, and those numbers can be incremented independently.<br />
<br />
Signature checking is flexible because the form of transaction that is signed can be controlled through the use of SIGHASH flags, which are stuck on the end of a signature. In this way, contracts can be constructed in which each party signs only a part of it, allowing other parts to be changed without their involvement. The SIGHASH flags have two parts, a mode and the ANYONECANPAY modifier:<br />
<br />
# SIGHASH_ALL: This is the default. It indicates that everything about the transaction is signed, except for the input scripts. Signing the input scripts as well would obviously make it impossible to construct a transaction, so they are always blanked out. Note, though, that other properties of the input, like the connected output and sequence numbers, ''are'' signed; it's only the scripts that are not. Intuitively, it means "I agree to put my money in, if everyone puts their money in and the outputs are this".<br />
# SIGHASH_NONE: The outputs are not signed and can be anything. Use this to indicate "I agree to put my money in, as long as everyone puts their money in, but I don't care what's done with the output". This mode allows others to update the transaction by changing their inputs sequence numbers.<br />
# SIGHASH_SINGLE: Like SIGHASH_NONE, the inputs are signed, but the sequence numbers are blanked, so others can create new versions of the transaction. However, the only output that is signed is the one at the same position as the input. Use this to indicate "I agree, as long as my output is what I want; I don't care about the others".<br />
<br />
The SIGHASH_ANYONECANPAY modifier can be combined with the above three modes. When set, only that input is signed and the other inputs can be anything.<br />
<br />
Scripts can contain the CHECKMULTISIG opcode. This opcode provides n-of-m checking: you provide multiple public keys, and specify the number of valid signatures that must be present. The number of signatures can be less than the number of public keys. An output can require two signatures to be spent by setting it to something like this:<br />
<br />
2 <pubkey1> <pubkey2> 2 CHECKMULTISIGVERIFY<br />
<br />
There are two general patterns for safely creating contracts:<br />
<br />
# Transactions are passed around outside of the P2P network, in partially-complete or invalid forms.<br />
# Two transactions are used: one (the contract) is created and signed but not broadcast right away. Instead, the other transaction (the payment) is broadcast after the contract is agreed to lock in the money, and then the contract is broadcast.<br />
<br />
This is to ensure that people always know what they are agreeing to.<br />
<br />
Together, these features let us build interesting new financial tools on top of the block chain.<br />
<br />
==Example 1: Providing a deposit==<br />
<br />
Imagine that you open an account on a website (eg, a forum or wiki) and wish to establish your trustworthiness with the operators, but you don't have any pre-existing reputation to leverage. One solution is to buy trust by paying the website some money. But if at some point you close your account, you'd probably like that money back. You may not trust the site enough to give them a deposit that they are tempted to spend. Another risk is that the site might just disappear one day. <br />
<br />
The goal is to prove that you made a sacrifice of some kind so the site knows you're not a spambot, but you don't want them to be able to spend the money. And if the operators disappear, you'd eventually like the coins back without needing anything from them.<br />
<br />
We can solve this problem with a contract:<br />
<br />
# The user and website send each other a newly-generated public key.<br />
# The user creates transaction Tx1 (the payment) putting 10 BTC into an output that requires both user and website to sign, but does not broadcast it. They use the key from the previous step for the site.<br />
# User sends the hash of Tx1 to the website.<br />
# The website creates a transaction Tx2 (the contract). Tx2 spends Tx1 and pays it back to the user via the address he provided in the first step. Note that Tx1 requires two signatures, so this transaction can't be complete. nLockTime is set to some date in the future (eg, six months). The sequence number on the input is set to zero.<br />
# Finally, the incomplete (half-signed) transaction is sent back to the user. The user checks that the contract is as expected - that the coins will eventually come back to him - but, unless things are changed, only after six months. Because the sequence number is zero, the contract can be amended in future if both parties agree. The script in the input isn't finished though; there are only zeros where the user's signature should be. He fixes that by signing the contract and putting the new signature in the appropriate spot.<br />
# The user broadcasts Tx1, then broadcasts Tx2.<br />
<br />
At this stage, the 10 BTC are in a state where neither the user nor the website can spend them independently. After six months, the contract will complete and the user will get the coins back, even if the website disappears.<br />
<br />
What if the user wishes to close his account early? The website creates a new version of Tx2 with nLockTime set to zero and the input sequence number set to UINT_MAX, then he re-signs it. The site hands the tx back to the user, who signs it as well. The user then broadcasts the transaction, terminating the contract early and releasing the coins.<br />
<br />
What if the six months is nearly up and the user wishes to keep his account? The same thing applies: the contract can be resigned with a newer nLockTime, a sequence number 1 higher than the previous and rebroadcast 2^32 times. No matter what happens, both parties must agree for the contract to change.<br />
<br />
Obviously, if the user turns out to be abusive (i.e., a spammer), the website will not allow an early close of the contract. If too much abuse is getting through, the size of the deposit can be raised or the length of the contract can be increased.<br />
<br />
==Example 2: Escrow and dispute mediation==<br />
<br />
A buyer wants to trade with somebody he doesn't know or trust. In the common case where the transaction goes well, the client doesn't want any third parties involved. If something goes wrong though, he'd like a third party to decide who gets the money - perhaps a professional dispute mediation service. Note that this concept can apply to either buyer or seller. The mediator might request proof of postage from the merchant, for example.<br />
<br />
In other words, one wants to lock up some coins so a third party has to agree in order for them to be spent:<br />
<br />
# Agree with the merchant on a dispute mediator (e.g., ClearCoin).<br />
# Ask the merchant for a public key (K1). Ask the mediator for a public key (K2). Create a new key for yourself (K3).<br />
# Send the merchant K2. The merchant challenges the mediator with a random nonce. The mediator signs the nonce with the private form of K2, thus proving it really belongs to merchant.<br />
# Create a transaction (Tx1) with an output script as follows and broadcast it:<br />
<br />
2 <K1> <K2> <K3> 3 CHECKMULTISIGVERIFY<br />
<br />
Now the coins are locked in such a way that they can only be spent by the following methods:<br />
<br />
# Client and the merchant agree (either a successful trade, or merchant agrees to reimburse client without mediation)<br />
# Client and the mediator agree (failed trade, mediator sides with client, like a charge-back)<br />
# The mediator and the merchant agree (goods delivered, merchant gets client's coins despite the dispute)<br />
<br />
When signing an input, the contents are set to the connected output. Thus, to redeem this transaction, the client creates a scriptSig containing zeros where the other signature should be, signs it, and then sets one of the slots to his new signature. The partially-complete transaction can then be sent to the merchant or mediator for the second signature.<br />
<br />
==Example 3: Assurance contracts==<br />
<br />
An [http://en.wikipedia.org/wiki/Assurance_contract assurance contract] is a way of funding the creation of a [http://www.auburn.edu/~johnspm/gloss/public_goods public good], that is, a good that, once created, anyone can benefit from for free. The standard example is a lighthouse: whilst everyone may agree that one should be built, it’s too expensive for an individual sailor to justify building one, given that it will also benefit all his competitors. <br />
<br />
One solution is for everyone to pledge money towards the creation of the public good, such that the pledges are only committed if the total value of all pledges is above the cost of creation. If not enough people contribute, nobody has to pay anything.<br />
<br />
Examples where Bitcoin is superior to traditional payment methods for assurance contract fundraising include applications where frequent, small pledges need to be made automatically, for instance internet radio station funding and [https://bitcointalk.org/index.php?topic=67255.msg788110#msg788110 web page translation]. Consider a browser extension that you send a bit of money to. It detects the current language of the page and broadcasts a pledge for a translation into your language to be prepared. If enough users with the extension land on the same page at the same time (eg, it was linked to from somewhere high traffic), then enough pledges are broadcast to trigger a payment to a company who prepares a high quality translation. When complete it automatically loads in your browser.<br />
<br />
We can model this in Bitcoin as follows:<br />
<br />
# An entrepreneur creates a new address and announces that the good will be created if at least 1000 BTC is raised. Anyone can contribute.<br />
# Each party wishing to pledge creates a new transaction spending some of their coins to the announced address, but they do not broadcast it. The transaction is similar to a regular transaction except for three differences: Firstly, there cannot be any change. If you don’t have any outputs of the right size, you must create one first by spending to one of your own addresses. Secondly, the input script signature is signed with SIGHASH_ALL | SIGHASH_ANYONECANPAY. Finally, the output value is set to 1000 BTC. Note that this is not a valid transaction because the output value is larger than the input value.<br />
# The transaction is uploaded to the entrepreneur's server, which saves it to disk and updates its count of how many coins have been pledged.<br />
# Once the server has enough coins, it merges the separate transactions together into a new transaction. The new transaction has a single output that simply spends to the announced address - it is the same as the outputs on each contributed transaction. The inputs to the transaction are collected from the contributed pledges.<br />
# The finished transaction is broadcast, sending the pledged coins to the announced address.<br />
<br />
This scheme relies on several aspects of the protocol. The first is the SIGHASH flags used. SIGHASH_ALL is the default and means the entire contents of the transaction are signed, except for the input scripts. SIGHASH_ANYONECANPAY is an additional modifier that means the signature only covers the input it’s found in - the other inputs are not signed and thus can be anything.<br />
<br />
By combining these flags together, we are able to create a signature that is valid even when other inputs are added, but breaks if the outputs or other properties of the transaction are changed.<br />
<br />
The second aspect we exploit is the fact that a transaction in which the output values are larger than the input values is invalid (for obvious reasons). This means it’s safe to send the entrepreneur a transaction that spends such coins - it’s impossible for him to claim the coins unless he has other inputs that sum to the output value or more.<br />
<br />
It's possible to create assurance contracts without using SIGHASH_ANYONECANPAY. Instead, a two step process is used in which pledges are collected without transactions, and once the total value is reached, a transaction with an input for each pledger is created and passed around until all signatures are collected. However, using SIGHASH_ANYONECANPAY and then merging is probably more convenient.<br />
<br />
An assurance contract can be prepared for '''[[Funding network security|funding network security]]''' for the next block. In this way, mining can be funded even if block space is not scarce.<br />
<br />
An elaboration of this concept is described by Tabarrok in his paper, [http://mason.gmu.edu/~atabarro/PrivateProvision.pdf “The private provision of public goods via dominant assurance contracts”]. In a dominant assurance contract, if a contract fails (not enough pledges within a set time window) the entrepreneur pays a fee to those who pledged so far. This type of contract attempts to arrange incentives such that taking part is always the right strategy. [[Dominant Assurance Contracts|A scheme for dominant assurance contracts]] in Bitcoin has been proposed.<br />
<br />
==Example 4: Using external state==<br />
<br />
Scripts are, by design, pure functions. They cannot poll external servers or import any state that may change as it would allow an attacker to outrun the block chain. What's more, the scripting language is extremely limited in what it can do. Fortunately, we can make transactions connected to the world in other ways.<br />
<br />
Consider the example of an old man who wishes to give an inheritance to his grandson, either on the grandson's 18th birthday or when the man dies, whichever comes first. <br />
<br />
To solve this, the man first sends the amount of the inheritance to himself so there is a single output of the right amount. Then he creates a transaction with a lock time of the grandson's 18th birthday that pays the coins to another key owned by the grandson, signs it, and gives it to him - but does not broadcast it. This takes care of the 18th birthday condition. If the date passes, the grandson broadcasts the transaction and claims the coins. He could do it before then, but it doesn't let him get the coins any earlier, and some nodes may choose to drop transactions in the memory pool with lock times far in the future.<br />
<br />
The death condition is harder. As Bitcoin nodes cannot measure arbitrary conditions, we must rely on an ''oracle''. An oracle is a server that has a keypair, and signs transactions on request when a user-provided expression evaluates to true.<br />
<br />
Here is an example. The man creates a transaction spending his output, and sets the output to:<br />
<br />
<hash> OP_DROP 2 <sons pubkey> <oracle pubkey> CHECKMULTISIG<br />
<br />
This is the oracle script. It has an unusual form - it pushes data to the stack then immediately deletes it again. The pubkey is published on the oracle's website and is well-known. The hash is set to be the hash of the user-provided expression stating that he has died, written in a form the oracle knows how to evaluate. For example, it could be the hash of the string:<br />
<br />
if (has_died('john smith', born_on=1950/01/02)) return (10.0, 1JxgRXEHBi86zYzHN2U4KMyRCg4LvwNUrp);<br />
<br />
This little language is hypothetical, it'd be defined by the oracle and could be anything. The return value is an output: an amount of value and an address owned by the grandson.<br />
<br />
Once more, the man creates this transaction but gives it directly to his grandson instead of broadcasting it. He also provides the expression that is hashed into the transaction and the name of the oracle that can unlock it.<br />
<br />
It is used in the following algorithm:<br />
<br />
# The oracle accepts a measurement request. The request contains the user-provided expression, a copy of the output script, and a partially complete transaction provided by the user. Everything in this transaction is finished except for the scriptSig, which contains just one signature (the grandson's) - not enough to unlock the output.<br />
# The oracle checks the user-provided expression hashes to the value in the provided output script. If it doesn't, it returns an error.<br />
# The oracle evaluates the expression. If the result is not the destination address of the output, it returns an error.<br />
# Otherwise the oracle signs the transaction and returns the signature to the user. Note that when signing a Bitcoin transaction, the input script is set to the connected output script. The reason is that when OP_CHECKSIG runs, the script containing the opcode is put in the input being evaluated, _not_ the script containing the signature itself. The oracle has never seen the full output it is being asked to sign, but it doesn't have to. It knows the output script, its own public key, and the hash of the user-provided expression, which is everything it needs to check the output script and finish the transaction.<br />
# The user accepts the new signature, inserts it into the scriptSig and broadcasts the transaction.<br />
<br />
If, and only if, the oracle agrees that the man is dead, the grandson can broadcast the two transactions (the contract and the claim) and take the coins.<br />
<br />
Oracles can potentially evaluate anything, yet the output script form in the block chain can always be the same. Consider the following possibilities:<br />
<br />
today() == 2011/09/25 && exchange_rate(mtgoxUSD) >= 12.5 && exchange_rate(mtgoxUSD) <= 13.5<br />
Require exchange rate to be between two values on a given date<br />
<br />
google_results_count(site:www.google.com/hostednews 'Mike Hearn' olympic gold medal) > 0<br />
A bet on me doing something that I will never actually do<br />
<br />
// Choose between one of two winners of a bet on the outcome of the Eurovision song contest.<br />
if (eurovision_winner() == 'Azerbaijan') <br />
return 1Lj9udBVDwptFffGSJSC2sohCfudQgSTPD; <br />
else <br />
return 1JxgRXEHBi86zYzHN2U4KMyRCg4LvwNUrp;<br />
<br />
The conditions that control whether the oracle signs can be arbitrarily complex, but the block chain never needs to contain more than a single hash.<br />
<br />
===Trust minimization: challenges===<br />
<br />
There are various ways to reduce the level of required trust in the oracle.<br />
<br />
Going back to our first example, the oracle has not seen the transaction the grandson is trying to unlock, as it was never broadcast, thus, it cannot hold the grandson to ransom because it does not know whether the transaction it's signing for even exists. People can, and should, regularly '''challenge''' the oracle in an automated fashion to ensure it always outputs what is expected. The challenges can be done without spending any coins because the tx to be signed can be invalid (ie, connected to transactions that don't exist). The oracle has no way to know whether a request to be signed is random or real. How to challenge the oracle with conditions that are not yet true is however an open research question. <br />
<br />
===Trust minimization: multiple independent oracles===<br />
<br />
The number of keys in the CHECKMULTISIG can be increased to allow for '''n-of-m''' oracles if need be. Of course, it is vital to check that the oracles really are independent and not in collusion.<br />
<br />
===Trust minimization: trusted hardware===<br />
<br />
Using commodity hardware, you can use '''trusted computing''' in the form of Intel TXT or the AMD equivalent (SKINIT) to set up a sealed hardware environment and then use the TPM chip to attest that fact to a third party. That third party can verify the hardware was in the required state. Defeating this requires someone to be able to interfere with the execution of a program that may run entirely on the CPU, even in extreme cases without any data traversing the memory bus (you can run entirely using on-die cache if the program is small enough).<br />
<br />
===Trust minimization: Amazon AWS oracles===<br />
<br />
Finally, perhaps the most practical approach currently is to use Amazon Web Services. As of November 2013, the closest we have to a working oracle is [https://bitcointalk.org/index.php?topic=301538.0 this recipe for creating a trusted computing environment using AWS], built in support of [https://bitcointalk.org/index.php?topic=173220.0 this project for doing selective SSL logging and decryption]. The idea is that an oracle, which can be proven trustworthy using the Amazon APIs with Amazon as the root of trust, records encrypted SSL sessions to an online banking interface in such a way that later if there is a dispute about a person-to-person exchange, the logs can be decrypted and the dispute settled.<br />
<br />
<br />
==Example 5: Trading across chains==<br />
<br />
The Bitcoin technology can be adapted to create [[Alternative chain|multiple, independent currencies]]. NameCoin is an example of one such currency that operates under a slightly different set of rules, and can also be used to rent names in a namespace. Currencies that implement the same ideas as Bitcoin can be traded freely against each other with limited trust. <br />
<br />
For example, imagine a consortium of companies that issue EURcoins, a crypto-currency that is backed 1:1 by deposits in the consortium's bank accounts. Such a currency would have a different set of tradeoffs to Bitcoin: more centralized, but without FX risk. People might wish to trade Bitcoins for EURcoins back and forth, with the companies only getting involved when cashing in/out of the regular banking system.<br />
<br />
To implement this, a [https://bitcointalk.org/index.php?topic=193281.msg2224949#msg2224949 protocol proposed by TierNolan] can be used:<br />
<br />
# Party 'A' generates some random data, x (the secret).<br />
# Party 'A' generates Tx1 (the payment) containing an output with the chain-trade script in it. See below for this script and a discussion of it. It allows coin release either by signing with the two keys (key 'A' and key 'B') or with (secret 'x', key 'B'). This transaction is not broadcast. The chain release script contains hashes, not the actual secrets themselves.<br />
# Party 'A' generates Tx2 (the contract), which spends Tx1 and has an output going back to key 'A'. It has a lock time in the future and the input has a sequence number of zero, so it can be replaced. 'A' signs Tx2 and sends it to 'B', who also signs it and sends it back.<br />
# 'A' broadcasts Tx1 and Tx2. Party 'B' can now see the coins but cannot spend them because it does not have an output going to him, and the tx is not finalized anyway.<br />
# 'B' performs the same scheme in reverse on the alternative chain. The lock time for 'B' should be much larger than the lock time for 'A'. Both sides of the trade are now pending but incomplete.<br />
# Since 'A' knows the secret, 'A' can claim his coins immediately. However, 'A', in the process of claiming his coin, reveals the secret 'x' to 'B', who then uses it to finish the other side of the trade with ('x', key 'B').<br />
<br />
This protocol makes it feasible to do trades automatically in an entirely peer-to-peer manner, which should ensure good liquidity.<br />
<br />
The chain-trade script could look like this:<br />
<br />
IF <br />
2 <key A> <key B> 2 CHECKMULTISIGVERIFY<br />
ELSE<br />
<key B> CHECKSIGVERIFY SHA256 <hash of secret x> EQUALVERIFY<br />
ENDIF<br />
<br />
The contract input script looks like either:<br />
<br />
<sig A> <sig B> 1<br />
<br />
or<br />
<br />
<secret x> <sig B> 0<br />
<br />
i.e., the first data element selects which phase is being used.<br />
<br />
See [[Atomic cross-chain trading]] for details.<br />
<br />
Note that whilst EURcoins is a natural idea, there are other ways to implement peer-to-peer currency exchange (Bitcoin to fiat and vice versa), see the [[Ripple currency exchange]] article for more information.<br />
<br />
Sergio Demian-Lerner proposed [https://bitcointalk.org/index.php?topic=91843.0 P2PTradeX], a solution requiring the validation rules for one blockchain to be effectively encoded into the validation rules for the other.<br />
<br />
==Example 6: Pay-for-proof contracts: buying a solution to any pure function==<br />
<br />
In example 4, we saw how to make payments conditional on the output of some arbitrary program. Those programs are very powerful and can do anything a regular program can do, like fetching web pages. The downside is that a third party is required (an oracle). Although there are techniques that can help reduce the trust needed in the oracle, none can reduce it to zero.<br />
<br />
For a restricted class of programs, pure functions, new cryptographic techniques are starting to become available that can actually reduce the trust needed all the way to zero with no third parties. These programs cannot perform any I/O, but in many cases this restriction turns out to be unimportant or can be worked around in other ways, like by giving the program a signed/timestamped document as an input instead of having the program download it.<br />
<br />
Read an explanation of the protocol here: [[Zero Knowledge Contingent Payment]]<br />
<br />
==Example 7: Rapidly-adjusted (micro)payments to a pre-determined party==<br />
<br />
Bitcoin transactions are very cheap relative to traditional payment systems, but still have a cost due to the need for it to be mined and stored. There are some cases in which you want to rapidly and cheaply adjust the amount of money sent to a particular recipient without incurring the cost of a broadcast transaction.<br />
<br />
For example, consider an untrusted internet access point, like a WiFi hotspot in a cafe you never visited before. You'd like to pay 0.001 BTC per 10 kilobytes of usage, without opening an account with the cafe. A zero-trust solution means it could be fully automatic, so you could just pre-allocate a budget on your phone's mobile wallet at the start of the month, and then your device automatically negotiates and pays for internet access on demand. The cafe also wants to allow anyone to pay them without the fear of being ripped off.<br />
<br />
To do this, the following protocol can be used. This protocol relies upon a '''different''' behavior of nLockTime to the original design. Starting around 2013 time-locked transactions were made non standard and no longer enter the memory pool, thus cannot be broadcast before the timelock expires. When the behaviour of nLockTime is restored to the original design from Satoshi, a variant of this protocol is required which is discussed below.<br />
<br />
We define the client to be the party sending value, and the server to be the party receiving it. This is written from the clients perspective.<br />
<br />
# Create a public key (K1). Request a public key from the server (K2). <br />
# Create and sign but do not broadcast a transaction (T1) that sets up a payment of (for example) 10 BTC to an output requiring both the server's public key and one of your own to be used. A good way to do this is use OP_CHECKMULTISIG. The value to be used is chosen as an efficiency tradeoff.<br />
# Create a refund transaction (T2) that is connected to the output of T1 which sends all the money back to yourself. It has a time lock set for some time in the future, for instance a few hours. Don't sign it, and provide the unsigned transaction to the server. By convention, the output script is "2 K1 K2 2 CHECKMULTISIG"<br />
# The server signs T2 using its public key K2 and returns the signature to the client. Note that it has not seen T1 at this point, just the hash (which is in the unsigned T2).<br />
# The client verifies the servers signature is correct and aborts if not.<br />
# The client signs T1 and passes the signature to the server, which now broadcasts the transaction (either party can do this if they both have connectivity). This locks in the money.<br />
# The client then creates a new transaction, T3, which connects to T1 like the refund transaction does and has two outputs. One goes to K1 and the other goes to K2. It starts out with all value allocated to the first output (K1), ie, it does the same thing as the refund transaction but is not time locked. The client signs T3 and provides the transaction and signature to the server.<br />
# The server verifies the output to itself is of the expected size and verifies the client's provided signature is correct.<br />
# When the client wishes to pay the server, it adjusts its copy of T3 to allocate more value to the server's output and less to its ow. It then re-signs the new T3 and sends the signature to the server. It does not have to send the whole transaction, just the signature and the amount to increment by is sufficient. The server adjusts its copy of T3 to match the new amounts, verifies the signature and continues.<br />
<br />
This continues until the session ends, or the 1-day period is getting close to expiry. The AP then signs and broadcasts the last transaction it saw, allocating the final amount to itself. The refund transaction is needed to handle the case where the server disappears or halts at any point, leaving the allocated value in limbo. If this happens then once the time lock has expired the client can broadcast the refund transaction and get back all the money.<br />
<br />
This protocol has [https://code.google.com/p/bitcoinj/wiki/WorkingWithMicropayments been implemented in bitcoinj].<br />
<br />
When nLockTime'd transactions are able to enter the memory pool (once more) and transaction replacement has been re-enabled, a variant on the protocol must be used. In this case, no refund transaction is used. Instead each T3 has a sequence number one higher than the previous and all T3's have a time lock set to the same period as above. Each time a payment is made the sequence number is incremented, ensuring that the last version will take precedence. If the channel protocol is not closed cleanly, this means the value transfer won't commit until the time lock expires. To avoid this both parties can cooperate by signing a T3 that has a sequence number of 0xFFFFFFFF resulting in immediate confirmation regardless of the value of nLockTime.<br />
<br />
The lock time and sequence numbers avoid an attack in which the AP provides connectivity, and then the user [[double-spending|double-spends]] the output back to themselves using the first version of TX2, thus preventing the cafe from claiming the bill. If the user does try this, the TX won't be included right away, giving the access point a window of time in which it can observe the TX broadcast, and then broadcast the last version it saw, overriding the user's attempted double-spend.<br />
<br />
The latter protocol that relies on transaction replacement is more flexible because it allows the value allocated to go down as well as up during the lifetime of the channel as long as the client receives signatures from the server, but for many use cases this functionality is not required. Replacement also allows for more complex configurations of channels that involve more than two parties. Elaboration on such use cases is a left as an exercise for the reader.<br />
<br />
==Example 8: Multi-party decentralised lotteries==<br />
<br />
Using some of the techniques from example 6 and some very advanced scripting, it becomes possible to build a multi-party lottery with no operator. The exact protocol used is explained in the paper [http://eprint.iacr.org/2013/784 "Secure multiparty computations on Bitcoin"]. A shorter explanation of how it works may be added to this wiki at some point in the future.<br />
<br />
<br />
==See Also==<br />
<br />
* [[Script]]<br />
<br />
[[Category:Technical]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=HashCoins&diff=46233HashCoins2014-04-08T15:10:46Z<p>Nanotube: written like an ad</p>
<hr />
<div>{{advert}} <br />
HashCoins™ develops coin mining technology for personal and business level mining devices. As a technology manufacturer, our company was created for the sole purpose of providing the average investor with the ability to participate in the new economy- digital currency. Historically, new trading vehicles have been controlled by mega corporations. With crypto currency mining capability, any investor can reap the benefits mega corporations have enjoyed for decades. As the market for crypto currency continues to expand, the demand for ever increasing algorithms and power capacity must concurrently grow. This provides a theoretical unlimited market opportunity. Application-specific integrated circuit (or ASIC) technology, has allowed the coin mining industry to launch crypto-currency generation to new levels. Our mining technology is built with ASIC 28mn chips, to provide our clientele with only the best mining hardware available on the market.<br />
<br />
https://www.hashcoins.com</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Talk:Comparison_of_cryptocurrencies&diff=46217Talk:Comparison of cryptocurrencies2014-04-07T22:44:16Z<p>Nanotube: market cap removal suggestion</p>
<hr />
<div>==suggestion not to include market cap==<br />
market cap changes too often, no point in adding that data to the wiki. Can just link to coinmarketcap or whatever.<br />
[[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 22:44, 7 April 2014 (UTC)</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Gocoin&diff=46216Gocoin2014-04-07T22:40:33Z<p>Nanotube: rearrange items in order of precedence.</p>
<hr />
<div>Gocoin can refer to one of the following:<br />
<br />
* [[Gocoin bitcoin software]] - a fully functional bitcoin solution created in Go language<br />
* [[GoCoin]] - payment processor</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitmain&diff=46029Bitmain2014-04-06T16:18:05Z<p>Nanotube: add advert template</p>
<hr />
<div>{{advert}}<br />
<br />
'''Bitmain technologies Limited''' is a Chinese IC design company founded in the first quarter of 2013, which specializes in research, development and sales for custom mining chips and miners. We aim to quickly deliver innovative and competitive custom hardware solutions to help the community. Bitmain is able to provide the most power effective Bitcoin mining solution on today’s market.<br />
<br />
==Description==<br />
Bitmain is a team of technologists, venture capitalists, entrepreneurs and Bitcoin enthusiasts. Our core members have years of ASIC development experience, and have designed and mass produced several digital signal processing ICs.<br />
<br />
We reject some business practice in the community, which is intended to distribute the risk and benefit asymmetrically. We are here to change it: we will not accept pre-order forever before we feel logically 100% sure that we can deliver on time. There will be no unexpected waiting and failed/delayed taping-out or any other kinds of delaying risks for our customers.<br />
<br />
We also give you a 24 Month Warranty to all our Products.<br />
<br />
We created a myth in bitcoin community: no pre-orders and shipping on time. We are earning more and more trust from worldwide customers.<br />
<br />
<br />
==External Links==<br />
<br />
* [https://www.bitmaintech.com Bitmaintech.com]<br />
<br />
<br />
[[Category:ECommerce]]<br />
[[Category:Shopping]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitmain&diff=46028Bitmain2014-04-06T16:09:07Z<p>Nanotube: take out useless 'yay we use ssl' section</p>
<hr />
<div>'''Bitmain technologies Limited''' is a Chinese IC design company founded in the first quarter of 2013, which specializes in research, development and sales for custom mining chips and miners. We aim to quickly deliver innovative and competitive custom hardware solutions to help the community. Bitmain is able to provide the most power effective Bitcoin mining solution on today’s market.<br />
<br />
==Description==<br />
Bitmain is a team of technologists, venture capitalists, entrepreneurs and Bitcoin enthusiasts. Our core members have years of ASIC development experience, and have designed and mass produced several digital signal processing ICs.<br />
<br />
We reject some business practice in the community, which is intended to distribute the risk and benefit asymmetrically. We are here to change it: we will not accept pre-order forever before we feel logically 100% sure that we can deliver on time. There will be no unexpected waiting and failed/delayed taping-out or any other kinds of delaying risks for our customers.<br />
<br />
We also give you a 24 Month Warranty to all our Products.<br />
<br />
We created a myth in bitcoin community: no pre-orders and shipping on time. We are earning more and more trust from worldwide customers.<br />
<br />
<br />
==External Links==<br />
<br />
* [https://www.bitmaintech.com Bitmaintech.com]<br />
<br />
<br />
[[Category:ECommerce]]<br />
[[Category:Shopping]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=AntMiner&diff=46022AntMiner2014-04-06T16:03:13Z<p>Nanotube: consolidate antminer pages</p>
<hr />
<div>{{stub}}<br />
<br />
AntMiner is a brand name for bitcoin mining ASIC hardware.<br />
<br />
ANTMINER S1 is a Bitcoin mining rig with a speed of 180 GH/s.<br />
<br />
AntMiner U1 Spec:<br />
*Default hash rate: 1.6 GH/s, over clock by command<br />
*Power consumption: 2 W on USB 5V @ 1.6G<br />
*Power supply: 5 V DC input<br />
*Size: 60 mm x 25 mm x 20 mm<br />
*MOQ: 500 units<br />
<br />
AntMiner U2+ Spec:<br />
*Default hash rate: 2.0 GH/s, over clock by command<br />
*Power consumption: 2.95 W on USB 5V @ 2 G<br />
*Power supply: 5 V DC input<br />
*Size: 60 mm x 25 mm x 15 mm<br />
<br />
<br />
== See Also ==<br />
* [https://www.bitmaintech.com Official website]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitmain&diff=46019Bitmain2014-04-06T16:00:02Z<p>Nanotube: Reverted edits by Gersics (talk) to last revision by Taras</p>
<hr />
<div>'''Bitmain technologies Limited''' is a Chinese IC design company founded in the first quarter of 2013, which specializes in research, development and sales for custom mining chips and miners. We aim to quickly deliver innovative and competitive custom hardware solutions to help the community. Bitmain is able to provide the most power effective Bitcoin mining solution on today’s market.<br />
<br />
==Description==<br />
Bitmain is a team of technologists, venture capitalists, entrepreneurs and Bitcoin enthusiasts. Our core members have years of ASIC development experience, and have designed and mass produced several digital signal processing ICs.<br />
<br />
We reject some business practice in the community, which is intended to distribute the risk and benefit asymmetrically. We are here to change it: we will not accept pre-order forever before we feel logically 100% sure that we can deliver on time. There will be no unexpected waiting and failed/delayed taping-out or any other kinds of delaying risks for our customers.<br />
<br />
We also give you a 24 Month Warranty to all our Products.<br />
<br />
We created a myth in bitcoin community: no pre-orders and shipping on time. We are earning more and more trust from worldwide customers.<br />
<br />
<br />
==Security==<br />
Bitmain uses SiteLock and verified +SSL for your protection!<br />
<br />
==External Links==<br />
<br />
* [https://www.bitmaintech.com Bitmaintech.com]<br />
<br />
<br />
[[Category:ECommerce]]<br />
[[Category:Shopping]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Mining_hardware_comparison&diff=46009Mining hardware comparison2014-04-06T15:55:33Z<p>Nanotube: Reverted edits by Gersics (talk) to last revision by Taras</p>
<hr />
<div>Below are some statistics about the mining performance of various hardware used in a Bitcoin [[mining rig]].<br />
<br />
'''Notes:''' <br />
* Mhash/s = millions hashes per second ([[Protocol_specification#Hashes|double sha256]] raw speed performance; may not be very energy efficient with some models)<br />
* Mhash/J = millions hashes per joule (energy efficiency; 1 joule of energy is 1 watt during 1 second: 1 J = 1 W*s)<br />
* W = watt (maximum power consumption, i.e. energy per unit of time: 1 W = 1 J/s)<br />
<br />
== ASIC ==<br />
<br />
'''Note that products which have not shipped, especially by new vendors, may be scams! Be sure to research any of these intensely before giving them any money.'''<br />
<br />
{| class="wikitable sortable"<br />
|+ Bitcoin [[Protocol_specification#Hashes|double SHA256]] ASIC mining hardware<br />
! data-sort-type="text" | Product !! data-sort-type="number" | Advertised Mhash/s !! data-sort-type="number" | Mhash/J !! data-sort-type="number" | Mhash/s/$ !! data-sort-type="number" | Watts !! data-sort-type="currency" | Price (USD) !! data-sort-type="date" | Currently shipping !! class="unsortable" | Comm ports !! class="unsortable" | Dev-friendly <br />
|- <br />
! [[AntMiner]] S1 <ref name="AntMinerS1"/><br />
| 180,000 || 500 || 155 || 360 || 615 || {{Yes}} || Ethernet || {{Yes|code, samples}}<br />
|-<br />
! [[AntMiner]] U1 <ref name="AntMinerU1"/><br />
| 1,600 || 800 || 55 || 2 || 29 || {{No|Discontinued}} || USB || {{Yes|code, samples}}<br />
|-<br />
! [[AntMiner]] U2+ <ref name="AntMinerU2"/><br />
| 2,000 || 1,000 || 115 || 2 || 17 || {{No|March 2014}} || USB || {{Yes|code, samples}}<br />
|- <br />
! [[Avalon]] ASIC #1<br />
| 66,300 <ref name="AvalonPowerUsage"/> || 107 || 52.34 || 620<ref name="AvalonPowerUsage"/> || 1299<ref name="avalon"/> || {{No|Discontinued}} || Ethernet, Wifi || {{No|code}}<br />
|-<br />
! [[Avalon]] ASIC #2<br />
| 82,000<ref name="avalon" /> || 117 || 54.70 || 700 || 1499<ref name="avalon" /> || {{No|Discontinued}} || Ethernet, Wifi || {{No|code}}<br />
|-<br />
! [[Avalon]] ASIC #3<br />
| 82,000<ref name="avalon" /> || 117 || 54.70 || 700 || 1499<ref name="avalon" /> || {{No|Discontinued}} || Ethernet, Wifi || {{No|code}}<br />
|-<br />
! [[Avalon2]]<br />
| 300,000 || {{Patch|}} || {{Patch|}} || {{Patch|}} || 3075 || {{Yes}} || USB or Ethernet(Power by OpenWrt) || {{No}}<br />
|-<br />
! [[bi*fury]]<br />
| 5,000 || 1,176 || 24 || 4.25 || 209 || {{Yes}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! [[BitBurner]]<br />
| {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || USB || {{No|code}}<br />
|-<br />
! [[Bitkey]] Valkyrie (4 Modules)<ref name="valk4">[https://www.bitkeylab.com "Bitkey Valkyrie 2.8 TH/s"] Bitkey Valkyrie</ref> <br />
| 2,800,000<ref name="valk4">[https://www.bitkeylab.com "Bitkey Valkyrie 2.8 TH/s"]. Bitkey. Retrieved February 5, 2014.</ref> || 1666 || 466 || 1680 || 5999<ref name="valk4" /> || {{Yes}} || USB, Ethernet || {{Yes|docs, samples}}<br />
|-<br />
! BFL SC 5Gh/s<br />
| 5,000<ref name="jap">[https://products.butterflylabs.com/homepage/5-gh-s-bitcoin-miner.html "BitForce 5 GH/s SC"]. Butterfly Labs. Retrieved November 18, 2013.</ref> || 166 || 18.24 || 30 || 274<ref name="jap" /> || {{No|Discontinued}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! BFL SC 10 Gh/s<br />
| 10,000 <ref name="bf10">[https://products.butterflylabs.com/homepage/10-gh-s-bitcoin-miner.html "BitForce 10 GH/s Miner"]. Butterfly Labs. Retrieved December 24, 2013.</ref> || {{Patch|}} || 27 || {{Patch|}} || 374<ref name="bf10" /> || {{No|Discontinued}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! BFL SC 25 Gh/s<br />
| 25,000 <ref name="bf25">[https://products.butterflylabs.com/homepage/25-gh-s-bitcoin-miner.html "BitForce 25 GH/s Miner"]. Butterfly Labs. Retrieved December 14, 2013.</ref> || 166 || 20.00 || 150 || 1249<ref name="bf25" /> || {{No|Discontinued}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! BFL Little Single<br />
| 30,000<ref name="ls" /> || {{Patch|}} || 46.22 || {{Patch|}} || 649<ref name="ls">[http://www.butterflylabs.com/pre-order-form-bitforce-little-single-sc/ "Pre Order Form – BitForce 'Little' Single SC"]. Butterfly Labs. Retrieved January 30, 2013.</ref> || {{No|Discontinued}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! BFL SC 50 Gh/s<br />
| 50,000 <ref name="bf50">[https://products.butterflylabs.com/homepage/50-gh-s-bitcoin-miner.html "BitForce 50 GH/s Miner"]. Butterfly Labs. Retrieved November 18, 2013.</ref> || 166 || 50 || 300|| 984<ref name="bf50" /> || {{Yes}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! BFL Single 'SC'<br />
| 60,000<ref name="sc">[http://www.butterflylabs.com/order-form-bitforce-sc-single "Pre Order Form – BitForce Single 'SC' "]. Butterfly Labs. Retrieved January 30, 2013.</ref> || 250 || 46.18 || 240 || 1299<ref name="sc" /> || {{No|Discontinued}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! BFL 230 GH/s Rack Mount<br />
| 230,000<ref name="bf250">[https://products.butterflylabs.com/homepage/250-gh-s-rack-mount-bitcoin-miner.html "250 GH/s Rack Mount Bitcoin Miner"]. Butterfly Labs. Retrieved December 14, 2013.</ref> || {{Patch|}} || 54 || {{Patch|}} || 4255<ref name="bf250" /> || {{Yes}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! BFL 500 GH/s Mini Rig SC<br />
| 500,000<ref name="bf500">[https://products.butterflylabs.com/homepage/500-gh-s-bitcoin-miner.html "BitForce 500 GH/s Mini Rig SC"]. Butterfly Labs. Retrieved November 18, 2013.</ref> || 185 || {{Patch|}} || 2700 || 22484 || {{No|Discontinued}} || Wifi || {{Yes|docs, samples}}<br />
|-<br />
! BFL Monarch BPU 300 C <ref name="Monarch300">[https://products.butterflylabs.com/homepage-new-products/300-gh-bitcoin-mining-card.html/ "300 GH Bitcoin Mining Card"]. Butterfly Labs.</ref><br />
| 300,000 || 1714 || 200 || 175 || 1497 || {{Patch|2014}} || PCIe, USB || {{Yes|docs, samples}}<br />
|-<br />
! BFL Monarch BPU 600 C <ref name="Monarch600">[https://products.butterflylabs.com/homepage-new-products/600-gh-bitcoin-mining-card.html/ "600 GH Bitcoin Mining Card"]. Butterfly Labs.</ref><br />
| 600,000 || 1714 || 273 || 350 || 2196 || {{Patch|2014}} || PCIe, USB || {{Yes|docs, samples}}<br />
|-<br />
! BitFury S.B.<br />
| {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || RPi GPIO || {{No}}<br />
|-<br />
! [[Bitmine.ch]] Avalon Clone 85GH<br />
| 85,000 || {{Patch|}} || 13 || 650 || 6489<ref>Depends on user configuration available from http://www.bitmine.ch</ref> || {{Yes}} || Ethernet, Wifi, USB || {{No|code}}<br />
|-<br />
! Black Arrow Prospero X-1<br />
| 64,000 || 1777 || 267<ref name="blackarrowx1">[http://www.blackarrowsoftware.com/store/prospero-x-1.html "Black Arrow Official Website - X1"]. Retrieved September 21, 2013.</ref> || 36 || 239<ref name="blackarrowx1"/> || {{Patch|May 2014}} || Ethernet || {{No}}<br />
|-<br />
! Black Arrow Prospero X-3<br />
| 1,344,000 || 1792 || 336<ref name="blackarrowx3">[http://www.blackarrowsoftware.com/store/prospero-x-3.html "Black Arrow Official Website - X3"]. Retrieved September 21, 2013.</ref> || 750 || 3999<ref name="blackarrowx3"/> || {{Patch|May 2014}} || Ethernet || {{No}}<br />
|-<br />
! Blue Fury<br />
| 2,500 || 1000 || 17.8 || 2.5 || 140 || {{Yes}} || USB || {{Yes|code, samples}}<br />
|-<br />
! Block Erupter Blade<br />
| 10,752 || 129 || 28<ref name="bcprice"/> || 83 || 350<ref name="bcprice"/> || {{No|Discontinued}} || Ethernet || {{Patch|samples}}<br />
|-<br />
! Block Erupter Cube<br />
| 30,000 || 150 || 55 || 200 || 550<ref name="bcprice"/> || {{Yes}} || Ethernet || {{Patch|samples}}<br />
|-<br />
! Block Erupter Emerald<br />
| 336 || {{Patch|}} || {{Patch|}} || {{Patch|}} || Promo || {{No}} || USB || {{Yes|samples}}<br />
|-<br />
! Block Erupter Sapphire<br />
| 333 || 130 || 17<ref name="bcprice"/> || 2.55 || 20<ref name="bcprice">Actual price is in bitcoins. USD value estimated.</ref> || {{No|Discontinued}} || USB || {{Yes|samples}}<br />
|- <br />
! [[CoinTerra]] TerraMiner IV<br />
| 2,000,000<ref name="TerraMiner">[http://cointerra.com/product/terraminer-iv-2ths-networked-asic-miner/ "CoinTerra TerraMiner IV"] </ref> || {{Patch|}} || 333.3 || 2200 || 5999<ref name="TerraMiner" /> || {{Yes}} || Ethernet || {{Yes|docs, code, samples}} <br />
|- <br />
! [[CoinTerra]] GSX I PCIe Card<br />
| 400,000<ref name="GSXI">[http://cointerra.com/product/gsxi/ "CoinTerra GSX I"] </ref> || {{Patch|}} || 250.2 || 450 || 1599<ref name="TerraMiner" /> || {{Patch|June 2014}} || USB || {{No}} <br />
|- <br />
! Drillbit<br />
| {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || USB || {{Yes|code, samples}}<br />
|-<br />
! [[Extolabs]] EX1<br />
| 3,600,000<ref name="EX1">[http://www.extolabs.com "Extolabs EX-1"]. Extolabs. Retrieved April 4, 2014.</ref> || 1895 || 379|| 1900<ref name="EX1"/> || 9499<ref name="EX1"/> || {{Patch|May 2014}} || USB, Ethernet || {{Yes|docs}}<br />
|-<br />
! HashBuster Micro<br />
| 20,000 || 869 || 29 || 23 || 688 || {{No|Discontinued}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! HashBuster Nano<br />
| {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{No|Discontinued}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! [[HashFast]] Baby Jet<br />
| 400,000<ref name="HFBJ1">[https://hashfast.com/shop "Baby Jet"]. HashFast. Retrieved October 4, 2013.</ref> || 1143 || 71|| 350<ref name="HFBJ1"/> || 5600<ref name="HFBJ1"/> || {{Yes}} || Ethernet, USB || {{Yes|docs, samples}}<br />
|-<br />
! [[HashFast]] Sierra<br />
| 1,200,000<ref name="HFSB2">[https://hashfast.com/shop "The Sierra"]. HashFast. Retrieved October 4, 2013.</ref> || 1143 || 169|| 1050<ref name="HFSB2"/> || 7080<ref name="HFSB2"/> || {{Yes}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! [[HashFast]] Sierra Evo 3<br />
| 2,000,000<ref name="HFSE3">[https://hashfast.com/shop "Sierra Evo 3"]. HashFast. Retrieved February 24, 2014.</ref> || 1492 || 294|| 2200<ref name="HFSE3"/> || 6800<ref name="HFSE3"/> || {{Patch|Q2 2014}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! Klondike<br />
| 4,500 || 140 || 47 || 32 || 95 || {{Yes}} || USB || {{Patch|samples}}<br />
|-<br />
! [[KnCMiner]] Mercury<br />
| 100,000 || {{Patch|}} || 50.04 || 250 || 1995 || {{No|Discontinued}} || Ethernet || {{Yes|code, samples}}<br />
|-<br />
! KnC Saturn <ref name="KNCMiner">[https://www.kncminer.com/categories/miners "KNC Mining Hardware"] KNC Miner</ref><br />
| 250,000 || 400|| 66 || 300<ref name="nopsu">Power supply not included</ref> || 2995 || {{No|Discontinued}} || Ethernet || {{Yes|code, samples}}<br />
|-<br />
! KnC Jupiter <ref name="KNCMiner"/><br />
| 500,000 || 400|| 80 || 600<ref name="nopsu"/> || 4995 || {{No|Discontinued}} || Ethernet || {{Yes|code, samples}}<br />
|-<br />
! KnC Neptune <ref name="KnC Neptune">[https://www.kncminer.com/categories/miners "KnC Neptunes 3TH first ever 20nm Chip"] KNC Miner</ref><br />
| 3,000,000 || 1429 || 231 || 2100 || 12995 <ref name="KnC Neptune">[https://www.kncminer.com/products/neptune "Neptune Online Store"] KnC Miner</ref>|| {{Patch|Q1/Q2 2014}} || Ethernet || {{Patch|}}<br />
|-<br />
! LittleFury<br />
| {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{No|Discontinued}} || USB || {{Yes|docs, samples}}<br />
|-<br />
! Metabank<br />
| 120,000 || 705 || 56 || 170 || 2160<ref>Actual costs higher outside Russia</ref> || {{No}} || {{Patch|}} || {{Yes|code, samples}}<br />
|- <br />
! [[Minerscube]] 5 - 5 Th/s <br />
| 5,000,000 || || 1250 || 825 || 4000 || {{Patch|May 2014}} || Ethernet || {{Yes|code, docs, samples}} <br />
|- <br />
! [[Minerscube]] 8.5 - 8.5 Th/s <br />
| 8,500,000 || || 1416 || 1400 || 6000 || {{Patch|May 2014}} || Ethernet || {{Yes|code, docs, samples}} <br />
|- <br />
! [[Minerscube]] 15 - 15 Th/s <br />
| 15,000,000 || || 1666 || 2475 || 9225 || {{Patch|May 2014}} || Ethernet || {{Yes|code, docs, samples}}<br />
|-<br />
! NanoFury / IceFury<br />
| 2,000 || 800 || {{Patch|}} || 2.5 || {{Patch|}} || {{Patch|}} || USB || {{Yes|code, docs, samples}}<br />
|-<br />
! NanoFury NF2<br />
| {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|}} || {{Patch|2014}} || USB || {{Yes|code, docs, samples}}<br />
|-<br />
! Red/BlueFury<br />
| 2,600 || 1040 || 4 || 2.5 || 640 || {{Patch|}} || USB || {{Yes|code, samples}}<br />
|-<br />
! [[TerraHash]] Klondike 16 <ref name="Klondike16">[https://terrahash.com/product/4-5-ghsec-module/ "4.5 GH/sec Modular Board (Klondike 16)"].</ref><br />
| 4,500 || 140 || 18 || 32|| 250 || {{No}} || USB || {{Patch|samples}}<br />
|-<br />
! TerraHash Klondike 64 <ref name="Klondike64">[https://terrahash.com/product/18-ghsec-modular-board/ "18 GH/sec Modular board (Klondike 64)"].</ref><br />
| 18,000 || 140 || 20 || 127 || 900 || {{No}} || USB || {{Patch|samples}}<br />
|-<br />
! TerraHash DX Mini (full)<br />
| 90,000 || 140 || 15 || 640 || 6000 || {{No}} || USB || {{Patch|}}<br />
|-<br />
! TerraHash DX Large (full)<br />
| 180,000 || 140 || 17.14 || 1,280 || 10500 || {{No}} || USB || {{Patch|}}<br />
|-<br />
! Twinfury<br />
| 4,500 || 1174 || 20 || 3.83 || 216 || {{Yes}} || USB || {{Yes|code, samples}}<br />
|- <br />
<br />
|}<br />
<references><br />
<ref name="AntMinerS1">[https://www.bitmaintech.com/productDetail.htm?pid=00020140107162747992Ce5uBuxW06D6 Ant Miner S1 product page] Retrieved 2014-03-11</ref><br />
<ref name="AntMinerU1">[https://www.bitmaintech.com/productDetail.htm?pid=000201401071629535717ycyGoWo06FE Ant Miner U1 Product page] Retrieved 2014-03-11</ref><br />
<ref name="AntMinerU2">[https://www.bitmaintech.com/productDetail.htm?pid=00020140227111546291QgbvQbVr06FB Ant Miner U2+ Product page] Retrieved 2014-03-11</ref><br />
<ref name="AvalonPowerUsage">http://garzikrants.blogspot.com/2013/02/avalon-miner-power-usage.html</ref><br />
<ref name="avalon">[http://avalon-asics.com/ "Avalon ASIC"]. Avalon. Retrieved January 30, 2013.</ref><br />
</references><br />
<br />
== FPGA ==<br />
<br />
{| class="wikitable sortable" style="text-align:center"<br />
|-<br />
! Product !! Hash rate<br />[Mhash/s] !! Efficiency<br />[Mhash/J] !! Efficiency<br />[Mhash/s/$] !! Power<br />[W] !! Price<br />[$]<br />
|-<br />
! Avnet Spartan-6 LX150T Development Kit<br />
| 100<ref>Fpgaminer (May 19, 2011). [https://bitcointalk.org/index.php?topic=9047.0 "Official Open Source FPGA Bitcoin Miner"]. Bitcointalk.org. Retrieved February 7, 2013.</ref> || || 0.10 || || 995<ref>[http://avnetexpress.avnet.com/store/em/EMController?action=products&catalogId=500201&storeId=500201&N=0&langId=-1&slnk=b&term=AES-S6DEV-LX150T-G&hrf=http%3A%2F%2Fwww.em.avnet.com%2Fen-us%2Fdesign%2Fdrc%2FPages%2FXilinx-Spartan-6-FPGA-LX150T-Development-Kit.aspx&intcmp=EMA-BUY-AES-S6DEV-LX150T-G "AES-S6DEV-LX150T-G Parts"]. Avnet Express. Retrieved February 7, 2013.</ref><br />
|-<br />
! Bitcoin Dominator X5000<br />
| 100<ref name="bd" /> || 14.7 || 0.22 || 6.8<ref name="bd" /> || 440<ref name="bd">NewMeat1 (August 18, 2011). [https://bitcointalk.org/index.php?topic=37904.0 "Custom FPGA Board for Sale!"]. Bitcointalk.org. Retrieved January 30, 2013.</ref><br />
|-<br />
! BitForce SHA256 Single<br />
| 832<ref name="single">[http://www.butterflylabs.com/product-details/ "BitForce SHA256 Single – Technical Specifications"]. Butterfly Labs. Retrieved January 30, 2013.</ref> || 10.4 || 1.38 || 80<ref name="single" /> || 599<ref name="single" /><br />
|-<br />
! Butterflylabs Mini Rig<br />
| 25,200<ref name="mini">[http://web.archive.org/web/20120514032732/http://www.butterflylabs.com/products "Products"]. Butterfly Labs. Archived from the original on May 14, 2012. Retrieved February 7, 2013.</ref> || 20.16 || 1.64 || 1,250<ref name="mini" /> || 15,295<ref name="mini2">[http://www.butterflylabs.com/order-form-bitforce-sha256-mini-rig/ "Order Form – BitForce SHA256 – Mini Rig"]. Butterfly Labs. Retrieved January 30, 2013.</ref><br />
|-<br />
! Digilent Nexys 2 500K<br />
| 5<ref>The Seven (June 3, 2011). [https://bitcointalk.org/index.php?topic=9047.msg164438#msg164438 "Re: Official Open Source FPGA Bitcoin Miner (Smaller Devices Now Supported!)"]. Bitcointalk.org. Retrieved February 7, 2013.</ref> || || 0.03 || || 149<ref name="dig">[http://www.digilentinc.com/Products/Detail.cfm?Prod=NEXYS2 "Nexys™2 Spartan-3E FPGA Board"]. Digilent. Retrieved January 30, 2013.</ref><br />
|-<br />
! Icarus<br />
| 380<ref name="ica">Nzghang (November 9, 2011). [https://bitcointalk.org/index.php?topic=51371.0 "FPGA development board 'Icarus' – DisContinued/ important announcement"]. Bitcointalk.org. Retrieved January 30, 2013.</ref> || 19.79 || 0.66 || 19.2<ref name="ica" /> || 569<ref name="ica" /><br />
|-<br />
! KnCMiner Mars<br />
| 6,000 || ??? || 2.15 || ??? || 2,795<br />
|-<br />
! Lancelot<ref name="lan">Nzghang (May 6, 2012). [https://bitcointalk.org/index.php?topic=79835.0 "FPGA development board "Lancelot" - accept bitsteam developer's orders."]. Bitcointalk.org. Retrieved January 30, 2013.</ref><br />
| 400<ref name="lan1">Black Arrow (Jun 11, 2013). [https://www.cardreaderfactory.com/shop/lancelot.html "Lancelot - Heavy Duty Dual Spartan6 Bitcoin Mining Device"]. cardreaderfactory.com. Retrieved Jun 11, 2013.</ref> || || || 26 || 350<ref name="lan1">Black Arrow (Jun 11, 2013). [https://www.cardreaderfactory.com/shop/lancelot.html "Lancelot - Heavy Duty Dual Spartan6 Bitcoin Mining Device"]. cardreaderfactory.com. Retrieved Jun 11, 2013.</ref><br />
|-<br />
! ModMiner Quad <br />
| 800<ref name="mmq">[http://www.btcfpga.com/index.php?route=product/product&product_id=50 "ModMiner Quad"]. BTCFPGA. Retrieved January 30, 2013.</ref> || 20 || 0.75 || 40<ref name="mmq" /> || 1,069<ref name="mmq" /><br />
|-<br />
! Terasic DE2-115<br />
| 80<ref>Fpgaminer (May 4, 2011). [https://bitcointalk.org/index.php?topic=5379.msg105544#msg105544 "Re: FPGA mining"]. Bitcointalk.org. Retrieved February 7, 2013.</ref> || || 0.13 || || 595<ref name="de2">[http://www.terasic.com.tw/cgi-bin/page/archive.pl?No=502 "Altera DE2-115 Development and Education Board"]. Terasic. Retrieved January 30, 2013.</ref><br />
|-<br />
! X6500 FPGA Miner <br />
| 400<ref name="x65" /> || 23.25 || 0.72 || 17.2<ref name="x65" /> || 550<ref name="x65">[http://store.fpgamining.com/ "FPGA Mining Store"]. FPGA Mining. Retrieved January 30, 2013.</ref><br />
|-<br />
! ZTEX USB-FPGA Module 1.15b<br />
| 90<ref name="miner" /> || || 0.27 || || 325<ref>http://shop.ztex.de/product_info.php?cPath=21&products_id=62</ref><br />
|-<br />
! ZTEX USB-FPGA Module 1.15x<br />
| 215<ref name="miner" /> || || 0.52 || || 406<ref>http://shop.ztex.de/product_info.php?cPath=21&products_id=66</ref><br />
|-<br />
! ZTEX USB-FPGA Module 1.15y<br />
| 860<ref name="miner">http://www.ztex.de/btcminer/</ref> || || 0.65 || || 1,304<ref name="1.15y">http://shop.ztex.de/product_info.php?cPath=21&products_id=74</ref><br />
|}<br />
<references/><br />
<br />
==Graphics cards==<br />
Due to the rising hashrate of the bitcoin network caused by the introduction of ASICs to the market, GPU mining Bitcoins has become impracticable. The hashrate of most GPU units is below 1GH/s, and as of 2014, some single ASIC units are able to reach speeds of over 1,000GH/s while consuming far less power than used by a GPU. The information in this table is preserved for historical interest, but does not include many GPUs which were released after the advent of ASIC mining.<br />
<br />
===AMD (ATI)===<br />
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.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! Mhash/s !! Mhash/J !! Mhash/s/$<ref name='amazon_20110625'/> !! Watts !! Clock !! SP !! SDK !! Slot !! Miner !! Notes <br />
|-<br />
| 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<br />
|-<br />
| 3XXX || || || || || || || || || || OpenCL Not Supported<br />
|-<br />
| 42XX || || || || || || || || || || OpenCL Not Supported (integrated/mobile GPU)<br />
|-<br />
| 4350 || 6.93 || 0.346 ||0.16 || 20 || 575 || 80 || - || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors<br />
|-<br />
| 4350 || 7.2 || || || || 600 || || 1.1 || PCI-E 2.0 x16 || cgminer/Linux || default settings<br />
|-<br />
| 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.<br />
|-<br />
| 4350 || 10.7 || -|| - || - || 730 || - || 2.6 || PCI-E 2.0 x16 || CGMiner/Windows7 || -v -w 64 Voltage set at 0.900 core set at 800MHZ and memory set to 200MHZ<br />
|-<br />
| 4550 || 7.23 || 0.289 ||0.13 || 25 || 600 || 80 || - || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors<br />
|-<br />
| 4550 || 7.8 || || || || || || - || PCI-E 2.0 x16 || guiminer /phoenix || worksize=64 VECTORS <br />
|-<br />
| 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<br />
|-<br />
| 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.<br />
|-<br />
| 4650 || 31.33 || 0.653|| 0.44 || 48 || 650 || 320 || - || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors<br />
|-<br />
| 4670 || 36.14 || 0.613|| 0.34 || 59 || 750 || 320 || - || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors<br />
|-<br />
| 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]<br />
|-<br />
| 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<br />
|-<br />
| 4730 || 72.29 || 0.657|| ? || 110 || 750 || 640 || - || PCI-E 2.0 x16 || - || <br />
|-<br />
| 4770 || 72.29 || 0.904|| 0.72 || 80 || 750 || 640 || - || PCI-E 2.0 x16 || - || <br />
|-<br />
| 4830 || 55.42 || 0.583|| || 95 || 575 || 640 || - || PCI-E 2.0 x16 || - || <br />
|-<br />
| 4830 || 61.7 || - || || - || 700 || - || 2.4 || PCI-E 2.0 x16 || poclbm-mod || Fedora 14<br />
|-<br />
| 4830 || 64.9 || - || - || - || 700 || - || 2.4 || PCI-E 2.0 x16 || poclbm-mod || Fedora 14<br />
|-<br />
| 4830 || 66.12 || 0.503|| || 105 || 700 || 1005 || - || PCI-E 2.0 x16 || - ||<br />
|-<br />
| 4850 || 75.30 || 0.685 || || 110 || 625 || 800 || - || PCI-E 2.0 x16 || - || <br />
|-<br />
| 4850 || 84.3 || 0.766 || || 110 || 725 || 300 || - || PCI-E 2.0 x16 || - || -w64 fan at 70% temp 73C, stock voltage -gui miner<br />
|-<br />
| 4850 || 87.4 || 0.79 || - || 110 || 785 || 800 || - || PCI-E 2.0 x16 || guiminer || Phoenix; -k poclbm<br />
|-<br />
| 4850 || 90.1 || 0.819 || || 110 || 800 || 500 || - || PCI-E 2.0 x16 || guiminer || -f 30; Tried phoenix and phatk, got same max<br />
|-<br />
| 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]<br />
|-<br />
| 4850x2 || 150.60 || 0.602 || || 250 || 625 || 1600 || - || PCI-E 2.0 x16 || - || <br />
|-<br />
| 4860 || 67.47 || 0.519|| || 130 || 700 || 640 || - || PCI-E 2.0 x16 || - || <br />
|-<br />
|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]<br />
|-<br />
|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!<br />
|-<br />
|style="background:#F8F8FF;"| 4870 || 90.36 || 0.602|| || 150 || 750 || 800 || 2.1 || PCI-E 2.0 x16 || clmine || <br />
|-<br />
|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)<br />
|-<br />
|style="background:#F8F8F8;"| 4870 || 96 || || || 140 || 750 || 800 || 2.4 || PCI-E 2.0 x16 || Smartcoin r657s / phoenix 1.50 / Linuxcoin 0.2b final || Powercolor @ GPU 830 MHz/ MEM 200 Mhz @ 80% FAN @ 69 temp @ Flags: -k phatk bfi_int=false FASTLOOP=false WORKSIZE=256 AGGRESSION=11 <br />
|-<br />
|style="background:#F8F8F8;"| 4870 || 104 || || || 140 || 750 || 800 || 2.4 || PCI-E 2.0 x16 || Smartcoin r657s / DiabloMiner / Linuxcoin 0.2b final || Powercolor @ GPU 830 MHz/ MEM 200 Mhz @ 80% FAN @ 69 temp @ Flags: -v 1 -w 256 <br />
|-<br />
|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.<br />
|-<br />
|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)<br />
|-<br />
|style="background:#F8F8F8;"| 4870 || 112 || || || 140 || 750 || 800 || 2.4 || PCI-E 2.0 x16 || BAMT 0.5c / cgminer || Powercolor @ GPU 875 MHz/ MEM 300 Mhz/ 1,25VDC @ 100% FAN @ 65 temp @ Flags: -v 1 -w 256 <br />
|-<br />
|style="background:#F8F8FF;"| 4870x2 || 180.6|| 0.632|| || 286 || 800 || 1600 || - || PCI-E 2.0 x16 || - || <br />
|-<br />
|style="background:#F8F8FF;"| 4870x2 || 180.72|| 0.632|| || 286 || 750 || 1600 || - || PCI-E 2.0 x16 || - || <br />
|-<br />
| 4870x2 || 203 || || || || 850(OC) || 1600 || 2.6 || PCI-E 2.0 x16 || poclbm-mod ver. 20 april 2011|| Gainward / Win7 x64 / -w 256 -f 1 / 850MHz GPU - 300MHz Mem - 1,262V - 100% fun : 72C<br />
|-<br />
| 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<br />
|-<br />
| 4890 || 102.41 || 0.539|| || 190 || 850 || 800 || - || PCI-E 2.0 x16 || - || <br />
|-<br />
| 4890 || 108.3 || 0.57|| || 190 || 975 || 800 || - || PCI-E 2.0 x16 || - || <br />
|-<br />
| 4890 || 121.5 || -|| || 190 || 1025 (OC) || 800 || 2.4 || PCI-E 2.0 x16 || poclbm || no flags, Vcore 1.4 <br />
|-<br />
|style="background:#FFF8EF;"| 5450 || 11.99|| 0.631|| || 19 || 650 || 80 || - || PCI-E 2.1 x16 || - || <br />
|-<br />
|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.<br />
|-<br />
|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"<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFF8EF;"| 5450 || 18.10|| || - || - || 774 || - || - || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 1 774.66MHz/300.37MHz<br />
|-<br />
|style="background:#FFF8EF;"| 5470 || 17.10|| || - || - || - || - || - || - || poclbm || -v -w 128 MobileGPU<br />
|-<br />
| 5550 || 40.59 || 1.041|| || 39 || 550 || 320 || - || PCI-E 2.1 x16 || - || <br />
|-<br />
| 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"<br />
|-<br />
|style="background:#FFFFEF;"| 5570 || 59.96 || 1.538|| || 39 || 650 || 400 || - || PCI-E 2.1 x16 || - || <br />
|-<br />
|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<br />
|-<br />
|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]<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFFEF;"| 5570 || 86.3 || 2.397|| || 36 || 775 || 300 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.75 OpenCL/Windows 7 x64 (no Aero) ||-k phatk VECTORS BFI_INT FASTLOOP=false AGGRESSION=11 -v WORKSIZE=256 Fan 100% 86C Undervolted @ 0.96v using Sapphire Trixx<br />
|-<br />
|style="background:#FFFFEF;"| 5570 || 94 || stock || || || 880 || 800 || 2.4 || PCI-E 2.1 x16 || GUI Miner 02-12/Windows 7 x86 || -v -w128 75C<br />
|-<br />
|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)<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
|style="background:#EEFFEE;"| 5670 || 71.49 || 1.117|| || 64 || 775 || 400 || - || PCI-E 2.1 x16 || - || <br />
|-<br />
|style="background:#EEFFEE;"| 5670 || 72 || 1.64|| || 44 || 850 || - || - || PCI-E 2.0 x16 || poclbm-mod (Win7-64) || Sapphire 100287VGAL card is low power<br />
|-<br />
|style="background:#EEFFEE;"| 5670 || 85|| || - || - || 900 || 400 || - || PCI-E 2.1 x16 || poclbm || -v -f 0 -w 128<br />
|-<br />
|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<br />
|-<br />
|style="background:#EEFFEE;"| 5670 || 100|| || - || - || 890 || 400 || - || PCI-E 2.1 x16 || cgminer 1.5.6 || GPU/Mem 890/800 temp 72C<br />
|-<br />
|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<br />
|-<br />
|style="background:#EEFFEE;"| 5670 || 127.8|| || - || - || 850 || - || - || PCI-E 2.1 x16 || Windows 7 (64bit) Phoenix 2.0 || Aggression=11 Worksize=128 Fastloop=False Opencl<br />
|-<br />
| 5750 || 105 || - || - || - || - || - || - || - || poclbm || Apple iMac 27inch (Mid 2010), Mac OSX 10.7 Lion <br />
|-<br />
| 5750 || 116.24 || 1.352|| || 86 || 700 || 720 || - || PCI-E 2.1 x16 || - || <br />
|-<br />
| 5750 || 137 || ||- || - || 710 || 720 || - || PCI-E 1.1 x16 || poclbm || -v -f 0 -w 128 using stock memory and GPU clocks<br />
|-<br />
| 5750 || 146.4 || || - || - || 775 || 720 || - || PCI-E 2.0 x16 || GUIMiner v2011-05-21 || -v -w128, AMD Catalyst overclock (775MHz GPU / 1225 MHz Memory)<br />
|-<br />
| 5750 || 154.56 || 1.45|| || 106 || 830 || 720 || - || PCI-E 2.1 x16 || - || -v -w128 -f20 underclocked memory clocks from 1150MHz to 300MHz<br />
|-<br />
| 5750 || 170 || - || || - || 870 || 720 || - || PCI-E 1.1 x16 || poclbm || -v -f 0 -w 128 patched BIOS to underclock memory to 300MHz<br />
|-<br />
| 5750 || 173 || - || ||- || 875 || 720 || - || PCI-E 1.1 x16 || phoenix || 875/300 w/MSI Afterburner, BFI_INT VECTORS AGGRESSION=12 FASTLOOP=FALSE -k phatk<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 5750 Vapor-X || 195 || - || - || 125 || 975/300 || - || 2.4 || PCI-E 1.1 x16 || cgminer 2.7.5 || (O.S. Ubuntu 12.01 AMD64 dedicated) cgminer options -Q 0 -I 9 -g 2 -w 256 --auto-fan --temp-target 65 --gpu-vddc 1.075 (Fan speed 60~65%)<br />
|-<br />
| 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<br />
|-<br />
|style="background:#FFFFEF;"| 5770 || 156.83 || 1.452|| || 108 || 850 || 800 || 2.1 || PCI-E 2.1 x16 || clmine || <br />
|-<br />
|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<br />
|-<br />
|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])<br />
|-<br />
|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)<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFFEF;"| 5770 || 205.58 || - || ||- || 935 || 300 || 2.1 || PCI-E 2.1 x16 || poclbm 2011-04-28 || -v -w 256<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
|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]<br />
|-<br />
|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)<br />
|-<br />
|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]<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
|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%<br />
|-<br />
|style="background:#FFFFEF;"| 5770 || 244 || -|| || - || 1050 || 300 || 2.1 || PCI-E 2.0 x16 || Phoenix 1.75 /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, Temp 75C, FAN 100% (manual)<br />
|-<br />
|style="background:#FFFFEF;"| 5770x2 || 425 || - || - || 225(+) || 960 || 800x2 || 2.1 || PCI-E 2.1 x16 || poclbm (guiminer) Win7x64 || -v -w128 (OC 960/1200)<br />
|-<br />
|style="background:#FFFDDD;"| 5830M || 120 || -|| || - || 570|| 120 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.50 OpenCL/Win7 x64|| -k phatk DEVICE=0 VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFDDD;"| 5830 || 245 || 1.28|| || 192 || 880 || 900 || 2.4 || PCI-E 2.1 x16 || poclbm (guiminer) || -v -w 256<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFDDD;"| 5830 || 256 || -|| || - || 900 || 300 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 || -k poclbm VECTORS BFI_INT AGGRESSION=7<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFDDD;"| 5830 || 290 || -|| || - || 996 || - || 2.4 || PCI-E 2.1 x16 || phoenix 1.4 / poclbm / Win7 64 || VECTORS AGGRESSION=12 BFI_INT<br />
|-<br />
|style="background:#FFFDDD;"| 5830 || 295 || -|| || - || 980 || 1120 || 2.1 || PCI-E 2.1 x16 || GUIMiner / poclbm / Win XP 32 || Extra flags -v -w 128<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFDDD;"| 5830 || 307 || -|| || - || 996 || - || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / Win7 64 || VECTORS AGGRESSION=12 BFI_INT<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFDDD;"| 5830 || 316 || ||- || - || 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<br />
|-<br />
|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<br />
|-<br />
|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]<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFDDD;"| 5830 (127$) || 325 || 1.98 || 2.57Mh/$ || 165W || 1040MHz || 200MHz || 2.6 || PCI-E 2.0 x8 || Guiminer/phatk-[http://forum.bitcoin.org/index.php?topic=25135.0 mod] w7 64bit || -k phatk AGGRESSION=12 VECTORS2 WORKSIZE=128 stock volt, watercooled 53C<br />
|-<br />
|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;<br />
|-<br />
|style="background:#FFFDDD;"| 5830 || 331 || - || 4.14 || - || 1010 || 1120 || 2.4 || PCI-E 1.0 x16 || WinXP 32 / Phoenix 1.7.5 / phatk2 || Stock Voltage, RAM 300, 64C, Fan 67%, -k phatk2 VECTORS BFI_INT AGGRESSION=11 WORKSIZE=256 FASTLOOP=false (+6Mh w/ Phoenix 1.7.5 over 1.6.2)<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFDDD;"| 5830 || 334 || -|| || - || 1040 || - || 2.5 || PCI-E 2.0 x16 || phoenix 1.75 / phatk 2.2 / Win7 64 || Stock voltage, 208Mhz Memory, VECTORS AGGRESSION=12 WORKSIZE=128 BFI_INT<br />
|-<br />
|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]<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFDDD;"| 5830x2 CF || 480 || -|| || - || 800 || - || 2.4 || PCI-E 2.1 x16 || Guiminer/ - / Win7 64bit |Guiminer || -v -f70 -w128<br />
|-<br />
|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 <br />
|-<br />
|style="background:#FFFDDD;"| 5830x2 || 608 || -|| || - || 990 || - || - || 2x PCI-E 2.0 x16 || phoenix 2.0/ phatk2 / Win7 32bit || Stock voltage, 300Mhz Memory, VECTORS GOFFSET AGGRESSION=12 WORKSIZE=256 BFI_INT FAN 51% 69°C (Open ATX case) <br />
|-<br />
|style="background:#FFFDDD;"| 5830x6 || 1967 || 1.62 || 1.97 || - || 1020/340 || 1120x6 || 2.4 || PCI-E 2.1 x1 || Phoenix 1.7.5/phatk2/BAMT Linux || 100% fan @65C / 1.162V / CCC 11.6 / BFI_INT VECTORS FASTLOOP=false AGGRESSION=11 WORKSIZE=256<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 240.77 || 1.595|| 1.49 || 151 || 725 || 1440 || - || PCI-E 2.1 x16 || - || <br />
|-<br />
|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]<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 252 || 1.575|| || 160 || 765 || 1440 || 2.3 || PCI-E 2.1 x16 || poclbm 2011-01-25 || <br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 255.3 || 1.593|| || 160 || 765 || 1440 || 2.2 || PCI-E 2.1 x16 || poclbm 2011-01-25 || <br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 264 || 1.748|| || 151 || 725 || 1440 || 2.4 || PCI-E 1.0 x8 || guiminer-20110501 || -v -w128<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 280 || 1.75|| || 160 || 765 || 1440 || 2.2 || PCI-E 2.1 x16 || Phoenix 1.3 || with BFI_INT<br />
|-<br />
|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<br />
|-<br />
|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]<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 292 || 1.825|| || 160 || 765 || 1440 || 2.1 || PCI-E 2.1 x16 || poclbm 2011-04-28 -v -f 1 || <br />
|-<br />
|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 || <br />
|-<br />
|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]<br />
|-<br />
|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 || <br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 314 || 1.8362|| || 171 || 820(OC) || 1440 || 2.4 || PCI-E 1.0 x8 || poclbm || -v -w128<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 328 || - || || - || 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 <br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
|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<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 344 || 1.8594|| || 185 || 890(OC) || 1440 || - || PCI-E 2.0 x16 || phoenix || <br />
|-<br />
|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<br />
|-<br />
|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]<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 356 || -|| || - || 870 (OC)|| 1440 || 2.5 || PCI-E 2.0 x16 || cgminer 2.1.2 / Win 7 x64 || 302Mhz Memory clock, 85% fan-speed, Stock Voltage, -I 6 -v 2 -w 256 (2012-02 by Swapper)<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 372 || 1.68 || - || 220 @ Wall || 900 || 300 || 2.5 || PCI-E 1.1 x8 || cgminer 2.3.1 from source / Ubuntu 11.11 x86_64 || -I 8 -v 2 -w 256 --- hex-core opteron cpu w/ 12GB RAM and cgminer CPU bug in linux makes power usage a little high ~210w in windows 7 x86_64<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 382 || 1.8454|| || 207 || 995(OC) || 1440 || - || PCI-E 2.0 x8 || phoenix || OC 1.177v on core<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 391 || - || - || 180 || 725 || 1440 || 2.4 || PCI-E 2.0 x16 || Win 7 Ultimate x64 / DiabloMiner / Catalyst 12.2 || ASUS DirectCU @ GPU 960 MHz / MEM 300 Mhz @ Voltage 1.2 @ 70% FAN @ 69 temp @ Flags: -v 2,1 -w 256<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
|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 <br />
|-<br />
|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 <br />
|-<br />
|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<br />
|-<br />
|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/<br />
|-<br />
|style="background:#EFEFFF;"| 5850 || 432.15 || -|| || - || 1040 || 500 || 2.5.793.1 || PCI-E 2.0 16x || phoenix 1.7.5 / phatk2 kernel / Win7 x64 SP1 || fan 100%, vcore 1.212 V, 69C, VECTORS4 BFI_INT AGGRESSION=13 FASTLOOP=false WORKSIZE=64 -k phatk2, proof: http://dl.dropbox.com/u/18704286/mining%205850.png/ ... Card is REF HIS 5850 ... i mining at this speed for stable but... max unstable (if i play video/flashvideo it will crash) is 436.48Mhash/sec with core 1051 mem 500 vcore 1.237 (same other settings) it's too hot in VRM that not sound good to me... i don't want to kill it for my fun mining ... - Nito Niwatori <br />
|-<br />
|style="background:#EFEFFF;"| 5850x2 || 620 || - || || - || 800 || 1440 || 2.4 || PCI-E 2.0 x16 || Guiminer ( cl miner ) v2012-02-19 Win7 x64 || MSI OC-Edition, -v -w 128 <br />
|-<br />
|style="background:#EFEFFF;"| 5850x2 || 702 || - || - || - || 905 (OC)|| 1440 || 2.5 || PCI-E 2.0 x16 (x2) || phoenix 2.0.0 / Win 7 x32 || ASUS DirectCU: 304Mhz Memory clock, 66% fan-speed, Voltage Tweak, AGGRESSION=13 FASTLOOP=false WORKSIZE=256 (https://www.dropbox.com/s/9u6f2jz3sz1poxb/5850.jpg)<br />
|-<br />
|style="background:#EFEFFF;"| 5850x2 || 720 || -|| || - || 875 (OC)|| 1440 || 2.5 || PCI-E 2.0 x16 || cgminer 2.1.2 / Win 7 x64 || 302Mhz Memory clock, 85% fan-speed, Stock Voltage, -I 6 -v 2 -w 256 (2012-02 by Swapper)<br />
|-<br />
|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 <br />
|-<br />
|style="background:#EFEFFF;"| 5850x4 || 1360 || 1.94|| || 700@wall || 900 || || || || poclbm|| <br />
|-<br />
|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 <br />
|-<br />
|style="background:#EFFFEF;"| 5870M || 152.5 || -|| || - || 750(OC) || 1000 || 2.1 || PCI-E 2.1 x16 || gui-miner (win-7) ||<br />
|-<br />
|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<br />
|-<br />
|style="background:#EFFFEF;"| 5870 || 313 || 1.665|| || 188 || 900? || 1600 || 2.3 || PCI-E 2.1 x16 || Diablo/Linux || <br />
|-<br />
|style="background:#EFFFEF;"| 5870 || 313.65 || 1.668||1.65 || 188 || 850 || 1600 || 2.1 || PCI-E 2.1 x16 || clmine || <br />
|-<br />
|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]<br />
|-<br />
|style="background:#EFFFEF;"| 5870 || 343 || 1.824|| || 188 || 900? || 1600 || 2.1 || PCI-E 2.1 x16 || Diablo/Linux || <br />
|-<br />
|style="background:#EFFFEF;"| 5870 || 355 || 1.888|| || 188 || 900? || 1600 || 2.1 || PCI-E 2.1 x16 || poclbm/Linux || <br />
|-<br />
|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]<br />
|-<br />
|style="background:#EFFFEF;"| 5870 || 379 || 2.015|| || 188 || 850 || 1600 || - || PCI-E 2.0 x16 || hashkill-0.2.5 alpha || -D -G2<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#EFFFEF;"| 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 <br />
|-<br />
|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<br />
|-<br />
|style="background:#EFFFEF;"| 5870 || 440 || 2.0000|| || 220 || 995 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix || <br />
|-<br />
|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)<br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#EFFFEF;"| 5870 || 461 || || || || 1000 || 1600 || 2.5 || PCI-E 2.0 x16 || phoenix 1.75/Windows 7 64 || -k phatk2 (phatk 2.2) VECTORS BFI_INT AGGRESSION=9 WORKSIZE=128, Memory Clock=213, stock voltage<br />
|-<br />
|style="background:#EFFFEF;"| 5870 || 481 || || || || 1050 || 1600 || 2.5 || PCI-E 1x || phoenix 1.75/Windows 7 64 || -k phatk2 (phatk 2.2) VECTORS BFI_INT WORKSIZE=64 AGGRESSION=20 [MSI HD 5870 Ref Design vs Zalman VF3000A 1200mv Mem 600MHz]<br />
|-<br />
|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)<br />
|-<br />
|style="background:#EFFFEF;"| 5870x2 (Ares) || 620 || -|| || - || 850 || 3200 || 2.1 || PCI-E 2.1 x16 || guiminer || -v -w 128<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#EFFFEF;"| 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 <br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFEFEF;"| 5970 || 535.06 || 1.820|| || 294 || 725 || 3200 || 2.1 || PCI-E 2.1 x16 || clmine || <br />
|-<br />
|style="background:#FFEFEF;"| 5970 || 560 || 1.905|| || 294 || 725 || 3200 || - || PCI-E 2.1 x16 || Diablo || <br />
|-<br />
|style="background:#FFEFEF;"| 5970 || 565 || 1.922|| || 294 || 725 || 3200 || 2.1 || PCI-E 2.1 x16 || clmine2 || <br />
|-<br />
|style="background:#FFEFEF;"| 5970 || 604 || 2.054|| || 294 || 725 || 3200 || 2.1 || PCI-E 2.1 x16 || clmine || <br />
|-<br />
|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<br />
|-<br />
|style="background:#FFEFEF;"| 5970 || 739 || || || || 795 || 3200 || 2.4 || PCI-E 2.1 x16 || cgminer 2.3.1 || -I 9 -k phatk -w 256 -v 2, memory clock @ 265MHz, Debian Squeeze, fglrx-driver 12.1.1, performance scales linearly with engine clock as long as memory clock is 1/3<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 6450 || 32.6 || 1.918 || - || 17 || 725 || 800 || 2.4 || PCI-E 2.0 x16 || guiminer/Phoenix1.75 Windows 7 x64 (no Aero)|| -k phatk VECTORS BFI_INT FASTLOOP=false AGGRESSION=11 -v WORKSIZE=64 Dell OEM HD6450 1gb ddr3 passive cooling/no fan 81C<br />
|-<br />
| 6450 || 37.8 || ? || - || 17 || 850 || 800 || 2.4 || PCI-E 2.0 x16 || Phoenix2.0.0 Windows 8 x64 || -k phatk2 VECTORS BFI_INT FASTLOOP=false AGGRESSION=11 -v WORKSIZE=64 Sapphire HD6450 1GB DDR3 passive cooling/no fan 150MHz memory/1000mV VCore<br />
|-<br />
| 6470M || 24.1 || - || ||- || - || - || 2.1 || Integrated/APU || guiminer || <br />
|-<br />
| 6470M || 31.0 || - || ||- || - || - || 2.1 || Integrated/APU || phoenix 1.48 || <br />
|-<br />
| 6480G || 24.1 || - || ||- || - || - || 2.1 || Integrated/APU || phoenix 1.75 || <br />
|-<br />
| 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<br />
|-<br />
| 6490M || 16.289 || 0.708|| || 23 || - || - || - || PCI-E 2.1 x16 || poclbm-mod (Mac OS X 10.6.7) || MacBook Pro early 2011<br />
|-<br />
| 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<br />
|-<br />
| 6490M || 32.1 || - || ||- || - || - || - || - || guiminer 2011-07-01 with poclbm (Win7-x64) ||MacBookPro8,2 (WinX64) -v -w128 -f0<br />
|-<br />
| style="background:#FFDD00;"| 6520G || 33.8 || - || || - || 400 || 320 || - || Integrated/APU || guiminer 2011-07-01 with OpenCL (Win7-64bit) || -v -w128 on Toshiba L775D-S7222<br />
|-<br />
|style="background:#FFDD00;"| 6530D || 40.5 || - || || - || 444 || 320 || 2.4 || FM-1 || cgminer 2.4.1 || Integrated/APU A6-3500; Linux; Catalyst 11.11; APP-SDK-v2.4 (595.10)<br />
|-<br />
|style="background:#FFDD00;"| 6550D(A8 Onboard) || 66.2 || -|| || - || - || - || 2.5 || FM-1 || guiminer 2011-07-01 with OpenCL (Win7-64bit) || -v -w128 -f60<br />
|-<br />
|style="background:#FFDD00;"| 6550D || 67.6 || -|| || - || 600 || 400 || 2.5 || FM-1 || guiminer 2011-07-01 with OpenCL (Win7-64bit) || -v -w128 -f2<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFDD00;"| 6570 || 112.0 || - || || - || 860 || 480 || 2.7 || PCI-E 2.0 x16 || guiminer 2012-02-19/poclbm (Win7-64bit) || -v -w128 -f1 . Sapphire 6570 Low Profile gddr3 1024mb<br />
|-<br />
|style="background:#FFDD00;"| 6570 || 114.0 || - || || - || 866 || 480 || 2.7 || PCI-E 2.0 x16 || guiminer 2012-02-19/poclbm (Win7-64bit) || -v -f 0 -w128 -a 3 . XFX 6570 Full Profile gddr3 1024mb 64 bit<br />
|-<br />
| 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<br />
|-<br />
| 6630M || 63.00 || -|| || - || 600 || 480 || 2.5 || PCI-E 2.0 x16 || DiabloMiner Windows || Lenovo ThinkPad Edge E320 (card overclocked using Sapphire TRIXX)<br />
|-<br />
| 6670 || 102.20 || -|| || - || 800 || - || - || PCI-E 2.1 x16 || poclbm/Debian sid || -v -f 0 -w 128<br />
|-<br />
| 6670 || 104.00 || - || 1.0 || - || 820 || - || - || PCI-E 2.1 x16 || guiminer(poclbm)/Win 7|| -v -a4 -f15 -d0 -w64<br />
|-<br />
| 6670 || 110.00 || - || 1.0 || - || 850 || - || - || PCI-E 2.1 x16 || guiminer(poclbm)/Win 7|| -v -f 0 -w 128 -q 6<br />
|-<br />
| 6670 || 111.77 || 1.69 || - || 66 || 910 || 480 || 2.7 || PCI-E 2.1 x16 || Phoenix 1.7.5 || -k phatk2 BFI_INT AGGRESSION=5 VECTORS WORKSIZE=128<br />
|-<br />
| 6670 || 120.1 || - || - || - || 900 || 480 || 2.7 || PCI-E 2.1 x16 || cgminer 2.7.4 || kernel: diablo i:10 core: 900 mem: 750<br />
|-<br />
| 6670 || 124.0 || - || - || 66 || 940 || 800 || 2.4 || PCI-E 2.0 x16 || Phoenix2.0.0 Windows 8 x64 || -k phatk2 VECTORS BFI_INT FASTLOOP=false AGGRESSION=11 -v WORKSIZE=128 Sapphire HD6670 Ultimate 1GB DDR5 passive cooling/no fan 300MHz memory/1100mV VCore<br />
|-<br />
| 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)<br />
|-<br />
| 6750 || 167.59 || -|| || - || 870 || - || - || PCI-E 2.1 x16 || guiminer || -v -f30 -w128<br />
|-<br />
| 6750 || 172.00 || -|| || - || 860 || 600 || - || PCI-E 2.1 x16 || guiminer 2012-02-19/poclbm (Win7-64bit) MSI Afterburner 2.2.3 || -v -w128 f-20 Sapphire 6570 GDDR3 1024Mb CCC ver. 11.12 OCL 2.5<br />
|-<br />
| 6750M || 41.48 || -|| || - || 870 || - || - || PCI-E 2.1 x16 || diablominer ||<br />
|-<br />
| 6750M || 60 || -|| || - || - || - || - || - || diablominer OSX 10.7 WorkSize=128||<br />
|-<br />
| 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<br />
|-<br />
| 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)<br />
|-<br />
| 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<br />
|-<br />
| 6770 || 221 || -|| || - || 1010 || 300 || 2.4 || PCI-E 2.0 x8 || Phoenix 1.50 || MSI 6770 -k phatk PLATFORM=0 DEVICE=0 VECTORS BFI_INT WORKSIZE=256 FASTLOOP=false AGGRESSION=13 3% Stock voltage.<br />
|-<br />
| 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.<br />
|-<br />
| 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.<br />
|-<br />
| 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<br />
|-<br />
| 6790 || 219 || 1.467|| || 150 || 960 || - || - || PCI-E 2.1 x16 || guiminer || -v -f0 -w128 / GPU OC to 960MHz under Windows7 64bit<br />
|-<br />
|style="background:#EFEFFF;"| 6850 || 171.59 || 1.351||1.07 || 127 || 775 || 960 || 2.1 || PCI-E 2.1 x16 || clmine || <br />
|-<br />
|style="background:#EFEFFF;"| 6850 || 196 || -|| || - || 850 || 960 || - || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 0<br />
|-<br />
|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] )<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#EFEFFF;"| 6850 || 244.2 || ||- || - || 960 || 960 || 2.1 || PCI-E 2.0 x16 || poclbm june-2011 || -v -w 128<br />
|-<br />
|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 <br />
|-<br />
|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])<br />
|-<br />
|style="background:#EFEFFF;"| 6850 || 256.2 || || - || 170 || 980 || 960 || 2.7 || PCI-E 2.0 x16 || phoenix 1.7.5 / Win7 32bit || -k phatk -VECTORS BFI_INT AGGRESSION=9, Sapphire VaporX 1GB, mem@250MHz, stock VDDC 1.150V <br />
|-<br />
|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)<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFF00;"| 6870 || 232.47 || 1.540||1.22 || 151 || 900 || 1120 || - || PCI-E 2.1 x16 || poclbm -v -w 128 || <br />
|-<br />
|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<br />
|-<br />
|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 <br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFF00;"| 6870 || 277.47 || -|| || - || 940 || 1120 || - || PCI-E 2.1 x16 || Phoenix 1.3 || AGGRESSION=8 WORKSIZE=128 VECTORS BFI_INT<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFF00;"| 6870 || 294 || || ||- || 985 || 1100|| 2.4 || PCI-E 2.0 x8 || Diablo || Powercolor branded card, Win 8 x64, -v 1 -w 256<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFF00;"| 6870 || 307 || 1.72 || - || 174 || 1001/\1001 || 1120 || 2.4 || PCI-E 2.1 x16 || poclbm windows7x86 cat11.8 || -v -w128 -f5,85°C<br />
|-<br />
|style="background:#FFFF00;"| 6870 || 310 || - || - || - || 1000 || 1120 || || PCI-E 2.1 x16 || cgminer 3.1.0 (Ubuntu Server 12.04 LTS AMD64) || intensity=13, vectors=2, worksize=128, kernel=diablo, gpu-engine=1000, gpu-memclock=900<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFF00;"| 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.<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFF00;"| 6870 || 320 || - || - || 160 || 950 || 1120 || 2.4 || PCI-E 2.0 x16 || Win 7 Ultimate x64 / DiabloMiner / Catalyst 12.1 || Saphire @ GPU 1030 MHz / MEM 300 Mhz @ Voltage 1.25 @ 80% FAN @ 69 temp @ Flags: -v 2 -w 128<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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.<br />
|-<br />
|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<br />
|-<br />
|style="background:#FFFF00;"| 6870 || 375 || - || - || - || 1000 || 1120 || 2.5 || PCI-E 2.0 x16 || Win 7 Ultimate 32-bit / Guiminer v2011-07-01 / phoenix 1.5 / phatk2 / Catalyst 11.9 || XFX / GPU @ 1000 MHz / MEM @ 200 Mhz / Voltage @ 1.187 V / FAN @ 40% / Temp @ 72 C / Flags: -k phatk2 platform=0 device=0 VECTORS BFI_INT AGGRESSION=6 worksize=128 FASTLOOP=false / Using 2 miners with equal settings on 1 GPU<br />
|-<br />
|style="background:#FFFF00;"| 6870x2 || 600 || - || - || - || 945 || 330 || 2.5 || PCI-E 2.0 x16 || Ubuntu 12.04 32-bit / Phoenix 2 / phatk2 / Catalyst 11.9 || XFX / GPU @ 945 MHz / MEM @ 330 Mhz / Voltage @ 1.175 / Config: phatk2 VECTORS4 BFI_INT AGGRESSION=12 worksize=128 FASTLOOP=false GOFFSET=True<br />
|-<br />
|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<br />
|-<br />
|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).<br />
|-<br />
|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.<br />
|-<br />
| 6930 || 320|| -|| - || - || 960 || 1200 || 2.1 || PCI-E 2.1 x16 || phoenix 1.75/phatk || stock voltage, BFI_INT FASTLOOP VECTORS AGGRESSION=13 WORKSIZE=64. 70C, FAN 80% (HIS brand)<br />
|-<br />
| 6930 || 370|| -|| - || - || 980 || 855 || 2.4 || PCI-E 2.1 x16 || cgminer-2.4.1 || stock voltage (1,160), -I9. 71C, FAN 85% (HIS brand)<br />
|-<br />
| 6930 || 372 || -||1.89(?) || - || 1000 || 900 || 2.4 || PCI-E 2.1 x16 || phoenix 1.75/poclbm || max stable @ 1200 mV, BFI_INT FASTLOOP VECTORS AGGRESSION=13 WORKSIZE=64<br />
|-<br />
| style="background:#00FFFF;"|6930x2|| 700 ||- || - ||400~|| 940 || 2560 || 2.4 || PCI-E 2.1 x16 || Guiminer || max stable @ 1100mV mem 300, Fan 80-90%, temp 70-75, -v -w64 -f10<br />
|-<br />
| 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<br />
|-<br />
| 6950 || 291 || -|| || - || 920 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1200mV, AGGRESSION = 7, BFI_INT, MSI 6950<br />
|-<br />
| 6950 || 295 || -|| || - || 930 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1275mV, AGGRESSION = 7, BFI_INT, MSI 6950<br />
|-<br />
| 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<br />
|-<br />
| 6950 || 300 || -|| || - || 940 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1300mV, AGGRESSION = 7, BFI_INT, MSI 6950<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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)<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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.<br />
|-<br />
| 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<br />
|-<br />
| 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)<br />
|-<br />
| 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.<br />
|-<br />
| 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<br />
|-<br />
| 6950 || 360 || -|| || - || 870 || 1375 || - || PCI-E 2.1 x16 || guiminer/poclbm || flashed with 6970 BIOS, -v -f30 -w128<br />
|-<br />
| 6950 || 365 || -|| || - || 925 || 1408 || - || PCI-E 2.1 x16 || guiminer/poclbm || stock bios, -v -f0 -w128, MSI twinfrozr III 2GB<br />
|-<br />
| 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.<br />
|-<br />
| 6950 || 381 || -|| || - || 850 || 1536 || - || PCI-E 2.1 x16 || cgminer/phatk || XFX 6950 2Gb reference @ shadermod on original Bios 6950 / 1100mV 850/1250, +10% powertune, I=5, Fan @ 54% ~3100RPM, temp 73C w128. Windows7x64, Catalyst 13.1 .<br />
|-<br />
| 6950 || 383 || -|| || - || 975 || 1408 || - || PCI-E 2.1 x16 || guiminer/poclbm || stock bios, -v -f0 -w128, voltage 1.274 @72c MSI twinfrozr III 2GB<br />
|-<br />
| 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.<br />
|- <br />
| 6950 || 389.9 || -|| || - || 950 || 1408 || - || PCI-E 2.0 x16 || cgminer 2.3.2/Diablo || stock bios, -I 9, VRAM @ 820Mhz, fan @ 100%, voltage 1.250v, temp @ 68c, HIS ICE-Q X 2GB, OCed using MSI Afterburner, Windows 7 Professional 64-bit SP 1<br />
|-<br />
| 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.<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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.<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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.<br />
|-<br />
| 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<br />
|-<br />
| 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.<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
|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.<br />
|-<br />
|style="background:#F0FF0F;"| 6970 || 365 || 2.28|| || 160 || 880 || 1536 || 2.5 || PCI-E 2.1 x16 || guiminer/phoenix || VECTORS AGGRESSION=9 WORKSIZE=128, fan @ 45%, 61C, 1.0 Vcore, 150 MHz mem, TX650w (84%), reference card<br />
|-<br />
|style="background:#F0FF0F;"| 6970 || 370 || -|| || - || 880 || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm || -v -w128, fan @ 50%/temp 72C, stock card<br />
|-<br />
|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<br />
|-<br />
|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%<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
|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)<br />
|-<br />
|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<br />
|-<br />
|style="background:#F0FF0F;"| 6970 || 407 || -|| || - || 955 || 1536 || 2.4 || PCI-E 2.1 x16 || poclbm || -v -w128, fan 75%/temp 75C, voltage +10%<br />
|-<br />
|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<br />
|-<br />
|style="background:#F0FF0F;"| 6970 || 420 || -|| || - || 975 || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm || -v -w128 -f0, clocks 975MHz/685MHz MSI Lightning<br />
|-<br />
|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<br />
|-<br />
|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], <br />
|-<br />
|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<br />
|-<br />
|style="background:#F0FF0F;"| 6970x2 || 710 || -|| || - || 900/880 || 1536 || 2.2 || PCI-E 2.1 x16 || poclbm || -w 256<br />
|-<br />
|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<br />
|-<br />
|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<br />
|-<br />
| 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].<br />
|-<br />
| 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)<br />
|-<br />
| 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]<br />
|-<br />
| 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)<br />
|-<br />
| 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]<br />
|-<br />
| 6990 || 758 || -|| || - || 880 || - || 2.4 || - || Phoenix with Poclbm || Catalyst 11.4, OC switch ON, VECTORS AGGRESSION=12 BFI_INT WORKSIZE=128 FASTLOOP=false<br />
|-<br />
| 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.<br />
|-<br />
| 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<br />
|-<br />
| 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]<br />
|-<br />
| 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.<br />
Diablo's args: -w 128 -g 5 -v 2 -f 0<br />
|-<br />
| 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]<br />
|-<br />
| 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<br />
|-<br />
| 6990 || 852 || -|| || - || 955|| 3072 || 2.5 || PCI-E 2.1 x16 || cgminer 2.1.2 || Memory: 830 Mhz, -v 2 -w 128 -I 9, Watercooled, stock voltage. (2012-02 by Swapper)<br />
|-<br />
| 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.<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 6990x3 || 2094 || -|| || - || 900 || - || 2.4 || PCI-E 2.0 x16 x8 x4 || poclbm || GPU 900MHz, Memory 1250MHz; poclbm.py -f 0 -w 256<br />
|-<br />
| 7750 || 104.15 || || || || 800 || || - || PCI-E 2.0 x16 || phoenix || worksize=128 VECTORS FASTLOOP AGGRESSION=10 WORKSIZE=128<br />
|-<br />
| 7750 || 117.15 || || || || 900 || || - || PCI-E 2.0 x16 || phoenix || worksize=128 VECTORS FASTLOOP AGGRESSION=10 WORKSIZE=128<br />
|-<br />
| 7750 || 125.5 || - || - || - || 830 || 512 || 2.6 (10.0.898.1) || PCI-E 2.0 x8 || DiabloMiner || GPU: 830MHz, Memory: 1125MHz; -v 1 -w 256 [https://bitcointalk.org/index.php?topic=64241.msg816946#msg816946 source]<br />
|-<br />
| 7750 || 134 || 2.66 || 1.21 || 50 || 880 || 512 || 2.6 (?) || PCI-E 2.0 x16 || cgminer 3.1.0 (Gentoo Linux AMD64) || factory-overclocked to 880 MHz; power draw measured with a Kill-a-Watt, intensity=13, vectors=1, worksize=128, kernel=diablo<br />
|-<br />
| 7750 || 136.1 || - || - || - || 900 || 512 || 2.6 (10.0.898.1) || PCI-E 2.0 x8 || DiabloMiner || GPU: 900MHz (CCC locked @ 900), Memory: 800MHz; -v 1 -w 256 [https://bitcointalk.org/index.php?topic=64241.msg816946#msg816946 source]<br />
|-<br />
| 7750 || 140 || - || - || - || 950 || 512 || - || PCI-E 3.0 x16 || bfgminer 3.0.0 || Memory: 900MHz; -I 5 -g 2 -k diablo<br />
|-<br />
| 7770 || 182 || - || - || 83 || 1020 || 640 || 2.6 || PCI-E 2.0 x16 || poclbm || Ubuntu 10.04 LTS amd64, GPU: 1020MHz<br />
|-<br />
| 7770 || 213 || - || - || - || 1150 || 640 || - || PCI-E 2.0 x16 || poclbm || Win7 32bit, Core2Duo, poclbm guiminer<br />
|-<br />
| 7790 || 313 || - || - || - || 1200 || 896|| - || PCI-E 2.0 x16 || poclbm || Saphire Radeon HD 7790 OC (2 fans & heatpipes) GPU 20% OC @ 1200mhz / TEMP 57C / FAN 36%, Win8 64bit, cgminer, "intensity" : "10", "vectors" : "1", "worksize" : "256", "kernel" : "poclbm", "thread-concurrency" : "8192",<br />
|-<br />
| 7790 || 325 || - || - || - || 1300 || 896 || - || PCI-E 2.0 x16 || poclbm || MSI Radeon HD 7790 GPU @ 1300mhz/ MEM @ 750mhz/ FAN @ 83 / TEMP 67C Win7 64bit, athlon x2, poclbm guiminer , -v -w 128 -f 1<br />
|-<br />
| 7850 || 287 || 1,91 || 1,1 || 150 || 950 || 1024 || 2.6 || PCI-E 2.0 x16 || cgminer || GPU:950 MEM:800, Linux 64bit, Intensive 14, GPU temp = 60°C, Room temp = 25°C, Fan = 60%<br />
|-<br />
| 7850 || 329 || - || - || 150 || 1100 || 1024 || 2.6 || PCI-E 2.0 x16 || cgminer 2.6.4 || Linux 64bit GTK+3, GPU temp = 60°C, Room temp = 25°C, Fan = 60%, -v 1 -k poclbm -I 6 --gpu-engine 1100 --gpu-memclock 950<br />
|-<br />
| 7850 || 363 || - || - || - || 1241 || 1024 || 2.6 || PCI-E 2.0 x16 || Guiminer || GPU:1241 MEM:4840 <br />
|-<br />
| 7870 || 405 || - || - || - || 1100 || 1280 || 2.6 || PCI-E 2.0 x16 || Guiminer || Sapphire 7870 OC , GPU: 1100MHz, Mem: 950 Mhz, GPU temp: 65°C, Fan 36% (1377 RPM).<br />
|-<br />
| 7870 || 406 || - || - || - || 1100 || 1280 || 2.6 || PCI-E 2.0 x16 || cgminer || Gigabyte GV-R787OC-2GD, GPU: 1200MHz, [cgminer -I 7]<br />
|-<br />
| 7870 || 422 || - || - || - || 1165 || 1280 || 2.6 || PCI-E 2.0 x16 || cgminer || Sapphire 7870 1ghz edition, GPU: 1165MHz, [cgminer.exe -d 0 -l 1 -T -I 8]<br />
|-<br />
| 7870 || 460 || - || - || - || 1250 || 1280 || 2.7? || PCI-E 2.0 x16 || Guiminer || MSI R7870 TFIII/oc, Catalyst 12.11 beta4, 455-460 mhash/s @1250 core, 750 mem, 0% Power limit, 1.218v, Zalman VF3000N = 42C, VRMS = 57C, ambient approx. 17-19C, -v -w128 -f10<br />
|-<br />
| 7870 XT || 485 || 3.09 || 1.8726 || 157 || 1200 || 1280 || 2.8 || PCI-E 3.0 x16 2.0 || cgminer ||7870XT clock/mem - 1200/1600<br />
|-<br />
| 7870xt || 520 || - || - || - || 1200 || 1536 || 2.7? lol || PCI-E 2.0 x4 || Guiminer || Sapphire HD7870xt, Catalyst 12.11 beta 4, 515-520 mhash/s @1200/core 750/mem, 0%PL, 1.17v/stock, Zalman vf3000a @60-62C even though its sandwiched between a 7870 and 5850. xD<br />
|- <br />
|style="background:#00FFFF;"| 7950 || 510 || - || - || - || 985 || 1792 || 2.6 || PCI-E 3.0 x16 || Diablo || Windows 8 x64, Asus P8Z77 WS, i7 3rd Gen, Card is XFX brand, Clock 985Mhz, Mem 1100Mhz, -v 1 -w 256<br />
|- <br />
|style="background:#00FFFF;"| 7950 || 512 || - || - || - || 1000 || 1792 || 2.6 || PCI-E 3.0 x8 || poclbm || GPU: 1000MHz, Memory: 850MHz<br />
|-<br />
|style="background:#00FFFF;"| 7950 || 550 || - || - || - || 1060 || 1792 || 2.8 || PCI-E 3.0 x16 || Diablo || Core 1060, Mem 800, -v 1 -w 256 Intesity 7<br />
|-<br />
|style="background:#00FFFF;"| 7950 || 605 || - || - || - || 1150 || 1792 || 2.6 (10.0.898.1) || PCI-E 3.0 x16 || DiabloMiner || GPU: 1150MHz, Memory: 1375MHz; -v 1 -w 256<br />
<br />
|-<br />
|style="background:#FF0000;"| 7970 || 555 || - || - || - || 925 || 2048 || 2.6 (10.0.898.1) || PCI-E 2.0 x16 || DiabloMiner || GPU: 925MHz, Memory: 1375MHz; -v 1 -w 256<br />
|-<br />
|style="background:#FF0000;"| 7970 || 640 || -|| || - || 1070 core/1000 mem || 2048 || 2.6 || PCI-E 3.0 x16 || cgminer 2.6.5 || MSI R7970 Lightning Win7 х64, Catalyst 12.8, GPU 1070 MHz, Memory 1000 MHz, GPU temp = 72°C, Room temp = 28°C, Fan = 57%, cgminer -k diablo -v 1 -w 256<br />
|-<br />
|style="background:#FF0000;"| 7970 || 650 || -|| || - || 1100 || 2048 || 2.4 || PCI-E 2.0 x16 x8 x4 || Diablo|| GPU 1100MHz, Memory 600MHz;<br />
|-<br />
|style="background:#FF0000;"| 7970 || 650 || -|| || - || 1100 || 2048 || 2.6 || PCI-E 2.0 x1 || cgminer 2.4.1 || Win7 х86, Catalyst 12.3, GPU 1100 MHz, Memory 950 MHz, GPU temp = 68°C, Room temp = 25°C, Fan = 58%, -k poclbm -v 1 -w 128<br />
|-<br />
|style="background:#FF0000;"| 7970 || 674 || -|| || - || 1130 core/1000 mem || 2048 || 2.6 || PCI-E 3.0 x16 || cgminer 2.6.5 || MSI R7970 Lightning Win7 х64, Catalyst 12.8, GPU 1130 MHz, Memory 1000 MHz, GPU temp = 72°C, Room temp = 28°C, Fan = 57%, cgminer -k diablo -v 1 -w 256<br />
|-<br />
|style="background:#FF0000;"| 7970 || 685 || -|| || - || 1150 core/1000 mem || 2048 || 2.6 || PCI-E 3.0 x16 || cgminer 2.6.5 || MSI R7970 Lightning Win7 х64, Catalyst 12.8, GPU 1150 MHz, Memory 1000 MHz, GPU temp = 72°C, Room temp = 28°C, Fan = 58%, cgminer -k diablo -v 1 -w 256<br />
|-<br />
|style="background:#FF0000;"| 7970 || 685 || -|| || - || 1177 || 2048 || 2.6 || PCI-E 2.0 x16 || cgminer 2.3.1 || Win7, Catalyst 12.3, driver: 2.95, E: 1177, M:685, -k diakgcn -v 2 -w 256<br />
|-<br />
|style="background:#FF0000;"| 7970 || 690 || - || - || - || 1150 || 2048 || 2.6 (10.0.898.1) || PCI-E 2.0 x16 || DiabloMiner || GPU: 1150MHz, Memory: 1375MHz; -v 1 -w 256<br />
|-<br />
|style="background:#FF0000;"| 7970 || 695 || - || - || - || 1160(core)/1050(mem) || 2048 || 2.6 || PCI-E 2.0 x16 || DiabloMiner (options: -v 1 -w 256) || Asus HD7970-DC2T-3GD5 @ 1.17V; Linux Ubuntu 11.10 64 bit; AMD SDK 2.6; Catalyst 12.3 <br />
|-<br />
|style="background:#FF0000;"| 7970 || 710 || -|| || - || 1200 || 2048 || 2.4 || PCI-E 2.0 x16 || DiabloMiner|| GPU 1200MHz, Memory 600MHz; -v 1 -w 256<br />
|-<br />
|style="background:#FF0000;"| 7970 || 714~ || -|| || - || 1210 || 2048 || 2.7 || PCI-E 1.1 x16 || cgminer 2.7.4 || MSI HD7970 R7970-2PMD3GD5/OC, core clock - 1210Mhz, memory clock - 685, core voltage (1.149V - MSI Afterburner, ~1.043V - GPU-Z), memory voltage 1.5V, temperature - 75C at mid-day and 65C w/ AC on at 20C, Catalyst 12.8, Windows 8 Release Preview 32-bit, kernel - poclbm, vector - 1, worksize - 64, intensity - 14, fan - 100% <br />
|-<br />
|style="background:#FF0000;"| 7970 || 825 || -|| || 214 || 1290 || 2048 || 2.4 || PCI-E 2.0 x16 || Bitminter|| Bitminter beta 1.1.1; GPU 1290MHz, Memory <br />
1375MHz (Trixx = 600); work size 256, "BFI_INT," Device-accessible CPU memory; full watercooled block; power stats from GPU-Z; Driver 11.12<br />
|-<br />
| 7970x3 || 1950 || 2.6 || 1.72 || 750 || 1100 || 2048x3 || - || PCI-E 2.0 x16 || cgminer 2.7.5 || Win8, Catalyst 12.8, driver: 8.982.0.0, E: 1100, M:750, kernel: poclbm, worksize: 256, intensity: 9, gpu-threads: 4, refitted Diamond 7970 HSF with new VRM pads to lower VRM temps ~15C. Undervolted each card until crash under load, then raised about 0.015v for stability. Settings using afterburner 2.2.1 with OC unlocked. Visiontek 7970: $370, Sapphire 7970: $360, Diamond 7970: $400<br />
|-<br />
| 7970x3 || 2050 || 2.41 || 1.22 || 850 || 1150 || 6144 || 2.6 || PCI-E 2.0 x16 || cgminer 2.3.1 || Win7, Catalyst 12.3, driver: 2.95, E: 1150, M:685, -k diakgcn -v 2 -w 256, 850W power consumption measured at the wall<br />
|-<br />
| FirePro V3800 || 69.0 || -|| || - || || || || PCI-E 2.0 x16 || BitMinter Client || <br />
|-<br />
| FirePro V4800 || 79.7 || -|| || - || 775 || 400 || 2.4 || PCI-E 2.1 x16 || GUIMiner v2011-05-01 || <br />
|-<br />
| FirePro V8700 || 84.8 || -|| || - || 750 || 800 || - || - || poclbm-mod.03.24.2011 || <br />
<br />
|-<br />
| FirePro M5800 || 61.4 || -|| || - || 650 || - || - || - || poclbm-mod.03.24.2011 || Ubuntu<br />
|-<br />
| FirePro M5800 || 69.3 || -|| || - || 650 || 400 || 2.1 || - || GUIMiner v2011-04-26 || -v -w128, Windows 7 32bit<br />
|-<br />
| FirePro M5950 || 96.7 || -|| || - || 725 || 900 || 2.5 || PCI-E 2.0 x16 || poclbm || -v -w128 (Windows 7 64 bit)<br />
|-<br />
| FirePro V5800 || 119 || -|| || - || 690 || 800 || - || PCI-E 2.0 x16 || GUIMiner v2011-05-01 || Windows 7 32bit<br />
|-<br />
| FirePro V5800 || 144 || -|| || - || 690 || 800 || - || PCI-E 2.0 x16 || GUIMiner v2011-05-01 || -v -w128 (Windows 7 32bit)<br />
|-<br />
| FirePro V5800 || 161 || -|| || - || 780 || 800 || - || PCI-E 2.0 x16 || GUIMiner v2011-05-01 || -v -w128 (Windows 7 32bit)<br />
|-<br />
| FirePro V7750 || 35.7 || -|| || - || - || 320 || 2.4 || PCI-E 2.0 x16 || GUIMiner v2011-05-21 || Windows 7 64bit<br />
|-<br />
| FirePro V7800 || 254.85 || -|| || - || - || 1440 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.48 with poclbm || Debian Squeeze<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|}<br />
<br />
<references><br />
<ref name='amazon_20110625'>$ Prices from http://www.amazon.com on 2011-06-25</ref><br />
</references><br />
<br />
===Nvidia===<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! Mhash/s !! Mhash/J !! Watts !! Clock !! SP !! Comment<br />
|-<br />
| ION || 1.8 || 0.067 || 27 || || 16 || poclbm; power consumption incl. CPU<br />
|-<br />
| 8200 mGPU || 1.2 || || || 1200 || 16 || 128 MB shared memory, "poclbm -w 128 -f 0"<br />
|-<br />
| 8400 GS || 2.3 || || || || || "poclbm -w 128"<br />
|-<br />
| 8400 GS || 1.6 || 0.013 || 128 || 1238 || || DiabloMiner -w 128 -f 1 [https://en.bitcoin.it/wiki/User:Knightmb source]<br />
|-<br />
| 8400M GS || 2.0 || || || || ||<br />
|-<br />
| 8500GT || 2.4 || || || 918 || 16 || poclbm under GUIMiner<br />
|-<br />
| 8600M GT || 4.93 || || || || 32 ||<br />
|-<br />
| 8600M GT || 3.8 || || || || || Macbook Pro running Diablo<br />
|-<br />
| 8600GT || 5.66 || || || 1188 || 32 ||<br />
|-<br />
| 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]<br />
|-<br />
| 8800GT || 25 || 0.24 || 105 || 1300 || ||<br />
|-<br />
| 8800GT || 24.5 || 0.23 || 105 || 1300 || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source]<br />
|-<br />
| 8800GT || 31.1 || 0.296 || 105 || 1855 || || Overclocked 715 GPU / 1030 Memory / 1855 Shader; GuiMiner v2011-05-21<br />
|-<br />
| 8800GT || 31.8 || 0.303 || 105 || 1836 || 112 || 713 gpu, 1026 memory. win7x86, phoenix 1.48, -k poclbm WORKSIZE=64 AGGRESSION=5<br />
|-<br />
| 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<br />
|-<br />
| 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]<br />
|-<br />
| 8800 GTS || 18.7 || 0.124 || 150 || 1200 || || poclbm -w 64 no vectors<br />
|-<br />
| 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.<br />
|-<br />
| 8800 GTX || 27.5 || || || 1404 || || phoenix 1.48, poclbm, no vectors, 83C with 50C ambient <br />
|-<br />
| 8800m GTX || 16.3 || || || || || rpcminer-cuda Win7-64<br />
|-<br />
| 9300GE || 1.57 || || || 1300 || 8 ||<br />
|-<br />
| 9300GS || 1.69 || || || 1400 || 8 ||<br />
|-<br />
| 9300/nForce 730i || 2.15 || || || 1200 || 16 ||<br />
|-<br />
| 9400GT || 3.37 || 0.067 || 50 || 1400 || 16 ||<br />
|-<br />
| 9400M (MacBook) || 1.90 || 0.32 || 6 || 700 || || poclbm -f 8 no vectors<br />
|-<br />
| 9500M GS || 3.2 || || || 950 || 32 || rpcminer-cuda<br />
|-<br />
| 9500GT || 6.75 || 0.135 || 50 || 1400 || 32 ||<br />
|-<br />
| 9500GT || 7.30 || 0.135 || 50 || 1400 || 32|| rpcminer-cuda, Overclocked 730 GPU/ 500 Memory / fan 100% 70C solid<br />
|-<br />
| 9500GT || 7.10 || 0.135 || 50 || 1767 || 32 || rpcminer-cuda, Overclocked 707 GPU / 500 Memory / fan 100% 73C steady<br />
|-<br />
| 9600GSO || 19.88 || 0.237 || 84 || 1375 || 96 ||<br />
|-<br />
| 9600GSO512 || 11.75 || 0.131 || 90 || 1625 || 48 ||<br />
|-<br />
| 9600GT || 15.66 || 0.165 || 95 || 1625 || 64 ||<br />
|-<br />
| 9600GT Zotac || 15 || || || 1650 || 64 ||<br />
|-<br />
| 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]<br />
|-<br />
| 9600M GS || 4.0 || || || 1075 || 32 || rpcminer-cuda<br />
|-<br />
| 9800GT || 30.36 || 0.289 || 105 || 1800 || 112 ||<br />
|-<br />
| 9800GT EE || 19.7 || 0.263 || 75 || 1375 || 112 || rpcminer-cuda<br />
|-<br />
| 9800GT OC || 29.5 || 0.283 || 105 || 1836 || 112 || poclbm.py, no options. Memory underclocked to 850Mhz, GPU overclocked to 733Mhz<br />
|-<br />
| 9800GTX || 32.54 || 0.232 || 140 || 1688 || 128 ||<br />
|-<br />
| 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!)<br />
|-<br />
| 9800GTX+ || 35.39 || 0.251 || 141 || 1836 || 128 ||<br />
|-<br />
| 9800GTX+ || 36 || || || || || factory OC ubuntu polclbm.py -w 128 -f 10 -a 10 (DO NOT USE -v)<br />
|-<br />
| 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)<br />
|-<br />
| 9800GTX+ || 40.20 || 0.287 || 140 || 835 || 128 || lowered memory clock higher core, unstable if going higher<br />
|-<br />
|style="background-color:#FFEFEF"| 9800GX2 || 57.83 || 0.294 || 197 || || 2x128 ||<br />
|-<br />
|style="background-color:#FFEFEF"| 9800GX2 || 28 || 0.142 || 197 || || 2x128 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37620#msg37620 source]<br />
|-<br />
| G210 || 3.38 || 0.111 || 30.5 || 1402 || 16 ||<br />
|-<br />
| G210 || 3.79 || 0.124 || 30.5 || 1402 || 16 || poclbm -f 1<br />
|-<br />
| GT220 || 10.8 || 0.084 || 128 || 1360 || || DiabloMiner -w 128 -f 1000 [https://en.bitcoin.it/wiki/User:Knightmb source]<br />
|-<br />
| GT230 || 15.5 || 0.161 || 96 || 650 || 64 || (9600GT rebranded one from in a medion pc)<br />
|-<br />
| GT240 || 19.37 || 0.281 || 69 || 1340 || 96 ||<br />
|-<br />
| 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]<br />
|-<br />
| GT240 || 28.1 || || || || 96 || poclbm -f0 -v (Gainward GT240 1024DDR5 OC core@670/stockmem@1700/shader@1700 - stable; max.temp=73)<br />
|-<br />
| GT240M || 9.8 || 0.426 || 23 || 550 || 48 || poclbm -f 0 -w 256 <br />
|-<br />
| GT240 OC || 25.6 || 0.365 || 70 || 1765 || 96 || poclbm<br />
|-<br />
| GTS250 || 35.39 || 0.244 || 145 || 1836 || 128 ||<br />
|-<br />
| GTS250 || 35.2 || 0.243 || 145 || 1836 || 128 ||<br />
|-<br />
| GTS250 OC || 37 || 0.255 || 145 || 2047 || 128 || 37.2 with the following OC: Core: 775MHz, Shader: 1900MHz, Memory: 1200MHz<br />
|-<br />
| GTX260M || 22.5 || || || 500 || 112 || poclbm 4/28/2011 Asus G71GX runs ~90c without cooling pad <br />
|-<br />
| GTX260 || 35.91 || 0.178 || 202 || 1242 || 192 ||<br />
|-<br />
| GTX260 || 44 || 0.242 || 182 || 1242 || 216 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]<br />
|-<br />
| GTX260c216 || 40.40 || 0.236 || 171 || 1242 || 216 ||<br />
|-<br />
| GTX260c216 || 47.4 || 0.260 || 182 || 1348 || 216 || poclbm -w 256<br />
|-<br />
| GTX260c216 || 50.00 || || || 1050 || 216 || m0mchil GPU client, Windows 7 64-bit, x6 @ 3.5ghz<br />
|-<br />
| GTX260c216 OC || 52.0 || || || 1461 || 216 || "poclbm -w 256 -f 1"<br />
|-<br />
| GTX260c216 OC || 58.9 || || || 756/400 || 216 || Core overclocked, Memory underclocked, Ubuntu 11.04 Classic Session(No Effects) "poclbm -w 256 -f 1"<br />
|-<br />
| GTX260c216 OC || 60.1 || || || 1706 || 216 || Core: 364 MHz, Shaders: 1706 MHz, Memory: 594 MHz, VDDC: 1.1800V. "poclbm-mod -w 256 -f 1"<br />
|-<br />
| GTX275 || 50.75 || 0.232 || 219 || 1404 || 240 ||<br />
|-<br />
| GTX275 || 58 || || || 729/1458 || 240 || poclbm -f 0 -w 256<br />
|-<br />
| GTX280 || 46.84 || 0.198 || 236 || 1296 || 240 ||<br />
|-<br />
| GTX280 || 64.34 || 0.289 || 245 || 1296 || 240 || phoenix.exe -k poclbm AGGRESSION=6 WORKSIZE=128 (61*C with Accelero XTREME GTX280)<br />
|-<br />
| GTX285 || 64.8 || || || 1607 || 240 || GuiMiner - Not sure about wattage yet. Still testing. Card runs around 74 C<br />
|-<br />
|-<br />
| GTX285 || 53.35 || 0.262 || 204 || 1476 || 240 ||<br />
|-<br />
| GTX295 || 89.78 || 0.311 || 289 || 1242 || 480 ||<br />
|-<br />
| GTX295 || 120.70 || 0.418 || 289 || 1242 || 480 || GUIMiner no oc.<br />
|-<br />
| GTX295 || 117.30 || 0.406 || 289 || 1476 || 490 ||<br />
|-<br />
| GT 320M (MacBook Air) || 6.12 || || || 1212 || 48 ||<br />
|-<br />
| 320M (Mac mini 2010) || 7.0 || 0.35 || 20 || 450 || 32 || poclbm no extra options, windows 7 x64<br />
|-<br />
| GT 325M || 7.5 || || || 990 || 48 || rpcminer-cuda<br />
|-<br />
| GT 325M || 10.5 || || || 325/650(mem)/1300(shaders) || || rpcminer-cuda, 71 degrees<br />
|-<br />
| GT 325M || 7.99 || || || || || poclbm -f 0 -w 256<br />
|-<br />
| GT330 || 21.65 || || || || || poclbm -f 0 -w 256<br />
|-<br />
| GT 330M || 7.97 || || || ||48|| 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<br />
|-<br />
| GT 330M || 10.8 || || ||650MHZ core||48|| 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.<br />
|-<br />
| GT 330M (Sony Vaio Z) || 7.8 || 0.71 ( 0.3 total) || 11 (26w total) || 1045 || 48 ||<br />
|-<br />
| GT 330M (Samsung R480) || 9.1 || || || 575(GPU)/1265(shader) || ||VRAM 1024MB. pocblm -vectors --verbose. Windows 7 Ultimate x86<br />
|-<br />
| GTS 350M (Toshiba A665-3DV) || 17.0 || 1.214 || 14 || 1080 || || DiabloMiner-Windows.exe<br />
|-<br />
| GTS 350M (Toshiba A665-3DV5) || 20.8 || || || 1350 || || DiabloMiner-Windows.exe, OC'd 550/850/1350 73C stable<br />
|-<br />
| GTS 360M || 25.0 || || || || || [toshiba qosmio laptop, ~150-165*F stock fans]<br />
|-<br />
| GTS 360M (ASUS G60jx) || 20.0 || || || || || everythins is stock, it cannot sustain. it reaches 90 degrees and freezes.<br />
|-<br />
| GTS 360M (ASUS G60jx) || 27.2 || || || Shader @ 1720, Memory @ 900 || || stock hardware (clean exhaust fan), Afterburner, 72 deg C Stable <br />
|-<br />
| GT430 || 20.24 || 0.413 || 49 || 1400 || 96 ||<br />
|- <br />
| GT440 || 20.4 || || || 1645 || 96 || rpcminer-cuda -aggression=8; winxp x64 driver 275.33<br />
|-<br />
| GT530 || 17.9 || 0.358 || 50 || 1400 || || BitMinter v1.1.2<br />
|-<br />
| GT520M || 8.9 || || || || || rpcminer-cuda, got up 2 10.2MH/s OC'ed<br />
|-<br />
| GT525M || 14.6 || || || || || rpcminer-cuda<br />
|-<br />
| GT540M || 16.0 || || || || || rpcminer-cuda<br />
|-<br />
| GT550M || 17.08 || || || || || rpcminer-cuda -aggression=8<br />
|-<br />
| GT610M (ASUS K45V) || 9.371 || || || 738 MHz || || 2GB RAM.<br />
|-<br />
| GT650M (rMBP) || 17.8 || || || 900 || 16 || cgminer 2.5.0 on OSX 10.7.4<br />
|-<br />
| GT650M OC || 27.4 || || || || || GUIMiner <br />
|-<br />
| GTS450 || 45.28 || 0.427 || 106 || 1566 || 192 ||<br />
|-<br />
| GTS450 (Sparkle One) || 40.0 || || || || || poclbcm git Oct 2012<br />
|- <br />
| GTS450 || 45.28 || 0.427 || 106 || 1566 || 192 ||<br />
|-<br />
| GTX460SE || 56.39 || 0.376 || 150 || 1300 || 288 ||<br />
|-<br />
| GTX460 || 66.32 || || || 814 || 336 || rpcminer-cuda 20110605, Graphics Clock @ 814MHz, Memory @ 1555MHz<br />
|-<br />
| GTX460 || 68.31 || 0.427 || 160 || 1350 || 336 ||<br />
|-<br />
| GTX460 768MB || 57.8 || || ? || 1350 || 336 || rpcminer-cuda -gputhreads=320 -gpugrid=336<br />
|-<br />
| 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). <br />
|-<br />
| GTX460 1GB DirectCU || 72.3 || ? || ? || 1672 || 336 || rpcminer-cuda -gputhreads=320 -gpugrid=336<br />
|-<br />
| GTX460 1GB DirectCU || 89.5 || ? || ? || 1000 || 336 || guiminer GPU:1000mhz MEM:900<br />
|-<br />
| GTX460 1GB ( evga FPB ) || 71.4 || -- || -- || 870/1744/1800 || 336 || guiminer-cuda v2012-02-19 FW290.53 Win7x64<br />
|-<br />
| GTX460 1GB ( evga ) || 83.1 || 0.519 || 160 || 925/1850/900@0.960v || 336 || guiminer (phoenix1.75) -k poclbm AGGRESSION=8 FASTLOOP BFI_INT -v WORKSIZE=256 ForceWare 301.42 Win7x64 Runs at 70°C with fan at 100%<br />
|-<br />
| GTX460 (2 cards) || 102 || 0.319? || 320? || 1350 || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26363#msg26363 source]<br />
|-<br />
| 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<br />
|-<br />
| GTX460 1GB OC (2x MsiHawksSLI) || 158 || 0.658 || 240w(used kill a watt) || core/shader/ram@vcore 930/1860/1150@1.087v (only vcore raised) || 2x 336 || rpcminer-cuda ver.20110227 -gpugrid=320 -gputhreads=320 -aggression=7 Watercooled stable @ 110°F/43° !!!USE ASUS GPU Tweak with GPU-Z (afterburner v2.2.3 wont OC with NVIDIA driver 306.97) I would need gpu bios mod to get more oc/volt. Setting faster ram did increase Mhash/s versus setting ram=core clock.<br />
|-<br />
| GTX465 || 64.41 || 0.322 || 200 || 1215 || 352 ||<br />
|-<br />
| GTX470 || 81.98 || 0.381 || 215 || 1215 || 448 ||<br />
|-<br />
| GTX470 || 94.7 || || || 1414 || ||<br />
|-<br />
| 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 <br />
|-<br />
| GTX470 || 111.9 || 0.520 || 215 || 1650 || 448 ||<br />
|-<br />
| GTX470 || 115 || || || 1616 || || phoenix 1.46 poclbm VECTORS BFI_INT FASTLOOP AGGRESSION=6<br />
|-<br />
| 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)<br />
|-<br />
| GTX480 || 101.28 || 0.405 || 250 || 1401 || 480 ||<br />
|-<br />
| GTX480 || 140.43 || || || 1700 || 480 || rpcminer-cuda -gpugrid=512 -gputhreads=480<br />
|-<br />
| 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)<br />
|-<br />
| GTX550 Ti || 45.0 || ? || ? || ? || ? || EVGA 1GB, WinXP rpcminer, no overclock<br />
|-<br />
| GTX560 Ti || 67.7 || 0.39 || 170 || 1700 || 384 || standard EVGA 560, no overclock<br />
|-<br />
| 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<br />
|-<br />
| GTX560 Ti || 74.8 || 0.41 || 180 || 1700 || 384 || gigabyte 900Mhz clock; -w 512 -v<br />
|-<br />
| GTX560 Ti || 81 || 0.45 || 180 || 835 || 384 || Gainward GTX560TI Phantom, default clock, rpcminer-cuda<br />
|-<br />
| GTX560 Ti || 85.1 || - || - || - || - || cgminer 2.5.0, linux 32bit, nvidia 295.41, Intensity: 14<br />
|-<br />
| GTX560 Ti || 100 || 0.5 || 200 || 1000 || 384 || GFX - MSI 560Ti HAWK; rpcminer-cuda.exe -aggression=8 -gpugrid=64 -gputhreads=384; GPU temp - 68°C; OS - Windows 8 x64 .<br />
|-<br />
| GTX 560M || 39.3 || 0.38 || 75 W || 775|| 192 || [http://www.examiner.com/computers-in-denver/toshiba-qosmio-x775-q7380-review-review source1] [http://www.notebookcheck.net/NVIDIA-GeForce-GTX-560M.48313.0.html source2] Note: Uses the 295.51 Beta Drivers<br />
|-<br />
| 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]<br />
|-<br />
| GTX570 || 105.83 || 0.483 || 219 || 1464 || 480 ||<br />
|-<br />
| 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<br />
|-<br />
| GTX570 || 157 || 0.717 || 219 || 850 || 480 || rpcminer-cuda.exe -aggression=11 -gpugrid=120 -gputhreads=960<br />
|-<br />
| GTX570 || 165 || || || 925 || 480 || rpcminer-cuda.exe -gpugrid=120 -gputhreads=960; vcore 1.1v; Win7 x64 304.79 Beta; -aggression=11 adds strong lag with minimal increase in hashrate.<br />
|-<br />
| GTX570 || 160 || || || 925 || 480 || rpcminer-cuda.exe -gpugrid=104 -gputhreads=832; No desktop lag, very minimal loss in hashrate compared to much laggier settings<br />
|-<br />
| GTX580 || 156.6 || 0.642 || 244 || 1544 || 512 || cgminer 2.11.3 on Win 8-64 with I=6, driver nVidia 314.22<br />
|-<br />
| GTX580x2 || 2x 146 || 0.598 || 244 || 1544 || 512 || rpcminer-cuda.exe -gpugrid=128 -gputhreads=1024 <br />
(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)<br />
|-<br />
| GTX590 || 193.1 || --- || --- || 1215 || 2x 512 || poclbm -v -w 256, Win<br />
|-<br />
| GTX590 || 2x 121.48 || --- || --- || 750 || 2x 512 || <br />
|-<br />
| GTX670 || 112.00 || 1.1 || 100 || 1275 || 1344 || EVGA GTX670FTW 2GB / GPU Clock offset +75Mhz with EVGA Precision X / GUIMiner -f 60 / Windows 7 64-Bit. (09-13-2012)<br />
|-<br />
| GTX680 || 127.3 || || || 1280 || 1536 || Asus GTX 680 2GB DirectCU II: Windows 7 64 bit: Nvidia 310.90 driver: Offset of 186: Runs at a constant 52C<br />
|-<br />
| GTX680 || 110.00 || || || 1110 || 1536 || RPCMiner with OpenCL or others. Might crash once mining stops. No Flags and Stock Settings (GPU Boost @ 1110mhz Core) with EVGA GTX 680, latest version of GUIMiner (2012-2-19) and Windows 7 x64.<br />
|-<br />
| GTX680 || 120.00 || 1.2 || 100 || 1272 || 1536 || Ufasoft Galaxy 4GB (GPU Clock offset +70Mhz with EVGA Precision X) (2012-7-28) and Windows 7 64-Bit.<br />
|-<br />
| Quadro FX 580 || 5.7 || 0.14 || 40 || 1125 || 4 ||rpcminer-cuda, Win, -gpugrid=128 -gputhreads=512<br />
|-<br />
| Quadro FX 770M || 5.75 || || || 500 || 32 || DiabloMiner-Windows.exe BFI_INT FASTLOOP AGGRESSION=6, Win<br />
|-<br />
|Quadro FX 770M || 6.39 || || || 500 || 32 || DiabloMiner-Windows.exe BFI_INT FASTLOOP AGGRESSION=6 w 64, Win 7x64<br />
|-<br />
|Quadro FX 880M || 9.6 || || || || || poclbm/guiminer<br />
|-<br />
| Quadro FX 1600M || 6 || 0.12 || 50 || 625 || 32 ||rpcminer-cuda, Win<br />
|-<br />
| Quadro FX 1800 || 13.6 || - || - || - || - || cgminer 2.5.0, linux 32bit, nvidia 256.44 Intensity: 4<br />
|-<br />
| Quadro FX 2000M || 23 || 0.397 || 58 || || || phoenix 1.48, -k poclbm, VECTORS, AGGRESION=6, Lenovo W520 platform<br />
|-<br />
| Quadro FX 2800M || 22 || 0.293 || 75 || 600 || 96 ||DiabloMiner, win<br />
|-<br />
| Quadro FX 3000M || 28.6 || - || - || - || - || cgminer 2.5.0, linux 32bit, nvidia 295.41 Intensity: 3<br />
|-<br />
| Quadro FX 3600M || 36 || 0.514 || 70 || 500 || 96 ||<br />
|-<br />
| Quadro FX 3800 || 33.3 || || || || || poclbm/guiminer -f0 -w128<br />
|-<br />
| Quadro NVS 135M || 1.05 || 0.1 || 10 || 800 || 1 || <br />
|-<br />
| Quadro NVS 295 || 1.7 || 0.07 || 23 || 567 || 8 || phoenix<br />
|-<br />
| Quadro NVS 3100M || 3.6 || 0.257 || 14 || 600 || 16 || rpcminer-cuda, Win, CUDA 3.1.1<br />
|-<br />
| Quadro NVS 4200M || 10.0 || || || 810 || || guiminer, Win7-64<br />
|-<br />
| Quadro 5000 || 67.7 || 0.445 || 152 || 513 || 352 || rpcminer-cuda.exe -aggression=7 gpugrid=352 gputhreads=704;<br />
|-<br />
| Tesla C1060 || 52.5 || || || 1296 || 240 || poclbm, Win7x64<br />
|-<br />
| Tesla K20 || 134.8 || || || 706 || 2496 || poclbm, Linux<br />
|-<br />
| Tesla M2050 || 79.8 || || || 1550 || 448 || DiabloMiner<br />
|-<br />
| Tesla M2050 || 94.5 || || || 1550 || || poclbm<br />
|-<br />
| Tesla S1070 || 155.2 || || 800 <ref name='nvidia_S1070'/> || 1440 (GT200b)<ref name='nvidia_S1070'/> || 960<ref name='nvidia_S1070'/> || rpcminer-cuda, Linux, CUDA 3.2, 4 instances (-gpu=0 through -gpu=3)<br />
|-<br />
| Tesla S2070 || 749.23 || || || 1150<ref name='nvidia_S2070'/> || 1792<ref name='nvidia_S2070'/> || rpcminer-cuda, Linux, CUDA 4.0, 8 instances (-gpu=0 through -gpu=7) <br />
|-<br />
| GTX280x2 || 102.7 || || || || ||<br />
|-<br />
|}<br />
<references><br />
<ref name='nvidia_S1070'>The S1070 is a dedicated supercomputing platform that features four Tesla units (GT200). Technical data taken from [http://www.nvidia.de/object/tesla_s1070_de.html NVIDIA]</ref><br />
<ref name='nvidia_S2070'>The S2070 is a dedicated supercomputing platform that features four Fermi units (C2070). Technical data taken from [http://de.wikipedia.org/wiki/Nvidia_Tesla Wikipedia] (Documentation from NVIDIA webpage is confusing)</ref><br />
</references><br />
<br />
==CPUs/APUs==<br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
===AMD===<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! nprocs !! Mhash/s !! Mhash/J !! TDP [W] !! CPU Clock !! Mhash/s CPU !! Mhash/s GPU !! GPU !! GPU Clock !! SP !! Software !! Notes<br />
|-<br />
| 4x Opteron 6174 || 48 || 115 || 0.36 || 320W || 2.2 GHz || 2.4<br />
|colspan=4|<br />
| cpuminer v0.8.1 || --alg 4way --threads 48<br />
|-<br />
| 2x Opteron 6172 || 24 || 55 || 0.24 || 230W || 2.1 GHz || 2.3<br />
|colspan=4|<br />
| cgminer v2.7.6 || --algo 4way -t 24<br />
|-<br />
| 2x Opteron 6128 || 16 || 32.4 || 0.141 || 230W || 2 GHz || 32.4<br />
|colspan=4|<br />
| 0.3.19 || -4way<br />
|-<br />
| Athlon XP 2000+ || 2 || 0.62 || 0.009 || 70W || 1.67 GHz || 0.62<br />
|colspan=4|<br />
| 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]<br />
|-<br />
| Athlon 64 3500+ || 1 || 1.18 || 0.013 || 89W || 2.54 GHz || 1.18<br />
|colspan=4|<br />
| ufasoft v0.4 || overclocked (originally 2.2 GHz)<br />
|-<br />
| Athlon 64 X2 3800+ || 2 || 1.73 || 0.03 || 65 W || 2.00 GHz || 1.73<br />
|colspan=4|<br />
| cpuminer (v0.8.1-1-g69529c3) || -algo=4way<br />
|-<br />
| Athlon 64 X2 4000+ || 2 || 1.9 || 0.02 || 65W || 2.1 GHz || 1.9<br />
|colspan=4|<br />
| rpc-miner ||<br />
|-<br />
| Athlon 64 X2 4400+ || || 2.09 || 0.032 || 65W || 2.3GHz || 2.09<br />
|colspan=4|<br />
| 0.3.19/Win x64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source]<br />
|-<br />
| Athlon 64 X2 6000+ || 2 || 2.81 || 0.02 || 125W || 3 GHz || 2.81<br />
|colspan=4|<br />
| || [http://www.bitcoin.org/smf/index.php?topic=1628.msg22881#msg22881 source]<br />
|-<br />
| Athlon 64 X2 6400+ Black Edition || 2 || 2.9 || 0.023 || 125W || 3.2 GHz || 2.9<br />
|colspan=4|<br />
| 0.3.20.2 BETA/Win 7 x64 || -4way<br />
|-<br />
| Athlon II X2 240e || 2 || 2.71 || 0.06 || 45W || 2.81 GHz || 2.71<br />
|colspan=4|<br />
| bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]<br />
|-<br />
| Athlon II X2 250 || 2 || 5.6 || 0.09 || 65W || 3.01GHz || 5.6<br />
|colspan=4|<br />
| bitcoin-miner 0.11 ||<br />
|-<br />
| Athlon II X4 630 || 4 || 10.7 || 0.11 || 95W || 2.8 GHz || 10.7<br />
|colspan=4|<br />
| bitcoin-miner 0.4 || <br />
|-<br />
| Opteron 8220 x16 || 16 || 25 || || || 2.8Ghz || 1.5 <br />
|colspan=4| <br />
| 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 ||<br />
|-<br />
| Phenom II X3 720 || 3 || 3.8 || 0.04 || 95W || 2.8 GHz || 3.8<br />
|colspan=4|<br />
| 0.3.1x/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]<br />
|-<br />
| Phenom X4 9950 BE || 4 || 9.3 || 0.07 || 126W || 2.6 GHz || 2.32<br />
|colspan=4|<br />
| bitcoin-miner 0.13/WinXP || No GPU<br />
|-<br />
| Phenom II X3 720 || 3 || 7.2 || 0.08 || 95W || 2.8 GHz || 7.2<br />
|colspan=4|<br />
| cpu-miner 0.2.1/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]<br />
|-<br />
| Phenom II X4 810 || 4 || 5.0 || || 95W || 2.8 GHz ||<br />
|colspan=4|<br />
| rpcminer-cpu ||<br />
|-<br />
| Phenom II X4 810 || 4 || 9.5 || || 95W || 2.8 GHz ||<br />
|colspan=4|<br />
| rpcminer-4way ||<br />
|-<br />
| Phenom II X4 810 || 4 || 10.5 || || 95W || 2.8 GHz ||<br />
|colspan=4|<br />
| ufasoft v0.10 ||<br />
|-<br />
| Phenom II X4 810 || 4 || 11.5 || || 95W || 2.8 GHz ||<br />
|colspan=4|<br />
| 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" <br />
|-<br />
| Phenom II X4 955 || 4 || 11 || 0.09 || 125W || 3.2 GHz || 11<br />
|colspan=4|<br />
| rpcminer-4way ||<br />
|-<br />
| Phenom II X4 965 || 4 || 12 || 0.09 || 140W || 3.4 GHz || 11<br />
|colspan=4|<br />
| rpcminer-4way ||<br />
|-<br />
| Phenom II X6 1055T || 6 || 15.84 || 0.13 || 125W || 2.82 GHz || 15.84 <br />
|colspan=4|<br />
| bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]<br />
|-<br />
| Phenom II X6 1055T || 6 || 23.6 || || 95W || 3.50 GHz || 23.6 <br />
|colspan=4|<br />
| [http://github.com/pooler/cpuminer pooler's cpuminer] 2.2.2 || --algo=sha256d<br />
|-<br />
| Phenom II X6 1075T || 6 || 21.3 || || 125W|| ||<br />
|colspan=4|<br />
| minerd || Ubuntu 11.04 amd64 runlevel=1 -algo=4way -threads=6<br />
|-<br />
| Phenom II X6 1090T || 6 || 18|| || 141W|| 3.50 GHz || 3<br />
|colspan=4|<br />
| minerd || <br />
|-<br />
| Phenom II X6 1100T || 6 || 22 || 0.176 || 125W || 3.82 GHz || 22<br />
|colspan=4|<br />
| bitcoin-miner || Aciid#bitcoin-dev<br />
|-<br />
| Sempron 3000+ || 2 || 0.8 || || 62W || 1.6 GHz || 0.8<br />
|colspan=4|<br />
| cpuminer || --alg 4way<br />
|-<br />
| Turion X2 RM-70 || 2 || 1.9 || || 65W || 2.1 GHz || 1.9<br />
|colspan=4|<br />
| cpuminer || --alg 4way<br />
|-<br />
| 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<br />
|-<br />
| Zacate E-350 || 2 || 12<br />
|colspan=2|<br />
| 1.648 Ghz || 1.252 || 10.87 || HD6310M || 492 Mhz || 80 || poclbm -v -w 256 -f 1 || "autotune" speed with ASUS EFI BIOS<br />
|-<br />
| 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 || <br />
|-<br />
| A4-3400 || 2 || 23.2 || || || 75W || 2.4 Ghz || || 23.2 || 6350 || stock || || GUIminer || ||<br />
|-<br />
| A8-3850 || 4 || 60 || || 100W || Stock || || 60 || HD6550D || Stock || 400 || poclbm.exe, Win7-32, 4GB RAM || All running at stock speeds, and set to auto in BIOS.<br />
|<br />
|-<br />
| A8-3870K || 4 || 95 || || 100W (@stock) || 3.3 Ghz || || 95 || HD6550D || 900MHz || 400 || phoenix.exe -k phatk VECTORS BFI_INT AGGRESSION=4 WORKSIZE=128, Win7-64, 8GB RAM 1667MHz || M/B ASUS F1 A75-M Pro, CPU/GPU BIOS overclocked<br />
|-<br />
| A10-5800K || 4 || 105 || || 100W || 3.8 Ghz || || 105 || HD7660D || 800MHz || 384 || cgminer Intensity=7 || Linux 64bit (Ubuntu 12.10), AMD-APP-SDK-v2.7-RC-lnx64, stock speeds *not* overclocked<br />
|}<br />
<br />
===ARM===<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! p/t !! Mhash/s !! Mhash/J !! Mhash/s/$ /€ !! ACP [W] !! Clock !! Version !! Comment<br />
|-<br />
| ARM926EJ-S || 1 || 0.187 || ? || ? || ? || 1.2 GHz || cpuminer || Seagate Dockstar [http://archlinuxarm.org/platforms/armv5/seagate-dockstar ArchLinux]<br />
|-<br />
| 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<br />
|-<br />
| ARM1136EJ-S || 1 || 0.11 || ? || ? || ? || 0.528 GHz || cpuminer git || T-Mobile Pulse, inside Debian chroot, 'c' algo<br />
|-<br />
| ARM1176JZ(F)-S || 1 || 0.119 || ? || ? || ? || 0.412 GHz || [http://github.com/pooler/cpuminer pooler's cpuminer] 2.2 || iPhone 3G, 'sha256d' algo<br />
|-<br />
| ARM1176JZ(F)-S || 1 || 0.2 || ? || ? || 3.75W || 800 Mhz || cgminer 2.5.0 || RaspberryPi Model B, SoC BCM2835, Debian Squezee 19-04-2012, Overclocked Cpu 800mhz<br />
|-<br />
| Cortex-A8 || 1 || 0.125 || 0.36 || <0.01 || 0.35 W || 0.6 GHz || cpuminer git (2011-03-26) || Nokia N900: 'cryptopp'<br />
|-<br />
| Cortex-A8 || 1 || 0.2 || 0.57 || <0.01 || 0.35 W || 0.6 GHz || cpuminer git (2011-03-26) || Nokia N900: 'c' algo<br />
|-<br />
| Cortex-A8 || 1 || 0.365 || ? || ? || ? || 0.6 GHz || [http://github.com/pooler/cpuminer pooler's cpuminer] || BeagleBoard: 'sha256d' algo<br />
|-<br />
| Cortex-A8 || 1 || 0.435 || ? || ? || ? || 0.8 GHz || [http://github.com/pooler/cpuminer pooler's cpuminer] 2.2 || 'sha256d' algo<br />
|-<br />
| Cortex-A8 || 1 || 0.44 || ? || ? || ? || 0.8 GHz || cpuminer 2.2.3 (-mfpu=neon) || EfikaMX (iMX.51), CRUX ARMHF, cpuminer -a sha256d<br />
|-<br />
| AllWinner A10(A8) || 1 || 0.568 || ? || ? || <2.5W || 1.0 GHz || [http://github.com/pooler/cpuminer pooler's cpuminer] 2.2 || -a sha256d #Native Lubuntu armhf build <br />
|-<br />
| 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<br />
|-<br />
| Cortex-A9 || 2 || 1.3 || ? || ? || ? || 1.2 GHz || [http://github.com/pooler/cpuminer pooler's cpuminer] 2.2.3 || Samsung Galaxy S II - CFLAGS="-O3 -mfpu=neon"<br />
|}<br />
<br />
===Intel===<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! p/t !! Mhash/s !! Mhash/J !! Mhash / $<ref name='amazon_20110625'/>/€<ref name='geizhals_20110625'/> !! ACP [W] !! Clock [GHz] !! Version !! Comment<br />
|-<br />
| Pentium III (Coppermine) || 2 || 0.39 || 0.008 |||| TDP 2× 26.1 W || 1 || Ufasoft 0.32 (compiled from source), Debian Squeeze || [http://en.wikipedia.org/wiki/List_of_Intel_Pentium_III_microprocessors#.22Coppermine.22_.28180_nm.29 source]<br />
|-<br />
| 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]<br />
|-<br />
| Pentium M 1.6ghz || 1 || 0.4 || || || || 1.6 || minerd (jgarzik's 1.0) || cryppto, Windows 7<br />
|-<br />
| Pentium M 1.6ghz || 1 || 0.62 || || || || 1.6 || Ufasoft 0.20 || Windows XP Professional<br />
|-<br />
| Pentium M 1.6ghz || 1 || 0.71 || || || || 1.6 || [http://github.com/pooler/cpuminer pooler's cpuminer] 2.2 || Gentoo Linux<br />
|-<br />
| Pentium M 1.73ghz || 1 || 0.5 || || || || 1.73 || minerd (jgarzik's 1.0) || cryppto, Windows 7<br />
|-<br />
| 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)<br />
|-<br />
| 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<br />
|-<br />
| Pentium 4 630 || 1/2 || 1.29 || || || || 3.0 || ufasoft 0.23 || Windows XP<br />
|-<br />
| Pentium Dual-Core E2180 || 2/2 || 1.75 || || || || 2.0 || rpcminer-cpu || Win7-64<br />
|-<br />
| Pentium Dual-Core E2180 || 2/2 || 4.1 || || || || 2.0 || cpuminer || sse2_64<br />
|-<br />
| Pentium Dual-Core E2180 || 2/2 || 4.5 || || || || 2.0 || ufasoft v0.11 || Win7-64<br />
|-<br />
| 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]<br />
|-<br />
| 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]<br />
|-<br />
|-<br />
| Celeron E3400 || 2/2 || 5.9 || - || - || - || 2.6 || Ufasoft v0.13 / GUIMiner v2011-06-14 || WinXP 32 bit, SSE2, Flags "-g no" <br />
|-<br />
| 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<br />
|-<br />
| Core 2 Quad Q8200 || 4/4 || 10.9 || || 0.06/0.10 || || 2.33 || Ufasoft 0.14 || -g no -l yes -t 4<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| 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]<br />
|-<br />
| Core i3-2100 || 2/4 || 8.28 || || || || 3.1 || ufasoft v0.20 || <br />
|-<br />
| 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]<br />
|- <br />
| Core i5-650 || 2/4 || 5.1 || 0.04 ? || 0.02/0.03 || || 3.2 || cpuminer-0.7 || -4way<br />
|-<br />
| Core i5-750 || 4/4 || 14 || || 0.06/0.10 || || 3.2 || bitcoin-miner 0.11 || -a 5 -g no -t 4<br />
|-<br />
| Core i5 ? || 4/? || 6.5 || || || || || client from svn || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37621#msg37621 source]<br />
|-<br />
| Core i5-2400 || 4/4 || 4.5 || 0.05 || 0.02/0.03 || 95 || 3.1 || cpuminer git (2011-01-22) || cryptopp_asm32<br />
|-<br />
| Core i5-2400 || 4/4 || 14 || 0.15 || 0.07/0.09 || 95 || 3.1 || cpuminer git (2011-03-26) || sse2_64<br />
|-<br />
| Core i5-2400S || 4/4 || 16.6 || || || 65 || 2.5 || [http://github.com/pooler/cpuminer pooler's cpuminer] 2.2.3 || Linux Mint 13<br />
|-<br />
| Core i5 2500K || 4/4 || 20.6 || ||0.10/0.12 || || 4.2 || bitcoin-miner || -g no<br />
|-<br />
| 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<br />
|-<br />
| 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<br />
|-<br />
| Core i7 2600 || 4/8 || 23.9 || || || || 3.4 || [http://github.com/pooler/cpuminer pooler's cpuminer] 2.2 || Ubuntu Linux 11.10<br />
|-<br />
| 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<br />
|-<br />
| Core i7 620M || 2/4 || 6.5 || || || || 3.33 || This is achieved by running RPC 4 way miner in VMware Fusion 4 (running win 7 in the VM) while in Mac OSX / Mac OS X 10.6.8 || Model: MacBookPro6,2 RAM: 8GB.The CPU appears to turbo boost to 3.33GHz in this way from 2.67GHz when running it in this way.The MBP gets very hot and uses a lot of energy though so watch those temps.It'll throttle after a while unless you keep the air vents clear underneath (ie don't put int in your lap,etc).<br />
|-<br />
| 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<br />
|-<br />
| Core i7 820 || 4/8 || 13.8 || || || || 2.8 || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] || -t 8<br />
|-<br />
| 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<br />
|-<br />
| Core i7 950 || 4/8 || 5.88 || 0.039 || || 150 || 3.83 (x23) || bitcoin-0.3.20.2 Win7-64 ||<br />
|-<br />
| 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 ||<br />
|-<br />
| Core i7 980x || 6/12 || 19.2 || 0.15 || || 130 || 4.4 (x33) || cpuminer/Win7-64 || <br />
|- <br />
| Core i7 980x || 6/12 || 8.7 || || || || 3.9 (x27) || 0.3.17/Win7-64 || <br />
|- <br />
| Core i7 990x || 6/12 || 33.3 || || || || 4.5 (x32) || ufasoft/Win2008 R2-64 || Ram - 12Gb, Rampage III BlackEdition, Water cooling<br />
|- <br />
| 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<br />
|- <br />
| 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 || <br />
|-<br />
| Core i7 2600k || 4/4 || 6.7 || || || || 4.00 || phoenix 0.48 ||<br />
|-<br />
| Core i7 3770k || 4/8 || 5.2 || || || || 4.4 || Guiminer v2012-12-03 || Windows 7 x64 : -v argument increased Mhash/s from 5.0 to 5.2<br />
|-<br />
| Core i7 3930k || 6/12 || 66.6 || || || || 4.625 (125 x 37) || Ufasoft bitcoin-miner v0.28 || Windows 7 x64, uses ~190watts : -v argument increased Mhash/s from 36.0 to 66.6<br />
|-<br />
| Core 2 Duo U7600 || 1 || 1.1 || || || || 1.2 || minerd (jgarzik's 1.0) || cryppto, Windows 7<br />
|-<br />
| Core 2 Duo E5200 || 2/2 || 6.2 || 0.086 || || 72 || 2.76 || Ufasoft/Win7-64 || TDP is 65W + 7W overclock<br />
|-<br />
| Core 2 Duo E6550 || 1/2 || 2.45 || || || || 2.33 || cpuminer 0.7.1 (Linux) || --algo=sse2_64<br />
|-<br />
| Core 2 Duo E6850 || 2/2 || 6.75 || 0.10 || || 65 || 3.0 || ufasoft-0.3 ||<br />
|- <br />
| Core 2 Duo E7300 || 2/2 || 7.76 || 0.11 || || 70 || 3.33 || ufasoft-0.3 || uncertain of overclock; miner optimized for Intel Core<br />
|-<br />
| 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]<br />
|-<br />
| Core 2 Duo E8200 || 2/2 || 2.3 || 0.035 || || 65 || 2.66 || rpcminer-cpu ||<br />
|-<br />
| Core 2 Duo E8400 || 2/2 || 6.9 || 0.106 || || 65 || 3.0 || ufasoft v0.10 || windows 7/64bit (-t 2)<br />
|-<br />
| Core 2 Duo E8500 || 1/2 || 3.6 || || || || 3.16 || guiminer v2011-06-14 || windows vista 32bit<br />
|-<br />
| Core 2 Duo E8500 || 2/2 || 7.2 || || || || 3.16 || guiminer v2011-06-14 || windows vista 32bit<br />
|-<br />
| Core 2 Duo P8700 || 2/2 || 5.9 || || || || 2.53 || ufasoft v0.21 || windows 7/64bit <br />
|-<br />
| Core 2 Duo T5450 || 2/2 || 2.5 || 0.07 || || 35 || 1.63 || bitcoin-miner 0.10 || Ubuntu 11.04<br />
|-<br />
| Core 2 Duo T5500 || 2/2 || 4.3 || || || || 1.66 || [http://github.com/pooler/cpuminer pooler's cpuminer] 2.2 || Gentoo Linux (amd64)<br />
|-<br />
| Core 2 Duo T6400 || 2/2 || 4.2 || 0.12 || || 35 || 2.00 || cpuminer git (Linux) || --algo=sse2_64<br />
|-<br />
| Core 2 Duo T7250 || 2/2 || 4.5 || 0.13 || || 35 || 2.00 || bitcoin-miner 0.13/WinXP || No GPU<br />
|-<br />
| Core 2 Duo T7450 || 2/2 || 3.7 || 0.10 || || 35 || 2.13 || bitcoin-miner 0.10 || Ubuntu 11.04<br />
|-<br />
| Core 2 Duo T9400 || 2/2 || 4.2 || || || || 2.53 || ufasoft v0.13 || Win7-64<br />
|-<br />
| Core 2 Extreme X9000 || 2/2 || 2.37 || || || || 2.8 || rpcminer-cpu || Win7-64<br />
|-<br />
| Core 2 Extreme X9000 || 2/2 || 6.2 || || || || 2.8 || ufasoft v0.11 || Win7-64<br />
|-<br />
| Core 2 Extreme X9000 || 2/2 || 7.2 || || || || 3.2 || ufasoft v0.11 || Win7-64 Overclocked from 2.8 GHz to 3.2 GHz<br />
|-<br />
| Xeon 2.8 || 2/2 || 0.8 || || || || 2.8 || cpuminer || cryptopp_asm32 <br />
|-<br />
| Xeon 3060 || 1/2 || 2.03 || 0.03 || || 65 || 2. || cpuminer 0.8.1 (Linux) || --algo=cryptopp_asm32<br />
|-<br />
| Xeon Prestonia 2.4 (dual) || 2x1/2 || 2.16 || 0.017 || || 130 || 2.4 || ufasoft v0.4 || <br />
|-<br />
| Xeon X5355 (dual) || 2x4/4 || 10.13 || 0.16 || || 120 || 2.6 || bitcoind || Roughly the same speed as the "c" algo in cpuminer<br />
|-<br />
| Xeon E3-1230 V2 (quad) || 4/8 || 19.7 || ? || ? || ? || 3.70 || cgminer 2.8.3 || -O2 -march=core-avx-i algo=sse2_64<br />
|-<br />
| Xeon X5355 (dual) || 2x4/4 || 22.76 || 0.09 || || 120 || 2.6 || cpuminer (v0.8.1-1-g69529c3) || -O2 -march=core2, algo=sse2_64<br />
|-<br />
| Xeon X5365 (dual) || 2x4/4 || 26.00 || ? || || ? || 3.0 || cpuminer git (2011-06-15) || algo=sse2_64<br />
|-<br />
| Xeon X5650 || 2x6/24 || 28.6 || ? || ? || ? || 2.67 || cpuminer 1.0.2 || --algo 4way<br />
|-<br />
| Xeon x5680 (dual) || 2x6/24 || 48 || ? || ? || ? || 3.33GHz || Ufasoft 0.29 || CentOS 6.2 x86_64<br />
|-<br />
| Xeon x5690 (dual) || 2x6/24 || 52 || ? || ? || ? || 3.46GHz || Ufasoft 0.29 || CentOS 6.2 x86_64<br />
|-<br />
| Xeon E5-2690 (dual) || 2x8/32 || 66 || ? || ? || 2x135W || 2.9GHz || Ufasoft 64-bit 0.31 || Windows Server 2008R2 x64<br />
|-<br />
| Xeon E5335 || 4/4 || 9.35 || 0.12 || || 80 || 2.00 || ufasoft v0.11 || Vista-32<br />
|-<br />
| Xeon E5410 || 4/4 || 9.8 || ? || || 80 || 2.33|| ufasoft v0.10 || CentOS 5.5 x64 <br />
|-<br />
| Xeon E5440 || 4/8 || 7.3 || ? || || 80 || 2.66|| Kiv's poclbm-gui || FIXME: Either wrong model # or wrong threads/speed info<br />
|-<br />
| Xeon E5506 || 4/4 || 9.6 || ? || || 80 || 2.13|| ufasoft v0.10 || CentOS 5.5 x64 <br />
|-<br />
| Xeon E5520 || 4/8 || 6.5 || 0.08 || || 80 || 2.27 || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]<br />
|-<br />
| Xeon E5530 || 4/8 || 7.14 || 0.09 || || 80 || 2.4 || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]<br />
|-<br />
| Xeon E5620 || 4/8 || 11.2 || ? || || 80 || 2.4 || ufasoft v0.10 -t 4 || CentOS 5.5 x64 Hyper-Threading is off<br />
|-<br />
| 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]<br />
|-<br />
| Xeon E6520 (dual) || 2x4/8 || 24.7 || || || || 2.53 || ufasoft v0.10 || windows 2008 R2 64bit (-t 16)<br />
|-<br />
| Xeon E7220 || 2/2 || 6.3 || ? || || 80 || 2.93|| ufasoft v0.10 || CentOS 5.5 x64 <br />
|-<br />
| 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)<br />
|-<br />
| Xeon E7450 (quad) || 4x6/24 || 60 || || || || 2.40 || ufasoft v0.13 || -t 24<br />
|-<br />
| Xeon E7520 (dual) || 2x4/16 || 18 || || || 95 || 1.87 || ufasoft v0.10 || windows 2008 R2 64bit (-t 16)<br />
|-<br />
| Xeon W3680 || 6/12 || 18 || || || 130 || 3.33 || cpuminer v1.0.2 --algo=4way || Ubuntu 11.04 64bit<br />
|-<br />
| Atom Z520 || 1/2 || 1.20 || || || 2 || 1.7 || ufasoft 1.18 || Asus Eee 1101HA with overclocking capabilities<br />
|-<br />
| Atom N230 || 1/2 || 0.375 || || || 4 || 1.6 || rpcminer-cpu || <br />
|-<br />
| Atom N230 || 1/2 || 0.245 || || || 4 || 1.6 || rpcminer-4way || <br />
|-<br />
| Atom N230 || 1/2 || 0.97 || || || 4 || 1.6 || ufasoft v0.10 || <br />
|-<br />
| Atom N270 || 1/2 || 1.19 || 0.24 || || 5 || 1.6 || ufasoft v0.10 || <br />
|-<br />
| Atom N450 || 1/2 || 1.60 || 0.31 || || 6.5 || 2.06 || ufasoft v0.10 || <br />
|-<br />
| Atom N550 || 2/4 || 1.97 || || || || 1.5 || ufasoft v0.21 || Windows 7/64 bit<br />
|-<br />
| Atom 330 || 2/4 || 1.80 || || || 8 || 1.6 || ufasoft v0.13 || -t 4<br />
|-<br />
| 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<br />
|-<br />
| Atom D510 || 4/4 || 2.3 || 0.07 || || 30 || 1.6 || bitcoin-miner 0.10 || Ubuntu 11.04 Server<br />
|}<br />
<br />
<references><br />
<ref name='amazon_20110625'>$ Prices from http://www.amazon.com on 2011-06-25</ref><br />
<ref name='geizhals_20110625'>€ Prices from http://geizhals.at/eu on 2011-06-25</ref><br />
</references><br />
<br />
===Other===<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! p/t !! Mhash/s !! Mhash/J !! Mhash/s/$ !! ACP [W] !! Clock !! Version !! Comment<br />
|-<br />
| 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.<br />
|-<br />
| 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.<br />
|-<br />
| 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.<br />
|-<br />
| MIPS || 1 || 0.026 || ? || ? || ? || 200 MHz || cpuminer || ASUS WL-500G Deluxe Router Running [http://openwrt.org/ OpenWrt]<br />
|-<br />
| VIA Eden || 1 || 1.3 || 0.17 || || 8W || 1600 MHz || cpuminer || VIA Eden w/ padlock<br />
|-<br />
| PowerPC 7447A || 1 || 0.53 || || || || 1420 MHz || cpuminer ||<br />
|-<br />
| PowerPC 7450 (G4e) || 1 || 1.29 || || || || 1670 MHz || cgminer 2.0.7 || PowerBook5,6; Mac OS X 10.5.8; Altivec<br />
|-<br />
| PowerPC 750 (G3) || 1 || 0.140 || || || || 600 MHz || cpuminer || iBook G3 600 w/ Cryptopp<br />
|-<br />
| IBM POWER4+ 2/way || 2/1 || 0.58 || || || || 1450 MHz || cpuminer 2.2.3 || CRUX PPC (64bit), cpuminer -a sha256d -t 1<br />
|-<br />
| IBM Power7 (PowerPC) || || 7.6 || || || || 3.5 Ghz || cgminer || IBM Power7 770, SuSE Linux 11.1, 4 cores, OpenCL, YASM, Altivec<br />
|-<br />
| Google App Engine || 1 || 0.144 || || || 0W || || pyminer || Modified version of [https://github.com/jgarzik/pyminer pyminer] for GAE.<br />
|-<br />
| Open Shift || 1 || 0.059 || || || 0W || || pyminer || <br />
|}<br />
<br />
<references></references><br />
<br />
==See Also==<br />
* [[TP's Bitcoin Calculator]]<br />
* [[Mining rig]]<br />
* [[ZTEX FPGA Boards for Bitcoin Mining]]<br />
* [[Generation Calculator]]<br />
* [[Power Calc]]<br />
* [[OpenCL miner]]<br />
* [http://www.pcper.com/article.php?aid=745 ATI Stream vs. NVIDIA CUDA - GPGPU computing battle royale] <br />
* [http://bitminer.info/ Bitminer.info] <br />
* [http://www.pcper.com/reviews/Graphics-Cards/Bitcoin-Currency-and-GPU-Mining-Performance-Comparison Bitcoin Mining Performance Compared]<br />
** [http://www.pcper.com/reviews/Graphics-Cards/Bitcoin-Mining-Update-Power-Usage-Costs-Across-United-States Bitcoin Mining Power Costs Compared]<br />
** [http://112bit.com Bitcoin Mining Hardware]<br />
[[Category:Mining]]<br />
[[Category:Hardware]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=AntMiner&diff=46008AntMiner2014-04-06T15:52:15Z<p>Nanotube: Reverted edits by Gersics (talk) to last revision by Malevolent</p>
<hr />
<div>ANTMINER S1 is a Bitcoin mining rig with a speed of 180 GH/s.<br />
<br />
<br />
== See Also ==<br />
* [https://www.bitmaintech.com Official website]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin.it_Wiki_Contributors%27_Award&diff=45983Bitcoin.it Wiki Contributors' Award2014-04-06T00:18:41Z<p>Nanotube: Removed protection from "Bitcoin:Contributors award"</p>
<hr />
<div><div style="border: 1px solid red; background-color: #cfc; padding: 10px;">'''The Contributors Award is still new. The rules may be changed to fix things that weren't initially planned, and nothing tells if this will happen again next month!'''<br />
<br />
The concept is however really simple: share received donations between people contributing on the wiki.</div><br />
<br />
The '''Contributors Award''' is a bitcoin sum awarded to the contributors of this wiki!<br />
<br />
It can be awarded to everyone who have been contributing, except [[User:MagicalTux|MagicalTux]], bots and anyone willing to help fine-tuning the scoring after the deadline for a session has been reached. Contributors are invited to provide their bitcoin address on their user page so they can receive their coins when awarded.<br />
<br />
'''Current Contributors Award''': [[Bitcoin:Contributors_Award/2011-01|January 31st 2011]] (also covers december). Received 170 BTC from donations. Added an extra 250 BTC, so the total is 420 BTC.<br />
<br />
'''Next Contributors Award''': March 31st 2011 (also covers february). Donate on [http://blockexplorer.com/q/getreceivedbyaddress/13fErNCN7ePWVdu27EsV9CVKbcp3C2UH2W 13fErNCN7ePWVdu27EsV9CVKbcp3C2UH2W] (click on there to see how much has been received for the next contributors award)<br />
<br />
== Rules ==<br />
<br />
=== Application ===<br />
<br />
To apply to the Contributors Award, you need to have a bitcoin address published on your user page. Only a bitcoin address you've put yourself will be used. If someone else changes the bitcoin address on your user page, the bot will look in previous revisions of your page to find one edited by you. The following format should be used on your page:<br />
<br />
Contributors Award participant: 1....................<br />
<br />
By applying to the Contributors Award you confirm you can legally receive bitcoins in your jurisdiction and take full responsibility.<br />
<br />
=== How are winners decided ===<br />
<br />
A bot will list most active contributors and rank them based on the amount of pages/lines/etc contributed. Only contributions that were not removed will be counted. The contributions will then be quickly checked by [[User:MagicalTux|MagicalTux]] and a list of winners will be compiled and published within one week. Scoring will also be based on other parameters, see below.<br />
<br />
Once the list is published, donations will be directed to the contributors within 3 days, after making sure the listed address for each contributor is correct. Contributors can choose to have their donations directed to somewhere else by directly putting the bitcoin address of the beneficiary of their choice. Contributors who do not publish a bitcoin address will not be counted when the Contributors Award is shared between contributors.<br />
<br />
Every contributor with serious contribution, no matter how small, will receive a part of the award, except if excluded.<br />
<br />
=== Sessions ===<br />
<br />
A session is the period of time covered by a given award. Sessions are planned to last for one month, however this may be changed in the future to reflect the amount of donations received and work required to establish a list of winners.<br />
<br />
=== Donations ===<br />
<br />
The Contributors Award fund is made only of donations from bitcoin users. Donations will be held by Tibanne Co. Ltd. until winners have been decided, at which points the received amount will be split between contributors proportionally to their score.<br />
<br />
Employees of Tibanne Co. Ltd., their family, relatives, dogs and cats are explicitly denied participation in the Contributors Award.<br />
<br />
=== Direct donations ===<br />
<br />
If you have a personal preference for a given contributor or feel this contributor is doing a great job, you are strongly encouraged to donate directly to this contributor. Donations to the Contributors Award will be distributed between contributors of the wiki using specific rules. Donating to the contributors award doesn't mean you get to choose who gets your coins.<br />
<br />
=== Abuse ===<br />
<br />
The wiki will be monitored at all time. Anyone trying to artificially improve his own score, or artificially reduce someone else's score will be excluded from the Contributors Award. The goal of this award is to improve the community work around bitcoin, and not make this wiki a war zone. Should abuse become uncontainable, the contributors award will be stopped, scoring will be computed up to the date the abuse started and bitcoins shared between honest members.<br />
<br />
=== Scoring ===<br />
<br />
The scoring for each contributor will be made based on the following rules.<br />
<br />
==== Text ====<br />
<br />
Of course, text contributions take an important place in the scoring calculation. The following parameters will be taken in account for each contribution:<br />
<br />
* Insertion of bulks of text will be scored based on the amount of text submitted. The ratio will be reduced if the text is found on other sites via a search engine (ie. not original text) and based on the number of afterward corrections. If the text is completly removed (and not restored afterward) then it won't be counted. Off-topic inclusions will also be ignored.<br />
* Corrections (typo, etc) will be counted based on the volume of text they apply to, minus the amount of corrections made by other people afterward.<br />
* Adding links to existing bulks of text will only count if the ratio of links is kept low (only the first link to a page on a given page will be counted)<br />
<br />
==== Templates ====<br />
<br />
Templates are an important part of the life of a wiki. Templates are scored on the following elements:<br />
<br />
* The template must be original. Templates copied from other sites will not be counted.<br />
* The template must be widely used. Scoring will be based on the number of other contributors using a given template.<br />
<br />
New uses of a template from a previous session will still be awarded to the original contributors of that template.<br />
<br />
==== Talk pages ====<br />
<br />
Modifiers will be given to contributors based on the feedback they receive from users on talk pages. Remember to be courteous at all time for best effect. Those modifiers will be manually collected and only applied to the most notable contributors in order to avoid any abuse.<br />
<br />
==== Vote for your contributor ====<br />
<br />
We might try to allow contributors who have earned points in one session to vote for another contributor in the next session.<br />
<br />
=== Rules change ===<br />
<br />
These rules may be changed should the need arise. If you wish to suggest a change, please use the [[Bitcoin Talk:Contributors Award|discussion page]].</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Talk:ICBIT&diff=45982Talk:ICBIT2014-04-05T23:47:50Z<p>Nanotube: Removed protection from "Talk:ICBIT"</p>
<hr />
<div>There are at least two different edit disputes on this page. Please try to put your comments in the appropriate section and please try to deal with only one of these disputes in each of your edits. Thanks. [[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 23:20, 26 August 2013 (GMT)<br />
<br />
<br />
__FORCETOC__<br />
<br />
== Whether ICBIT is an Exchange providing full Central Counterparty backing ==<br />
<br />
Please stop deleting material from this page. For a very long time ICBIT's webpage clearly explained that it was not a central counterparty. Now it's been changed to something absurdly self-contradictory that essentially says "we call ourselves a central counterparty but we aren't one and we explicitly deny the responsibilities that define the role of a central counterparty". The whole point of having a futures exchange is that you're exposed to credit risk from only one party and you know who that party is (the exchange). ICBIT is not doing that. If they decide to do that and say so publicly, then feel free to change this page, but unless/until then please stop deleting important facts. [[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 16:04, 13 August 2013 (GMT)<br />
<br />
<br />
First of all, finally thank you for taking this into Discussion page. The thing is that you seem to misunderstand how exchanges work. Indeed, ICBIT acts as a counterparty to all futures contracts trades happening, and all major fiat money futures exchanges out there do the same.<br />
<br />
That means that if one trader buys 2 BTC/USD contracts, counterparty is ICBIT, and it is also counterparty to those traders who sold these 2 contracts!<br />
<br />
Graphically:<br />
<br />
Trader 1 Trader 4<br />
Trader 2 <==> ICBIT <==> Trader 5<br />
Trader 3 Trader 6<br />
<br />
Now, the most important fact: Sum of all money paid by loosing users equals to sum of all money paid to profiting users!<br />
<br />
And when any user from loosing side goes bankrupt, central counterparty (aka exchange) has to pay its own money. We do that, but we can't do that all the time, and we can't guarantee it happens all the time, so that's why we say that we guarantee to pay as much, as loosing traders are able to pay.<br />
<br />
Again, that's absolutely same to how fiat-money "real-world" exchanges work. They have reserve funds, and they often go bankrupt (lookup recent Hong Kong's derivatives market bankrupcy, for example).<br />
<br />
[[User:Fireball|Fireball]]<br />
<br />
<br />
No, Fireball, ''you'' misunderstand how exchanges work, and you do not appear to understand what [http://en.wikipedia.org/wiki/Credit_risk#Counterparty_risk Counterparty Risk] is. Being a central counterparty is much more then simply being a central intermediary. Your diagram shows a central ''intermediary,'' not a central counterparty.<br />
<br />
Here, since you like pictures:<br />
<br />
Trader 1 Trader 4<br />
Trader 2 <==> Intermediary <==> Trader 5<br />
Trader 3 Trader 6<br />
<br />
You write "and when any user from loosing side goes bankrupt, central counterparty (aka exchange) has to pay its own money. We do that, but we can't do that all the time, and we can't guarantee it happens '''all the time'''" -- then you are not a central counterparty '''all the time'''. It's just that simple. When you're ready to do that all the time like COMEX and Nasdaq do, '''all the time''' with a pledge of the assets and equity of the exchange itself to fulfill any default like COMEX and Nasdaq do, then announce it publicly and you'll be an exchange (at least in that essential respect). Until then stop posting factually incorrect information on the wiki.<br />
<br />
Here's the problem:<br />
<br />
Trader 1 defaults ======> ICBIT unable to collect ======> Trader 4 is told "you lose"<br />
<br />
This means that ''Trader 1'' was the counterparty, not ICBIT.<br />
<br />
If I buy a call option from on Nasdaq and it is cleared against an uncovered sell order by Bob Jones of Louisiana, I am not exposed to Bob Jones' bankruptcy even though selling uncovered calls has unlimited risk. Nasdaq will make good on the option '''all the time''', and if it doesn't Nasdaq itself is in default. This is the one and only reason why I don't care (and in fact don't know) who the hell Bob Jones is.<br />
<br />
If I buy a COMEX contract for December delivery of gold and it is cleared against a sell order by Karl Marx of Zimbabwe, I am not exposed to Karl Marx's bankruptcy. COMEX will make delivery of the gold '''all the time''', and if it doesn't COMEX itself is in default. This is the one and only reason why I don't care (and in fact don't know) who the hell Karl Marx is.<br />
<br />
Note that this is in stark contrast, to, say, credit default swaps which are not centrally cleared. And, in fact, note that there is no credit default swap exchange since CDS don't have a central counterparty. A CDS is always a direct transaction between two parties; the identity of the other party is always known and in fact ''who'' the counterparty is has a massive effect on the value of the CDS.<br />
<br />
Stop vandalizing the page with your marketing propaganda.<br />
<br />
[[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 23:10, 13 August 2013 (GMT)<br />
<br />
<br />
Your last three paragraphs are absolutely correct, and it happens same way on ICBIT! That is what I am trying to explain you for weeks.<br />
We do NOT bind futures contracts directly - e.g. you bought 1 contract from Friedrich Engels of South Africa, he went bankrupt and you did not get the money, and everyone else got their profit because they were lucky to make a deal with Karl Marx instead, who is more credible.<br />
<br />
So when you trade at ICBIT, you also do not care who the Karl Marx is. In ICBIT, your futures transaction 2nd party is always exchange (when you buy someone's order, there will be at least 2 transactions 1 buy and 1 sell, both of them will have same 2nd party - the exchange).<br />
<br />
Now take the example with COMEX and gold. It will make delivery of gold (same way as ICBIT delivers profit for contracts, pledging its own assets) and non-paying Karl Marx will be sued by banks/brokers, government enforcement agency will sell his car and house to cover losses.<br />
ICBIT allows anonymous trades, so to prevent default we have to employ various risk reducing strategies, however theoretically (what I am trying to get you to understand again!) COMEX can easily go default, ICBIT can easily go default and Hong Kong's exchange already went default (even though it was/is an exchange, not some gambling house).<br />
In that case, as it's explained on our webpage, we just pay as much as possible, close as much traders position as it's necessary and then traders are free to reopen them. This is because traders are anonymous, though we do reserve the right to pursue debtors.<br />
<br />
Is this finally clear, and could *you* please stop vandalizing the page? I see that you are not new to finances, however if you want to redefine what exchange is, what counterparty is - please go to Wikipedia instead. I'm not for marketing propoganda, I'm for facts.<br />
<br />
[[User:Fireball|Fireball]] ([[User talk:Fireball|talk]]) 11:57, 14 August 2013 (GMT)<br />
<br />
<br />
> Your last three paragraphs are absolutely correct,<br />
<br />
If that is true, point me to ICBIT's publicly-stated commitment that it pledges its own assets and equity to "make delivery of (the relevant asset) all the time, and if it doesn't ICBIT itself is in default" as I wrote in the second-to-last and third-to-last paragraphs. Until then the page stays the way it was. Don't revert it again. "We just pay as much as possible" is vague and useless; what matters is whether the exchange pledges its own assets and equity.<br />
<br />
[[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 07:04, 15 August 2013 (GMT)<br />
<br />
> The reference was and is there (https://bitcointalk.org/index.php?topic=50817.msg1402414#msg1402414), on the wiki page itself, which lets user read the original thread and make his opinion. So exchange does pledge the assets, and hence I restored the webpage.<br />
<br />
[[User:Fireball|Fireball]] ([[User talk:Fireball|talk]]) 23:31, 15 August 2013 (GMT)<br />
<br />
> The reference was and is there (https://bitcointalk.org/index.php?topic=50817.msg1402414#msg1402414), on the wiki page itself, which lets user read the original thread and make his opinion. So exchange does pledge the assets,<br />
<br />
What? You're not making any sense. That forum posting does not address the issue here.<br />
<br />
> and hence I restored the webpage.<br />
<br />
I have reported your repeated unconstructive edits to the wiki administrators.<br />
<br />
[[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 02:26, 16 August 2013 (GMT)<br />
<br />
If you are not able to understand what's written there, it's your problem, not a problem of users visiting this page. Your actions are harming the community. Look around, the only scam reports are from you and another guy who lost money trading and now blackmails me asking for 1/4 of "his" money to be back in exchange for not spamming this page and forums. Get out of your small world and look around, again. Do you want Bitcoin to succeed? Or you want to kill it, one by one? We really run an honest service for more than 2 years. We contribute to the Bitcoin economy. We work on it every day and every hour. Don't spoil the fun. Hopefully, it's my last message to you.<br />
<br />
[[User:Fireball|Fireball]] ([[User talk:Fireball|talk]]) 13:52, 24 August 2013 (GMT)<br />
<br />
I haven't posted anything about scam reports; I just revert your unjustified deletions. You are seriously confused. Take your nonsense elsewhere. Here's an idea: if you don't like the part about scam reports, how about '''removing only that part''' instead of huge chunks of unrelated text? Yeah, I know, that would be way too easy...<br />
<br />
[[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 02:40, 25 August 2013 (GMT)<br />
<br />
If you can find time for reverts, you could find time for editing, not just reverting. Anyway, I reverted it to the good version, BUT added a text that YOU dispute that ICBIT is not the central counterparty for all trades. And referenced this page so that anyone interested could read through this page and get their own impression.<br />
Because it's YOUR impression, and it must not be forced to EVERYONE reading the page. Readers should get their own impression. And wikipage must state facts, not a biased opinion of some stranger.<br />
The version of text now is as precise as it is. Your description is not correct because you mislead customers into thinking that they trade futures with each other, when in fact they are trading with the exchange (it's a simple fact that I am one of those people who built this exchange from the ground up, and thus I know its internals much better than you do)<br />
<br />
[[User:Fireball|Fireball]] ([[User talk:Fireball|talk]]) 12:38, 25 August 2013 (GMT)<br />
<br />
<br />
You work for ICBIT. I have no stake in its success or failure, nor am I in any way involved with any of its competitors or alternatives.<br />
<br />
[[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 12:45, 25 August 2013 (GMT)<br />
<br />
<br />
So why the hell did you revert proper version of the text, mentioning your dispute? I think you don't notice this line.<br />
<br />
[[User:Fireball|Fireball]] ([[User talk:Fireball|talk]]) 13:14, 25 August 2013 (GMT)<br />
<br />
<br />
I see that you have made your policy ''even more self-contradictory'' than it was before.<br />
<br />
Look, I've grown very tired of re-explaining what a counterparty is to you, but I'll mention one last thing. It seems like you're attempting in vain to come up with some policy that lets you force-close adequately-margined positions and still claim that you are the counterparty. This is totally impossible. If you're force-closing adequately-margined positions, the price used to force closure is not a market-determined price! You're shutting down the market (and perhaps letting it restart, but that's irrelevant) so whatever price you use to force-close is of your own choosing. You've robbed the asset holder of the ability to hold-to-maturity and take delivery. You might think the price you're offering them is fair compensation, but that's beside the point. Without the option to hold-to-maturity there is no way to determine the fair price.<br />
<br />
I know you really really really want there to be some magical way you can be an exchange and still retain the ability to force-close the positions of people who have adequate margin because other people (their COUNTERPARTIES) no longer have adequate margin. There is no such magic. So make your choice -- either pledge the exchange's assets+equity to back positions taken (not just whatever part of the position you claim to be "as much to profiting traders as loosing traders lost (in total)") or stop calling yourself an exchange. Putting your business itself on the hook, financially, for the full extent of all positions taken is the only way you can be trusted to run a sufficiently careful margin system, since you are the one exposed for failure to police margins. Reserving the right to dump that risk on your customers whenever you screwed up… well, you can do whatever you want, but there's a damn good reason why no real exchange does this.<br />
<br />
[[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 09:28, 26 August 2013 (GMT)<br />
<br />
<br />
Here is a [http://blogs.law.harvard.edu/corpgov/2011/07/17/an-introduction-to-the-us-cleared-swap-infrastructure/ really great article] explaining what central counterparty clearing is. It's being required for swaps markets in the USA starting in a few days, so seeing the sorts of changes that come with it give a good idea of what it entails. Most important part:<br />
<br />
<blockquote><br />
Guaranty of financial obligations. A DCO guaranties the financial integrity of all transactions that it has accepted. In the event that a clearing member’s customer defaults on its obligation to answer margin calls, it is the duty of that clearing member to satisfy its customer’s obligation, with a DCO satisfying any part of the default that exceeds the clearing member’s resources.<br />
</blockquote><br />
<br />
This is the essence of central counterparty clearing, and it's basically what the exchange gets paid to do. This stuff is 100% routine for all financial markets except swaps, and that's being changed as we speak.<br />
<br />
[[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 07:07, 28 September 2013 (GMT)<br />
<br />
Sorry Eldentyrell, you can't accept anything except your own vision. You can't even accept an unbiased, correct third-party explanation... I'm sorry about you. I guess you need to find some other place in the world which lives according to your vision.<br />
[[User:Fireball|Fireball]]<br />
<br />
<br />
Fireball, [https://en.bitcoin.it/wiki/ICBIT#cite_note-0 what you call an "unbiased correct third-party explanation"] actually agrees with me, writing "ICBIT it is not acting as a clearing house, nor is it the counterparty to the futures trades it brokers. There is no clearing house guarantee, and counterparty risk remains largely unknown.". So what are you talking about? Apparently you emailed whoever writes that blog with a rebuttal; the blogger posted your rebuttal and then <span style="background:#FF0000;color:white">'''you quoted the blogger quoting your rebuttal'''</span>. What planet are you from where quoting yourself is considered a third-party explanation? [[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 23:54, 28 September 2013 (GMT)<br />
<br />
<br />
This seems to be at a stalemate. I've put what I believe to be a fair compromise (not knowing the situation) locked for 2 weeks (thanks nanotube!) to let things cool down and hopefully you guys can come to some kind of agreement. Might I suggest scheduling a day/time to discuss the matter [http://webchat.freenode.net/?channels=#bitcoin-wiki on IRC]? (feel free to ping me by saying "luke-jr" if you need/want my attention) --[[User:Luke-jr|Luke-jr]] ([[User talk:Luke-jr|talk]]) 17:49, 30 September 2013 (GMT)<br />
<br />
I don't really IRC, but an email discussion would be great. I've sent an email to nanotube/luke-jr so they know how to reach me. I tried emailing the wiki admins six weeks ago to request intervention and nothing happened, which is why I had to resort to extreme measures. I'm very happy with Luke-jr's resolution of the page, except for the use of the word "exchange" in the first paragraph (where it is technically correct but very misleading since ICBIT's business is mainly futures) and the second paragraph (where it is definitely incorrect).<br />
[[User:Eldentyrell|Eldentyrell]] ([[User talk:Eldentyrell|talk]]) 22:58, 30 September 2013 (GMT)<br />
<br />
== Fireball, wanting money back that was taken through dishonest practices is not blackmail. ==<br />
<br />
If you are comfortable with the practices you engage in on your website, why don't you address some of the accusations that have been made against you and your site?<br />
<br />
1) Prices are blatantly manipulated through last clearing. The site encourages this, apparently because one or more site owners profit from it. A person expects prices to derive from movements in bitcoin, not overt manipulations. I have provided screenshots on the linked post below. <br />
<br />
2) People running the site use their access to client financial information to conduct trades running positions against those clients.<br />
<br />
For other observations refer to https://bitcointalk.org/index.php?topic=246845 which you have so far refused to even respond to. <br />
<br />
If you want to defend your practices either here or on the forum Fireball, please do so.<br />
<br />
No serious trader will stay on your site when they see the kinds of things you do. You are not running an honest financial exchange, you are running a scam built on keeping your clients in the dark about how you operate. <br />
<br />
I have made and lost a lot of money on financial exchanges in the last 30+ years and I have never in my life made any sort of complaint against any exchange until yours.<br />
<br />
<br />
<br />
[[User:FleaSpirit|FleaSpirit]] ([[User talk:FleaSpirit|talk]]) 16:41, 26 August 2013 (GMT)FleaSpirit<br />
<br />
=== The only solution ===<br />
<br />
Fireball, any time you want to end this nonsense, all you have to do is man up and admit you have made serious mistakes in running your site and those mistakes need to be fixed.<br />
<br />
Make things right then build a proper futures site or shut down. <br />
<br />
Your choice.<br />
<br />
[[User:FleaSpirit|FleaSpirit]] ([[User talk:FleaSpirit|talk]]) 19:22, 29 September 2013 (GMT)FleaSpirit</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=ICBIT&diff=45981ICBIT2014-04-05T23:44:55Z<p>Nanotube: Removed protection from "ICBIT"</p>
<hr />
<div>ICBIT is a trading website which runs a few markets. Both the USD/BTC exchange and Futures markets are live now, however the most active is the Futures market.<br />
<br />
== Counterparty risks ==<br />
The ICBIT site acts as the central intermediary for trades in futures contracts. It does not act as a final guarantor for the clearing process itself, with the results of the clearing process still ultimately dependent upon the counterparty risk exposure to other traders. Thus, the exchange does not act as a counterparty.<br />
<br />
In some cases, icbit may attempt to make up the difference using a margin call, but this is not guaranteed. The policy for this is explained on the [https://icbit.se/margincall ICBIT website].<br />
<br />
== Features ==<br />
For its currency exchange section ICBIT makes an accent on the following:<br />
* State-of-the-art technologies usage. Instead of using old, slow, polling-based algorithms ICBIT builds atop of the most up to date technologies. Its web trading client is in pure HTML and JavaScript (even compatible with most mobile devices), however it's fully realtime thanks to websockets and AJAX.<br />
* Speed of trading. Bitcoin forum is full of anger against slowness of existing exchanges. ICBIT implements special high performance trading engine and uses high-performance "no SQL" database to eliminate the problem.<br />
* No limits. Most of the existing exchanges put rather restrictive limitations and require users to prove their identity. ICBIT finds this totally unacceptable and does not put any limits at all.<br />
<br />
==Futures==<br />
Futures traded include:<br />
<br />
Futures contracts on USD/BTC rate<br />
* [https://icbit.se/BUQ3 BUQ3] (expires August 15, 2013, settled in BTC)<br />
* [https://icbit.se/BUU3 BUU3] (expires September 16, 2013, settled in BTC)<br />
* [https://icbit.se/BUV3 BUV3] (expires October 14, 2013, settled in BTC)<br />
* [https://icbit.se/BUZ3 BUZ3] (expires December 16, 2013, settled in BTC)<br />
<br />
Futures contract on Bitcoin difficulty<br />
* [https://icbit.se/DFU3 DFU3] (expires September 16, 2013, settled in BTC)<br />
* [https://icbit.se/DFZ3 DFZ3] (expires December 16, 2013, settled in BTC)<br />
<br />
Futures contract on LTC/BTC rate<br />
* [https://icbit.se/LBU3 LBU3] (expires September 17, 2013, settled in BTC)<br />
<br />
Futures contract on S&P500 index<br />
* [https://icbit.se/ESU3 ESU3] (expires September 16, 2013, settled in BTC)<br />
<br />
Settled futures:<br />
* [https://icbit.se/BUZ2 BUZ2] (Futures contract, expired December 15, 2012, settled in BTC)<br />
* [https://icbit.se/BUH3 BUH3] (Futures contract, expired March 15, 2013, settled in BTC)<br />
* [https://icbit.se/CLG3 CLG3] (Crude Oil Futures contract, expired February 14, 2013, settled and quoted in BTC)<br />
* [https://icbit.se/GDG3 GDG3] (Gold Futures contract, expired February 14, 2013, settled and quoted in BTC)<br />
<br />
==Exchange==<br />
Traded on the exchange are:<br />
<br />
* BTC/USD<br />
* BTC/RUB (Russian Ruble)<br />
<br />
<br />
==Depositing==<br />
<br />
Bitcoin: There is no fee for Bitcoin deposits to the account's BTC EWallet. Funds are added to the account's wallet after six (6) confirmations. Transactions made by [[DeepBit]] mining pool are added instantly.<br />
<br />
USD: There are no methods to add USD funds.<br />
<br />
RUB: QIWI vouchers can be used to add funds to an account's Russian ruble EWallet.<br />
<br />
<br />
==Withdrawing==<br />
<br />
BTC: There is no fee for Bitcoin withdrawals from the account's BTC EWallet.<br />
<br />
USD: There are no USD withdrawal methods.<br />
<br />
RUB: Funds can be withdrawn from the account's Russian ruble EWallet as QIWI vouchers.<br />
<br />
==Security==<br />
<br />
Accounts can be protected where both login and any money withdrawal operation requires the one-time password (OTP) feature known as two-step authentication. A mobile smartphone with Google Authenticator is the most commonly used OTP device.<br />
<br />
== History ==<br />
First mentions of ICBIT appeared in June and July 2011 in the Bitcoin Stock Exchange Security Standards thread at bitcointalk.org<ref>[https://bitcointalk.org/index.php?topic=20377.msg319099#msg319099 Bitcoin Stock Exchange Security Standards thread]</ref> and Bitcoin futures market discussion <ref>[https://bitcointalk.org/index.php?topic=15818.msg250391#msg250391 Fireball's statement about ongoing futures exchange work]</ref>. By that time a very first version of the trading engine was developed.<br />
<br />
A more detailed thread specific to ICBIT futures market was started <ref>[https://bitcointalk.org/index.php?topic=50817.msg605807#msg605807 ICBIT derivatives market thread]</ref> in November, 2011. The first closed test of futures market was performed, and work on the new version of web trading client was started.<br />
<br />
Finally in January, 2012 the currency exchange section went live <ref>[https://bitcointalk.org/index.php?topic=60548.0 Bitcointalk announcement of a new exchange live testing]</ref><br />
<br />
== Criticism ==<br />
−''''' There have been complaints about several core practices at icbit.'''''−<br />
<br />
-The primary complaint involves contract price manipulations that allow larger traders, including the site owner, to make profits from smaller traders regardless of bitcoin price movements. <br />
<br />
The first comprehensive post questioning various practices at icbit is https://bitcointalk.org/index.php?topic=125376.0<br />
<br />
Examples of contract manipulations, including screenshots, is included in some complaints, including https://bitcointalk.org/index.php?topic=246845<br />
<br />
Complaints directed to the owner of icbit, who also is the principle contributor to this wiki page, include https://bitcointalk.org/index.php?topic=173928.0<br />
<br />
−'''Any potential investor should thoroughly understand the issues raised in the complaints. If you are not sure please ask questions in a public forum like bitcointalk.org and do not invest until all questions are answered to your satisfaction.'''−<ref>[http://trilema.com/2012/icbitse-the-bucket-shop/ Article by Mircea Popescu, proprietor of MPEx]</ref> <ref>[https://bitcointalk.org/index.php?topic=173928.0]</ref> <ref>[https://bitcointalk.org/index.php?topic=125376.0 Bitcointalk "bucket shop" thread]</ref> <ref>[https://bitcointalk.org/index.php?topic=246845 Bitcointalk "icbit warning" thread]</ref><br />
<br />
ICBIT is a trading website which runs a few markets. Both the Exchange and Futures markets are live now.<br />
<br />
'''ICBIT is not an exchange''' since it does not act as a central counterparty. [http://web.archive.org/web/20130510221928/https://icbit.se/margincall According to their website] users '''are totally exposed to counterparty risk from other traders''' whose identities are concealed from them; the exchange does not pledge its own assets to back the full extent of the other side of a customer's position -- it pledges only "as much to profiting traders as loosing traders lost (in total)". Traders are not allowed to conduct background or reputation checks of any kind on these anonymous counterparties. ICBIT recently modified the linked page and it '''now contains self-contradictory information,''' such as "we do pledge our own assets, it's not always the case" and "your profitable position will be closed" at whatever price the exchange deems convenient rather than value-at-maturity. Since the exchange pledges only "as much to profiting traders as loosing traders lost (in total)" it is, by definition, not the [http://en.wikipedia.org/wiki/Counterparty counterparty] -- the "loosing [sic] traders" are the counterparty.<br />
<br />
A third party's blogger's assessment<ref>http://psychologicalinvestor.com/lib/real-markets/bitcoin-derivatives-liquidity-counterparty-risk-134/</ref> of the situation is that "ICBIT it is not acting as a clearing house, nor is it the counterparty to the futures trades it brokers. There is no clearing house guarantee, and counterparty risk remains largely unknown." The aforementioned blog also contains a rebuttal from ICBIT.<br />
<br />
This site is said<sup>[source?]</sup> to be founded by Fireball and [[DeepBit]] by combining best practices in high-performance trading and Bitcoin experience.<br />
<br />
At one point in the past, somebody who goes by the identifier "Fireball" [https://bitcointalk.org/index.php?topic=50817.msg1402414#msg1402414 voluntarily took the took one "bad customers" debt]. Fireball is believed to be the owner of icbit and the principle contributor to this wiki page. He is alleged to have a history of 'refunding' bitcoin when there is a threat that improper practices may be exposed. See http://trilema.com/2012/icbitse-the-bucket-shop/ and then note the post at https://bitcointalk.org/index.php?topic=140484.0 which was apparently made after Fireball returned "~500 BTC".<br />
<br />
==See Also==<br />
<br />
* [[Buying bitcoins]]<br />
* [[Selling bitcoins]]<br />
<br />
== External Links ==<br />
* [https://icbit.se ICBIT] website.<br />
* [https://icbit.se/WebTrade/ Trading client] Direct link to the web trading client logon.<br />
<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Exchanges]]<br />
[[Category:Stock_Exchanges]]<br />
[[Category:Bonds_Markets]]<br />
[[Category:Futures_Exchanges]]<br />
[[Category:Investing]]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Issue_Tracker&diff=45448Bitcoin Wiki:Issue Tracker2014-03-27T00:46:56Z<p>Nanotube: issue resolved by clearing cache.</p>
<hr />
<div>This page serves as the Wiki issue tracker. <br />
<br />
To file a new issue, add a second-level heading (==), and describe your issue in detail.<br />
<br />
Issue discussion should happen on the Talk page.<br />
<br />
Do not delete resolved issues unless you are a wiki administrator, or the creator of the issue.<br />
<br />
==Insert first issue here==</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Contact&diff=45447Bitcoin Wiki:Contact2014-03-27T00:45:55Z<p>Nanotube: create contacts page</p>
<hr />
<div>To get help with a wiki issue, the following avenues are suggested:<br />
* Post a thread on the [https://bitcointalk.org/index.php?board=168.0 BitcoinTalk Wiki subforum]<br />
* Join us on {{Freenode IRC|bitcoin-wiki}} IRC channel on Freenode</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Help&diff=45446Bitcoin Wiki:Help2014-03-27T00:38:13Z<p>Nanotube: Separate wiki help from bitcoin help</p>
<hr />
<div>{{stub}}<br />
<br />
{{Help navbar}}<br />
<br />
__NOTOC__<br />
<br />
{| cellspacing="0" cellpadding="0" align="center" style="width:100%; border:2px #a3b1bf solid; background:#f5faff; text-align:center;" <br />
|-<br />
|colspan="2" align="center" style="background:#cee0f2; border-bottom:1px #a3b1bf solid;" |<div style="position:relative;"><div style="position:absolute; right:0px; top:30px;"></div></div><br />
<h2 style="margin:.5em; margin-top:.1em; margin-bottom:.1em; border-bottom:0; font-weight:bold;">Wiki Help</h2><br />
|-<br />
<!-- ROW 1 --><br />
<!-- LEFT COLUMN --><br />
| align="center" style="width:50%; padding:15px 2% 5px 2%;" valign="top"|<br />
<span style="font-size: 140%;">[[Wiki Help Contacts]]</span><br /><br />
Points of contact for help with this wiki.<br />
<!-- RIGHT COLUMN --><br />
| align="center" style="width:50%; padding:15px 2% 5px 2%;;" valign="top"|<br />
<span style="font-size: 140%;">[http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Manual of Style]</span><br /><br />
How to format and organizes pages and text.<br />
|-<br />
<!-- ROW 2 --><br />
<!-- LEFT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top"|<br />
<span style="font-size: 140%;">[http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Cheatsheet]</span><br /><br />
A sheet of many simple and common wikicode examples.<br />
<!-- RIGHT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top"|<br />
<span style="font-size: 140%;">[http://en.wikipedia.org/wiki/Wikipedia:Images Images]</span><br /><br />
Using and formatting images<br />
|-<br />
<!-- ROW 3 --><br />
<!-- LEFT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top"|<br />
<span style="font-size: 140%;">[[Help:Group_rights|Administrators]]</span><br /><br />
A list of staff members on the Bitcoin Wiki<br />
<!-- RIGHT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top" |<br />
<span style="font-size: 140%;">[http://en.wikipedia.org/wiki/Help:Table Tables]</span><br /><br />
Help with formatting tables<br />
|}<br />
<br />
<br />
<br />
{| cellspacing="0" cellpadding="0" align="center" style="width:100%; border:2px #a3b1bf solid; background:#f5faff; text-align:center;" <br />
|-<br />
|colspan="2" align="center" style="background:#cee0f2; border-bottom:1px #a3b1bf solid;" |<div style="position:relative;"><div style="position:absolute; right:0px; top:30px;"></div></div><br />
<h2 style="margin:.5em; margin-top:.1em; margin-bottom:.1em; border-bottom:0; font-weight:bold;">Bitcoin Help</h2><br />
|-<br />
<!-- ROW 1 --><br />
<!-- LEFT COLUMN --><br />
| align="center" style="width:50%; padding:15px 2% 5px 2%;" valign="top"|<br />
<span style="font-size: 140%;">[[Getting started]]</span><br /><br />
Getting started with using Bitcoin<br />
<!-- RIGHT COLUMN --><br />
| align="center" style="width:50%; padding:15px 2% 5px 2%;" valign="top" |<br />
<span style="font-size: 140%;">[[Introduction|Bitcoin Introduction]]</span><br /><br />
An introduction to Bitcoins and how they work<br />
|-<br />
<!-- ROW 2 --><br />
<!-- LEFT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top"|<br />
<span style="font-size: 140%;">[[FAQ|Frequently Asked Questions]]</span><br /><br />
Questions asked and answered<br />
<!-- RIGHT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top" |<br />
<span style="font-size: 140%;">[[:Category:Economics|Economics]]</span><br /><br />
The economics of bitcoins<br />
|-<br />
<!-- ROW 3 --><br />
<!-- LEFT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top"|<br />
<span style="font-size: 140%;">[[IRC channels]]</span><br /><br />
Channels for using IRC to communicate and trade<br />
<!-- RIGHT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top" |<br />
<span style="font-size: 140%;">[[:Category:Mining|Mining]]</span><br /><br />
An introduction to Bitcoin mining<br />
|-<br />
<!-- ROW 4 --><br />
<!-- LEFT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top"|<br />
<span style="font-size: 140%;">[[:Category:Technical|Technical Pages]]</span><br /><br />
Additional information regarding the technical details of Bitcoins<br />
<!-- RIGHT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top" |<br />
<br />
|-<br />
<!-- BOTTOM ROW --><br />
|-<br />
| align="center" colspan="2" style="padding:10px 2% 3px 2%;" |<br />
[[Help:Contents/Expanded|Expanded Selection]]<br />
|-<br />
| align="center" colspan="2" style="border-top:1px solid #cedff2; padding:0px 2% 3px 2%;" |<br />
<br />
|}</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Group_rights&diff=45445Bitcoin Wiki:Group rights2014-03-27T00:22:22Z<p>Nanotube: link to automatic group lists</p>
<hr />
<div>__NOTOC__<br />
<br />
This page documents users with elevated privileges here on the Bitcoin Wiki<br />
<br />
'''Note:''' All editors' contributions are constantly evaluated, so there is no application process for elevated privileges. <br />
<br />
==Bureaucrats==<br />
Users who have all administrator abilities, as well as the ability to promote/demote users.<br />
<br />
[https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=bureaucrat list of bureaucrats]<br />
<br />
==Content Administrators==<br />
Users with extended moderator abilities.<br />
<br />
[https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=sysop list of administrators]<br />
<br />
==Bots==<br />
Semi-automated bots designed to reduce edit load. Edits by bots will not appear in the [[Special:RecentChanges|Recent Changes]] feed by default.<br />
<br />
[https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=bot list of bots]</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Issue_Tracker&diff=45444Bitcoin Wiki:Issue Tracker2014-03-27T00:08:03Z<p>Nanotube: create issue tracker</p>
<hr />
<div>This page serves as the Wiki issue tracker. <br />
<br />
To file a new issue, add a second-level heading (==), and describe your issue in detail.<br />
<br />
Issue discussion should happen on the Talk page.<br />
<br />
Do not delete resolved issues unless you are a wiki administrator, or the creator of the issue.<br />
<br />
==History view while not logged in==<br />
<br />
Reported via IRC:<br />
<br />
<topynate> i'm getting unusual behaviour trying to view the history for Script at https://en.bitcoin.it/w/index.php?title=Script&action=history while logged-out-<br />
<topynate> it redirects me to a page-not-found in spanish<br />
<topynate> well, not exactly. i see a standard "no history" page in spanish<br />
<nanotube> topynate: i can confirm, seeing the same behavior.</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=CryptoPayment&diff=45415CryptoPayment2014-03-26T04:09:13Z<p>Nanotube: note current fee amount</p>
<hr />
<div>'''CryptoPayment''' is a MediaWiki extension to limit spam by requiring a small one-time bitcoin payment before a user is allowed to edit or create pages. While the payment is deliberately small for a normal user, it presents a barrier to a mass-spammer. Funds sent to this Wiki will be used offset moderate expenses (hosting, DDoS protection, security maintenance). If any money is remaining it will go toward funding Bitcoin development.<br />
<br />
==Usage==<br />
<br />
In order to enable your user account to edit pages, log in and visit [[Special:CryptoPayment]], and you'll be given an address to which to send a small amount of bitcoins. The current fee amount is 0.001 BTC, which is presently less than 1 USD.<br />
<br />
Once you send the requested bitcoin amount to the address displayed and your payment is confirmed, your account will automatically be added to the [https://en.bitcoin.it/w/index.php?title=Special:ListUsers&group=trusted trusted group] and be afforded edit privileges.<br />
<br />
===Confirmations===<br />
<br />
Payments will be considered paid after it is confirmed in a Bitcoin block.<br />
<br />
==Privacy==<br />
<br />
Note that this may allow adversaries to connect your bitcoin wallet to your wiki account via blockchain analysis. If this is a concern to you, take the appropriate steps to protect your [[Anonymity]].<br />
<br />
== Code ==<br />
Source will be released after the backend interface to bitcoind is rewritten.<br />
<br />
==Questions or comments?==<br />
<br />
If you have questions, comments or a support request, please post in the [https://bitcointalk.org/index.php?board=168.0 Bitcoin Wiki Support forum]. We also have a chatroom at [http://webchat.freenode.net/?channels=#bitcoin-wiki #bitcoin-wiki on freenode IRC]. Please ask your question and be prepared to stick around for a few hours before you get a response.</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Talk:CryptoPayment&diff=45414Talk:CryptoPayment2014-03-26T04:07:15Z<p>Nanotube: update fee amount, which is actually 0.001</p>
<hr />
<div>==Fee Reduced to 0.001 as of 22 March 2014==<br />
Per the Bitcoin protocol rules, be sure that you include at least a fee of 0.0001 to ensure that this payment will eventually be mined.<br />
<br />
==Amount reduction==<br />
<br />
As the value of BC rose, I propose to reduce the amount.<br />
<br />
0.01BTC is a day's salary in certain countries. And why are you waiting for 6 confirmations if this measure is really only a spam barrier?<br />
21:15, 22 April 2013 (GMT)<br />
<br />
:: This was made back when the price of BTC was in the low two digits. :) Yes payment amount could be reduced, but then you'd have to pay 0.0005 BTC fee for sending < 0.01. <br />
:: Also, 6 conf is required since this uses the MtGox payment processing API, which requires 6 conf. Not really worth it to special-case it. [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 13:47, 30 April 2013 (GMT)<br />
<br />
:: To this day, the editing fee is worth 5€ or 5.5$. I already contacted MagicalTux, and posted on Bitcointalk.org (got flamed btw) while BTC was around $100, and I see that the problem is not yet answered. Thanks you MagicalTux for preventing this wiki to gain content and active users ! --[[User:Twix|Twix]] ([[User talk:Twix|talk]]) 22:59, 19 November 2013 (GMT)<br />
<br />
== Require payment for new user creation ==<br />
<br />
I believe that a payment is required on each new user creation, not just in order to gain edit powers.<br />
Currently a new spam user is created every few minutes, and the [[Special:RecentChanges|Recent Changes]] page has become completely spammed.<br />
<br />
[[User:Ripper234|Ripper234]] ([[User talk:Ripper234|talk]]) 10:54, 30 April 2013 (GMT)<br />
<br />
:: Payment is only required to activate edit privileges, hence the flood of spam users. but it's not a bad idea to have it be required for user creation too, to avoid that spam. The problem is that it'd require more development, and mtux doesn't really have time to do this for the wiki right now. <br />
:: In the meantime as a quick hack, you can just filter the recent changes list to exclude everything from the User namespace. [https://en.bitcoin.it/w/index.php?namespace=2&invert=1&title=Special%3ARecentChanges try this]. It's not perfect, since it also excludes user page edits... but it's good. :) [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 13:44, 30 April 2013 (GMT)<br />
<br />
== Informing new users ==<br />
<br />
It's not very clear right now that people need to visit this page to learn how to contribute. I didn't find out until I was reading through some questions on StackExchange, saw somebody someone ask why he couldn't edit.<br />
<br />
I know there's a line on the front page in font-size 10 saying "Anti-spam protection from BitcoinPayment", but people unfamliar with BitcoinPayment will not notice that. When they don't see an edit button they're likely to assume that you either need to wait for manual approval or that you need to know the right people within the community.<br />
<br />
It's been ages since I tried to write code for MediaWiki, so I don't know if on of the following suggestions is possible:<br />
<br />
* don't hide the edit link, but instead redirect the user to this page for instructions<br />
* next to the "Show source" link, show "Want to contribute?"<br />
<br />
Or this solution, which doesn't require code:<br />
* put a text like "If you want to contribute, please read these instructions" in a very prominent place on the landing page.<br />
<br />
<br />
: You're completely right, I was thinking the same thing for a long time. I don't know how to implement it - I just asked it on [http://webapps.stackexchange.com/questions/44319/can-a-mediawiki-moderator-put-a-system-message-for-each-new-user webapps Stackexchange]. If you know of a good way to implement that without having access to the backened/php, let us know. [[User:Ripper234|Ripper234]] ([[User talk:Ripper234|talk]]) 15:44, 17 May 2013 (GMT)<br />
<br />
:: We have edited the "no permission" message to point to BitcoinPayment. Also note that the login screen has had the prominent orange banner mentioning the requirement for BitcoinPayment all this time, also. I suppose "ideally" any user who is not trusted should get a persistent banner in the header or something, but that requires editing on the backend. [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 03:47, 24 May 2013 (GMT)<br />
<br />
::: Can we change "View Source" to "Edit" so new users actually get to the explanation screen? --[[User:Luke-jr|Luke-jr]] ([[User talk:Luke-jr|talk]]) 04:55, 25 May 2013 (GMT)</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Talk:Meetups&diff=45413Talk:Meetups2014-03-26T04:05:11Z<p>Nanotube: yes to cut stale data</p>
<hr />
<div>==Stale meetups==<br />
<br />
Is this page supposed to be an archive of meetups that have occurred or upcoming meetups? I'd like to purge old events if its for upcoming meetups. Some of the data is pretty stale. [[User:Imsaguy|Imsaguy]] ([[User talk:Imsaguy|talk]]) 02:12, 26 March 2014 (UTC)<br />
: I'd vote to cut the old one-off events that have already happened, to keep this page more useful for finding ongoing meetups. [[User:Nanotube|Nanotube]] ([[User talk:Nanotube|talk]]) 04:05, 26 March 2014 (UTC)</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Main_Page&diff=45343Main Page2014-03-25T02:47:35Z<p>Nanotube: guess the languages don't autopopulate from the sidebar template >_></p>
<hr />
<div>{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"<br />
| style="width:61%; color:#000;" |<br />
<!-- "WELCOME TO BITCOIN" AND ARTICLE COUNT --><br />
{| style="width:100%; border:none; background:none;"<br />
| style="text-align:center; white-space:nowrap; color:#000;" |<br />
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] wiki,</div><br />
<div style="top:+0.2em; font-size:95%;">For all your Bitcoin information needs.</div><br />
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles. Anti-spam protection from [[Special:CryptoPayment]]</div><br />
'''[[:Category:Stubs|This wiki]] is maintained by the Bitcoin community.'''<br />
|}<br />
<!-- PORTAL LIST ON RIGHT-HAND SIDE --><br />
| style="width:13%; font-size:120%;" |<br />
* <span class="plainlinks">[http://bitcoin.org Frontpage]</span><br />
| style="width:13%; font-size:120%;" |<br />
* <span class="plainlinks">[[Forums]]</span><br />
| style="width:13%; font-size:120%; padding-right: 40px;" |<br />
* <span class="plainlinks">[[IRC channels|Chatrooms]]</span><br />
|}<br />
<br />
<!-- TODAY'S FEATURED ARTICLE; DID YOU KNOW --><br />
{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"<br />
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div><br />
|-<br />
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why</h2><br />
|-<br />
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div><br />
|}<br />
| style="border:1px solid transparent;" |<br />
<!-- IN THE NEWS; ON THIS DAY --><br />
| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"<br />
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2><br />
|-<br />
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div><br />
|-<br />
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2><br />
|-<br />
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div><br />
|}<br />
|}<br />
<br />
<br />
== Other pages ==<br />
<br />
* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.<br />
* '''[[Bitcoin.it Wiki|About]]''' - Information on this site.<br />
* '''[http://dump.bitcoin.it/ Dumps]''' Backup this wiki.<br />
[[de:Hauptseite]]<br />
[[es:Página Principal]]<br />
[[fr:Accueil]]<br />
[[he:עמוד ראשי]]<br />
[[it:Pagina principale]]<br />
[[pl:Strona główna]]<br />
[[ru:Заглавная страница]]<br />
[[zh-cn:首页]]<br />
[[ro:Pagina principală]]<br />
<br />
__NOTOC____NOEDITSECTION__</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Main_Page&diff=45342Main Page2014-03-25T02:45:23Z<p>Nanotube: clean up a bit</p>
<hr />
<div>{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"<br />
| style="width:61%; color:#000;" |<br />
<!-- "WELCOME TO BITCOIN" AND ARTICLE COUNT --><br />
{| style="width:100%; border:none; background:none;"<br />
| style="text-align:center; white-space:nowrap; color:#000;" |<br />
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] wiki,</div><br />
<div style="top:+0.2em; font-size:95%;">For all your Bitcoin information needs.</div><br />
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles. Anti-spam protection from [[Special:CryptoPayment]]</div><br />
'''[[:Category:Stubs|This wiki]] is maintained by the Bitcoin community.'''<br />
|}<br />
<!-- PORTAL LIST ON RIGHT-HAND SIDE --><br />
| style="width:13%; font-size:120%;" |<br />
* <span class="plainlinks">[http://bitcoin.org Frontpage]</span><br />
| style="width:13%; font-size:120%;" |<br />
* <span class="plainlinks">[[Forums]]</span><br />
| style="width:13%; font-size:120%; padding-right: 40px;" |<br />
* <span class="plainlinks">[[IRC channels|Chatrooms]]</span><br />
|}<br />
<br />
<!-- TODAY'S FEATURED ARTICLE; DID YOU KNOW --><br />
{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"<br />
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div><br />
|-<br />
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why</h2><br />
|-<br />
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div><br />
|}<br />
| style="border:1px solid transparent;" |<br />
<!-- IN THE NEWS; ON THIS DAY --><br />
| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"<br />
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2><br />
|-<br />
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div><br />
|-<br />
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2><br />
|-<br />
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div><br />
|}<br />
|}<br />
<br />
<br />
== Other pages ==<br />
<br />
* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.<br />
* '''[[Bitcoin.it Wiki|About]]''' - Information on this site.<br />
* '''[http://dump.bitcoin.it/ Dumps]''' Backup this wiki.<br />
<br />
<br />
__NOTOC____NOEDITSECTION__</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=MediaWiki:Badaccess-groups&diff=45341MediaWiki:Badaccess-groups2014-03-25T02:42:51Z<p>Nanotube: update link to cryptopayment</p>
<hr />
<div>{{#ifeq: $1 | Trusted users | Editing wiki pages requires anti-spam verification using [[CryptoPayment]]. | The action you have requested is limited to users in {{PLURAL:$2|the group|one of the groups}}: $1. }}</div>Nanotubehttps://en.bitcoin.it/w/index.php?title=Main_Page&diff=45340Main Page2014-03-25T02:11:22Z<p>Nanotube: link to he wiki</p>
<hr />
<div>{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"<br />
| style="width:61%; color:#000;" |<br />
<!-- "WELCOME TO BITCOIN" AND ARTICLE COUNT --><br />
{| style="width:100%; border:none; background:none;"<br />
| style="text-align:center; white-space:nowrap; color:#000;" |<br />
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] wiki,</div><br />
<div style="top:+0.2em; font-size:95%;">For all your Bitcoin information needs.</div><br />
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles. Anti-spam protection from [[Special:Cryptopayment]]</div><br />
'''[[:Category:Stubs|This wiki]] is maintained by the Bitcoin community.'''<br />
|}<br />
<!-- PORTAL LIST ON RIGHT-HAND SIDE --><br />
| style="width:13%; font-size:120%;" |<br />
* <span class="plainlinks">[http://bitcoin.org Frontpage]</span><br />
| style="width:13%; font-size:120%;" |<br />
* <span class="plainlinks">[[Forums]]</span><br />
| style="width:13%; font-size:120%; padding-right: 40px;" |<br />
* <span class="plainlinks">[[IRC channels|Chatrooms]]</span><br />
|}<br />
<br />
<!-- TODAY'S FEATURED ARTICLE; DID YOU KNOW --><br />
{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"<br />
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div><br />
|-<br />
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why</h2><br />
|-<br />
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div><br />
|}<br />
| style="border:1px solid transparent;" |<br />
<!-- IN THE NEWS; ON THIS DAY --><br />
| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"<br />
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2><br />
|-<br />
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div><br />
|-<br />
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2><br />
|-<br />
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div><br />
|}<br />
|}<br />
<br />
<br />
== Other pages ==<br />
<br />
* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.<br />
* '''[[Bitcoin.it Wiki|About]]''' - Information on this site.<br />
* '''[http://dump.bitcoin.it/ Dumps]''' Backup this wiki.<br />
[[de:Hauptseite]]<br />
[[es:Página Principal]]<br />
[[fr:Accueil]]<br />
[[he:עמוד ראשי]]<br />
[[it:Pagina principale]]<br />
[[pl:Strona główna]]<br />
[[ru:Заглавная страница]]<br />
[[zh-cn:首页]]<br />
[[ro:Pagina principală]]<br />
<br />
__NOTOC____NOEDITSECTION__</div>Nanotube