> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/wiki/mining-and-consensus/mining/getblocktemplate-interface.md).

# GetBlockTemplate interface

getblocktemplate is a now deprecated protocol used to transmit block template information from nodes to remote hash machines. It was developed in 2012 and superseded the original "getwork" protocol.

1. Reasons for development The original getwork protocol only provided ASIC Miners with a single block header, which was sufficient for a total of 4 GH of mining. With the "rollntime" extension, this was extended to 4 GH **per second**, but even that was far from sufficient for mining equipment at the time which was already capable of 1000 GH/s on the high end.
2. Attribution This content is based on content sourced from <https://en.bitcoin.it/wiki/Getblocktemplate> under [Creative Commons Attribution 3.0](https://creativecommons.org/licenses/by/3.0/). Although it may have been extensively revised and updated, we acknowledge the original authors.


---

# 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://hub.bsvblockchain.org/wiki/mining-and-consensus/mining/getblocktemplate-interface.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.