> 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/why-create-a-new-protocol-here.md).

# Why create a new protocol here?

**TL;DR:** A protocol brings the following fundamental benefits:

1. Bootstrap network effects to maximize innovation
2. Properly aligned interests
3. Significantly reduce development & service costs for all developers.

A protocol brings the most value when more developers build on top of it, creating a network effect which benefits all network participants.

From a technical perspective, when considering on-chain data retrieval and the use cases built on top of it, many technical components can be standardized due to the uniform formats of underlying on-chain data. Therefore, it makes the most sense to create a protocol network that addresses these demands which also evolves over time, benefiting the entire ecosystem. Traditionally, building decentralized indexing protocol often involves performance compromises. However, Hemera Protocol's  Account-Centric Indexing architecture makes it feasible to develop such a protocol without sacrificing performance. 

From a business perspective, opting to make Hemera an open protocol presents the most logical choice for several reasons:

1. Alignment of ecosystem interests: Hemera Protocol enables the support of valuable proprietary intellectual properties, mitigating the risks associated with Web2 models where enterprises monopolize these assets and profit solely from their corporate networks. This approach ensures that Hemera Protocol can maximize its value from inception。
2. Significant cost reduction for all protocol users:
   * **Reduce development costs**: standardize the account-level data retrieval and provide it as a protocol, removing the needs for Dapp developers to build everything from scratch in house.
   * **Reduce the service costs:** the protocol distributes the cost-intensive indexing workload across the Hemera Network, which encompasses participants such as miners, developers, and individual users, ensuring computational coverage across all geographical locations.


---

# 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/why-create-a-new-protocol-here.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.