> For the complete documentation index, see [llms.txt](https://faq.rollercoin.com/rollercoin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.rollercoin.com/rollercoin/f.a.q./homepage/11.-what-is-league-power.md).

# 11. What is League Power?

League Power, also known as the hash rate or network hash rate, refers to the total computational power being used by all miners within a blockchain network. In simple terms, it represents the total amount of power utilized to mine new blocks and validate transactions on the blockchain.

<figure><img src="https://2737827904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE61cnyjygmf0YfudWjeE%2Fuploads%2FrJ35KHHu3FiwuuwIHnzM%2Fimage.png?alt=media&amp;token=b031124e-d07f-48ba-b15a-404f56229885" alt=""><figcaption></figcaption></figure>

Additionally, League Power determines the difficulty of mining new blocks. As League Power increases, the difficulty also rises, making it harder for miners to successfully mine new blocks and earn rewards. This mechanism helps ensure that the rate of new block creation remains stable and predictable while preventing the network from being overwhelmed with too many new blocks too quickly.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://faq.rollercoin.com/rollercoin/f.a.q./homepage/11.-what-is-league-power.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.