> For the complete documentation index, see [llms.txt](https://docs.thehemera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thehemera.com/welcome/account-centric-indexing-protocol/the-hemera-network/indexers.md).

# Indexers

Indexers are the foundational node operators providing account-centric indexing capabilities to the network.  Indexers earn $DAY token rewards in the following ways:

1. **Data accessibility:** indexers keep the indexed data available to requests at all time, and as such earn rewards for maintaining accessibility given SLA requirements. To join the network as indexers, $DAY tokens are staked to secure the network, and subject to slashing if serving malicious or incorrect data to applications, or if SLA conditions aren't met. 
2. **Query rewards:** by serving queries requests from validators, indexers earn token rewards for the work. 
3. **Indexing bonus:** network consumers create demands for sought-after data sets, indexers earn one-time bonus for providing indexing services to meet such demands.  

Indexers play a crucial role in providing data accessibility within the account-centric indexing network. Their evolution occurs in three phases, with later stages offering more fine-grained indexing capabilities to address needs of network consumers. 

In the first phase of the Hemera network, indexers will assist in establishing data coverage for prominent chains that are in demand by consumers. They will be allocated indexing tasks based on geographically locations and network latency to ensure that Hemera can provide global network coverage and data accessibility. 

**In future phases of indexer releases, indexer operators can configure the node to:** 

1\. optimize indexing earnings by assigning tasks based on network demands; 

2\. configure wallets-of-interests and chains to cover, catering to Dapp developers who prioritize their own data needs over earnings.


---

# 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://docs.thehemera.com/welcome/account-centric-indexing-protocol/the-hemera-network/indexers.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.