> For the complete documentation index, see [llms.txt](https://support.spiderpool.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.spiderpool.com/about-mining/the-evolution-of-bitcoin-mining-machines.md).

# The Evolution of Bitcoin Mining Machines

In 2010, most mining was done using personal computers. As the number of participants rapidly increased, mining shifted from CPUs to more powerful GPUs. In just seven months, GPU mining dominated the market. By June 2011, specialized mining equipment known as FPGA (Field Programmable Gate Array) appeared, marking the first professionally designed mining chips. FPGAs boosted hash rates to the GH/s level. In January 2013, the first commercial Bitcoin ASIC miner, the Avalon miner, was delivered, ushering in the ASIC hash rate era. ASIC miners continually evolved in low-power, high-performance pathways, marking the beginning of the high-hash rate era post-2013, reaching TH/s levels.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.spiderpool.com/about-mining/the-evolution-of-bitcoin-mining-machines.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.