> 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/the-miner-use-case.md).

# The Miner Use Case

Miners are an important part of the ecosystem so its valuable to examine their requirements. Miners may of course have many motivations for participating in the building of the Bitcoin blockchain including a long term view for example, but the analysis below considers the requirements for a Miner that is interested in the short-term, in the immediate profitability. A Miners top priority is to ensure that any blocks they mine are accepted by the majority of other Miners and that the other Miners mine on top of these blocks.

1. Block Distribution The most critical feature is block distribution. If the Miner has discovered a new block they must distribute that block as quickly as possible so that other Miners build on top of that block, thereby cementing the block as part of the longest chain of proof of work and ensuring that the block reward and fees will be valid. If the Miner has accepted a new block from another Miner, then they will start mining on top of that block. In this case, the Miner is also highly motivated in distributing this new block to other Miners so that the block is not orphaned and the mining effort is not wasted. Speed is essential for block distribution. Every fraction of time that it takes to distribute the block to other Miners and for those Miners to start mining on top of the block, creates the possibility for a competing block to be found. The longer it takes to distribute the block, the higher the risk of a competing block. Notice that the Miner is primarily interested in distributing the block to other Miners. Distributing the block to other network participants is substantially less of a priority. It may be mildly interesting because those other network participants may themselves distribute the block to a Miner, but a direct connection to the other Miner would be more preferable. Other network participants will of course, also need the block, to fulfill their various business needs, but this is not time critical from the point of view of the Miner. Note that in general only distributing the latest block is a priority for Miners. Providing older blocks is not of interest, see below for more details. However, in some circumstances it may be necessary to prioritise distribution of more than just the tip, such as when multiple blocks are mined in succession very quickly.
2. Block Reception Miners are highly motivated to quickly receive new blocks from other Miners. If a new valid block is discovered on the network the Miner is highly motivated to switch to mining on top of that block as quickly as possible, on the assumption that this block will be accepted by the rest of the network. If the Miner finds a block when they have already discovered a new block on the network but have not finished retrieving or validating that block, then the Miner has found a competing block. Given that the Miner has already detected the other block, it is highly likely that the Miner is already at a disadvantage with their competing block and will probably lose the competition.
3. Transaction Acquisition The Miner is motivated to acquire as many transactions as possible to include those transactions in the block they are mining.
4. Transaction Distribution The primary motivation for Miners to distribute transactions is to enhance the speed at which their block would be propagated, if the block was found. A strong secondary motivation is to support the network as a whole by preventing zero-conf double spends, or alerting other nodes and users to the existence of double spend attempts.
5. Other Features Providing block download of older blocks is not of interest to Miners. At this stage of development, Miners may support this feature to generally support the network, but it is not a required feature. As the eco-system evolves, we can expect specialised providers of block archiving.


---

# 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/the-miner-use-case.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.