https://en.bitcoin.it/w/api.php?action=feedcontributions&user=Firestorm&feedformat=atomBitcoin Wiki - User contributions [en]2024-03-19T13:12:38ZUser contributionsMediaWiki 1.30.0https://en.bitcoin.it/w/index.php?title=User_talk:Nanotube&diff=13356User talk:Nanotube2011-07-21T16:40:25Z<p>Firestorm: /* Help Page */</p>
<hr />
<div>Hi Nanotube,<br />
can you please delete [[Mining pool reward FAQ]]? I created it to provide information about some commonly confused issues, but it's being abused and thus can't serve this purpose. [[User:Holy-Fire|Holy-Fire]] 18:43, 26 May 2011 (GMT)<br />
: I removed the troublesome content and left it to-the-point. This should serve to remove any abuse. --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 18:51, 26 May 2011 (GMT)<br />
::Sorry, it really doesn't, see my comment on your talk page. [[User:Holy-Fire|Holy-Fire]] 19:08, 26 May 2011 (GMT)<br />
:::posted my comments on firestorm's user talk page and the faq-page talk page. https://en.bitcoin.it/wiki/Talk:Mining_pool_reward_FAQ<br />
<br />
==Help Page==<br />
<br />
Hello, Nanotube. I've created a fairly simple [[Help:Contents|Help page]] that I'm going to be expanding over time. Would it be a good idea to link to this in the sidebar? --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 14:46, 30 May 2011 (GMT)<br />
: add it as "Wiki Help", you think?--[[User:Nanotube|Nanotube]] 16:44, 30 May 2011 (GMT)<br />
:: Just "Help" should be fine. I'll collaborate links to various FAQs and help pages regarding Bitcoin itself. I hope to make it the resource to go to if you need information on anything --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 17:06, 30 May 2011 (GMT)<br />
::: How's the page looking? --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 05:19, 1 June 2011 (GMT)<br />
:::: Looking good to me. :) Sorry for delay in response, been busy. --[[User:Nanotube|Nanotube]] 03:11, 30 June 2011 (GMT)<br />
::::: Could you add it to the sidebar, then? I think it would be more useful than the FAQ --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 16:40, 21 July 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=User_talk:Giner&diff=9643User talk:Giner2011-06-03T14:22:14Z<p>Firestorm: Created page with "{{subst:sp}}--~~~~"</p>
<hr />
<div>[[File:Information.png|25px]] Please make use of the '''Show preview''' button. It gives you a preview of the edit you make, allowing you to perfect it before you save the page.--[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 14:22, 3 June 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=User_talk:Nanotube&diff=9434User talk:Nanotube2011-06-01T05:19:59Z<p>Firestorm: /* Help Page */</p>
<hr />
<div>Hi Nanotube,<br />
can you please delete [[Mining pool reward FAQ]]? I created it to provide information about some commonly confused issues, but it's being abused and thus can't serve this purpose. [[User:Holy-Fire|Holy-Fire]] 18:43, 26 May 2011 (GMT)<br />
: I removed the troublesome content and left it to-the-point. This should serve to remove any abuse. --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 18:51, 26 May 2011 (GMT)<br />
::Sorry, it really doesn't, see my comment on your talk page. [[User:Holy-Fire|Holy-Fire]] 19:08, 26 May 2011 (GMT)<br />
:::posted my comments on firestorm's user talk page and the faq-page talk page. https://en.bitcoin.it/wiki/Talk:Mining_pool_reward_FAQ<br />
<br />
==Help Page==<br />
<br />
Hello, Nanotube. I've created a fairly simple [[Help:Contents|Help page]] that I'm going to be expanding over time. Would it be a good idea to link to this in the sidebar? --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 14:46, 30 May 2011 (GMT)<br />
: add it as "Wiki Help", you think?--[[User:Nanotube|Nanotube]] 16:44, 30 May 2011 (GMT)<br />
:: Just "Help" should be fine. I'll collaborate links to various FAQs and help pages regarding Bitcoin itself. I hope to make it the resource to go to if you need information on anything --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 17:06, 30 May 2011 (GMT)<br />
::: How's the page looking? --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 05:19, 1 June 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Help&diff=9433Bitcoin Wiki:Help2011-06-01T05:16:28Z<p>Firestorm: </p>
<hr />
<div>{{stub}}<br />
<br />
{{Help navbar}}<br />
<br />
__NOTOC__<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%;">[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: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%;">[http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Manual of Style]</span><br /><br />
How to format and organizes pages and text.<br />
<!-- RIGHT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top" |<br />
<span style="font-size: 140%;">[[Getting started]]</span><br /><br />
Getting started with using Bitcoin<br />
|-<br />
<!-- ROW 3 --><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/Help:Table Tables]</span><br /><br />
Help with formatting tables<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 4 --><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%;">[[FAQ|Frequently Asked Questions]]</span><br /><br />
Questions asked and answered<br />
|-<br />
<!-- ROW 5 --><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:Images Images]</span><br /><br />
Using and formatting images<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 6 --><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%;">[[:Category:Technical|Technical Pages]]</span><br /><br />
Additional information regarding the technical details of Bitcoins<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>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Help/Expanded&diff=9431Bitcoin Wiki:Help/Expanded2011-06-01T05:10:27Z<p>Firestorm: Created page with "__NOTOC__ {{columns |bgcol = #FFCCBB |colwidth = 100em |col1 = =Wiki Help= == Editing Articles == *Cheatsheet *[[Wikipedia:Help:Links#..."</p>
<hr />
<div>__NOTOC__<br />
{{columns<br />
|bgcol = #FFCCBB<br />
|colwidth = 100em<br />
|col1 = <br />
<br />
=Wiki Help=<br />
== Editing Articles ==<br />
*[[Wikipedia:Wikipedia:Cheatsheet|Cheatsheet]]<br />
*[[Wikipedia:Help:Links#Wikilinks|How to make links]]<br />
*[[Wikipedia:Help:Table#Pipe_syntax_tutorial|Using tables]]<br />
**[[Wikipedia:Wikipedia:Collapsible_tables|Using Collapsible tables]]<br />
* [[Help:Using ToDo Lists|Using ToDo lists]]<br />
<br />
== Wiki Resources and lists ==<br />
*[http://www.mediawiki.org/wiki/Help:Tracking_changes Keeping track of changes]<br />
*[http://www.mediawiki.org/wiki/Help:Contents User help on MediaWiki]<br />
*[[Wikipedia:Wikipedia:Manual_of_Style|Manual of style]]<br />
**[[Wikipedia:Wikipedia:Naming conventions|Naming conventions]]<br />
**[[Wikipedia:Wikipedia:Guide to layout|Guide to layout]]<br />
*[[IRC channels]]<br />
<br />
|col2 = <br />
=Bitcoin Help=<br />
== Client Help ==<br />
* [[Introduction]]<br />
* [[Getting started]]<br />
* [[Securing your wallet]]<br />
* [[FAQ|General Frequently Asked Questions]]<br />
* [[Secure Trading|Best practices for traders]]<br />
* [[:Category:Clients|Clients]]<br />
* [[:Category:Exchanges|Exchanges]]<br />
* [[Trade|Bitcoin-accepting sites]]<br />
* [[Myths]]<br />
* [[Meetups]]<br />
* [[Transaction fees]]<br />
<br />
== Mining Help==<br />
* [[:Category:Mining|Mining]]<br />
* [[:Category:Mining contractors|Where to rent Mining services]]<br />
* [[Pooled mining]]<br />
* [[Mining hardware comparison]]<br />
<br />
== Technical Resources ==<br />
* [[PHP developer intro]]<br />
* [[API reference (JSON-RPC)]]<br />
* [[Protocol specification]]<br />
* [[Press|Press coverage]]<br />
* [[:Category:Technical|More technical articles]]<br />
<br />
== Markets and Trading ==<br />
* [[:Category:Economics|Economics]]<br />
* [[:Category:Marketing|Marketing resources]]<br />
* [[Donation-accepting_organizations_and_projects|Donation-accepting sites]]<br />
}}</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Help&diff=9430Bitcoin Wiki:Help2011-06-01T05:10:26Z<p>Firestorm: Work in progress</p>
<hr />
<div>{{stub}}<br />
<br />
{{Help navbar}}<br />
<br />
__NOTOC__<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%;">[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:15px 2% 5px 2%;" valign="top" |<br />
<span style="font-size: 140%;">[[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%;">[http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style Manual of Style]</span><br /><br />
How to format and organizes pages and text.<br />
<!-- RIGHT COLUMN --><br />
| align="center" style="width:50%; padding:5px 2%;" valign="top" |<br />
<span style="font-size: 140%;">[[Getting started]]</span><br /><br />
Getting started with using Bitcoin<br />
|-<br />
<!-- ROW 3 --><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/Help:Table Tables]</span><br /><br />
Help with formatting tables<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 4 --><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%;">[[FAQ|Frequently Asked Questions]]</span><br /><br />
Questions asked and answered<br />
|-<br />
<!-- ROW 5 --><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:Images Images]</span><br /><br />
Using and formatting images<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 6 --><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%;">[[:Category:Technical|Technical Pages]]</span><br /><br />
Additional information regarding the technical details of Bitcoins<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>Firestormhttps://en.bitcoin.it/w/index.php?title=User_talk:Mattpker&diff=9423User talk:Mattpker2011-06-01T04:29:09Z<p>Firestorm: Created page with "{{Subst:sp}}--~~~~"</p>
<hr />
<div>[[File:Information.png|25px]] Please make use of the '''Show preview''' button. It gives you a preview of the edit you make, allowing you to perfect it before you save the page.--[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 04:29, 1 June 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Talk:Difficulty&diff=9397Talk:Difficulty2011-05-31T02:10:10Z<p>Firestorm: </p>
<hr />
<div>''Difficulty is a measure of how difficult it is to find a new [[block]] '''compared to the easiest it can ever be'''.'' <br />
<br />
What does this mean? <br />
[[User:Tybeet|Tybeet]]<br />
<br />
:I could be wrong, but I believe it means that if the difficulty is 10, then it is 10x more difficult to find a block compared to a difficulty of 1, which means that it will take 10x as long to find a new block, on average. Someone please correct me if I'm wrong so we can rewrite that phrase --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 02:10, 31 May 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=User_talk:Humble&diff=9396User talk:Humble2011-05-31T02:07:52Z<p>Firestorm: Created page with "{{Subst:sp}} --~~~~"</p>
<hr />
<div>[[File:Information.png|25px]] Please make use of the '''Show preview''' button. It gives you a preview of the edit you make, allowing you to perfect it before you save the page. --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 02:07, 31 May 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Template:Help_navbar&diff=9319Template:Help navbar2011-05-30T19:09:15Z<p>Firestorm: </p>
<hr />
<div>{| class="wikitable" cellpadding=0 style="margin: 10px auto; align: center; width: 80%;"<br />
|-<br />
! valign="center" | [[Image:Help center.png|65px]]<br />
| align="center" |<br />
<span class="plainlinks">'''[[Help:Contents|Wiki Help]]:''' [[Help:Editing|Editing]] • [[Help:Group_rights|Administrators]] • [http://www.mediawiki.org/wiki/Help:Images Images] • [http://www.mediawiki.org/wiki/Help:Tables Tables] <br />
<br><br />
'''Bitcoin Help''': [[Introduction]] • [[FAQ|Frequently Asked Questions]] • [[Getting started]] • [[:Category:Mining|Mining]]</span> <br />
|}</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Help&diff=9317Bitcoin Wiki:Help2011-05-30T18:30:14Z<p>Firestorm: </p>
<hr />
<div>{{stub}}<br />
<br />
{{Help navbar}}<br />
<br />
__NOTOC__<br />
<br />
{{columns<br />
|bgcol = #FFCCBB<br />
|colwidth = 50em<br />
|col1 = <br />
<br />
=Wiki Help=<br />
== Editing Articles ==<br />
*[[Wikipedia:Wikipedia:Cheatsheet|Cheatsheet]]<br />
*[[Wikipedia:Help:Links#Wikilinks|How to make links]]<br />
*[[Wikipedia:Help:Table#Pipe_syntax_tutorial|Using tables]]<br />
**[[Wikipedia:Wikipedia:Collapsible_tables|Using Collapsible tables]]<br />
* [[Help:Using ToDo Lists|Using ToDo lists]]<br />
<br />
== Wiki Resources and lists ==<br />
*[http://www.mediawiki.org/wiki/Help:Tracking_changes Keeping track of changes]<br />
*[http://www.mediawiki.org/wiki/Help:Contents User help on MediaWiki]<br />
*[[Wikipedia:Wikipedia:Manual_of_Style|Manual of style]]<br />
**[[Wikipedia:Wikipedia:Naming conventions|Naming conventions]]<br />
**[[Wikipedia:Wikipedia:Guide to layout|Guide to layout]]<br />
*[[IRC channels]]<br />
<br />
|col2 = <br />
=Bitcoin Help=<br />
== Client Help ==<br />
* [[Introduction]]<br />
* [[Getting started]]<br />
* [[Securing your wallet]]<br />
* [[FAQ|General Frequently Asked Questions]]<br />
* [[Secure Trading|Best practices for traders]]<br />
* [[:Category:Clients|Clients]]<br />
* [[:Category:Exchanges|Exchanges]]<br />
* [[Trade|Bitcoin-accepting sites]]<br />
* [[Myths]]<br />
* [[Meetups]]<br />
* [[Transaction fees]]<br />
<br />
== Mining Help==<br />
* [[:Category:Mining|Mining]]<br />
* [[:Category:Mining contractors|Where to rent Mining services]]<br />
* [[Pooled mining]]<br />
* [[Mining hardware comparison]]<br />
<br />
== Technical Resources ==<br />
* [[PHP developer intro]]<br />
* [[API reference (JSON-RPC)]]<br />
* [[Protocol specification]]<br />
* [[Press|Press coverage]]<br />
* [[:Category:Technical|More technical articles]]<br />
<br />
== Markets and Trading ==<br />
* [[:Category:Economics|Economics]]<br />
* [[:Category:Marketing|Marketing resources]]<br />
* [[Donation-accepting_organizations_and_projects|Donation-accepting sites]]<br />
}}</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Help&diff=9316Bitcoin Wiki:Help2011-05-30T17:25:38Z<p>Firestorm: Will be adding to later, and making it prettier</p>
<hr />
<div>{{stub}}<br />
<br />
{{Help navbar}}<br />
<br />
__NOTOC__<br />
<br />
{{columns<br />
|bgcol = #FFCCCC <br />
|colwidth = 50em<br />
|col1 = <br />
<br />
=Wiki Help=<br />
== Editing articles ==<br />
*[[Wikipedia:Wikipedia:Cheatsheet|Cheatsheet]]<br />
*[[Wikipedia:Help:Links#Wikilinks|How to make links]]<br />
*[[Wikipedia:Help:Table#Pipe_syntax_tutorial|Using tables]]<br />
**[[Wikipedia:Wikipedia:Collapsible_tables|Using Collapsible tables]]<br />
* [[Help:Using ToDo Lists|Using ToDo lists]]<br />
<br />
== Resources and lists ==<br />
*[http://www.mediawiki.org/wiki/Help:Tracking_changes Keeping track of changes]<br />
*[http://www.mediawiki.org/wiki/Help:Contents User help on MediaWiki]<br />
*[[Wikipedia:Wikipedia:Manual_of_Style|Manual of style]]<br />
**[[Wikipedia:Wikipedia:Naming conventions|Naming conventions]]<br />
**[[Wikipedia:Wikipedia:Guide to layout|Guide to layout]]<br />
*[[IRC channels]]<br />
<br />
|col2 = <br />
=Bitcoin Help=<br />
== Tutorials ==<br />
* [[Introduction]]<br />
* [[Getting started]]<br />
* [[Securing your wallet]]<br />
* [[Secure Trading|Best practices for traders]]<br />
* [[PHP developer intro]]<br />
* [[API reference (JSON-RPC)]]<br />
* [[Protocol specification]]<br />
* [[Myths]]<br />
<br />
== Developer Assistance ==<br />
* [[:Category:Clients|Clients]]<br />
* [[:Category:Mining|Mining]]<br />
* [[:Category:Exchanges|Exchanges]]<br />
* [[Press|Press coverage]]<br />
* [[:Category:Marketing|Marketing resources]]<br />
* [[:Category:Technical|Technical articles]]<br />
* [[:Category:Economics|Economics]]<br />
* [[Trade|Bitcoin-accepting sites]]<br />
* [[Donation-accepting_organizations_and_projects|Donation-accepting sites]]<br />
* [[Meetups]]<br />
}}</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Template:Columns/doc&diff=9315Template:Columns/doc2011-05-30T17:17:30Z<p>Firestorm: Created page with "{{see also|Template:Columns-list}} Template in the vein of navbox templates such as {{tl|Navbox}} to aid the creation of (up to seven) columns across a page. == Syntax == <pre> ..."</p>
<hr />
<div>{{see also|Template:Columns-list}}<br />
Template in the vein of navbox templates such as {{tl|Navbox}} to aid the creation of (up to seven) columns across a page.<br />
<br />
== Syntax ==<br />
<pre><br />
{{columns<br />
|bgcol = <!--Background colo/ur (default none)--><br />
|colwidth = <!--Width of each column (default 15em)--><br />
|gap = <!--Gap between each column (default 1.25em)--><br />
|col1width = <!--use to set a different width for col1--><br />
|col1 = <!--mandatory--><br />
|col2width = <!--use to set a different width for col2 (etc)--><br />
|col2 = <!--mandatory--><br />
|col3width = <br />
|col3 = <br />
...<br />
|col7width = <br />
|col7 = <br />
}}<br />
</pre><br />
<br />
== Examples ==<br />
; Code<br />
<pre><br />
{{columns<br />
|col1 = Simplest<br/>instantiation<br/>of<br />
|col2 = this<br/>template<br />
}}<br />
</pre><br />
<br />
; Result<br />
{{columns<br />
|col1 = Simplest<br/>instantiation<br/>of<br />
|col2 = this<br/>template<br />
}}<br />
<br />
<br/><hr/><br />
; Code<br />
<pre><br />
{{columns |bgcol=beige |width=8.5em |gap=3.25em<br />
<br />
|col1 =<br />
* These<br />
* columns<br />
* are<br />
* more<br />
* complex<br />
<br />
|col2 =<br />
The<br/>background<br/>is<br/>beige<br />
<br />
|col3 =<br />
; Each : column<br />
; is : 8.5[[Em (typography)|em]]<br />
; wide<br />
<br />
|col4 =<br />
{{{!}}<br />
!colspan="2"{{!}} and<br />
{{!-}}<br />
{{!}} the {{!!}} gap<br />
{{!-}}<br />
{{!}}colspan="2"{{!}} between<br />
{{!-}}<br />
{{!}} each {{!!}} is<br />
{{!-}}<br />
!colspan="2" align="center"{{!}} 3.25em<br />
{{!}}}<br />
}}<br />
</pre><br />
<br />
; Result<br />
{{columns |bgcol=beige |width=8.5em |gap=3.25em<br />
<br />
|col1 =<br />
* These<br />
* columns<br />
* are<br />
* more<br />
* complex<br />
<br />
|col2 =<br />
The<br/>background<br/>is<br/>beige<br />
<br />
|col3 =<br />
; Each : column<br />
; is : 8.5{{w|Em (typography)|em}}<br />
; wide<br />
<br />
|col4 =<br />
{{{!}}<br />
!colspan="2"{{!}} and<br />
{{!-}}<br />
{{!}} the {{!!}} gap<br />
{{!-}}<br />
{{!}}colspan="2"{{!}} between<br />
{{!-}}<br />
{{!}} each {{!!}} is<br />
{{!-}}<br />
!colspan="2" align="center"{{!}} 3.25em<br />
{{!}}}<br />
}}<noinclude>[[Category:Template documentation]]</noinclude></div>Firestormhttps://en.bitcoin.it/w/index.php?title=Template:Columns&diff=9314Template:Columns2011-05-30T17:17:10Z<p>Firestorm: Imported Template from another Wiki</p>
<hr />
<div>{| style="background:{{{bgcol|transparent}}}; {{{bodystyle|}}}" cellspacing="0" cellpadding="0"<br />
|- valign="top"<br />
|style="width:{{{col1width|{{{colwidth|{{{width|15em}}}}}}}}};"|<br />
{{{col1}}}<br />
|style="width:{{{gap|1.25em}}};"|<br />
|style="width:{{{col2width|{{{colwidth|{{{width|15em}}}}}}}}};"|<br />
{{{col2}}}<br />
|style="width:{{{gap|1.25em}}};"|<br />
{{#if:{{{col3<includeonly>|</includeonly>}}}|<!--then:--><br />
{{!}}style="width:{{{col3width|{{{colwidth|{{{width|15em}}}}}}}}};"{{!}}<br />
{{{col3}}}<br />
{{!}}style="width:{{{gap|1.25em}}};"{{!}}<br />
}}<br />
{{#if:{{{col4<includeonly>|</includeonly>}}}|<!--then:--><br />
{{!}}style="width:{{{col4width|{{{colwidth|{{{width|15em}}}}}}}}};"{{!}}<br />
{{{col4}}}<br />
{{!}}style="width:{{{gap|1.25em}}};"{{!}}<br />
}}<br />
{{#if:{{{col5<includeonly>|</includeonly>}}}|<!--then:--><br />
{{!}}style="width:{{{col5width|{{{colwidth|{{{width|15em}}}}}}}}};"{{!}}<br />
{{{col5}}}<br />
{{!}}style="width:{{{gap|1.25em}}};"{{!}}<br />
}}<br />
{{#if:{{{col6<includeonly>|</includeonly>}}}|<!--then:--><br />
{{!}}style="width:{{{col6width|{{{colwidth|{{{width|15em}}}}}}}}};"{{!}}<br />
{{{col6}}}<br />
{{!}}style="width:{{{gap|1.25em}}};"{{!}}<br />
}}<br />
{{#if:{{{col7<includeonly>|</includeonly>}}}|<!--then:--><br />
{{!}}style="width:{{{col7width|{{{colwidth|{{{width|15em}}}}}}}}};"{{!}}<br />
{{{col7}}}<br />
{{!}}style="width:{{{gap|1.25em}}};"{{!}}<br />
}}<br />
{{#if:{{{col8<includeonly>|</includeonly>}}}|<!--then:--><br />
{{!}}style="width:{{{col8width|{{{colwidth|{{{width|15em}}}}}}}}};"{{!}}<br />
{{{col8}}}<br />
{{!}}style="width:{{{gap|1.25em}}};"{{!}}<br />
}}<br />
{{#if:{{{col9<includeonly>|</includeonly>}}}|<!--then:--><br />
{{!}}style="width:{{{col9width|{{{colwidth|{{{width|15em}}}}}}}}};"{{!}}<br />
{{{col9}}}<br />
{{!}}style="width:{{{gap|1.25em}}};"{{!}}<br />
}}<br />
{{#if:{{{col10<includeonly>|</includeonly>}}}|<!--then:--><br />
{{!}}style="width:{{{col10width|{{{colwidth|{{{width|15em}}}}}}}}};"{{!}}<br />
{{{col10}}}<br />
{{!}}style="width:{{{gap|1.25em}}};"{{!}}<br />
}}<br />
|}<noinclude><br />
{{Template doc}}<br />
[[Category:Formatting templates|Columns]]<br />
</noinclude></div>Firestormhttps://en.bitcoin.it/w/index.php?title=Template:!!&diff=9313Template:!!2011-05-30T17:16:36Z<p>Firestorm: Created page with "||<noinclude> ==Description== This template is an acronym for two pipe characters and returns such for use in template calls. !!</noinclude>"</p>
<hr />
<div>||<noinclude><br />
==Description==<br />
This template is an acronym for two pipe characters and returns such for use in template calls.<br />
<br />
[[Category:Formatting templates|!!]]</noinclude></div>Firestormhttps://en.bitcoin.it/w/index.php?title=Template:!-&diff=9312Template:!-2011-05-30T17:16:18Z<p>Firestorm: Created page with "|-<noinclude>!-</noinclude>"</p>
<hr />
<div>|-<noinclude>[[Category:Formatting templates|!-]]</noinclude></div>Firestormhttps://en.bitcoin.it/w/index.php?title=User_talk:Nanotube&diff=9311User talk:Nanotube2011-05-30T17:06:23Z<p>Firestorm: /* Help Page */</p>
<hr />
<div>Hi Nanotube,<br />
can you please delete [[Mining pool reward FAQ]]? I created it to provide information about some commonly confused issues, but it's being abused and thus can't serve this purpose. [[User:Holy-Fire|Holy-Fire]] 18:43, 26 May 2011 (GMT)<br />
: I removed the troublesome content and left it to-the-point. This should serve to remove any abuse. --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 18:51, 26 May 2011 (GMT)<br />
::Sorry, it really doesn't, see my comment on your talk page. [[User:Holy-Fire|Holy-Fire]] 19:08, 26 May 2011 (GMT)<br />
:::posted my comments on firestorm's user talk page and the faq-page talk page. https://en.bitcoin.it/wiki/Talk:Mining_pool_reward_FAQ<br />
<br />
==Help Page==<br />
<br />
Hello, Nanotube. I've created a fairly simple [[Help:Contents|Help page]] that I'm going to be expanding over time. Would it be a good idea to link to this in the sidebar? --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 14:46, 30 May 2011 (GMT)<br />
: add it as "Wiki Help", you think?--[[User:Nanotube|Nanotube]] 16:44, 30 May 2011 (GMT)<br />
:: Just "Help" should be fine. I'll collaborate links to various FAQs and help pages regarding Bitcoin itself. I hope to make it the resource to go to if you need information on anything --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 17:06, 30 May 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=User_talk:Eleuthria&diff=9306User talk:Eleuthria2011-05-30T16:15:08Z<p>Firestorm: Created page with "{{subst:sp}} --~~~~"</p>
<hr />
<div>[[File:Information.png|25px]] Please make use of the '''Show preview''' button. It gives you a preview of the edit you make, allowing you to perfect it before you save the page. --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 16:15, 30 May 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Group_rights&diff=9298Bitcoin Wiki:Group rights2011-05-30T15:39:12Z<p>Firestorm: </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 />
*[[User:MagicalTux|MagicalTux]]<br />
<br />
==Content Administrators==<br />
Users with extended moderator abilities.<br />
<br />
*[[User:Genjix|Genjix]] <br />
*[[User:Kiba|Kiba]] <br />
*[[User:MagicalTux|MagicalTux]] <br />
*[[User:Nanotube|Nanotube]] <br />
<br />
==Moderators==<br />
Users with the ability to protect, move and delete pages as well as block users.<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 />
*[[User:WikiBot|WikiBot]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Autoconfirmed_users&diff=9297Bitcoin Wiki:Autoconfirmed users2011-05-30T15:36:00Z<p>Firestorm: Redirected page to Help:Group rights</p>
<hr />
<div>#redirect [[Help:Group rights]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Users&diff=9296Bitcoin Wiki:Users2011-05-30T15:35:20Z<p>Firestorm: Redirected page to Help:Group rights</p>
<hr />
<div>#Redirect [[Help:Group rights]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Weaknesses&diff=9295Weaknesses2011-05-30T15:13:30Z<p>Firestorm: </p>
<hr />
<div>== Might be a problem ==<br />
<br />
=== Forcing clock drift against a target node ===<br />
<br />
See [http://culubas.blogspot.com/2011/05/timejacking-bitcoin_802.html Timejacking] for a description of this attack. It can be fixed by changing how nodes calculate the current time.<br />
<br />
=== Tracing a coin's history ===<br />
Tracing a coin's history can be used to connect identities to addresses. [[Anonymity|More info]].<br />
<br />
=== Cancer nodes ===<br />
It's trivial for an attacker to fill the network with clients controlled by him. This might be helpful in the execution of other attacks.<br />
<br />
For example, an attacker might connect 100,000 IP addresses to the IRC bootstrap channel. You would then be very likely to connect only to attacker nodes. This state can be exploited in (at least) the following ways:<br />
* The attacker can refuse to relay blocks and transactions from everyone, disconnecting you from the network.<br />
* The attacker can relay only blocks that he creates, putting you on a separate network. You're then open to double-spending attacks.<br />
* If you rely on transactions with 0 confirmations, the attacker can just filter out certain transactions to execute a double-spending attack.<br />
* Low-latency encryption/anonymization of Bitcoin's transmissions (With Tor, JAP, etc.) can be defeated relatively easy with a timing attack if you're connected to several of the attacker's nodes and the attacker is watching your transmissions at your ISP.<br />
<br />
Bitcoin makes these attacks more difficult by only making an outbound connection to one IP address per /16 (x.y.0.0). Incoming connections are unlimited and unregulated, but this is generally only a problem in the anonymity case, where you're probably already unable to accept incoming connections.<br />
<br />
Looking for suspiciously low network hash-rates may help prevent the second one.<br />
<br />
=== No authentication for IP transfers ===<br />
Since there's no authentication when sending to an [[IP address]] (as opposed to a [[Address|Bitcoin address]]), executing a man-in-the-middle attack and stealing the sent BitCoins is trivial. This attack is downright ''likely'' if you're using Tor.<br />
<br />
=== Packet sniffing ===<br />
Someone who can see all of your Internet traffic can easily see when you send a transaction that you didn't receive (which means that it's yours). This would be made more difficult (but not impossible) if node-to-node encryption was used.<br />
<br />
=== Denial of Service (DoS) attacks ===<br />
Sending lots of data to a node may make it so busy it cannot process normal bitcoin transactions. Bitcoin has some denial-of-service prevention built-in (it will drop connections to peers that send it too much data too quickly), but is likely still vulnerable to more sophisticated denial-of-service attacks.<br />
<br />
== Probably not a problem ==<br />
<br />
===Breaking the cryptography===<br />
SHA-256 and ECDSA are considered very strong currently, but they might be broken in the far future. If that happens, BitCoin can shift to a stronger algorithm. [http://www.bitcoin.org/smf/index.php?topic=191.msg1585#msg1585 More info].<br />
<br />
===Scalability===<br />
BitCoin can easily scale beyond the level of traffic VISA sees globally today. See the discussion on the [[scalability]] page for more information.<br />
<br />
===Segmentation===<br />
If there is even a "trickle" of a connection between two sides of a segmented network, things should still work perfectly. When block chains are combined, all of the non-generation transactions in the shorter chain are re-added to the transaction pool -- they'll start over at 0/unconfirmed, but they'll still be valid. No mature transactions will be lost unless the segmentation persists for longer than ~120 blocks. Then generations will start to mature, and any transactions based on those generations will become invalid when recombined with the longer chain. [http://www.bitcoin.org/smf/index.php?topic=241.msg2071#msg2071 More info].<br />
<br />
=== Attacking all users ===<br />
The IP addresses of most users are totally public. You can use Tor to hide this, but the network won't work if everyone does this. BitCoin requires that ''some'' country is still free.<br />
<br />
=== Dropping transactions ===<br />
Nodes that generate blocks can choose not to include a transaction in their blocks. When this happens, the transaction remains "active" and can be included in a later block. Two things discourage this:<br />
* Nodes only hash a fixed-size ''header'', so there is no speed advantage to dropping transactions.<br />
* [[Satoshi]] has [http://www.bitcoin.org/smf/index.php?topic=165.msg1595#msg1595 communicated] that he will write code to stop this kind of thing if it becomes a problem.<br />
<br />
=== Attacker has a lot of computing power ===<br />
An attacker that controls more than 50% of the network's computing power can, for the time that he is in control, exclude and modify the ordering of transactions. This allows him to:<br />
* Reverse transactions that he sends while he's in control<br />
* Prevent some or all transactions from gaining any confirmations<br />
* Prevent some or all other generators from getting any generations<br />
The attacker ''can't'':<br />
* Reverse other people's transactions<br />
* Prevent transactions from being sent at all (they'll show as 0/unconfirmed)<br />
* Change the number of coins generated per block<br />
* Create coins out of thin air<br />
* Send coins that never belonged to him<br />
<br />
It's much more difficult to change historical blocks, and it becomes exponentially more difficult the further back you go. As above, changing historical blocks only allows you to exclude and change the ordering of transactions. It's impossible to change blocks created before the last checkpoint.<br />
<br />
Since this attack doesn't permit all that much power over the network, it is expected that no one will attempt it. A profit-seeking person will always gain more by just following the rules, and even someone trying to destroy the system will probably find other attacks more attractive. However, if this attack is successfully executed, it will be difficult or impossible to "untangle" the mess created -- any changes the attacker makes might become permanent.<br />
<br />
=== Spamming transactions ===<br />
<br />
It is easy to send transactions to yourself repeatedly. If these transactions fill blocks to the maximum size (1MB), other transactions would be delayed until the next block.<br />
<br />
This is made expensive by the [[transaction fee|fees]] that would be required after the 50KB of free transactions per block are exhausted. An attacker will eventually eliminate free transactions, but Bitcoin fees will always be low because raising fees above 0.01 BTC per KB would require spending transaction fees. An attacker will eventually run out of money. Even if an attacker wants to waste money, transactions are further prioritized by the time since the coins were last spent, so attacks spending the same coins repeatedly are less effective.<br />
<br />
=== The "Finney" attack ===<br />
Named for Hal Finney, who first described this variation of a double-spend attack involving accepting [http://www.bitcoin.org/smf/index.php?topic=3441.msg48384#msg48384 0-confirmation transactions]. Accepting 0-confirmation large-value transactions is problem; accepting them for low-value transactions (after waiting several seconds to detect an ordinary double-spend attempt) is probably not a problem.<br />
<br />
== Definitely not a problem ==<br />
<br />
===Coin destruction===<br />
BitCoin has 8 decimals of precision, so the entire network could operate on just a handful of BitCoins. An attacker could never destroy them all. If deflation gets to the point where transactions of more than 10BC are unheard of, the client can just shift the decimal point over so that, for example, people with 0.01 BitCoins have 1.000 BitCents.<br />
<br />
===Generating tons of addresses===<br />
Generating an address doesn't touch the network at all. You'd only be wasting your CPU resources and disk space.<br />
<br />
===Rival/malicious client code===<br />
Any rival client must follow BitCoin's rules or else all current BitCoin clients will ignore it. You'd have to actually get people to ''use'' your client.<br />
<br />
===Everyone calculates at the same rate===<br />
If everyone began with identical blocks and started their nonce at 1 and incremented, the fastest machine would always win. However, each block contains a new, random public key known only to you in the list of transactions. The 256-bit "Merkle tree" hash of this is part of the block header.<br />
<br />
So everyone begins with slightly different blocks and everyone truly has a random chance of winning (modified by CPU power).<br />
<br />
===Generate "valid" blocks with a lower difficulty than normal===<br />
Using unmodified Bitcoin code, an attacker could segment himself from the main network and generate a long block chain with a lower difficulty than the real network. These blocks would be totally valid for his network. However, it would be impossible to combine the two networks (and the "false" chain would be destroyed in the process).<br />
<br />
* Even though your network's difficulty can be less than the real difficulty, this doesn't give you any advantage over the real network. You'll gain ground when the real network is taking more than 10 minutes to generate a block, but you'll lose ground when the network takes less than 10 minutes.<br />
* Every few releases of Bitcoin, a recent block hash is hardcoded into the source code. Any blocks before that point can't be changed. An attacker starting at that point would have to reduce the difficulty, but this would require him to generate blocks at a much slower rate than once per 10 minutes. By the time he finally gets to a difficulty of 1, a new version of Bitcoin with an updated hardcoded block will probably have been released.<br />
* "Block chain length" is calculated from the combined difficulty of all the blocks, not just the number of blocks in the chain. The one that represents the most CPU usage will win.<br />
<br />
[[Category:Technical]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Vocabulary&diff=9294Vocabulary2011-05-30T15:13:24Z<p>Firestorm: </p>
<hr />
<div>;'''Bitcoin'''<br />
: The name of a decentralized p2p crypto-currency application.<br />
;'''[[Bitcoins]]''' ''(abbreviated BTC)''<br />
: The currency used and generated within the Bitcoin system.<br />
;'''[[Block]]'''<br />
: Blocks are links in a chain of transaction verifications. Outstanding transactions get bundled into a block and are verified roughly every ten minutes on average. Each subsequent block strengthens the verification of previous blocks. Each block contains one or more transactions.<br />
;'''[[Block Chain]]'''<br />
: Each block includes the difficult-to-produce verification hash of the previous block. This allows each subsequent block to be linked to all previous blocks. These blocks which are linked together for the purpose of verifying transactions within blocks is called the block chain.<br />
;'''Branching Point'''<br />
: The block at which the block chain diverges into multiple chain branches<br />
;'''Chain Branching'''<br />
;'''Checkpoint Lockin'''<br />
: Every once in a while, a recent block hash is hardcoded into Bitcoin. This prevents pretty much any possible attack from affecting transactions made up to this point. No matter what happens (except perhaps if SHA-256 is broken), these transactions will survive. Satoshi announced the feature [http://www.bitcoin.org/smf/index.php?topic=437 here] and it was discussed to death [http://www.bitcoin.org/smf/index.php?topic=1647 here].<br />
;'''Coinbase'''<br />
: "Coinbase" is another name for a generation transaction. The input of such a transaction contains some arbitrary data where the scriptSig would go in normal transactions -- this data is sometimes called the "coinbase", as well.<br />
;'''[[Confirmation]]'''<br />
: To protect against double spending, a transaction should not be considered as "confirmed" until a certain number of blocks in the block chain confirm, or verify that the transaction. The classic bitcoin client will show a transaction as "n/unconfirmed" until 6 blocks confirm the transaction.<br />
;'''[[Difficulty]]'''<br />
: Every 2016 blocks, Bitcoin adjusts the difficulty of verifying blocks based on the time it took to verify the previous 2016 blocks. The difficulty is adjusted so that given the average estimated computing power of the whole bitcoin network, only one block will verified on average every ten minutes for the next 2016 blocks. The difficulty is usually expressed as a number, optionally accurate to many decimal places (eg. in [http://blockexplorer.com/b/100000 block 100,000] it was 14,484.162361. The difficulty is inversely proportional to the hash target, which is expressed as a hex number with around 50 digits, and is the number under which a block's generated hash must be to qualify as an officially verified block. The hash target is equal to ((65535 << 208) / difficulty). Difficulty is also often called block difficulty, hash difficulty, verification difficulty or the difficulty of generating bitcoins.<br />
;'''Discouraged block'''<br />
: A discouraged [[block]] is considered to be a valid part of the chain, but blocks you generate will build onto the block before it instead of that block. If most of the network is discouraging a block, then it will almost always be replaced by another block and not end up making it into the final [[block chain]]. Unlike rejecting a block, discouraging a block has no risk of splitting the network. Bitcoin currently doesn't discourage any blocks, but the mechanism may be used in the future to handle certain issues such as unreasonably high or low fees.<br />
;'''Double Spending'''<br />
: Attempting to spend coins that have already been spent in another transaction<br />
;'''Generate Bitcoins'''<br />
: The phrase generating bitcoins comes from the file menu option 'Generate Coins' in the Bitcoin which enables or disables the CPU intensive process of verifying blocks. When Bitcoin verifies a block before any other Bitcoin client, it receives newly minted bitcoins and the transaction fees which may or may not be included in the verified block. The amount of bitcoins awarded for verifying a block is ?50.00 for the first 210,000 blocks and half the previous amount of bitcoins for each subsequent 210,000 blocks. On average, 210,000 blocks take about 4 years to verify. The total amount of bitcoins that will ever be minted is roughly 21,000,000.00000000. Currently the decimal places more than two to the right of the decimal point are not displayed in the official Bitcoin client.<br />
;'''[[Hash]]'''<br />
: A computer algorithm which produces an identification key that can be used to easily verify that data has not been altered. If you change any single bit of the original data and run the hash algorithm, the hash will completely change. Because the hash is seemingly random, it is prohibitively difficult to try to produce a specific hash by changing the data which is being hashed.<br />
;'''Low Priority'''<br />
: See Priority.<br />
;'''Memory pool'''<br />
: Generators store [[transactions]] waiting to get into a block in their memory pool after receiving them. Received transactions are stored even if they are invalid to prevent nodes from constantly requesting transactions that they've already seen. The memory pool is cleared when Bitcoin is shut down, causing the [[network]] to gradually forget about transactions that haven't been included in a [[block]].<br />
;'''Merkle root'''<br />
: Every [[transactions|transaction]] has a [[hash]] associated with it. In a [[block]], all of the transaction hashes in the block are themselves hashed (sometimes several times -- the exact process is complex), and the result is the Merkle root. In other words, the Merkle root is the hash of all the hashes of all the transactions in the block. The Merkle root is included in the [[block hashing algorithm|block header]]. With this scheme, it is possible to securely verify that a transaction has been accepted by the network (and get the number of confirmations) by downloading just the tiny block headers and [[Wikipedia:Merkle tree|Merkle tree]] -- downloading the entire block chain is unnecessary. This feature is currently not used in Bitcoin, but it will be in the future.<br />
;''' Miner'''<br />
: Computer software which is designed to repeatedly calculate hashes with the intention to create a successful block and earn coins from transaction fees and new coins created with the block itself. The term references an analogy of gold miners who dig gold out of the ground and thus "discover" new gold that can be used to create new coins with a similar kind of discovery occurring with a successful hash to create new Bitcoins.<br />
;'''Node'''<br />
: Each Bitcoin client currently running within the network is referred to as a Node of the system.<br />
;'''Nonce'''<br />
: A nonce is an otherwise meaningless number which is used to alter the outcome of a hash. Each time Bitcoin hashes a block, it increments a nonce within the block which it is trying verify. If the numeric value of the effectively random hash is below a certain amount determined by the block generation difficulty, then the block is accepted by other clients and gets added to the chain.<br />
;'''Orphan block'''<br />
: An orphan block is a block that is not in the currently-longest [[block chain]].<br />
;'''Priority'''<br />
: A scoring mechanism to help ensure that expensive data storage isn't consumed by lower quality and spam Low priority transactions will not get included by a miner if the limited space is already filled by higher priority transactions. A [[Transaction Fee|transaction fee]] will affect priority.<br />
;'''[[Proof of work]]'''<br />
: A result that can only be obtained through the use of computational resources. Changing the data in the proof of work requires redoing the work.<br />
;'''Reorganize'''<br />
: A block chain reorganize (or '''reorg''') happens when one chain becomes longer than the one you are currently working on. All of the blocks in the old chain that are not in the new one become orphan blocks, and their generations are invalidated. Transactions that use the newly-invalid generated coins also become invalid, though this is only possible in large chain splits because generations can't be spent for 100 blocks. The number of confirmations for transactions may change after a reorg, and transactions that are not in the new chain will become "0/unconfirmed" again. If a transaction in the old chain conflicts with one in the new chain (as a result of double-spending), the old one becomes invalid.<br />
;'''Satoshi'''<br />
: The base unit of Bitcoin (0.00000001 BTC) is sometimes called a Satoshi, after Bitcoin's creator Satoshi Nakamoto.<br />
;'''Seed Nodes'''<br />
: Nodes whose IP addresses are included in the [[Original Bitcoin client|Bitcoin client]] for use during a new installation when the normal bootstrapping process through IRC wasn't possible.<br />
;'''Subsidy'''<br />
: The block subsidy is the BTC created for generating a block. The subsidy is halved every four years.<br />
;'''Super Nodes'''<br />
: A participant in a p2p network which connects to as many other nodes as possible.<br />
;'''[[Tonal BitCoin]]''' ''(abbreviated TBC)''<br />
: Adaptation of Bitcoin to the [http://en.wikipedia.org/wiki/John_W._Nystrom#Tonal_System_.28Hexadecimal.29 Tonal System]. 1 TBC is defined as 1,0000 (65,536 decimal) base bitcoin units. Not widely used.<br />
;'''[[Transaction Fee]]'''<br />
: A voluntary fee which can be added to a transaction which is used as an incentive to add the bitcoin transaction to a block. The fee determines the likelihood of inclusion in any given block, where a high fee included with a transaction has a priority over transactions with a lower fee included or no fee at all.<br />
;'''Virgin bitcoin'''<br />
: The reward for generating a [[Block|block]] that has not yet been spent, a state which might increase the ability to transact [[anonymity|anonymously]].<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary| ]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Miner_fees&diff=9293Miner fees2011-05-30T15:13:18Z<p>Firestorm: </p>
<hr />
<div>[[File:fee.png|thumb|Receiving a transaction fee of 0.44 BC]]<br />
Transaction fees may be included with any transfer of bitcoins from one address to another. At the moment, many [[transactions]] are typically processed in a way where no fee is expected at all, but for transactions which draw coins from many bitcoin addresses and therefore have a large data size, a small transaction fee is usually expected.<br />
<br />
The transaction fee is processed by and received by the bitcoin miner. When a new bitcoin block is generated with a successful hash, the information for all of the transactions is included with the block and all transaction fees are collected by that user creating the block, who is free to assign those fees to himself.<br />
<br />
Transaction fees are voluntary on the part of the person making the bitcoin transaction, as the person attempting to make a transaction can include any fee or none at all in the transaction. On the other hand, nobody mining new bitcoins necessarily needs to accept the transactions and include them in the new block being created. The transaction fee is therefore an incentive on the part of the bitcoin user to make sure that a particular transaction will get included into the next block which is generated.<br />
<br />
It is envisioned that over time the cumulative effect of collecting transaction fees will allow somebody creating new blocks to "earn" more bitcoins than will be "mined" from new bitcoins created by the new block itself. This is also an incentive to keep trying to create new blocks even if the value of the newly created block from the "mining" activity is zero.<br />
<br />
It works like this:<br />
* Whoever sends the transaction is often able to guess what the appropriate fee will be based on their own fee rules. The [[Original Bitcoin client|original client]] will always assess the transaction, and if a fee will typically be expected, it will not allow you to send the transaction without the calculated fee.<br />
* The user is prompted to confirm the fee before the transaction is sent.<br />
* The sender makes a transaction with more coins in the "In" portion than the "Out" portion so that there are "leftovers" not assigned to any address.<br />
* Whoever ends up publishing the [[block]] which contains this transaction will take these (and any) "leftover" coins. They are included with their normal generated coins and is an extra "bonus" for creating the block.<br />
* If a generating node receives a transaction that should include a transaction fee but doesn't, they refuse to include it in their blocks. It might be included in a later block if someone is willing to accept it. Generators can't force a certain fee on transactions -- they can only accept or reject the transaction's "fee offer".<br />
[[File:lfm_fee.png|thumb|This balance is made entirely of 0.01 BTC "cents". Since sending them requires a lot of data, a very large fee is required.]]<br />
<br />
Different versions of Bitcoin have different rules for determining which transactions to accept and how large of a fee to send.<br />
<br />
Current "Default" Rules for the regular Bitcoin client (Bitcoin 0.3.20)<br />
* 0.01 BTC fee if sending any transaction less than 0.01 BTC. This is to help prevent DoS attacks against the network. Remember: fees are not network-enforced, so it's still ''possible'' to send these small transactions without the fee -- you just have to generate the blocks that contain them yourself (after modifying Bitcoin).<br />
* 0.01 BTC fee per kilobyte of transaction, but:<br />
** If the blocksize (size of all transactions currently waiting to be included in a block) is less than 27 kB, transactions are free.<br />
** If the blocksize is more than 250 kB, transactions get increasingly more expensive as the blocksize approaches the limit of 500 kB. Sending a transaction when the blocksize is 400 kB will cost 5 times the normal amount; sending when it's 499 kB will cost 500x, etc.<br />
* Transactions within each fee tier are prioritized based on several factors. Most importantly, a transaction has more priority if the coins it is using have a lot of confirmations. Someone spamming the network will almost certainly be re-using the same coins, which will lower the priority of their transactions. Priority is also increased for transactions with more BTC, and reduced for transactions with more data.<br />
* If the blocksize is over 4kB, free transactions in the above rules are only allowed if the transaction's priority is above a certain level.<br />
<br />
Note that if you want to send a transaction with less than the "default" rules, or if you are a miner and want to include them in your blocks, you may need to peer with the [[Free transaction relay policy|Free transaction relay network]].<br />
<br />
An advantage for bitcoin users to include a transaction fee is that the likelihood of getting a transaction included into the next block is going to be higher than if a transaction fee is not included. This is a trade off of time vs. money put forward on the transaction fees, as you can be patient with a low or non-existent fee included in a transaction, or you can make sure that the transaction is processed immediately by including a higher fee than is typical.<br />
<br />
The rules are far from set in stone, and the network can support many different rules simultaneously. If there are 10 generating nodes that never require a transaction fee and your client is modified to never send any transaction fee, then your transactions will eventually be picked up by one of those free nodes when they generate a block, though it will probably take a very long time. In the far future, different rules about transaction fees among generating nodes will probably create a clear choice between fees and transaction speed. For example, you might choose to spend 2% for a guaranteed spot in the next block or 0.01% for the transaction to be sent in a few hours.<br />
<br />
As an example, clients that have block generation turned off don't know what the current blocksize is, and will therefore never pay a fee on transactions under 10 kilobytes. If you notice that your sent transactions take a very long time to accrue confirmations, this is possibly the cause. If this happens a lot (probably because the network is under attack), run Bitcoin with the -paytxfee switch: -paytxfee=0.01 will force a minimum fee of 0.01 per kilobyte for all sent transactions, which will prioritize your transactions over all free transactions.<br />
[[File:feesend.png|thumb|Sending a transaction when the sender doesn't have enough money to actually pay the fee]]<br />
<br />
ArtForz, who makes up a large percentage of the network's CPU power, never charged transaction fees (even for micro-transactions) for a period of several months.<br />
<br />
==Technical info==<br />
<br />
Transaction priority is calculated as a value-weighted sum of input age, divided by transaction size in bytes:<br />
priority = sum(input_value_in_base_units * input_age)/size_in_bytes<br />
Transactions need to have a priority of above a certain threshold to avoid the enforced limit (as of client version 0.3.21). (todo: look up threshold in code - is it 57600000?)<br />
<br />
So, for example, a transaction that has 2 inputs, one of 5 btc with 10 confirmations, and one of 2 btc with 3 confirmations, and has a size of 500bytes, will have a priority of<br />
(500000000 * 10 + 200000000 * 3) / 500 = 11800000<br />
<br />
==See Also==<br />
<br />
* [[Free transaction relay policy]]<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]<br />
[[Category:Mining]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Target&diff=9292Target2011-05-30T15:13:12Z<p>Firestorm: </p>
<hr />
<div>The '''target''' is a 256-bit number (extremely large) that all Bitcoin clients share. The SHA-256 [[hash]] of a [[block]]'s header must be lower than or equal to the current target for the block to be accepted by the network. The lower the target, the more [[difficulty|difficult]] it is to generate a block.<br />
<br />
It's important to realize that block generation is not a long, set problem (like doing a million hashes), but more like a lottery. Each hash basically gives you a random number between 0 and the maximum value of a 256-bit number (which is huge). If your hash is below the target, then you win. If not, you increment the nonce (completely changing the hash) and try again. <br />
<br />
For reasons of stability and low latency in transactions, the network tries to produce one block every 10 minutes. Every 2016 blocks -- which should take two weeks if this goal is kept perfectly --, every Bitcoin client compares the actual time it took to generate these blocks with the two week goal and modifies the target by the percentage difference. This makes the proof-of-work problem more or less difficult. A single retarget never changes the target by more than a factor of 4 either way to prevent large changes in difficulty.<br />
<br />
=== What is the target now? === <br />
* [http://blockexplorer.com/q/hextarget Current target]<br />
* [http://blockexplorer.com/q/getdifficulty Current difficulty], as output by Bitcoin's getDifficulty<br />
* [http://blockexplorer.com/q/probability Current probability of winning a block per attempt]<br />
<br />
=== When does the target change next? ===<br />
<br />
* [http://blockexplorer.com/q/nextretarget Next retarget]<br />
<br />
=== What has the target been in the past? ===<br />
<br />
* [http://blockexplorer.com/q/nethash Difficulty history, (at row 5)]<br />
* [http://www.bitcoin.org/smf/index.php?topic=2345.msg31405#msg31405 Re: difficulty over time data?]<br />
* [http://bitcoin.sipa.be/ Bitcoin network graphs] <br />
<br />
=== What is the maximum target? ===<br />
0x00000000ffff0000000000000000000000000000000000000000000000000000<br />
<br />
Since a lower target makes Bitcoin generation more difficult, the maximum target is the ''lowest'' possible [[difficulty]].<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Running_Bitcoin&diff=9291Running Bitcoin2011-05-30T15:12:33Z<p>Firestorm: </p>
<hr />
<div>There are two variations of the official bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called [[bitcoind]]). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).<br />
<br />
__TOC__<br />
==Command-line arguments==<br />
<br />
Give Bitcoin (or bitcoind) the -? or –help argument and it will print out a list of the most commonly used command-line arguments and then exit:<br />
<br />
Usage:<br />
bitcoin [options] <br />
bitcoin [options] <command> [params] Send command to -server or bitcoind<br />
bitcoin [options] help List commands<br />
bitcoin [options] help <command> Get help for a command<br />
Options:<br />
-conf=<file> Specify configuration file (default: bitcoin.conf)<br />
-gen Generate coins<br />
-gen=0 Don't generate coins<br />
-min Start minimized<br />
-datadir=<dir> Specify data directory<br />
-proxy=<ip:port> Connect through socks4 proxy<br />
-addnode=<ip> Add a node to connect to<br />
-connect=<ip> Connect only to the specified node<br />
-nolisten Don't accept connections from outside<br />
-noupnp Don't attempt to use UPnP to map the listening port<br />
-upnp Attempt to use UPnP to map the listening port<br />
-paytxfee=<amt> Fee per KB to add to transactions you send<br />
-server Accept command line and JSON-RPC commands<br />
-daemon Run in the background as a daemon and accept commands<br />
-testnet Use the test network<br />
-rpcuser=<user> Username for JSON-RPC connections<br />
-rpcpassword=<pw> Password for JSON-RPC connections<br />
-rpcport=<port> Listen for JSON-RPC connections on <port> (default: 8332)<br />
-rpcallowip=<ip> Allow JSON-RPC connections from specified IP address<br />
-rpcconnect=<ip> Send commands to node running on <ip> (default: 127.0.0.1)<br />
-keypool=<n> Set key pool size to <n> (default: 100)<br />
-rescan Rescan the block chain for missing wallet transactions<br />
-rpcssl Use OpenSSL (https) for JSON-RPC connections<br />
-? This help message<br />
<br />
==Bitcoin.conf Configuration File==<br />
All command-line options (except for -datadir and -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.<br />
<br />
The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character.<br />
<br />
The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, Bitcoin (or bitcoind) will look for a file named 'bitcoin.conf' in the bitcoin [[data directory]], but both the data directory and the configuration file path may be changed using the -datadir and -conf command-line arguments.<br />
{|<br />
! Operating System<br />
! Default bitcoin datadir<br />
! Typical path to configuration file<br />
|-<br />
| Windows<br />
| %APPDATA%\Bitcoin\<br />
| :\Documents and Settings\username\Application Data\Bitcoin\bitcoin.conf<br />
|-<br />
| Linux<br />
| $HOME/.bitcoin/<br />
| /home/username/.bitcoin/bitcoin.conf<br />
|-<br />
| Mac OSX<br />
| $HOME/Library/Application Support/Bitcoin/<br />
| /Users/username/Library/Application Support/Bitcoin/bitcoin.conf<br />
|}<br />
<br />
==Sample Bitcoin.conf==<br />
Here is a sample bitcoin.conf file, containing every option set to its default value.<br />
<br />
# bitcoin.conf configuration file. Lines beginning with # are comments.<br />
<br />
<br />
# Network-related settings:<br />
<br />
# Run on the test network instead of the real bitcoin network.<br />
#testnet=1<br />
<br />
# Connect via a socks4 proxy<br />
#proxy=127.0.0.1:9050<br />
<br />
##############################################################<br />
## Quick Primer on addnode vs connect ##<br />
## Let's say for instance you use addnode=4.2.2.4 ##<br />
## addnode will connect you to and tell you about the ##<br />
## nodes connected to 4.2.2.4. In addition it will tell ##<br />
## the other nodes connected to it that you exist so ##<br />
## they can connect to you. ##<br />
## connect will not do the above when you 'connect' to it. ##<br />
## It will *only* connect you to 4.2.2.4 and no one else.##<br />
## ##<br />
## So if you're behind a firewall, or have other problems ##<br />
## finding nodes, add some using 'addnode'. ##<br />
## ##<br />
## If you want to stay private, use 'connect' to only ##<br />
## connect to "trusted" nodes. ##<br />
## ##<br />
## If you run multiple nodes on a LAN, there's no need for ##<br />
## all of them to open lots of connections. Instead ##<br />
## 'connect' them all to one node that is port forwarded ##<br />
## and has lots of connections. ##<br />
## Thanks goes to [Noodle] on Freenode. ##<br />
##############################################################<br />
<br />
# Use as many addnode= settings as you like to connect to specific peers<br />
#addnode=69.164.218.197<br />
#addnode=10.0.0.2:8333<br />
<br />
# ... or use as many connect= settings as you like to connect ONLY<br />
# to specific peers:<br />
#connect=69.164.218.197<br />
#connect=10.0.0.1:8333<br />
<br />
# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to<br />
# find other peers.<br />
#noirc=1<br />
<br />
# Maximum number of inbound+outbound connections.<br />
#maxconnections=<br />
<br />
<br />
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)<br />
<br />
# server=1 tells Bitcoin to accept JSON-RPC commands.<br />
#server=1<br />
<br />
# You must set rpcuser and rpcpassword to secure the JSON-RPC api<br />
#rpcuser=Ulysseys<br />
#rpcpassword=YourSuperGreatPasswordNumber_385593<br />
<br />
# How many seconds bitcoin will wait for a complete RPC HTTP request.<br />
# after the HTTP connection is established. <br />
rpctimeout=30<br />
<br />
# By default, only RPC connections from localhost are allowed. Specify<br />
# as many rpcallowip= settings as you like to allow connections from<br />
# other hosts (and you may use * as a wildcard character):<br />
#rpcallowip=10.1.1.34<br />
#rpcallowip=192.168.1.*<br />
<br />
# Listen for RPC connections on this TCP port:<br />
rpcport=8332<br />
<br />
# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind<br />
# running on another host using this option:<br />
rpcconnect=127.0.0.1<br />
<br />
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate<br />
# with Bitcoin -server or bitcoind<br />
#rpcssl=1<br />
<br />
# OpenSSL settings used when rpcssl=1<br />
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH<br />
rpcsslcertificatechainfile=server.cert<br />
rpcsslprivatekeyfile=server.pem<br />
<br />
<br />
# Miscellaneous options<br />
<br />
# Set gen=1 to attempt to generate bitcoins<br />
gen=0<br />
<br />
# Use SSE instructions to try to generate bitcoins faster.<br />
#4way=1<br />
<br />
# Pre-generate this many public/private key pairs, so wallet backups will be valid for<br />
# both prior transactions and several dozen future transactions.<br />
keypool=100<br />
<br />
# Pay an optional transaction fee every time you send bitcoins. Transactions with fees<br />
# are more likely than free transactions to be included in generated blocks, so may<br />
# be validated sooner.<br />
paytxfee=0.00<br />
<br />
# Allow direct connections for the 'pay via IP address' feature.<br />
#allowreceivebyip=1<br />
<br />
<br />
# User interface options<br />
<br />
# Start Bitcoin minimized<br />
#min=1<br />
<br />
# Minimize to the system tray<br />
#minimizetotray=1<br />
<br />
==Platforms==<br />
===Windows===<br />
<br />
====Start automatically====<br />
To configure the Bitcoin client to start automatically:<br />
<br />
Settings -> Options<br />
<br />
then mark the checkbox titled:<br />
[X] Start Bitcoin on window system startup<br />
[[{{ns:file}}:Client_Settings_Options.png]]<br />
<br />
====Generate on startup====<br />
To configure the Bitcoin client so that mining on startup is automatic:<br />
Configure bitcoin.conf as follows:<br />
gen=1<br />
<br />
===Mac===<br />
<br />
===Linux===<br />
[[Category:Technical]][[Category:Developer]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Man_page&diff=9290Man page2011-05-30T15:12:22Z<p>Firestorm: </p>
<hr />
<div>This page is for frequently asked questions that do not yet appear in the main [[FAQ]].<br />
<br />
It's also a place for questions in progress, so feel free to ask new questions, or answer and/or refine existing answers.<br />
<br />
== Ask your question here: ==<br />
How much electrical energy per transaction is projected?<br />
<br />
== Answered Questions ==<br />
<br />
=== How does it work (for non-geeks) ===<br />
<br />
====Why can't somebody just create a version of the software that gives you extra bitcoins?====<br />
<br />
When you spend some bitcoins, the software on your machine has to prove to the software running on everybody else's machine that those bitcoins are valid.<br />
<br />
How does it do that? Well, it is a little bit complicated; you've got to understand how bitcoins are created, and how they are traded.<br />
<br />
First, how they're created: 50 bitcoins are created approximately every 10 minutes. Everybody who is trying to create bitcoins is in a race to try to find those 50 bitcoins; they are really hard to find, but, once found, it is easy to verify that, yes, indeed, your bitcoin software found them, so you get to spend them.<br />
<br />
Second, how they're traded: Imagine you did find 50 bitcoins (well, your computer found them by running the bitcoin software for a few months or a year-- they are not easy to find, and are harder to find the more people who are looking for them). You trade them to me by sending them to my bitcoin address. Inside the software, a messages is created and then broadcast to everybody that says "These 50 bitcoins that we all agree are valid are hereby officially traded to somebody else (me-- well, one of my bitcoin receiving addresses, actually)."<br />
<br />
Now I've got them. If you try to trade those same 50 bitcoins to somebody else, it won't work-- everybody running Bitcoin sees all the trades, so if you try to spend the same coins a second time everybody else's software will reject your attempt to cheat.<br />
<br />
And that's it-- that's how it works. Bitcoins are scarce because only about 50 are created every ten minutes. And you can't claim to have more than you really have because everybody else can check to see if your coins really were created by the "race" process, or if they were from valid trades.<br />
<br />
=== Uncatagorized ===<br />
<br />
==== Why did this generation give me more bitcoins than normal (like 50.07)? ====<br />
<br />
You collected a [[transaction fee]].<br />
<br />
==== Why must users back up their wallets every 100 actions? ====<br />
<br />
Bitcoin transactions send bitcoins to a specific public key. A Bitcoin address is an encoded hash of a public key. In order to use received bitcoins, you need to have the private key matching the public key you received with. This is sort of like a super long password associated with an account (public key). Your Bitcoin wallet contains all of the private keys necessary for spending your received transactions. If you delete your wallet without a backup, then you no longer have the authorization information necessary to claim your coins, and the coins associated with those keys are lost forever.<br />
<br />
Creating a new address generates a new pair of public and private keys, which are added to your wallet. Each keypair is mostly random numbers, so they cannot be known prior to generation. If you backup your wallet and then create a new address, the keypair associated with the new address will not be in the old wallet because the new keypair is only know ''after'' creating it. Any coins received at this address will be lost if you restore from the backup.<br />
<br />
The situation is made somewhat more confusing because the receiving addresses shown in the UI are not the only keys in your wallet. Each Bitcoin generation is given a new public key, and, more importantly, each sent transaction also sends a random number of bitcoins back to yourself at a new key. When sending bitcoins to anyone, you generate a new keypair for yourself and simultaneously send bitcoins to your new public key and the actual recipient's public key. This is an anonymity feature -- it makes tracking Bitcoin transactions much more difficult.<br />
<br />
So if you create a backup, send some bitcoins, and then restore from the backup, some bitcoins will be lost. Bitcoin has not deleted any keys (keys are ''never'' deleted) -- it has created a new key that is not in your old backup and then sent bitcoins to it.<br />
<br />
To mitigate this problem, the wallet contains a pool of 100 queued keys. When you need an address for whatever reason (send, "new address", generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose bitcoins.<br />
<br />
Linux users can setup cron by running 'crontab -e' and adding this line:<br />
01 */1 * * * /usr/local/bin/backupwallet.sh<br />
<br />
backupwallet.sh:<br />
<pre>#!/usr/bin/env bash<br />
<br />
GPGU="My GPG User"<br />
<br />
TS=$(date "+%Y%m%d-%H-%M")<br />
<br />
WALLET=/tmp/wallet${TS}<br />
WALLET_E=/tmp/wallet${TS}.crypt<br />
<br />
~/bin/bitcoind backupwallet $WALLET<br />
/usr/bin/gpg -r "$GPGU" --output $WALLET_E --encrypt $WALLET<br />
~/bin/s3cmd put $WALLET_E s3://NAME_OF_MY_S3_BUCKET<br />
rm $WALLET $WALLET_E</pre><br />
<br />
The shell script does:<br />
* Call bitcoind backupwallet to create a time/date-stamped wallet file.<br />
* GPG encrypt the wallet with my public key.<br />
* Copy the result to an off-machine backup location.<br />
<br />
It's using Amazon S3, which is itself redundantly backed up to multiple geographic locations automatically. Replace the s3cmd with an scp to copy somewhere if you're not an S3 user; you could even ftp somewhere, since the wallet is encrypted it doesn't matter if somebody is eavesdropping<br />
<br />
==== How many nodes are there? ====<br />
<br />
You can get a rough estimate by counting the number of users on the [irc://irc.lfnet.org/bitcoin #bitcoin] channel at irc.lfnet.org. Most Bitcoin nodes are constantly connected to this channel while running, though Bitcoin can be configured not to do so. A more accurate number can be gotten by running Bitcoin nonstop for a few days and then using [https://github.com/gavinandresen/bitcointools bitcointools] to analyze your addr.dat file. This shows the "last seen" times for ''all'' Bitcoin nodes.<br />
<br />
=== Economics ===<br />
<br />
==== I've lost my wallet, is there a way to recreate the lost coins in the system? ====<br />
No, coins that are lost are lost forever.<br />
The lost coins will not be recovered or regenerated at any time.<br />
<br />
==== Where does the value of Bitcoin stem from? What backs up Bitcoin? ====<br />
<br />
Bitcoin has value because it is accepted as payment by many. The initial market value was achieved when people speculated, that because of its properties, the currency would be accepted by others later on.<br />
<br />
When we say that a currency is backed up by gold, we mean that there's a promise in place that you can exchange the currency for gold. In a sense, you could say that Bitcoin is "backed up" by the price tags of merchants and currency exchangers - a price tag is a promise to exchange goods for a specified amount of currency. Of course, price tags may or may not be as long-term promises as those made by central banks or governments.<br />
<br />
It's a common misconception that Bitcoins gain their value from the cost of electricity required to generate them. Cost doesn't equal value - hiring 1,000 men to shovel a big hole in the ground may be costly, but not valuable. Also, even though scarcity is a critical requirement for a currency to be useful, it alone doesn't make anything valuable. Your fingerprints are scarce, but that doesn't mean they have any exchange value.<br />
<br />
At the time of this writing, Bitcoin's chain of proof is the result of over 6 quadrillion cryptographically secure, verified calculations carried out by many independent computers. This large and growing input of energy and technology is part of Bitcoin's value, and represents a substantial investment of resources by Bitcoin users in creating the benefits of a trustworthy medium of exchange.<br />
<br />
==== Isn't the minting process a waste of resources? ====<br />
<br />
All currencies need a method for regulating the money supply and creating circulation. To make Bitcoin secure, a large amount of computer work is required. The Bitcoin process for introducing new coins into circulation is designed to make the currency secure by encouraging users to perform the necessary computational work by awarding the role of introducing new coins into circulation in rough proportion the amount of computer power contributed to this goal.<br />
<br />
=== Technical ===<br />
<br />
==== Can generating nodes charge different transaction fees, or is this enforced by the network? ====<br />
<br />
Currently a generating node can charge whatever [[transaction fee]] they want. A transaction that doesn't pay the fee won't be included in any blocks produced by that node, but it will appear in later blocks by cheaper generators.<br />
<br />
It is [http://www.bitcoin.org/smf/index.php?topic=165.msg1595#msg1595 possible] for the network to enforce a fee rate, but this is not currently implemented. If [[Satoshi]] tried to implement this, only ''generating'' nodes would have a vote in whether the change would be accepted, so the change would have to be beneficial in some way to generators (ie, not too low).<br />
<br />
==== Does including more transactions in your block slow down your hashing rate? ====<br />
<br />
Not at all. You're hashing the block header, which contains only a fixed-size hash of all the transactions.<br />
<br />
==== Why is it using so much CPU? ====<br />
<br />
If you have "Generate coins" turned on, Bitcoin will calculate millions of [[hash|hashes]] per second in an attempt to solve the current [[block]]. This will use all of your idle CPU time, but Bitcoin runs at a low priority, so none of your other programs should be slowed down. Turning off coin generation should eliminate most CPU usage.<br />
<br />
==== Why can't it be doing something useful for humanity instead? ====<br />
<br />
[[hash|SHA-256 hashing]] has very specific properties that we need. In particular, it generates (with predictable CPU required) numbers that are for all practical purposes purely random, but in a way that is easily verifiable. There are no known "beneficial" calculations that could replace this.<br />
<br />
This CPU time and electricity is not entirely wasted, though: it helps protect the network from attack.<br />
<br />
==== How much network traffic does the bitcoin client generate? ====<br />
<br />
Almost none. These statistics were recorded before the outgoing connection limit was reduced from 15 to 8, so the current usage is probably even lower:<br />
<br />
* Bytes sent without Bitcoin: 2475590 (2.4MiB) per day<br />
* Bytes received without Bitcoin: 2798454 (2.7MiB) per day<br />
* Bytes sent with Bitcoin (not port forwarded): 2210854 (2.1MiB) per day<br />
* Bytes received with Bitcoin (not port forwarded): 4699445 (4.5MiB) per day<br />
* Bytes sent with Bitcoin (port forwarded): 20879040 (19.9MiB) per day<br />
* Bytes received with Bitcoin (port forwarded): 10954438 (10.4MiB) per day<br />
<br />
==== Can we expand the transaction protocol so it includes a message as well as an amount? ====<br />
<br />
The current implementation already supports processing arbitrary data in transactions through the complex transaction scripting mechanism. However:<br />
* You will be charged 0.01 BTC per kilobyte, just like all other transactions.<br />
* ECDSA (the public-key algorithm used by Bitcoin) doesn't support encryption, so you'll have to use something else if you want encryption.<br />
* The ability to actually use this feature to send messages will probably never be implemented in Bitcoin. It's not what the block chain was designed for.<br />
<br />
==== What happens when two nodes generate a block at the same time? ====<br />
<br />
This is very unlikely to happen but if it does: The tiebreak is which block the NEXT block builds on.<br />
<br />
Each node sends out it's 'winning' block. Some nodes on the network will hear about 'block A' first and assume it is the winning block, and some will hear about 'block B' first and assume it is the winning block. Then each 'half' will proceed hashing from there trying to generate the next block as normal.<br />
If a machine with 'block B' as its predecessor wins the next race by generating 'block C', it becomes the official winner, and the nodes who were working on A give up and start on C. (In this case the generator of 'block A' might be disappointed, because he thought he generated some coins, but he didn't because the network decided his block was no longer valid.)<br />
<br />
Note: block A and block B will usually contain the same list of transactions. Transactions not included will be made available to other future blocks for inclusion into the chain.<br />
<br />
==== What happens if someone sends me some coins but I am not connected? ====<br />
<br />
Any transfer to a 'valid' address should be successful. <br />
You don't need to have a client running to receive bitcoins.<br />
Once you create an address, any coins sent to it will just sit there waiting for you to spend them.<br />
<br />
==== Can I start bitcoind without it becoming a daemon process? ====<br />
<br />
No. That is expected to be added to the client at some point.<br />
<br />
=== Technical (Windows) ===<br />
<br />
==== Why am I not downloading any blocks? ====<br />
<br />
Add bitcoin.exe to the "Excluded processes" list of Microsoft Security Essentials.<br />
<br />
=== Developing ===<br />
<br />
==== Is there a mailing list? ====<br />
Yes. http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-list<br />
<br />
==== Is there a test network? ====<br />
Yes, run Bitcoin or bitcoind with the -testnet switch (beginning with version 0.3.14).<br />
<br />
There is a -testnet version of the Bitcoin Faucet at https://freebitcoins.appspot.com/TEST/.<br />
<br />
==== How do I build bitcoin? ====<br />
Forum thread on building v0.3: http://www.bitcoin.org/smf/index.php?topic=298.msg2366#msg2366<br />
There are some [http://heliacal.net/~solar/bitcoin/bitcoin-linuxbuild.pdf Build notes for linux type systems (pdf)]<br />
<br />
== See Also ==<br />
<br />
* [[FAQ]]<br />
<br />
[[Category:Technical]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Incidents&diff=9289Incidents2011-05-30T15:12:13Z<p>Firestorm: </p>
<hr />
<div>== Micropayment contamination ==<br />
Around September 29, 2010, people started [http://www.bitcoin.org/smf/index.php?topic=1306.0 reporting] that their sent transactions would not confirm. This happened because people modified Bitcoin to send sub-0.01 transactions without any fees. A 0.01 fee is required by the network for such transactions (essentially prohibiting them), so the transactions remained at 0 confirmations forever. This became a more serious issue because Bitcoin would send transactions using bitcoins gotten from transactions with 0 confirmations, and these resulting transactions would also never confirm. Because Bitcoin tends to prefer sending smaller coins, these invalid transactions quickly multiplied, contaminating the wallets of everyone who received them.<br />
<br />
Bitcoin was changed to only select coins with at least 1 confirmation. The remaining sub-0.01 transactions were cleared by generators who modified their version of Bitcoin to not require the micropayment fee. It took a while for everything to get cleared, though, because many of the intermediate transactions had been forgotten by the network by this point and had to be rebroadcast by the original senders.<br />
<br />
== Value overflow ==<br />
<br />
On August 15 2010, it was [http://www.bitcoin.org/smf/index.php?topic=822.0 discovered] that block 74638 contained a transaction that created over 184 billion bitcoins for two different addresses. This was possible because the code used for checking transactions before including them in a block didn't account for the case of outputs so large that they overflowed when summed. A new version was published within a few hours of the discovery. The block chain had to be forked. Although many unpatched nodes continued to build on the "bad" block chain, the "good" block chain overtook it at a block height of 74691. The bad transaction no longer exists for people using the longest chain.<br />
<br />
The block and transaction:<br />
<pre>CBlock(hash=0000000000790ab3, ver=1, hashPrevBlock=0000000000606865, hashMerkleRoot=618eba,<br />
nTime=1281891957, nBits=1c00800e, nNonce=28192719, vtx=2)<br />
CTransaction(hash=012cd8, ver=1, vin.size=1, vout.size=1, nLockTime=0)<br />
CTxIn(COutPoint(000000, -1), coinbase 040e80001c028f00)<br />
CTxOut(nValue=50.51000000, scriptPubKey=0x4F4BA55D1580F8C3A8A2C7)<br />
CTransaction(hash=1d5e51, ver=1, vin.size=1, vout.size=2, nLockTime=0)<br />
CTxIn(COutPoint(237fe8, 0), scriptSig=0xA87C02384E1F184B79C6AC)<br />
CTxOut(nValue=92233720368.54275808, scriptPubKey=OP_DUP OP_HASH160 0xB7A7)<br />
CTxOut(nValue=92233720368.54275808, scriptPubKey=OP_DUP OP_HASH160 0x1512)<br />
vMerkleTree: 012cd8 1d5e51 618eba<br />
<br />
Block hash: 0000000000790ab3f22ec756ad43b6ab569abf0bddeb97c67a6f7b1470a7ec1c<br />
Transaction hash: 1d5e512a9723cbef373b970eb52f1e9598ad67e7408077a82fdac194b65333c9</pre><br />
<br />
== OP_CHECKSIG abuse ==<br />
<br />
On July 29 2010, it was discovered that block [http://blockexplorer.com/block/00000000000997f9fd2fe1ee376293ef8c42ad09193a5d2086dddf8e5c426b56 71036] contained several transactions with a ton of OP_CHECKSIG commands. There should only ever be one such command. This caused every node to do extra unnecessary work, and it could have been used as a denial-of-service attack. A new version of Bitcoin was quickly released. The new version did not cause a fork on the main network, though it did cause one on the test network (where someone had played around with the attack more).<br />
<br />
== LSHIFT and RETURN bugs ==<br />
<br />
On July 28 2010 two bugs were discovered and demonstrated on the test network. The first caused bitcoin to crash on some machines when processing a transaction containing an OP_LSHIFT. The second exploited another bug in the transaction handling code and allowed an attacker to spend coins that they did not own. Neither were exploited on the main network, and both were fixed by Bitcoin version 0.3.5.<br />
<br />
After these bugs were discovered, many currently-unused [[script]] words were disabled for safety.<br />
<br />
[[Category:Technical]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Category:History&diff=9288Category:History2011-05-30T15:12:05Z<p>Firestorm: </p>
<hr />
<div>* October 31, 2008<br />
** [http://article.gmane.org/gmane.comp.encryption.general/12588/ Bitcoin design paper] published<br />
* November 09, 2008<br />
** Bitcoin project registered at SourceForge.net<br />
* January 3, 2009<br />
** Genesis block established at 18:15:05 GMT<br />
* January 11, 2009<br />
** Bitcoin v0.1 released and announced on the [http://www.mail-archive.com/cryptography@metzdowd.com/msg10152.html cryptography mailing list]<br />
* December 16, 2009<br />
** Bitcoin v0.2 released<br />
* December 30, 2009<br />
** First difficulty increase at 06:11:04 GMT<br />
* February 6, 2010<br />
** [[Bitcoin Market]] established<br />
* May 22, 2010<br />
** laszlo first to buy pizza with Bitcoins [http://www.bitcoin.org/smf/index.php?topic=137.msg1195#msg1195 agreeing] upon paying 10,000 BTC for ~$25 worth of pizza courtesy of jercos<br />
* July 7, 2010<br />
** Bitcoin v0.3 released<br />
* July 11, 2010<br />
** Bitcoin v0.3 release [http://news.slashdot.org/story/10/07/11/1747245/Bitcoin-Releases-Version-03 mentioned on slashdot], bringing a large influx of new bitcoin users.<br />
* July 17, 2010<br />
** [[MtGox]] established<br />
* July 18, 2010<br />
** ArtForz generated his first block after establishing his personal OpenCL GPU hash farm<br />
* August 15, 2010<br />
** [[Incidents#Value_overflow|74638]]<br />
* September 14, 2010<br />
** jgarzik [http://www.bitcoin.org/smf/index.php?topic=133.msg12921#msg12921 offered] 10,000 BTC (valued at ~$600-650) to puddinpop to open source their windows-based CUDA client<br />
* September 18, 2010<br />
** puddinpop [http://www.bitcoin.org/smf/index.php?topic=133.msg13135#msg13135 released] source to their windows-based CUDA client under MIT license<br />
* September 29, 2010<br />
** kermit [http://www.bitcoin.org/smf/index.php?topic=1306.0 discovered] a microtransactions exploit which precipitated the Bitcoin v0.3.13 release<br />
* October 01, 2010<br />
** First public OpenCL miner released<br />
* October 04, 2010<br />
** Original Bitcoin History wiki page (this page) established (ooh so meta) on Bitcoin.org's wiki.<br />
* October 28, 2010<br />
** First bitcoin short sale transaction initiated, with a loan of 100 BTC by nanotube to [[User:Kiba|kiba]], facilitated by the [[Bitcoin-otc|#bitcoin-otc]] market.<br />
* November 6, 2010<br />
** The [http://www.bitcoin.org/smf/index.php?topic=1672 Bitcoin economy passed US $1 million]. The MtGox price touched USD $0.50.<br />
* December 7, 2010<br />
** Bitcoind was compiled for the Nokia N900 mobile computer by doublec. The following day, ribuck sent him 0.42 BTC in the first portable-to-portable Bitcoin transaction.<br />
* December 9, 2010<br />
** The generation difficulty passed 10,000.<br />
** First bitcoin call option contract sold, from nanotube to [[User:Sgornick|sgornick]], via the [[Bitcoin-otc|#bitcoin-otc]] market.<br />
* December 16, 2010<br />
** [http://mining.bitcoin.cz/ Bitcoin Pooled Mining], operated by slush, found its first block<br />
* January 2, 2011<br />
** [[Tonal BitCoin]] units standardized.<br />
* January 8, 2011<br />
** [[History of Bitcoin]] page (this page) created after replicating from original Bitcoin History page on Bitcoin.org.<br />
** Bitcoin Pooled Mining reached a total of 10,000 Mhash/s<br />
* January 27, 2011<br />
** Largest numeric value ever traded for bitcoins thus far occurred on this date. Three currency bills from Zimbabwe, known as Zimdollars, were traded on [[Bitcoin-otc|#bitcoin-otc]] at the rate of 4 BTC for each of the one-hundred trillion dollar ($100,000,000,000,000) Zimbabwe notes<ref>Serial numbers for Zimdollars sold: AA1669317, AA1669318 and AA1669319</ref><br />
* January 28, 2011<br />
** Block 105000 was generated. This means that 5.25 million bitcoins have been generated, which is just over one-quarter of the eventual total of nearly 21 million.<br />
* February 9, 2011<br />
** Decimal Bitcoin reached parity with the US dollar, touching $1 per BTC at [[MtGox]].<br />
* February 10, 2011<br />
** Bitcoin.org website struggles to handle [http://www.bitcoin.org/smf/index.php?topic=3444.0 traffic] resulting from mentions on Slashdot<ref>[http://news.slashdot.org/story/11/02/10/189246/Online-Only-Currency-BitCoin-Reaches-Dollar-Parity Online-Only Currency BitCoin Reaches Dollar Parity]</ref>, Hacker News and Twitter following the news that parity had been reached.<br />
* February 14, 2011<br />
** A vehicle was, for the first time, offered in exchange for a certain number of bitcoins<ref>[http://www.bitcoin.org/smf/index.php?topic=3485.0 Car for Sale - Australia]</ref>.<br />
* March 6, 2011<br />
** Total Bitcoin network computation speed for a short time [http://bitcoin.sipa.be/speed-lin.png reached an all-time high of almost 900Ghash/sec], dropping to 500Ghash/sec soon after. Some speculate that this was due to some supercomputer or bot-net that joined the network ([http://bitcoin.atspace.com/mysteryminer.html mystery miner]).<br />
* March 18, 2011<br />
** BTC/USD exchange rate reaches a 6-week low point at almost $0.70/BTC, after what appeared to be a short burst of, possibly automated, BTC sales at progressively lower prices. BTC price had been declining since the February 9 high.<br />
* March 25, 2011<br />
** Difficulty decreased nearly 10%. A decrease has only occurred once before, and this decrease of nearly 10% was the largest.<br />
* March 27, 2011<br />
** The first market for exchanging bitcoins to and from the British Pound Sterling BTC/GBP, [[Britcoin]], opens.<br />
* March 31, 2011<br />
** The first market for exchanging bitcoins to and from Brazilian Reals, [[Bitcoin Brazil]], opens.<br />
* April 5, 2011<br />
** The first market for exchanging bitcoins to and from the Polish złoty, [[BitMarket.eu]], opens.<br />
* April 12, 2011<br />
** First bitcoin put option contract sold via the [[Bitcoin-otc|#bitcoin-otc]] market.<br />
* April 16, 2011<br />
** TIME does [http://techland.time.com/2011/04/16/online-cash-bitcoin-could-challenge-governments/ an article on Bitcoin].<br />
* April 23, 2011<br />
** BTC/USD exchange rate reaches and passes parity with the Euro (EUR) on [[MtGox]] exchange.<br />
** BTC/USD exchange rate reaches and passes parity with the British Sterling Pound (GBP) on [[MtGox]] exchange.<br />
** Value of the Bitcoin money stock at current exchange rate passes $10 million USD threshold.<br />
* April 27, 2011<br />
** [[VirWoX]] opens first market to trade bitcoins against a virtual currency on BTC/SL (Second Life Lindens) exchange.<br />
* April 28, 2011<br />
** Block [http://blockexplorer.com/b/120630 120,630] is first to be mined using split allocation of the generation reward.<br />
* April 30, 2011<br />
** The generation difficulty passed 100,000.<br />
* May 10, 2011<br />
** The exchange rate at [[MtGox]] touched 6 USD per BTC.<br />
<br />
==References==<br />
<references /></div>Firestormhttps://en.bitcoin.it/w/index.php?title=Help:FAQ&diff=9287Help:FAQ2011-05-30T15:11:58Z<p>Firestorm: </p>
<hr />
<div>Here you will find answers to the most commonly asked questions.<br />
<br />
== General ==<br />
=== What are bitcoins? ===<br />
Bitcoins are the unit of currency of the Bitcoin system. A commonly used shorthand for this is “BTC” to refer to a price or amount (eg: “100 BTC”)<br />
A Bitcoin isn't actually a 'thing' you can point at. It is just a number associated with a [[Address|Bitcoin Address]]. See also an [[Introduction|easy intro]] to bitcoin.<br />
<br />
=== How can I get Bitcoins? ===<br />
<br />
There are four ways to get Bitcoins:<br />
<br />
* Buy them on an exchange such as [https://www.mtgox.com/ Mt. Gox] or [http://www.bitcoin-otc.com/ #bitcoin-otc] on FreeNode.<br />
* Accept Bitcoins as payment for goods or services.<br />
* Find a local trader on [http://tradebitcoin.com tradebitcoin] (or somewhere else) and trade with him in cash<br />
* Create a new [[block]] (currently yields 50 Bitcoins).<br />
* Participate in a [[Pooled mining|mining pool]].<br />
<br />
=== Can I buy Bitcoins with Paypal? ===<br />
<br />
While it's possible to find an individual who wishes to sell Bitcoin to you via Paypal, (perhaps via [http://www.bitcoin-otc.com/ #bitcoin-otc] ) most major exchanges do not allow funding through Paypal. This is due to repeated cases where someone pays for Bitcoins with Paypal, receives their Bitcoins, and then fraudulently complains to Paypal that they never received their goods. Paypal too often sides with the fraudulent buyer in this case, and so exchangers no longer allow this method of funding.<br />
<br />
Buying Bitcoins from individuals with this method is still possible, but requires mutual trust. In this case, Bitcoin seller beware.<br />
<br />
=== How are new Bitcoins created? ===<br />
<br />
[[File:total_bitcoins_over_time_graph.png|thumb|Number of bitcoins over time, assuming a perfect 10-minute interval.]]<br />
New coins are generated by a network node each time it finds the solution to a certain mathematical problem (i.e. creates a new [[block]]), which is difficult to perform and can demonstrate a [[proof of work]]. The reward for solving a block is [[controlled inflation|automatically adjusted]] so that in the first 4 years of the Bitcoin network, 10,500,000 BTC will be created. The amount is halved each 4 years, so it will be 5,250,000 over years 4-8, 2,625,000 over years 8-12 and so on. Thus the total number of coins will approach 21,000,000 BTC over time.<br />
<br />
In addition, built into the network is a system that attempts to allocate new coins in blocks about every 10 minutes, on average, somewhere on the network. As the number of people who attempt to generate these new coins changes, the difficulty of creating new coins changes. This happens in a manner that is agreed upon by the network as a whole, based upon the time taken to generate the previous 2016 blocks. The difficulty is therefore related to the average computing resources devoted to generate these new coins over the time it took to create these previous blocks. The likelihood of somebody "discovering" one of these blocks is based on the computer they are using compared to all of the computers also generating blocks on the network.<br />
<br />
=== What's the current total number of Bitcoins in existence? ===<br />
<br />
[http://blockexplorer.com/q/totalbc Current count]<br />
<br />
The number of blocks times the coin value of a block is the number of coins in existence. The coin value of a block is 50 BTC for each of the first 210,000 blocks, 25 BTC for the next 210,000 blocks, then 12.5 BTC, 6.25 BTC and so on.<br />
<br />
=== How divisible are Bitcoins? ===<br />
<br />
Technically, a Bitcoin can be divided down to 8 decimals using existing data structures, so 0.00000001 BTC is the smallest amount currently possible. Discussions about and ideas for ways to provide for even smaller quantities of Bitcoins may be created in the future if the need for them ever arises.<br />
<br />
=== How does the halving work when the number gets really small? ===<br />
<br />
The reward will go from 0.00000001 BTC to 0. Then no more coins will likely be created. <br />
<br />
The calculation is done as a right bitwise shift of a 64-bit signed integer, which means it is divided by 2 and rounded down. The integer is equal to the value in BTC * 100,000,000. This is how all Bitcoin balances/values are stored internally.<br />
<br />
Keep in mind that using current rules this will take nearly 100 years before it becomes an issue and Bitcoins may change considerably before that happens.<br />
<br />
=== How long will it take to generate all the coins? ===<br />
<br />
The last block that will generate coins will be block #6,929,999. This should be generated around year 2140. Then the total number of coins in circulation will remain static at 20,999,999.9769 BTC.<br />
<br />
Even if the allowed precision is expanded from the current 8 decimals, the total BTC in circulation will always be slightly below 21 million (assuming everything else stays the same). For example, with 16 decimals of precision, the end total would be 20999999.999999999496 BTC.<br />
<br />
=== If no more coins are going to be generated, will more blocks be created? ===<br />
<br />
Absolutely! Even before the creation of coins ends, the use of [[transaction fee|transaction fees]] will likely make creating new blocks more valuable from the fees than the new coins being created. When coin generation ends, what will sustain the ability to use bitcoins will be these fees entirely. There will be blocks generated after block #6,929,999, assuming that people are still using Bitcoins at that time.<br />
<br />
=== But if no more coins are generated, what happens when Bitcoins are lost? Won't that be a problem? ===<br />
<br />
Not at all. Because of the law of supply and demand, when fewer Bitcoins are available the ones that are left will be in higher demand, and therefore will have a higher value. So when Bitcoins are lost, the remaining Bitcoins will increase in value to compensate. As the value of Bitcoins increase, the number of Bitcoins required to purchase an item '''de'''creases. This is known as a [[Deflationary spiral|deflationary economic model]]. Eventually, if and when it gets to the point where the largest transaction is less that 1BTC, then it's a simple matter of shifting the decimal place to the right a few places, and the system continues.<br />
<br />
=== If every transaction is broadcast via the network, does BitCoin scale? ===<br />
The Bitcoin protocol allows lightweight clients that can use Bitcoin without downloading the entire transaction history. As traffic grows and this becomes more critical, implementations of the concept will be developed. Full network nodes will at some point become a more specialized service.<br />
<br />
With some modifications to the software, full BitCoin nodes could easily keep up with both VISA and MasterCard combined, using only fairly modest hardware (a couple of racks of machines using todays hardware). It's worth noting that the MasterCard network is structured somewhat like BitCoin itself - as a peer to peer broadcast network.<br />
<br />
Learn more about [[Scalability]].<br />
<br />
=== How does the BitCoin network handle [http://en.wikipedia.org/wiki/CAP_theorem the CAP theorem]? ===<br />
<br />
=== Why do I have to wait 10 minutes before I can spend money I received? ===<br />
<br />
The reason you have to wait 10 minutes is that's the average time taken to find a block. It can be significantly more or less time than that depending on luck, 10 minutes is simply the average case. <br />
<br />
Blocks (shown as "confirmations" in the GUI) are how the BitCoin achieves consensus on who owns what. Once a block is found everyone agrees that you now own those coins, so you can spend them again. Until then it's possible that some network nodes believe otherwise, if somebody is attempting to defraud the system by reversing a transaction. The more confirmations a transaction has, the less risk there is of a reversal. Only 6 blocks or 1 hour is enough to make reversal computationally impractical. This is dramatically better than credit cards which can see chargebacks occur up to three months after the original transaction!<br />
<br />
Why ten minutes specifically? It is a tradeoff chosen by Satoshi between propagation time of new blocks in large networks and the amount of work wasted due to chain splits. If that made no sense to you, don't worry. Reading [http://www.bitcoin.org/bitcoin.pdf the technical paper] should make things clearer.<br />
<br />
=== Do you have to wait 10 minutes in order to buy or sell things with BitCoin? ===<br />
<br />
No, it's reasonable to sell things without waiting for a confirmation as long as the transaction is not of high value.<br />
<br />
When people ask this question they are usually thinking about applications like supermarkets or snack machines, as discussed in [http://www.bitcoin.org/smf/index.php?topic=423.msg3819#msg3819 this thread from July 2010]. Zero confirmation transactions still show up in the GUI, but you cannot spend them. You can however reason about the risk involved in assuming you ''will'' be able to spend them in future. In general, selling things that are fairly cheap (like snacks, digital downloads etc) for zero confirmations will not pose a problem if you are running a well connected node.<br />
<br />
=== Why does my Bitcoin address keep changing? ===<br />
<br />
Whenever the address listed in "Your address" receives a transaction, Bitcoin replaces it with a new address. This is meant to encourage you to use a new address for every transaction, which enhances [[anonymity]]. All of your old addresses are still usable: you can see them in ''Settings -> Your Receiving Addresses''.<br />
<br />
==Economy==<br />
=== Where does the value of Bitcoin stem from? What backs up Bitcoin? ===<br />
Bitcoins have value because they are accepted as payment by many. See the [[Trade|list of Bitcoin-accepting sites]].<br />
<br />
When we say that a currency is backed up by gold, we mean that there's a promise in place that you can exchange the currency for gold. In a sense, you could say that Bitcoin is "backed up" by the price tags of merchants – a price tag is a promise to exchange goods for a specified amount of currency.<br />
<br />
It's a common misconception that Bitcoins gain their value from the cost of electricity required to generate them. Cost doesn't equal value – hiring 1,000 men to shovel a big hole in the ground may be costly, but not valuable. Also, even though scarcity is a critical requirement for a useful currency, it alone doesn't make anything valuable. For example, your fingerprints are scarce, but that doesn't mean they have any exchange value.<br />
<br />
=== What if someone bought up all the existing Bitcoins? ===<br />
What if somebody bought up all the gold in the world? Well, by attempting to buy it all, the buyer would just drive the prices up until he runs out of money.<br />
<br />
Not all Bitcoins are for sale. Just as with gold, no one can buy a Bitcoin that isn't available for sale.<br />
<br />
=== Bitcoin's monetary policy causes a deflationary spiral ===<br />
See the article [[Deflationary spiral]].<br />
<br />
=== Doesn't Bitcoin unfairly benefit early adopters? ===<br />
Early adopters have a large number of bitcoins now because they took a risk and invested resources in an unproven technology. By so doing, they have helped Bitcoin become what it is now and what it will be in the future (hopefully, a ubiquitous decentralized digital currency). It is only fair they will reap the benefits of their successful investment.<br />
<br />
In any case, any bitcoin generated will probably change hands dozens of time as a medium of exchange, so the profit made from the initial distribution will be insignificant compared to the total commerce enabled by Bitcoin.<br />
<br />
=== Is Bitcoin a Ponzi scheme? ===<br />
In a Ponzi Scheme, the founders persuade investors that they’ll profit. Bitcoin does not make such a guarantee. There is no central entity, just individuals building an economy.<br />
<br />
A ponzi scheme is a zero sum game. Early adopters can only profit at the expense of late adopters. Bitcoin has possible win-win outcomes. Early adopters profit from the rise in value. Late adopters profit from the usefulness of a stable and widely accepted p2p currency.<br />
<br />
The fact that early adopters benefit more doesn't alone make anything a ponzi scheme. Apple stocks aren't ponzi even though the early investors got rich.<br />
<br />
==Networking==<br />
=== Do I need to configure my firewall to run bitcoin? ===<br />
<br />
Bitcoin will connect to other nodes, usually on tcp port 8333. You will need to allow outgoing TCP connections to port 8333 if you want to allow your bitcoin client to connect to many nodes. Bitcoin will also try to connect to IRC (tcp port 6667) to meet other nodes to connect to.<br />
<br />
If you want to restrict your firewall rules to a few ips and/or don't want to allow IRC connection, you can find stable nodes in the [[Fallback Nodes|fallback nodes list]]. If your provider blocks the common IRC ports, note that lfnet also listens on port 7777. Connecting to this alternate port currently requires either recompiling Bitcoin, or changing routing rules. For example, on Linux you can evade a port 6667 block by doing something like this:<br />
<br />
echo 173.246.103.92 irc.lfnet.org >> /etc/hosts<br />
iptables -t nat -A OUTPUT -p tcp --dest 173.246.103.92 --dport 6667 -j DNAT --to-destination :7777 -m comment --comment "bitcoind irc connection"<br />
<br />
<br />
=== How does the peer finding mechanism work? ===<br />
Bitcoin finds peers primarily by connecting to an IRC server (channel #bitcoin on irc.lfnet.org). If a connection to the IRC server cannot be established (like when connecting through TOR), an in-built node list will be used and the nodes will be queried for more node addresses.<br />
<br />
==Mining==<br />
===What is mining?===<br />
Mining is the process of spending computation power to find valid blocks and thus create new Bitcoins.<br />
<br />
Technically speaking, mining is the calculation of a [[hash]] of the previous block and a [[nonce]]. If the hash value is found to be less than the current [[difficulty]], a new block is formed and the miner gets 50 newly generated Bitcoins. If the hash is not less than the current difficulty, a new nonce is used, and a new hash is calculated. This is done thousands or millions of times per second by each miner.<br />
<br />
===I've been mining for a long time and haven't created any new Bitcoins. What's wrong?===<br />
<br />
In the early days of Bitcoin, it was easy for anyone to find new blocks using standard CPUs. As more and more people started mining, the [[difficulty]] of finding new blocks has greatly increased to the point where the average time for a CPU to find a single block can be many years. The only cost- or time-effective method of mining is using a high-end graphics card with special software (see also [[Why a GPU mines faster than a CPU]]). Since CPU mining is essentially useless, it may be removed from future versions of the Bitcoin software.<br />
<br />
===Is mining used for some useful computation?===<br />
The computations done when mining are internal to Bitcoin and not related to any other distributed computing projects. They serve the purpose of securing the Bitcoin network, which is useful.<br />
<br />
===Is it not a waste of energy?===<br />
Spending energy on creating a free monetary system is hardly a waste. Also, services necessary for the operation of currently widespread monetary systems, such as banks and credit card companies, also spend energy, arguably more than Bitcoin would.<br />
<br />
===Why don't we use calculations that are also useful for some other purpose?===<br />
To provide security for the Bitcoin network, the calculations involved need to have some very specific features. These features are incompatible with leveraging the computation for other purposes.<br />
<br />
==Help==<br />
===I'd like to learn more. Where can I get help?===<br />
<br />
* Read the [[Introduction|introduction to bitcoin]] <br />
* See the videos, podcasts, and blog posts from the [[Press]]<br />
* Read and post on the [[Bitcoin:Community_portal#Bitcoin_Community_Forums|forums]]<br />
* Chat on one of the [[Bitcoin:Community_portal#IRC_Chat|Bitcoin IRC]] channels<br />
* Listen to [http://omegataupodcast.net/2011/03/59-bitcoin-a-digital-decentralized-currency/ this podcast], which goes into the details of how bitcoin works<br />
<br />
==See Also==<br />
<br />
* [[Man page]]<br />
* [[Introduction]]<br />
<br />
[[zh-cn:FAQ]]<br />
[[fr:FAQ]]<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Difficulty&diff=9286Difficulty2011-05-30T15:11:01Z<p>Firestorm: </p>
<hr />
<div>''See also: [[target]]''<br />
<br />
=== What is "difficulty"? ===<br />
<br />
Difficulty is a measure of how difficult it is to find a new [[block]] compared to the easiest it can ever be.<br />
<br />
=== How often does the difficulty change? ===<br />
<br />
Every 2016 [[block|blocks]].<br />
<br />
=== What is the formula for difficulty? ===<br />
<br />
difficulty = maximum_target / current_target <br />
<br />
(target is a 256 bit number)<br />
<br />
===How is difficulty stored in blocks?===<br />
<br />
Difficulty is stored in blocks as a 4 byte integer, and the actual hexadecimal [[target]] is derived from it via a predefined formula. For example, if the difficulty in the block is 0x1b0404cb, the hexadecimal target is<br />
0x0404cb * 2**(8*(0x1b - 3)) = 0x00000000000404CB000000000000000000000000000000000000000000000000<br />
<br />
The highest possible target (difficulty 1) is defined as 0x1d00ffff, which gives us a hex target of<br />
0x00ffff * 2**(8*(0x1d - 3)) = 0x00000000FFFF0000000000000000000000000000000000000000000000000000<br />
<br />
So the difficulty at 0x1b0404cb is therefore:<br />
0x00000000FFFF0000000000000000000000000000000000000000000000000000 /<br />
0x00000000000404CB000000000000000000000000000000000000000000000000 <br />
= 16307.420938523983<br />
<br />
=== What is the current difficulty? ===<br />
[http://blockexplorer.com/q/getdifficulty Current difficulty], as output by BitCoin's getDifficulty.<br />
<br />
[http://nullvoid.org/bitcoin/difficultiez.php Difficulty History]<br />
<br />
[http://bitcoin.sipa.be Graphs]<br />
<br />
=== What is the maximum difficulty? ===<br />
The maximum difficulty is roughly: maximum_target / 1, which is a ridiculously huge number (about 2^224). <br />
<br />
The actual maximum difficulty is when current_target=0, but we would not be able to calculate the difficulty if that happened. (fortunately it never will, so we're ok.)<br />
<br />
=== Can the difficulty go down? ===<br />
Yes it can. See discussion in [[target]].<br />
<br />
=== What is the minimum difficulty? ===<br />
The minimum difficulty, when the target is at the maximum allowed value, is 1.<br />
<br />
=== What network hash rate results in a given difficulty? ===<br />
The difficulty is adjusted every 2016 blocks based on the time it took to find the previous 2016 blocks. At the desired rate of one block each 10 minutes, 2016 blocks would take exactly two weeks to find. If the previous 2016 blocks took more than two weeks to find, the difficulty is reduced. If they took less than two weeks, the difficulty is increased. The change in difficulty is in proportion to the amount of time over or under two weeks the previous 2016 blocks took to find.<br />
<br />
To find a block, the hash must be less than the target. The hash is effectively a random number between 0 and 2**256-1. The offset for difficulty 1 is<br />
0xffff * 2**208<br />
and for difficulty D is<br />
0xffff * 2**208)/D<br />
<br />
The expected number of hashes we need to calculate to find a block with difficulty D is therefore<br />
D * 2**256 / (0xffff * 2**208)<br />
or just<br />
D * 2**48 / 0xffff<br />
<br />
The difficulty is set such that the previous 2016 blocks would have been found at the rate of one every 10 minutes, so we were calculating (D * 2**48 / 0xffff) hashes in 600 seconds. That means the hash rate of the network was<br />
D * 2**48 / 0xffff / 600<br />
over the previous 2016 blocks. Can be further simplified to<br />
D * 2**32 / 600<br />
without much loss of accuracy.<br />
<br />
At difficulty 1, that is around 7 Mhashes per second.<br />
<br />
At the time of writing, the difficulty is 22012.4941572, which means that over the previous set of 2016 blocks found the average network hash rate was<br />
22012.4941572 * 2**32 / 600 = around 157 Ghashes per second.<br />
<br />
=== How soon might I expect to generate a block? ===<br />
(The [https://www.bitcoin.org/smf/index.php?topic=1682.0 eternal question].)<br />
<br />
The average time to find a block can be approximated by calculating:<br />
time = difficulty * 2**32 / hashrate<br />
where difficulty is the current difficulty, hashrate is the number of hashes your miner calculates per second, and time is the average in seconds between the blocks you find.<br />
<br />
For example, using Python we calculate the average time to generate a block using a 1Ghash/s mining rig when the difficulty is 20000:<br />
$ python -c "print 20000 * 2**32 / 10**9 / 60 / 60.0"<br />
23.85<br />
and find that it takes just under 24 hours on average.<br />
<br />
* Any one grinding of the hash stands the same chance of "winning" as any other. The numbers game is how many attempts your hardware can make per second.<br />
* You need to know the difficulty (above) and your khash/sec rate (reported by the client).<br />
** [[Mining Hardware Comparison]] has some stats that may help you predict what you could get.<br />
* Visit a calculator or perform the maths yourself,<br />
** http://www.alloscomp.com/bitcoin/calculator.php<br />
* Remember it's just probability! There are no guarantees you will win every N days.<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Block&diff=9285Block2011-05-30T15:10:52Z<p>Firestorm: </p>
<hr />
<div>Data is permanently recorded in the Bitcoin network through '''blocks'''. Each block contains all recent [[transactions]], a [[nonce]] (random number), and the [[hash]] of the previous block. A block is "solved" (published and considered valid by peers) when the SHA-256 hash of the entire block is below the current [[target]]. This is very unlikely to occur after being hashed only once, so the nonce must be incremented and the block re-hashed millions of times until it does. <br />
<br />
Bitcoin transactions are broadcast to the [[network]] by the sender, and all peers generating coins collect them and add them to the block they're working on. If the transaction is much larger than the average transaction size, a small [[transaction fee]] may be charged.<br />
<br />
The first transaction in the block is special: it creates new [[Bitcoins]] for the person who generated it. Other peers will only accept the block if this transaction is of the correct amount. The number of [[Bitcoins]] generated per block starts at 50 and is halved every 210,000 blocks (about four years).<br />
<br />
The network tries to create 6 blocks per hour. Every 2016 blocks (about two weeks), all Bitcoin clients compare the actual number created with this goal and modify the target by the percentage that it varied. This increases (or decreases) the difficulty of generating blocks.<br />
<br />
The client accepts the 'longest' chain of blocks as valid. The 'length' of the entire [[block chain]] refers to the chain with the most combined difficulty, not the one with the most blocks. This prevents someone from forking the chain and creating a large number of low-difficulty blocks, and having it accepted by the network as 'longest'. <br />
<br />
== Common Questions about Blocks ==<br />
<br />
=== How many blocks are there? ===<br />
[http://blockexplorer.com/q/getblockcount Current block count]<br />
<br />
=== What is the maximum number of blocks? ===<br />
There is no maximum number, blocks just keep getting added to the end of the chain at an average rate of one every 10 minutes.<br />
<br />
==== Even when all 21 million coins have been generated? ====<br />
Yes. The blocks are for proving that transactions existed at a particular time. Transactions will still occur once all the coins have been generated, so blocks will still be created as long as people are trading Bitcoins.<br />
<br />
=== How long will it take me to generate a block? ===<br />
No-one can say exactly. There is a [[Generation Calculator|generation calculator]] that will tell you how long it '''might''' take.<br />
<br />
=== What if I'm 1% towards calculating a block and...? ===<br />
There's no such thing as being 1% towards solving a block. You don't make progress towards solving it. After working on it for 24 hours, your chances of solving it are equal to what your chances were at the start or at any moment.<br />
<br />
It's like trying to flip 37 coins at once and have them all come up heads. Each time you try, your chances of success are the same.<br />
<br />
=== Where can I find more technical detail? ===<br />
There is more technical detail on the [[block hashing algorithm]] page.<br />
<br />
==See Also==<br />
<br />
* [http://en.bitcoin.it/wiki/File:Total_bitcoins_over_time_graph.png Total Bitcoins Over Time]<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]<br />
<br />
[[fr:Blocs]][[zh-cn:Block]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Block_hashing_algorithm&diff=9284Block hashing algorithm2011-05-30T15:10:43Z<p>Firestorm: </p>
<hr />
<div>When generating, you constantly hash the block header. The block is also occasionally updated as you are working on it. A block header contains these fields:<br />
{| class="wikitable"<br />
|-<br />
! Field<br />
! Purpose<br />
! Updated when...<br />
|-<br />
|Version<br />
|Block version number<br />
|You upgrade the software and it specifies a new version<br />
|-<br />
|Previous hash<br />
|Hash of the previous block<br />
|A new block comes in<br />
|-<br />
|Merkle root<br />
|256-bit hash based on all of the transactions<br />
|A transaction is accepted<br />
|-<br />
|Timestamp<br />
|Current timestamp<br />
|Every few seconds<br />
|-<br />
|"Bits"<br />
|Current [[target]] in compact format<br />
|The [[difficulty]] is adjusted<br />
|-<br />
|Nonce<br />
|32-bit number (starts at 0)<br />
|A hash is tried (increments)<br />
|}<br />
<br />
The body of the block contains the transactions. These are hashed only indirectly through the Merkle root. Because transactions aren't hashed directly, hashing a block with 1 transaction takes exactly the same amount of effort as hashing a block with 10,000 transactions.<br />
<br />
Most of these fields will be the same for all users. There might be some minor variation in the timestamps. The nonce will usually be different, but it increases in a strictly linear way. "Nonce" starts at 0 and is incremented for each hash. Whenever Nonce overflows (which it does frequently), the extraNonce portion of the generation transaction is incremented, which changes the Merkle root.<br />
<br />
Given just those fields, people would frequently generate the exact same sequence of hashes as each other and the fastest CPU would almost always win. However, it is (nearly) impossible for two people to have the same Merkle root because the first transaction in your block is a generation "sent" to one of ''your'' unique Bitcoin addresses. Since your block is different from everyone else's blocks, you are (nearly) guaranteed to produce different hashes. Every hash you calculate has the same chance of winning as every other hash calculated by the network.<br />
<br />
Bitcoin uses: SHA256(SHA256(Block_Header))<br />
<br />
For some people, seeing a working example is best, [http://pastebin.com/Ya3604J0 here] is a version in plain C without any optimization, threading or error checking.<br />
<br />
[[Category:Technical]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=API_reference_(JSON-RPC)&diff=9283API reference (JSON-RPC)2011-05-30T15:10:32Z<p>Firestorm: </p>
<hr />
<div>== Controlling Bitcoin ==<br />
<br />
Run ''bitcoind'' or ''bitcoin -server''. You can control it via the command-line or by [http://json-rpc.org/wiki/specification| HTTP JSON-RPC] commands.<br />
<br />
You must create a bitcoin.conf configuration file setting an rpcuser and rpcpassword; see [[Running Bitcoin]] for details.<br />
<br />
Now run:<br />
$ ./bitcoind<br />
bitcoin server starting<br />
$ ./bitcoind help<br />
# shows the help text<br />
<br />
A [[Original Bitcoin client/API Calls list|list of RPC calls]] will be shown.<br />
<br />
$ ./bitcoind getbalance<br />
2000.00000<br />
<br />
== JSON-RPC ==<br />
<br />
Running Bitcoin with the -server argument (or running bitcoind) tells it to function as a [http://json-rpc.org/wiki/specification| HTTP JSON-RPC] server, but <br />
[http://en.wikipedia.org/wiki/Basic_access_authentication Basic access authentication] must be used when communicating with it, and, for security, by default, the server only accepts connections from other processes on the same machine. If your HTTP or JSON library requires you to specify which 'realm' is authenticated, use 'jsonrpc'.<br />
<br />
Bitcoin supports SSL (https) JSON-RPC connections beginning with version 0.3.14. See the [[Enabling SSL on original client daemon|rpcssl wiki page]] for setup instructions and a list of all bitcoin.conf configuration options.<br />
<br />
To access the server you should find a [http://json-rpc.org/wiki/implementations|suitable library] for your language.<br />
<br />
== Proper money handling ==<br />
<br />
See the [[Proper Money Handling (JSON-RPC)|proper money handling page]] for notes on avoiding rounding errors when handling bitcoin values.<br />
<br />
== Python ==<br />
<br />
[http://json-rpc.org/wiki/python-json-rpc python-jsonrpc] is the official JSON-RPC implementation for Python.<br />
It automatically generates Python methods for RPC calls.<br />
However, due to its design for supporting old versions of Python, it is also rather inefficient.<br />
[[User:jgarzik|jgarzik]] has forked it as [https://github.com/jgarzik/python-bitcoinrpc Python-BitcoinRPC] and optimized it for current versions (at least Python 2.6+, though not 3.x).<br />
Generally, this version is recommended.<br />
<br />
While BitcoinRPC lacks a few obscure features from jsonrpc, software using only the ServiceProxy class can be written the same to work with either version the user might choose to install:<br />
<br />
<source lang="python"><br />
from jsonrpc import ServiceProxy<br />
<br />
access = ServiceProxy("http://user:password@127.0.0.1:8332")<br />
access.getinfo()<br />
access.listreceivedbyaddress(6)<br />
#access.sendtoaddress("11yEmxiMso2RsFVfBcCa616npBvGgxiBX", 10)<br />
</source><br />
<br />
== Ruby ==<br />
<br />
<source lang="ruby"><br />
=begin<br />
Make sure to do:<br />
gem install rest-client<br />
<br />
Usage:<br />
h = ServiceProxy.new('http://user:password@127.0.0.1:8332')<br />
puts h.getinfo.call<br />
puts h.getbalance.call 'accname'<br />
=end<br />
require 'json'<br />
require 'rest_client'<br />
<br />
class JSONRPCException < RuntimeError<br />
def initialize()<br />
super()<br />
end<br />
end<br />
<br />
class ServiceProxy<br />
def initialize(service_url, service_name=nil)<br />
@service_url = service_url<br />
@service_name = service_name<br />
end<br />
<br />
def method_missing(name, *args, &block)<br />
if @service_name != nil<br />
name = "%s.%s" % [@service_name, name]<br />
end<br />
return ServiceProxy.new(@service_url, name)<br />
end<br />
<br />
def respond_to?(sym)<br />
end<br />
<br />
def call(*args)<br />
postdata = {"method" => @service_name, "params" => args, "id" => "jsonrpc"}.to_json<br />
respdata = RestClient.post @service_url, postdata<br />
resp = JSON.parse respdata<br />
if resp["error"] != nil<br />
raise JSONRPCException.new, resp['error']<br />
end<br />
return resp['result']<br />
end<br />
end<br />
</source><br />
<br />
== PHP ==<br />
<br />
The [http://jsonrpcphp.org/ JSON-RPC PHP] library also makes it very easy to connect to Bitcoin. For example:<br />
<br />
<source lang="php"><br />
require_once 'jsonRPCClient.php';<br />
<br />
$bitcoin = new jsonRPCClient('http://user:password@127.0.0.1:8332/');<br />
<br />
echo "<pre>\n";<br />
print_r($bitcoin->getinfo()); echo "\n";<br />
echo "Received: ".$bitcoin->getreceivedbylabel("Your Address")."\n";<br />
echo "</pre>";<br />
</source><br />
<br />
== Java ==<br />
<br />
The easiest way to tell Java to use HTTP Basic authentication is to set a default Authenticator:<br />
<br />
<source lang="java"><br />
final String rpcuser ="...";<br />
final String rpcpassword ="...";<br />
<br />
Authenticator.setDefault(new Authenticator() {<br />
protected PasswordAuthentication getPasswordAuthentication() {<br />
return new PasswordAuthentication (rpcuser, rpcpassword.toCharArray());<br />
}<br />
});<br />
</source><br />
<br />
Once that is done, any JSON-RPC library for Java (or ordinary URL POSTs) may be used to communicate with the Bitcoin server.<br />
<br />
== Perl ==<br />
<br />
The JSON::RPC package from CPAN can be used to communicate with Bitcoin. You must set the client's credentials; for example:<br />
<br />
<source lang="perl"><br />
use JSON::RPC::Client;<br />
use Data::Dumper;<br />
<br />
my $client = new JSON::RPC::Client;<br />
<br />
$client->ua->credentials(<br />
'localhost:8332', 'jsonrpc', 'user' => 'password' # REPLACE WITH YOUR bitcoin.conf rpcuser/rpcpassword<br />
);<br />
<br />
my $uri = 'http://localhost:8332/';<br />
my $obj = {<br />
method => 'getinfo',<br />
params => [],<br />
};<br />
<br />
my $res = $client->call( $uri, $obj );<br />
<br />
if ($res){<br />
if ($res->is_error) { print "Error : ", $res->error_message; }<br />
else { print Dumper($res->result); }<br />
} else {<br />
print $client->status_line;<br />
}<br />
</source><br />
<br />
== .NET (C#) ==<br />
The communication with rpc service can be achieved using the standard httprequest/response objects.<br />
A library for serialising and deserialising Json will make your life a lot easier:<br />
<br />
* JayRock for .NET 4.0<br />
* Json.Net for .NET 2.0 and above <br />
<br />
The following example uses Json.Net:<br />
<br />
<source lang="csharp"><br />
HttpWebRequest webRequest = (HttpWebRequest)WebRequest.Create("http://localhost.:8332");<br />
webRequest.Credentials = new NetworkCredential("user", "pwd");<br />
/// important, otherwise the service can't desirialse your request properly<br />
webRequest.ContentType = "application/json-rpc";<br />
webRequest.Method = "POST";<br />
<br />
JObject joe = new JObject();<br />
joe.Add(new JProperty("jsonrpc", "1.0"));<br />
joe.Add(new JProperty("id", "1"));<br />
joe.Add(new JProperty("method", Method));<br />
// params is a collection values which the method requires..<br />
if (Params.Keys.Count == 0)<br />
{<br />
joe.Add(new JProperty("params", new JArray()));<br />
}<br />
else<br />
{<br />
JArray props = new JArray();<br />
// add the props in the reverse order!<br />
for (int i = Params.Keys.Count - 1; i >= 0; i--)<br />
{<br />
.... // add the params<br />
}<br />
joe.Add(new JProperty("params", props));<br />
}<br />
<br />
// serialize json for the request<br />
string s = JsonConvert.SerializeObject(joe);<br />
byte[] byteArray = Encoding.UTF8.GetBytes(s);<br />
webRequest.ContentLength = byteArray.Length;<br />
Stream dataStream = webRequest.GetRequestStream();<br />
dataStream.Write(byteArray, 0, byteArray.Length);<br />
dataStream.Close();<br />
<br />
<br />
WebResponse webResponse = webRequest.GetResponse();<br />
<br />
... // deserialze the response<br />
</source><br />
<br />
== Command line (cURL) ==<br />
<br />
You can also send commands and see results using [http://curl.haxx.se/ cURL] or some other command-line HTTP-fetching utility; for example:<br />
<br />
<source lang="bash"><br />
curl --user user --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' <br />
-H 'content-type: text/plain;' http://127.0.0.1:8332/<br />
</source><br />
<br />
You will be prompted for your rpcpassword, and then will see something like:<br />
<br />
<source lang="javascript"><br />
{"result":{"balance":0.000000000000000,"blocks":59952,"connections":48,"proxy":"","generate":false,<br />
"genproclimit":-1,"difficulty":16.61907875185736,"error":null,"id":"curltest"}<br />
</source><br />
<br />
== See Also==<br />
<br />
* [[Original_Bitcoin_client/API_Calls_list|API calls list]]<br />
* [[Running Bitcoin]]<br />
* [[Lazy API]]<br />
<br />
[[Category:Technical]]<br />
[[Category:Developer]]<br />
[[zh-cn:API_reference_(JSON-RPC)]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Invoice_address&diff=9282Invoice address2011-05-30T15:10:18Z<p>Firestorm: </p>
<hr />
<div>A '''Bitcoin Address''' is a 160-bit hash of the public portion of a public/private [[Wikipedia:Elliptic_Curve_DSA|ECDSA]] keypair. Using some mathemagic, you can "sign" data with your private key and anyone who knows your public key can verify that the signature is valid. See the [[Wikipedia:Public-key_cryptography|Wikipedia article]] for more information about how this works. See [[Protocol_specification#Addresses|protocol specification]] for details on how a bitcoin address is formed.<br />
<br />
A new keypair is generated for each receiving address. Bitcoin addresses (the public keys) and their associated private keys are stored in the [[wallet]] data file. This is the only file you need to [[backup|back up]]. A "send" transaction to a specific Bitcoin address requires that the corresponding private key exist in the recipient's wallet. This has the implication that if you create a receiving address and receive coins to that address, then restore the wallet from an earlier backup, before the address was generated, then the coins associated with that address are lost. Addresses are added to an address [[key pool]] prior to being used for receiving coins. If you lose your wallet entirely, all of your coins are lost and can never be recovered.<br />
<br />
"Generate" transactions happen in the same way as a send transaction: each batch of 50 generated coins is "sent" to a unique address that you generate just for that purpose. These addresses are also stored in your wallet, but they are not shown in the "your receiving addresses" section.<br />
<br />
Bitcoin allows you to create as many addresses as you want, and each one is completely separate. There is no "master address": the "Your Bitcoin address" area in the Bitcoin UI has no special importance. It's only there for your convenience, and it will change automatically from time to time to enhance your anonymity. All of your other addresses will continue to work forever. They're listed in the "your receiving addresses" section. Each address takes up only about 500 bytes, so having a large number of addresses in your wallet is generally not a problem.<br />
<br />
Bitcoin addresses contain a built-in check code, so it's generally not possible to send Bitcoins to a mistyped address. However, if the address is well-formed but no one owns it (or the owner lost their wallet.dat), any coins sent to that address will be lost forever.<br />
<br />
Addresses can contain all alphanumeric characters except 0, O, I, and l. Normal addresses currently always start with 1, though this might change in a future version. Testnet addresses usually start with ''m'' or ''n''. Mainline addresses can be 25-34 characters in length, and testnet addresses can be 26-34 characters in length. Most addresses are 33 or 34 characters long, though.<br />
<br />
It is also possible to send Bitcoins directly to an [[IP address]].<br />
<br />
Since Bitcoin addresses are basically random numbers, it is possible, although extremely unlikely, for two people to independently generate the same address. This is called a [[Wikipedia:Collision_(computer_science)|collision]]. If this happens, then both the original owner of the address and the colliding owner could spend money sent to that address. It would not be possible for the colliding person to spend the original owner's entire wallet (or vice versa). If you were to intentionally try to make a collision, it would currently take 2^126 times longer to generate a colliding Bitcoin address than to generate a block. As long as the signing and hashing algorithms remain cryptographically strong, it will likely always be more profitable to collect generations and [[transaction fee|transaction fees]] than to try to create collisions.<br />
<br />
[[Category:Technical]]<br />
[[Category:Vocabulary]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Help:Accounts_explained&diff=9281Help:Accounts explained2011-05-30T15:09:38Z<p>Firestorm: </p>
<hr />
<div>== Introduction ==<br />
<br />
You can have different [[address|addresses]] in order to receive payments. Think of addresses as multiple postboxes around the outside of your house. Bitcoin allows accounts too. Each account owns a bunch of addresses. Taking our earlier analogy, you can imagine separate accounts as different houses. You (Bitcoin user) receive all the mail (balance shown in Bitcoin). Mail goes to a postbox (address) at one of your houses (accounts).<br />
<br />
The balance you see displayed is a total from all your accounts.<br />
<br />
== Accounts ==<br />
<br />
Bitcoin version 0.3.18 and later implements several RPC methods to maintain separate account balances in a single Bitcoin wallet. The accounts feature makes it easy to create web services that maintain a separate bitcoin balance for each customer.<br />
<br />
== Account Names ==<br />
<br />
Accounts are named with arbitrary strings; you may use any [http://www.json.org/ JSON] string other than "*" (JSON strings are sent and returned as UTF-8 encoded Unicode).<br />
<br />
Bitcoin creates two accounts automatically: it implicitly creates a default account with the empty string as its name, and it explicitly creates an account named '''Your Address''' when a new wallet is created.<br />
<br />
== The Default Account ==<br />
<br />
The default account is named with the empty string ("" in JSON). Generated coins are always credited to the default account, and the ''sendtoaddress'' method always debits the default account.<br />
<br />
== Accounts and Receiving Addresses ==<br />
<br />
Each account is associated with zero or more receiving addresses, and every receiving address is associated with exactly one account. Coins sent to a receiving address in the wallet are credited to the associated account.<br />
<br />
Accounts are associated with receiving addresses by using the ''getaccountaddress'', ''getnewaddress'' or ''setaccount'' methods.<br />
<br />
''getaccountaddress'' will return the same address until coins are received on that address; once coins have been received, it will generate and return a new address.<br />
<br />
''getnewaddress'' always generates and returns a new address.<br />
<br />
''setaccount'' changes the account associated with an existing address. Coins previously received on that address (if any) will be debited from the previous account's balance and credited to the address' new account. Note that doing so may make the previous account's balance negative.<br />
<br />
Use the ''getaddressesbyaccount'' method to list all addresses associated with an account.<br />
<br />
== Sending ==<br />
<br />
The ''sendfrom'' method sends coins and debits the specified account. It does **not** change Bitcoin's algorithm for selecting which coins in the wallet are sent-- you should think of the coins in the wallet as being mixed together when they are received. There is no way to ask Bitcoin to "create a payment transaction using the coins received from these previously received transactions."<br />
<br />
The ''sendtoaddress'' method works like ''sendfrom'', but always debits the default account.<br />
<br />
The send will fail if the account has insufficient funds, with two exceptions:<br />
<br />
- Sends from the default account always succeed if there are sufficient funds in the<br />
server's wallet. For example, if your wallet account balances were 100 BTC in account<br />
'foo' and 0 BTC in the default account, then the balances after ''sendtoaddress<br />
15VjRaDX9zpbA8LVnbrCAFzrVzN7ixHNsC 10.00'' would be 100 in account 'foo' and -10.00 in<br />
the default account (and the overall server balance would go from 100 to 90 BTC).<br />
<br />
- The check for sufficient funds is done before paying transaction fees (if any); if a<br />
[[transaction fee]] is needed, and there are sufficient funds in the wallet, then the<br />
transaction fee will be paid and debited from the account. For example, if account<br />
'foo' contains 10 bitcoins, you ''sendfrom foo 15VjRaDX9zpbA8LVnbrCAFzrVzN7ixHNsC 10'',<br />
and the transaction costs 0.01, 'foo's balance will be -0.01 bitcoins.<br />
<br />
== Account -> Account Transfers ==<br />
<br />
Use the ''move'' method to transfer balances from one account to another. Moves from the default account to any other account always succeed; moves from any other account will fail if the account has insufficient funds. Moves are not broadcast to the network, and never incur transaction fees; they just adjust account balances in the wallet.<br />
<br />
== Account Balance and History==<br />
<br />
The ''getbalance'' method returns the bitcoin balance for either the entire wallet (if no argument is given) or for a particular account.<br />
<br />
The ''listtransactions <account> [N]'' method returns the last N (default 10) transactions that affected the account's balance. "listtransactions '*' [N]" will return the last N transactions for all accounts.<br />
<br />
== Typical Uses ==<br />
<br />
This section describes how typical web site code running on a web server uses the JSON-RPC API to keep track of customers' accounts.<br />
* Customer '''creates an account''' on the website: web server either assigns them a unique customer id number or uses their email address or other unique identifier, calls ''getaccountaddress "userid"'' and tells the customer to send to that address to fund their account.<br />
* Customer '''receives coins''' to fund their account: web server isn't involved.<br />
* Customer is shown their '''current balance''': ''getbalance "userid" 1'' to get their 'confirmed' balance, and subtracts it from ''getbalance "userid" 0'' to get their 'unconfirmed' balance.<br />
* Show the customer an **itemized list** of transactions: ''listtransactions "userid"''<br />
* Customer '''sends coins''' to another bitcoin address: ''sendfrom "userid" <address> <amount>''<br />
* Customer '''transfers coins''' to another customer: ''move "userid1" "userid2" <amount>''<br />
* You '''make a sale''', paid for with bitcoins in the customer's account: ''move "userid" "" <amount> 6 "purchased item"'', and if it succeeds, send them the product.<br />
* Customer is '''charged a fee''' for use of the service: ''move "userid" "FEES" <amount>'' (using special accounts like "FEES" can make your application's logic much simpler)<br />
* Customer '''purchases bitcoins''' from you: ''move "AVAILABLE" "userid" <amount>'' (assuming the bitcoins you are selling are kept track of in an "AVAILABLE" account)<br />
<br />
[[Category:Technical]]<br />
[[Category:Developer]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Mining_hardware_comparison&diff=9280Mining hardware comparison2011-05-30T15:08:39Z<p>Firestorm: </p>
<hr />
<div>Below are some statistics about the mining performance of various hardware used in a [[mining rig]].<br />
<br />
The table shows (mostly) stock clock numbers. 10-20% performance improvement can be achieved via overclocking.<br />
<br />
'''Note:''' Clock refers to the Shader clock only with nVidia cards (not Core or Memory). With AMD card the shader clock is not separate, but is part of the GPU clock.<br />
<br />
==Graphics cards==<br />
<br />
===AMD===<br />
To get the maximum performance use the 2.1 release of the ATI Stream SDK. 2.2 wastes CPU time, and 2.3/2.4 drop mining performance by 5-10%.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! Mhash/s !! Mhash/J !! W !! Clock !! SP !! SDK !! Slot !! Miner !! Notes<br />
|-<br />
| 3XXX || || || || || || || || OpenCL Not Supported<br />
|-<br />
| 42XX || || || || || || || PCI-E 2.0 x16 || || OpenCL Not Supported (intergrated/mobile GPU)<br />
|-<br />
| 4350 || 6.93 || 0.346 || 20 || 575 || 80 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors <br />
|-<br />
| 4550 || 7.23 || 0.289 || 25 || 600 || 80 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use 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 || 80 || || PCI-E 2.0 x16 || Diablo/Windows7 || -w 64, SDK 2.4, Cat 11.4. Model: Sony Vaio NW. O/C core 680->825. U/C memory 800->500.<br />
|- <br />
| 4650 || 31.33 || 0.653 || 48 || 650 || 320 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors <br />
|- <br />
| 4670 || 36.14 || 0.613 || 59 || 750 || 320 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors<br />
|-<br />
| 4670 || 40.11 || || 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 />
| 4730 || 72.29 || 0.657 || 110 || 750 || 640 || || PCI-E 2.0 x16 || ||<br />
|- <br />
| 4770 || 72.29 || 0.904 || 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 />
| 4850 || 75.30 || 0.685 || 110 || 625 || 800 || || PCI-E 2.0 x16 || ||<br />
|- <br />
| 4850 || 101 || || || 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 />
| 4860 || 67.47 || 0.519 || 130 || 700 || 640 || || PCI-E 2.0 x16 || ||<br />
|-<br />
| 4870 || 90.36 || 0.602 || 150 || 750 || 800 || 2.1 || PCI-E 2.0 x16 || clmine ||<br />
|-<br />
| 4870 || 78 || || || || || || PCI-E 2.0 x16 || m0mchil's OpenCL/Vista 64bit || [http://www.bitcoin.org/smf/index.php?topic=1628.msg25069#msg25069 source]<br />
|- <br />
| 4890 || 102.41 || 0.539 || 190 || 850 || 800 || || PCI-E 2.0 x16 || ||<br />
|- <br />
| 4890 || 108.3 || || 190 || 975 || 800 || || PCI-E 2.0 x16 || ||<br />
|- <br />
| 4850X2 || 150.60 || 0.602 || 250 || 625 || 1600 || || PCI-E 2.0 x16 || ||<br />
|- <br />
| 4870X2 || 180.72 || 0.632 || 286 || 750 || 1600 || || PCI-E 2.0 x16 || ||<br />
|- <br />
| 4870X2 || 180.6 || || 286 || 800 || 1600 || || PCI-E 2.0 x16 || ||<br />
|- <br />
| 5450 || 11.99 || 0.631 || 19 || 650 || 80 || || PCI-E 2.1 x16 || ||<br />
|- <br />
| 5550 || 40.59 || 1.041 || 39 || 550 || 320 || || PCI-E 2.1 x16 || ||<br />
|- <br />
|style="background:#FFFFEF;"| 5570 || 59.96 || 1.538 || 39 || 650 || 400 || || PCI-E 2.1 x16 || ||<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 || 62 || 1.59 || 39 || 650 || 800 || 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 || 73 || || 39 || 700 || 800 || 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 />
| 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 />
| 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 />
| 5670 || 85 || || || 900 || 400 || || PCI-E 2.1 x16 || poclbm || -v -f 0 -w 128<br />
|- <br />
| 5750 || 116.24 || 1.352 || 86 || 700 || 720 || || PCI-E 2.1 x16 || ||<br />
|-<br />
| 5750 || 137 || || || 710 || || || PCI-E 1.1 x16 || poclbm || -v -f 0 -w 128 using stock memory and GPU clocks<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 || || || PCI-E 1.1 x16 || poclbm || -v -f 0 -w 128 patched BIOS to underclock memory to 300MHz<br />
|-<br />
| 5750 || 173 || || || 875 || || || PCI-E 1.1 x16 || phoenix || 875/300 w/MSI Afterburner, BFI_INT VECTORS AGGRESSION=12 FASTLOOP=FALSE -k phatk<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 || 180 || 1.406 || 128[*] || 950 || 800 || 2.4RC1 || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 30 (*Overclocked wattage calculated [http://bakkap.free.fr/Misc/wCalc.html here] )<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 || 223 || || 100+ || 1050 || 300 || 2.4 || PCI-E 2.1 x16 || guiminer || -v -w256 [http://www.smpake.com/?p=59 source]<br />
|-<br />
|style="background:#FFFFFF;"| 5830 || 206.64 || 1.181 || 175 || 800 || 1120 || || PCI-E 2.1 x16 || ||<br />
|- <br />
|style="background:#FFFFFF;"| 5830 || 241 || 1.377 || 175 || 1006 || || 2.3 || PCI-E 2.1 x16 || poclbm 2011-03-11 / Win7 64 ||<br />
|-<br />
|style="background:#FFFDDD;"| 5830 || 245 || 1.4 || 175 || 880 || 900 || 2.4 || PCI-E 2.1 x16 || poclbm (guiminer) || -v -w 256<br />
|-<br />
|style="background:#FFFDDD;"| 5830 || 248 || 1.42 || 175 || 880 || 500 || 2.4 || PCI-E 2.1 x16 || phoenix 1.46 || -k poclbm VECTORS BFI_INT AGGRESSION=11<br />
|-<br />
|style="background:#FFFFFF;"| 5830 || 285 || || || 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:#FFFFFF;"| 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:#FFFFFF;"| 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:#EFEFFF;"| 5850 || 240.77 || 1.595 || 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 || 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 || 314 || 1.8362 || 171 || 820 (OC) || 1440 || 2.4 || PCI-E 1.0 x8 || poclbm || -v -w128 <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 || 382 || 1.8454 || 207 || 995 (OC) || 1440 || || PCI-E 2.0 x8 || phoenix || OC 1.177v on core<br />
|-<br />
| 5870M || 116.5 || ? || ? || ? || ? || 2.1 || PCI-E 2.1 x16 || gui-miner (win-7) ||<br />
|- <br />
|style="background:#EFFFEF;"| 5870 || 313.65 || 1.668 || 188 || 850 || 1600 || 2.1 || PCI-E 2.1 x16 || clmine ||<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 || 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 || 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 || 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 || 377 || 2.008 || 188 || 850 || 1600 || || PCI-E 2.0 x16 || hashkill-0.2.5 alpha || -D -G2 <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 || 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 || 398 || 1.980 || 201 || 900 || 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 || 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 || 440 || 2.0000 || 220 || 995 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix || <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:#FFEFEF;"| 5970 || 530 || 1.803 || 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 || 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:#EFFFEF;"| 5870x2 || 620 || || || 850 || 3200 || 2.1 || PCI-E 2.1 x16 || guiminer || -v -w 128<br />
|- <br />
|style="background:#EFFFEF;"| 5870x2 || 826 || || 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 || 826 || || 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 || 878 || || 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 />
| 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 />
| 6470M || 24.1 || ? || ? || ? || ? || 2.1 || Integrated/APU || guiminer || ||<br />
|- <br />
| 6470M || 31.0 || ? || ? || ? || ? || 2.1 || Integrated/APU || phoenix 1.48 || ||<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 || 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 />
| 6750 || 167.59 || || || 870 || || || PCI-E 2.1 x16 || guiminer || -v -f30 -w128<br />
|- <br />
| 6850 || 171.59 || 1.351 || 127 || 775 || 960 || 2.1 || PCI-E 2.1 x16 || clmine ||<br />
|- <br />
| 6850 || 196 || || || 850 || 960 || || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 0<br />
|- <br />
| 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 || 220 || 1.236 || 178[*] || 1000 || 960 || 2.4RC1 || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 30 (*Overclocked wattage calculated [http://bakkap.free.fr/Misc/wCalc.html here] )<br />
|-<br />
|style="background:#FFFF00;"| 6870 || 232.47 || 1.540 || 151 || 900 || 1120 || || PCI-E 2.1 x16 || poclbm -v -w 128 ||<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 || 260.1 || 1.611 || 175 || 1001 || 1150 || 2.2 || PCI-E 2.1 x16 || poclbm-gui windows7x86 cat 11.3 || -v -w 128 -f 1 <br />
|-<br />
|style="background:#FFFF00;"| 6870 || 276 || 1.828 (?) || 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 || 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 || 306 || 1.748 (?) || 175 (?) || 1000 || 1120 || 2.4 || PCI-E 2.1 x16 || hashkill-0.2.5 alpha cat 11.4 sdk 2.4 || -G2 -D overclocked to 1000, debian linux 64bit <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 || 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 />
| 6950 || 295 || || 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 || 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 || || 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 || 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 || 360 || || 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 || 417 || || +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 />
|style="background:#F0FF0F;"| 6970 || 323 || 1.468 || 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 || 372 || || 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 || 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 || 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 />
| 6990 || 670 || 1.94 || 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 || 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 || 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 || 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 />
|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 />
|FirePro M5800 || 61.4 || || || 650 || || || || poclbm-mod.03.24.2011 || Ubuntu || <br />
|- <br />
|}<br />
<br />
===Nvidia===<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! Mhash/s !! Mhash/J !! W !! Clock !! SP !! Comment<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 || || 128 || 1238 || || DiabloMiner -w 128 -f 1 [https://en.bitcoin.it/wiki/User:Knightmb source]<br />
|-<br />
| 8600M GT || 4.93 || || || || 32 ||<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 || || 105 || 1855 || || Overclocked 715 GPU / 1030 Memory / 1855 Shader; GuiMiner v2011-05-21<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 />
| 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 />
| 9500GT || 6.75 || 0.135 || 50 || 1400 || 32 ||<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 />
| 9800GT || 30.36 || 0.289 || 105 || 1800 || 112 ||<br />
|-<br />
| 9800GTX || 32.54 || 0.232 || 140 || 1688 || 128 ||<br />
|-<br />
| 9800GTX+ || 35.39 || 0.251 || 141 || 1836 || 128 ||<br />
|-<br />
| 9800GTX+ || 37.23 || 0.266 || 140 || 1890 || 128 || win7x64 275.27 phoenix(1.48) -k poclbm AGGRESSION=3 WORKSIZE=64<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 || || 128 || 1360 || || DiabloMiner -w 128 -f 1000 [https://en.bitcoin.it/wiki/User:Knightmb source]<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 />
| 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 ||<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 || 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 />
| 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 />
| GTX285 || 53.35 || 0.262 || 204 || 1476 || 240 ||<br />
|-<br />
| GTX295 || 89.78 || 0.311 || 289 || 1242 || 480 ||<br />
|-<br />
| GT 320M (MacBook Air) || 6.12 || || || 1212 || 48 ||<br />
|-<br />
| GT 330M || 7.97 || || || || || Model: MacBookPro6,2 VRAM: 512MB Software: [http://forum.bitcoin.org/index.php?topic=8994.0 DiabloMiner GUI] v2011-05-22 / Mac OS X 10.6.7<br />
|-<br />
| GT 330M (Sony Vaio Z) || 7.8 || 0.71 ( 0.3 total) || 11 (26w total) || 1045 || 48 ||<br />
|-<br />
| GT430 || 20.24 || 0.413 || 49 || 1400 || 96 ||<br />
|-<br />
| GTS450 || 45.28 || 0.427 || 106 || 1566 || 192 ||<br />
|-<br />
| GTX460SE || 56.39 || 0.376 || 150 || 1300 || 288 ||<br />
|-<br />
| GTX460 || 68.31 || 0.427 || 160 || 1350 || 336 ||<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 />
| 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 || 111.9 || || 215 || 1650 || 448 ||<br />
|-<br />
| GTX470 || 115 || || || 1616 || || phoenix 1.46 poclbm VECTORS BFI_INT FASTLOOP AGGRESSION=6<br />
|-<br />
| GTX480 || 101.28 || 0.405 || 250 || 1401 || 480 ||<br />
|-<br />
| GTX560 Ti || 67.7 || 0.39 || 170 || 1700 || 384 || standard EVGA 560, no overclock<br />
|-<br />
| GTX560 Ti || 74.8 || 0.41 || 180 || 1700 || 384 || gigabyte 900Mhz clock; -w 512 -v<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 />
| GTX580 || 140.05 || --- || 244 || 1544 || 512 ||<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 1600M || 6 || 0.12 || 50 || 625 || 32 ||rpcminer-cuda, Win<br />
|-<br />
| Quadro NVS 135M || 1.05 || 0.1 || 10 || 800 || 1 || <br />
|-<br />
| Quadro NVS 3100M || 3.6 || 0.257 || 14 || 600 || 16 || rpcminer-cuda, Win, CUDA 3.1.1<br />
|-<br />
| Tesla M2050 || 79.8 || || || || || DiabloMiner<br />
|-<br />
| Tesla M2050 || [http://glennfrancismurray.com/cost-defective-mining-with-gpu-clusters-amazo 100] || 0 || 0 || - || 512 || Amazon AWS [http://glennfrancismurray.com/cost-defective-mining-with-gpu-clusters-amazo CUDA RPC Miner & CUDA 2.0]<br />
|-<br />
|}<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 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 X4 630 || 4 || 10.7 || 0.11 || 95W || 2.8 GHz || 10.7<br />
|colspan=4|<br />
| bitcoin-miner 0.4 || <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 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 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 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 />
| 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 />
<br />
===ARM===<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! p/t !! Mhash/s !! Mhash/J !! ACP [W] !! Clock !! Version !! Comment<br />
|-<br />
| ARM1136EJ-S || 1 || 0.11 || ? || ? || 0.528 GHz || cpuminer git || T-Mobile Pulse, inside Debian chroot, 'c' algo<br />
|-<br />
| Cortex-A8 || 1 || 0.125 || 0.36 || 0.35 W || 0.6 GHz || cpuminer git (2011-03-26) || Nokia N900: 'cryptopp'<br />
|-<br />
| Cortex-A8 || 1 || 0.2 || 0.57 || 0.35 W || 0.6 GHz || cpuminer git (2011-03-26) || Nokia N900: 'c' algo<br />
|-<br />
| 2x Cortex-A9 || 2 || 0.57 || 1.14 || 0.5 W || 1.0 GHz || cpuminer git (2011-03-24) || Toshiba AC100, ubuntu, 'c' algo<br />
|}<br />
<br />
===Intel===<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! p/t !! Mhash/s !! Mhash/J !! ACP [W] !! Clock !! Version !! Comment<br />
|-<br />
| Pentium III mobile ? || 1 || 0.3 || 0.014 || 21W || 1.07 GHz || 0.3.1x/Win2K || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source] [http://ark.intel.com/Product.aspx?id=27380 source]<br />
|-<br />
| Pentium M 1.6ghz || 1 || .4 || || || 1.6 GHZ || minerd (jgarzik's 1.0) || cryppto, Windows 7<br />
|-<br />
| Pentium M 1.73ghz || 1 || .5 || || || 1.73 GHZ || minerd (jgarzik's 1.0) || cryppto, Windows 7<br />
|-<br />
| Old Xeon 512k (Dual) || 2x1/2 || 2.0 || ? || ? || 3.06GHz || cpuminer (v0.8.1-1-g69529c3) || HT disabled, algo=4way (twice as fast as the 2nd best algo)<br />
|-<br />
| Pentium 4 2.0A || 1 || 0.85 || || || 2.0 GHz || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft-0.4]/WinXP || -g no -t 2<br />
|-<br />
| Pentium Dual-Core E2180 || 2/2 || 1.75 || || || 2.0 GHz || rpcminer-cpu || Win7-64<br />
|-<br />
| Pentium Dual-Core E2180 || 2/2 || 4.5 || || || 2.0 GHz || ufasoft v0.11 || Win7-64<br />
|-<br />
| Pentium Dual-Core E5400 || 2/2 || 2.27 || 0.03 || 65W || 2.7 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]<br />
|-<br />
| Celeron E330 || 2/2 || 2.2 || 0.03 || 65W || 2.5 GHz || 0.3.19/Ubuntu10.04 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37620#msg37620 source]<br />
|-<br />
| Core 2 Quad Q6600 || 4/4 || 11.0 || || 105W || 2.40 GHz || bitcoin-miner 0.10 || -a 60 -g no -t 4<br />
|-<br />
| Core 2 Quad Q9400 || 4/4 || 11 || 0.046 || 95W || 2.66 GHz || bitcoin-miner 0.10 || -a 60 -g no -t 4<br />
|-<br />
| Core 2 Quad Q9650 || 4/4 || 18.67 || || 95W || 4.00 GHz || bitcoin-miner 0.10 || -a 60 -g no -t 4<br />
|-<br />
| Core i3 530 || 2/4 || 8.31 || 0.10 || 80W || 3.66 GHz || Ufasoft 0.7 || -v -a5 -g no -t 4<br />
|-<br />
| Core i3 M350 || 2/4 || 1.48 || 0.04 || 35W || 2.27 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]<br />
|- <br />
| Core i5 M450 || 2/4 || 1.8 || 0.05 || 35W || 1.2 GHz || 0.3.17/Win7-54 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26292#msg26292 source]<br />
|- <br />
| Core i5-650 || 2/4 || 5.1 || 0.04 ? || || 3.2 GHz || cpuminer-0.7 || -4way<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 || 95W || 3.1 GHz || cpuminer git (2011-01-22) || cryptopp_asm32<br />
|-<br />
| Core i5-2400 || 4/4 || 14 || 0.15 || 95W || 3.1 GHz || cpuminer git (2011-03-26) || sse2_64<br />
|-<br />
| Core i7 620M || 2/4 || 1.888 || || || 2.66 GHz || [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 920 || 4/8 || 19.2 || 0.10 || 195 || 4.0 GHz (x21) || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] || -a 5<br />
|-<br />
| Core i7 950 || 4/8 || 5.88 || 0.039 || 150W || 3.83 GHz (x23) || bitcoin-0.3.20.2 Win7-64 ||<br />
|-<br />
| Core i7 950 || 4/8 || 18.9 || 0.126 || 150W || 3.83 GHz (x23) || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] v0.4 ||<br />
|-<br />
| Core i7 980x || 6/12 || 19.2 || 0.15 || 130 || 4.4 GHz (x33) || cpuminer/Win7-64 || <br />
|- <br />
| Core i7 980x || 6/12 || 8.7 || || || 3.9 GHz (x27) || 0.3.17/Win7-64 || <br />
|- <br />
| Core i7 2635QM || 4/8 || 2.93 || || || 2.00 GHz || [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 GHz || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] v0.4 || <br />
|-<br />
| Core 2 Duo U7600 || 1 || 1.1 || || || 1.2 GHZ || minerd (jgarzik's 1.0) || cryppto, Windows 7<br />
|-<br />
| Core 2 Duo E5200 || 2/2 || 6.2 || 0.086 || 72W || 2.76 Ghz || Ufasoft/Win7-64 || TDP is 65W + 7W overclock<br />
|-<br />
| Core 2 Duo E6550 || 1/2 || 2.45 || ? || ? || 2.33 GHz || cpuminer 0.7.1 (Linux) || --algo=sse2_64<br />
|-<br />
| Core 2 Duo E6850 || 2/2 || 6.75 || 0.10 || 65W || 3.0 Ghz || ufasoft-0.3 ||<br />
|- <br />
| Core 2 Duo E7300 || 2/2 || 7.76 || 0.11 || 70W || 3.33 GHz (o/c?) || ufasoft-0.3 || miner optimized for Intel Core<br />
|-<br />
| Core 2 Duo E7300 || 2/2 || 2.52 || 0.04 || 65W || 2.66 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]<br />
|-<br />
| Core 2 Duo E8400 || 2/2 || 6.9 || ? || ? || 3.0 GHz || ufasoft v0.10|| windows 7/64bit (-t 2)<br />
|-<br />
| Core 2 Duo T6400 || 2/2 || 4.2 || 0.12 || 35 W || 2.00 GHz || cpuminer git (Linux) || --algo=sse2_64<br />
|-<br />
| Core 2 Extreme X9000 || 2/2 || 2.37 || || || 2.8 GHz || rpcminer-cpu || Win7-64<br />
|-<br />
| Core 2 Extreme X9000 || 2/2 || 6.2 || || || 2.8 GHz || ufasoft v0.11 || Win7-64<br />
|-<br />
| Core 2 Extreme X9000 || 2/2 || 7.2 || || || 3.2 GHz || ufasoft v0.11 || Win7-64 Overclocked from 2.8 GHz to 3.2 GHz<br />
|-<br />
| Xeon 3060 || 1/2 || 2.03 || 0.03 || 65W || 2.4GHz || cpuminer 0.8.1 (Linux) || --algo=cryptopp_asm32<br />
|-<br />
| Xeon Prestonia 2.4 (dual) || 2x1/2 || 2.16 || 0.017 || 130W || 2.4 GHz || ufasoft v0.4 || <br />
|-<br />
| Xeon X5355 (dual) || 2x4/4 || 10.13 || 0.16 || 120W || 2.66GHz || bitcoind || Roughly the same speed as the "c" algo in cpuminer<br />
|-<br />
| Xeon X5355 (dual) || 2x4/4 || 22.76 || 0.09 || 120W || 2.66GHz || cpuminer (v0.8.1-1-g69529c3) || -O2 -march=core2, algo=sse2_64<br />
|-<br />
| Xeon E5440 || 4/8 || 7.3 || ? || 80W || 2.66 GHz|| Kiv's poclbm-gui || FIXME: Either wrong model # or wrong threads/speed info<br />
|-<br />
| Xeon E5520 || 4/8 || 6.5 || 0.08 || 80W || 2.27 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]<br />
|-<br />
| Xeon E5530 || 4/8 || 7.14 || 0.09 || 80W || 2.4 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]<br />
|-<br />
| Xeon E5630 (dual) || 2x4/8 || 8 || 0.1 || 80W || 2.53 GHz || 0.3.17/Win7-64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg29471#msg29471 source]<br />
|-<br />
| Xeon E6520 (dual) || 2x4/8 || 24.7 || ? || ? || 2.53 GHz || ufasoft v0.10 || windows 2008 R2 64bit (-t 16)<br />
|-<br />
| Xeon E7520 (dual) || 2x4/16 || 18 || ? || 95W || 1.87 GHz || ufasoft v0.10 || windows 2008 R2 64bit (-t 16)<br />
|-<br />
| Atom N270 || 2 || 1.19 || 0.24 || 5W || 1.6 GHz || ufasoft v0.10 || <br />
|}<br />
<br />
===Other===<br />
{| class="wikitable sortable"<br />
|-<br />
! Model !! p/t !! Mhash/s !! Mhash/J !! ACP [W] !! Clock !! Version !! Comment<br />
|-<br />
| Cell || 6 || 21 || 0.35 || 60W || 3.2 GHz || cellminer || Sony Playstation 3 (FAT): Needs custom firmware (no links to it, potential issues with Sony assholes.) [https://github.com/verement/cellminer source] [http://www.bitcoin.org/smf/index.php?topic=4704.20 source] Total power usage of PS3 fat is 120W but only the Cell cpu is active.<br />
|-<br />
| Cell || 6 || 21 || 0.7 || 35W || 3.2 GHz || cellminer || Sony Playstation 3 (SLIM): Total power usage of PS3 slim is 70W but only the Cell cpu is active.<br />
|-<br />
| MIPS || 1 || 0.026 || ? || ? || 200 MHz || cpuminer || ASUS WL-500G Deluxe router running [http://openwrt.org/ OpenWrt]<br />
|}<br />
<br />
==See Also==<br />
<br />
* [[Mining rig]]<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 />
<br />
[[Category:Mining]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Editing&diff=9279Bitcoin Wiki:Editing2011-05-30T14:56:45Z<p>Firestorm: </p>
<hr />
<div>{{help navbar}}<br />
<br />
== Basic formatting ==<br />
<!--COMMENT MARKUP. Displays:Edit mode only.--><br />
{|align="center" class="wikitable" style="width:100%"<br />
|-<!--COLUMN HEADINGS--><br />
| class="header" width="25%" style="text-align:center;"|'''Description'''<br />
| class="header" style="text-align:center;"|'''You type''' <br />
| class="header" width="25%" style="text-align:center;"|'''You get'''<br />
|-<!--1ST ROW 1ST COLUMN--><br />
|Italic text<br />
|<!--2ND COLUMN--><br />
<tt><nowiki>''italic''</nowiki></tt><br />
|<!--3RD COLUMN--><br />
''italic''<br />
|-<!--HORIZONTAL LINE--><br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<!--2ND ROW 1ST COLUMN--><br />
|Bold text<br />
|<br />
<tt><nowiki>'''bold'''</nowiki></tt><br />
|<br />
'''bold'''<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Bold and italic<br />
|<br />
<tt><nowiki>'''''bold & italic'''''</nowiki></tt><br />
|<br />
'''''bold & italic'''''<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Internal link<br /><br />
<div style="padding: 0em .5em; font-size:0.9em;">''(within the wiki)''</div><br />
|<br />
<tt><nowiki>[[Getting started]]</nowiki></tt><br /><br />
<tt><nowiki>[[Getting started|How to start]]</nowiki></tt><br />
|<br />
[[Getting started]]<br /><br />
[[Getting started|How to start]]<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Categorization<br />
|<br />
<nowiki>[[Category:Help]]</nowiki> <br /><br />
<nowiki> [[Category:Help/fr]]</nowiki> (on French pages)<br />
|<br />
''Places the page in [[:Category:Help]]''<br /><br />
''Places the page in [[:Category:Help/fr]]''<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|External link<br /><br />
<div style="padding: 0em .5em; font-size:0.9em;">''(to other websites)''</div><br />
|<br />
<tt><nowiki>[http://www.example.org Text to display]</nowiki></tt><br /><br />
<tt><nowiki>[http://www.example.org]</nowiki></tt><br /><br />
<tt><nowiki>http://www.example.org</nowiki></tt><br />
|<br />
[http://www.example.org Text to display]<br /><br />
[http://www.example.org]<br /><br />
http://www.example.org<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Citation Needed<br />
|<br />
<nowiki>{{Citation needed}}</nowiki><br />
|<br />
{{Cite}}<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Redirect to another page<br />
|<br />
<tt><nowiki>#REDIRECT [[Target page]]</nowiki></tt><br />
|<br />
[[Image:Redirect arrow.png]][[Target page]]<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Redirect to a non-english page<br />
|<br />
<tt><nowiki>#REDIRECT [[Target page/x]] {{R lang|x}}</nowiki></tt> where <code>x</code> is the language's code (de, fr, es, ru...)<br />
|<br />
[[Image:Redirect arrow.png]][[Target page/x]]<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Section headings<br /><br />
<div style="padding: 0em .5em; font-size:0.9em;">''A Table of Contents will automatically be generated when four headings are added to an article.''</div><br />
|<br />
<tt><nowiki>== Level 1 ==</nowiki></tt><br /><br />
<tt><nowiki>=== Level 2 ===</nowiki></tt><br /><br />
<tt><nowiki>==== Level 3 ====</nowiki></tt><br /><br />
<tt><nowiki>===== Level 4 =====</nowiki></tt><br /><br />
<tt><nowiki>====== Level 5 ======</nowiki></tt><br />
|<br />
== Level 1 ==<br />
=== Level 2 ===<br />
==== Level 3 ====<br />
===== Level 4 =====<br />
====== Level 5 ======<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Bulleted list<br />
|<br />
<tt>* One</tt><br /><br />
<tt>* Two</tt><br /><br />
<tt>** Two point one</tt><br /><br />
<tt>* Three</tt><br />
|<br />
* One<br />
* Two<br />
** Two point one<br />
* Three<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Numbered list<br /><br />
<div style="padding: 0em .5em; font-size:0.9em;">''Empty lines between list items restarts numbering at 1.''</div><br />
|<br />
<tt># One</tt><br /><br />
<tt># Two</tt><br /><br />
<tt>## Two point one</tt><br /><br />
<tt># Three</tt><br /><br />
|<br />
# One<br />
# Two<br />
## Two point one<br />
# Three<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Indenting text<br />
|<br />
<tt><nowiki>no indent (normal)</nowiki></tt><br/><br />
<tt><nowiki>:first indent</nowiki></tt><br/><br />
<tt><nowiki>::second indent</nowiki></tt><br/><br />
<tt><nowiki>:::third indent</nowiki></tt><br />
|<br />
no indent (normal)<br/><br />
:first indent<br />
::second indent<br />
:::third indent<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Image<br />
|<br />
<tt><nowiki>[[Image:Logo.png|100px]]</nowiki></tt><br />
|<br />
[[Image:Logo.png|100px]]<br />
|-<br />
|colspan="3" style="border-top:1px solid #FFE4C4;"|<br />
|-<br />
|Thumbnail image<br />
|<br />
<tt><nowiki>[[</nowiki>Image:Logo.png|thumb|Caption text<nowiki>]]</nowiki></tt><br />
|<br />
[[File:Logo.png|thumb|100px|Caption text]]<br />
|-<br />
<br />
|-<!--TALKPAGES--><br />
| colspan="3" style="text-align:center;background:#FFE4C4;" | For Talk Pages<br />
|-<br />
|Sign your posts on talk pages<br />
|<br />
<tt><nowiki>~~~~</nowiki></tt><br />
|<br />
[[Special:Mypage|Username]] ([[Special:Mytalk|talk]]) {{CURRENTTIME}}, {{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}} (UTC)<br />
|}<br />
<br />
== Creating a page ==<br />
There are three ways to create a new page on Bitcoin Wiki:<br />
<br />
Firstly you can simply type the name of the new page you wish to create into the Search box on the left navigation menu. If the page does not currently exist, the page displayed will advise you that '''There is no page titled "''[page you searched for]''"'''. You can <span style="color:red">create this page</span>. Click the <span style="color:red">'create this page'</span> link to create the new page.<br />
<br />
Secondly, you can navigate to the [[Wikipedia:Uniform Resource Locator|URL]] of the new page directly. For example, typing out <tt><nowiki>https://en.bitcoin.it/wiki/New_page</nowiki></tt> into your browser's URL address bar and hitting the enter button will take you to a '''New page''' document. On that page you can click the '''Create''' tab to bring up the editing box.<br />
<br />
Alternatively any page that contains a red link such as [[Help:Non-existent page]] indicates that the page does not exist. Clicking on the link will take you to a page where the first version can be written and saved. <br />
<br />
== Creating a subpage ==<br />
Subpages can be thought of as ''children'' of articles in the document tree. As such they should be used when you wish to create an article that is intrinsically linked to the parent article. Articles that have been translated into different languages use subpages to store the separate content, for example the [[Main Page]] has a [[Main Page/pl]] which has the translated content in Polish.<br />
<br />
To create a subpage, the same procedure should be used as above using the forward slash ('''/''') to indicate the separation between the original page, and the subpage. Example:- '''<code><nowiki>Original page name/Subpage name</nowiki></code>'''.<br />
<br />
== Saving pages ==<br />
Once edited, before actually saving your changes, make good use of the ''''Show preview'''' button to preview the changes. Avoid saving too often or saving just to see what it looks like. Each page save will generate an entry in [[Special:Recentchanges|recent changes]]. Repeated trivial and unnecessary saves tend to clutter up that list and inconvenience users who make use of that list to watch for vandals or misinformed edits. Once you are happy with your changes, enter a brief summary of what changes you have made in the ''''Summary:'''' text box and click the ''''Save page'''' button.<br />
<br />
The ''''This is a minor edit'''' tick box should be used if small changes (for example, grammar corrections) have been made. The ''''Watch this page'''' tick box is useful to keep an eye on changes to that article, these will show up in your ''''My Watchlist'''' (found at the top right of the wiki when you are logged in) if any changes have been made.<br />
<br />
== See also ==<br />
* [[Help:Contents]] &ndash; main help page<br />
<br />
=== External ===<br />
* From [http://www.mediawiki.org/wiki/Help:Contents MediaWiki Help]:<br />
** [http://www.mediawiki.org/wiki/Help:Formatting Formatting]<br />
** [http://www.mediawiki.org/wiki/Help:Links Links]<br />
** [http://www.mediawiki.org/wiki/Help:Images Images]<br />
** [http://www.mediawiki.org/wiki/Help:Tables Tables]<br />
* [[wikipedia:Wikipedia:Cheatsheet|Wikipedia Cheatsheet]]<br />
<br />
__NOTOC__ __NOEDITSECTION__</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Template:Help_navbar&diff=9278Template:Help navbar2011-05-30T14:55:36Z<p>Firestorm: Created page with "{| class="wikitable" cellpadding=0 style="margin: 10px auto; align: center; width: 80%;" |- ! valign="center" | 50px | align="center" | [[Help:Contents|..."</p>
<hr />
<div>{| class="wikitable" cellpadding=0 style="margin: 10px auto; align: center; width: 80%;"<br />
|-<br />
! valign="center" | [[Image:Help center.png|50px]]<br />
| align="center" | [[Help:Contents|'''Help center''']]<br />
<span class="plainlinks">[[Help:Editing|Editing]] • [[Help:Group_rights|Administrators]] • [http://www.mediawiki.org/wiki/Help:Images Images] • [http://www.mediawiki.org/wiki/Help:Tables Tables] </span> <br />
|}</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Help&diff=9277Bitcoin Wiki:Help2011-05-30T14:55:09Z<p>Firestorm: </p>
<hr />
<div>{{stub}}<br />
<br />
{{Help navbar}}<br />
<br />
== Editing articles ==<br />
*[[Wikipedia:Wikipedia:Cheatsheet|Cheatsheet]]<br />
*[[Wikipedia:Help:Links#Wikilinks|How to make links]]<br />
*[[Wikipedia:Help:Table#Pipe_syntax_tutorial|Using tables]]<br />
**[[Wikipedia:Wikipedia:Collapsible_tables|Using Collapsible tables]]<br />
* [[Help:Using ToDo Lists|Using ToDo lists]]<br />
<br />
== Resources and lists ==<br />
*[http://www.mediawiki.org/wiki/Help:Tracking_changes Keeping track of changes]<br />
*[http://www.mediawiki.org/wiki/Help:Contents User help on MediaWiki]<br />
*[[Wikipedia:Wikipedia:Manual_of_Style|Manual of style]]<br />
**[[Wikipedia:Wikipedia:Naming conventions|Naming conventions]]<br />
**[[Wikipedia:Wikipedia:Guide to layout|Guide to layout]]<br />
*[[IRC channels]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Help&diff=9276Bitcoin Wiki:Help2011-05-30T14:54:49Z<p>Firestorm: /* Editing articles */</p>
<hr />
<div>{{stub}}<br />
<br />
{| class="wikitable" cellpadding=0 style="margin: 10px auto; align: center; width: 80%;"<br />
|-<br />
! valign="center" | [[Image:Help center.png|50px]]<br />
| align="center" | [[Help:Contents|'''Help center''']]<br />
<span class="plainlinks">[[Help:Editing|Editing]] • [[Help:Group_rights|Administrators]] • [http://www.mediawiki.org/wiki/Help:Images Images] • [http://www.mediawiki.org/wiki/Help:Tables Tables] </span> <br />
|}<br />
<br />
<br />
== Editing articles ==<br />
*[[Wikipedia:Wikipedia:Cheatsheet|Cheatsheet]]<br />
*[[Wikipedia:Help:Links#Wikilinks|How to make links]]<br />
*[[Wikipedia:Help:Table#Pipe_syntax_tutorial|Using tables]]<br />
**[[Wikipedia:Wikipedia:Collapsible_tables|Using Collapsible tables]]<br />
* [[Help:Using ToDo Lists|Using ToDo lists]]<br />
<br />
== Resources and lists ==<br />
*[http://www.mediawiki.org/wiki/Help:Tracking_changes Keeping track of changes]<br />
*[http://www.mediawiki.org/wiki/Help:Contents User help on MediaWiki]<br />
*[[Wikipedia:Wikipedia:Manual_of_Style|Manual of style]]<br />
**[[Wikipedia:Wikipedia:Naming conventions|Naming conventions]]<br />
**[[Wikipedia:Wikipedia:Guide to layout|Guide to layout]]<br />
*[[IRC channels]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Bitcoin_Wiki:Using_to-do_lists&diff=9275Bitcoin Wiki:Using to-do lists2011-05-30T14:54:40Z<p>Firestorm: Created page with "{{Help navbar}} When using Todo lists, please add them on the '''discussion''' page rather than the main article. ==Creating a List== :1. Once on the '''discussion''' page, '..."</p>
<hr />
<div>{{Help navbar}}<br />
<br />
When using Todo lists, please add them on the '''discussion''' page rather than the main article. <br />
<br />
==Creating a List==<br />
<br />
:1. Once on the '''discussion''' page, '''Edit''' the page and at the top of the text add a <br />
<br />
::<pre>{{Todo}}</pre><br />
<br />
:to the top of the article text. This will create a reference to the list (as you don't actually populate the list on the article page.)<br />
<br />
:2. After you have typed this, click the '''Save page''' button. The ''Todo'' list will then become visible on the '''discussion''' page.<br />
<br />
:3. Click the '''Edit''' button on the ToDo list. This will create a page for the Todo contents with some default text (basic instructions) on it.<br />
<br />
:4. Once you save this article (the contents), it will show up in the Todo list (at the top of the discussion page) and in the [[:Category:ToDo]] list pages.<br />
<br />
<br />
Don't worry about it showing in the [[:Category:ToDo]] list starting with '''Help talk:''' because it will be sorted into the alphabetical order of the page name (for example, '''A''' for '''Adding Custom Maps''').<br />
<br />
==Using the ''Watch'' icon==<br />
<br />
You can use the '''Watch''' link at the top of any ''Todo'' list to add the ''Todo'' list to your [[Special:Watchlist]] and track any changes.<br />
<br />
== Completing Todo items ==<br />
<br />
When completing items, add your name against the item and strike it out. Striking an item out can be achieved by adding <code><nowiki><s></nowiki></code> at the beginning and a <code><nowiki></s></nowiki></code> at the end of the item (see example below). If all the items have been completed, you can then remove the <code><nowiki>{{Todo}}</nowiki></code> from the discussion page.<br />
<br />
=== Example ===<br />
<br />
<pre>*Add a picture to the article.</pre><br />
<br />
To complete the item, change it to:<br />
<br />
<pre>*<s>Add a picture to the article.</s> - Done --~~~~</pre><br />
<br />
Which will show as:<br />
<br />
*<s>Add a picture to the article.</s> - Done --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 14:54, 30 May 2011 (GMT)<br />
<br />
<br />
__NOEDITSECTION__<br />
[[Category:Help]]</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Talk:Transaction&diff=9274Talk:Transaction2011-05-30T14:49:04Z<p>Firestorm: </p>
<hr />
<div>Can someone explain "number of Satoshi"? --[[User:0xlemming|0xlemming]] 09:43, 28 May 2011 (GMT)<br />
<br />
:Considering that the "Founder" of bitcoin is Satoshi Nakamoto, I can only presume that a Satoshi is something named after him --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 16:16, 28 May 2011 (GMT)<br />
<br />
::It's explained in the article: "(1 BTC = 100,000,000 Satoshi)". It's the smallest unit Bitcoin can handle. It was originally referred to as a "nanocoin" when I wrote it, but someone changed it to this, which IMO is less clear... [[User:Theymos|theymos]] 02:44, 30 May 2011 (GMT)<br />
<br />
::: It looks like the bitcoin community won't adopt the Satoshi, but instead the [http://forum.bitcoin.org/index.php?topic=10049.0 Microbitcoin(UBC)] --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 14:49, 30 May 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=User_talk:Nanotube&diff=9273User talk:Nanotube2011-05-30T14:46:40Z<p>Firestorm: </p>
<hr />
<div>Hi Nanotube,<br />
can you please delete [[Mining pool reward FAQ]]? I created it to provide information about some commonly confused issues, but it's being abused and thus can't serve this purpose. [[User:Holy-Fire|Holy-Fire]] 18:43, 26 May 2011 (GMT)<br />
: I removed the troublesome content and left it to-the-point. This should serve to remove any abuse. --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 18:51, 26 May 2011 (GMT)<br />
::Sorry, it really doesn't, see my comment on your talk page. [[User:Holy-Fire|Holy-Fire]] 19:08, 26 May 2011 (GMT)<br />
:::posted my comments on firestorm's user talk page and the faq-page talk page. https://en.bitcoin.it/wiki/Talk:Mining_pool_reward_FAQ<br />
<br />
==Help Page==<br />
<br />
Hello, Nanotube. I've created a fairly simple [[Help:Contents|Help page]] that I'm going to be expanding over time. Would it be a good idea to link to this in the sidebar? --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 14:46, 30 May 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Talk:Transaction&diff=9159Talk:Transaction2011-05-28T16:17:08Z<p>Firestorm: </p>
<hr />
<div>Can someone explain "number of Satoshi"? --[[User:0xlemming|0xlemming]] 09:43, 28 May 2011 (GMT)<br />
<br />
:Considering that the "Founder" of bitcoin is Satoshi Nakamoto, I can only presume that a Satoshi is something named after him --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 16:16, 28 May 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Talk:Transaction&diff=9158Talk:Transaction2011-05-28T16:16:59Z<p>Firestorm: </p>
<hr />
<div>Can someone explain "number of Satoshi"? --[[User:0xlemming|0xlemming]] 09:43, 28 May 2011 (GMT)<br />
Considering that the "Founder" of bitcoin is Satoshi Nakamoto, I can only presume that a Satoshi is something named after him --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 16:16, 28 May 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=User_talk:Leetnet&diff=9123User talk:Leetnet2011-05-27T23:03:23Z<p>Firestorm: </p>
<hr />
<div>[[File:Information.png|25px]] Please make use of the '''Show preview''' button. It gives you a preview of the edit you make, allowing you to perfect it before you save the page. --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 21:27, 27 May 2011 (GMT)<br />
::You can edit the entire page at one time using the edit button in the top right. Use this to move content around so you don't need to save over and over again --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 23:03, 27 May 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=User_talk:Leetnet&diff=9114User talk:Leetnet2011-05-27T21:27:25Z<p>Firestorm: Created page with "{{Subst:sp}} --~~~~"</p>
<hr />
<div>[[File:Information.png|25px]] Please make use of the '''Show preview''' button. It gives you a preview of the edit you make, allowing you to perfect it before you save the page. --[[User:Firestorm|<span style="text-shadow:orange 0px 0px 3px;"><font color="#FF6600"><tt><big><u>'''Firestorm'''</u></big></tt></font>]]</span> 21:27, 27 May 2011 (GMT)</div>Firestormhttps://en.bitcoin.it/w/index.php?title=User:Firestorm/vector.js&diff=9080User:Firestorm/vector.js2011-05-27T13:39:55Z<p>Firestorm: Created page with "// install Wikipedia:User:Cacycle/wikEd in-browser text editor document.write('<script type="text/javascript" src="' + 'http://en.wikipedia.org/w/index.php?title=User:Cacycle..."</p>
<hr />
<div>// install [[Wikipedia:User:Cacycle/wikEd]] in-browser text editor<br />
document.write('<script type="text/javascript" src="'<br />
+ 'http://en.wikipedia.org/w/index.php?title=User:Cacycle/wikEd.js'<br />
+ '&action=raw&ctype=text/javascript"></' + 'script>');</div>Firestormhttps://en.bitcoin.it/w/index.php?title=Mining_pool_reward_FAQ&diff=9079Mining pool reward FAQ2011-05-27T13:35:23Z<p>Firestorm: Removed Share-based disadvantage until clarified in talk page.</p>
<hr />
<div>== How does mining in a pool improve my payouts? ==<br />
Pooled mining will not have a significant effect on the [http://en.wikipedia.org/wiki/Expected_value expectation] of your payouts (it can decrease a bit due to fees), but it can dramatically decrease their [http://en.wikipedia.org/wiki/Variance variance].<br />
<br />
== What reward systems are there? ==<br />
All reward systems use the concept of "share", a hash which is easier than the real difficulty and proves you have worked on finding a valid block. Your reward when the pool finds a valid block depends on the shares you submitted.<br />
<br />
The main reward systems used are:<br />
:'''Pay per share''': Every share submitted receives a fixed BTC reward known in advance. This has virtually 0 variance and is thus good for beginners. However, the operator is subject to enormous variance, and will thus take a large fee to cover his risk. This means the expectation for participants is low, so it's not an attractive long-term solution. It is also vulnerable to sabotage where the miner simply withholds all block-finding shares, causing a loss to the pool operator.<br />
<br />
:'''Proportional''' ("Share-based"): Every time a block is found, its reward is split between participants according to the number of shares they submitted. This method is vulnerable to a type of exploit known as "pool-hopping". In the theoretical limit, this can reduce the payout for non-hopping participants by up to 30% (in practice the decrease would be much less, but can still be significant).<br />
<br />
:'''Score-based''': Each share submitted receives a score based on its age, and the block reward is split between participants according to their score. Certain mining pools, like Slush's pool and BTC mine, are designed to be resistant while the one used by Continuum pool ("geometric method") is designed to be completely immune. The amount of bitcoins a miner may recieve from their effors will vary over time, due to the variance of this system.<br />
<br />
== What will be my expected payout per share? ==<br />
Every share will give you, on average, the block reward (minus any pool fees) divided by the difficulty. For example, with a block reward of 50 BTC, 2% fee and difficulty of 240000, each share submitted will give on average 0.000204 BTC (204 μBTC).<br />
<br />
== How many hashes does it take to find a share? ==<br />
On average, one share will be found for every 2^32, or 4.295 billion, hashes calculated. So at 1 MHash/s, you will find a share on average every 72 minutes.<br />
<br />
== How much will the pool decrease my variance? ==<br />
If you constitute a significant part of the pool (say, above 1%), your variance will be roughly proportional to your portion of the pool. If, for example, you are 20% of the pool, your variance will be 20% of solo mining variance (a decrease factor of 5 times).<br />
<br />
If not, your variance will not depend on the size of yourself or the pool, but rather on the scoring method used. For proportional, the decrease factor is roughly difficulty/ln(difficulty). For the geometric method the decrease factor is roughly (1 + 2*difficulty*c), where c is the score fee parameter used.<br />
<br />
Increasing the size of the pool will always decrease the variance, but at some point you will have diminishing marginal utility.</div>Firestorm