# Decentralized Indexer Competition is healthy The RuneMine Indexer network offers the premiere alternative "always available" view of all historical Runes data. Our decentralized indexer is the heart beat of our protocol (and the Runes ecosystem) ensuring Runes data is fully available without relying on centralized servers and entities A decentralized indexer is a crucial backbone in the Rune ecosystem for organizing and making transaction data easily accessible, enhancing searchability and user experience. It bolsters transparency and trust by distributing data control across the network, preventing manipulation. By facilitating seamless integration with wallets, exchanges, and DeFi applications, it also promotes broader adoption and utility. Additionally, it enables advanced analytics for insights into market trends and network health, while decentralization ensures resilience against single points of failure. Essentially, it's a foundational component that supports the ecosystem's usability, innovation, and decentralized integrity. {% hint style="success" %} Our indexer removes the Ordinals baggage, exposing only the data required to provide in-depth data analytics on Runes. {% endhint %} Drawing parallels to the Chainlink consensus mechanism, RuneMine Decentralized Indexer Network (dIN) consists of a set of approved nodes reaching consensus (agreement) and posting data to one or more BTC L2 data availability layer(s) Further decentralization is achieved via staking and open node membership utilizing our RuneMine token as the basis > Node operator docs coming soon. --- # Agent Instructions: 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: ``` GET https://runemine.gitbook.io/runemine/runemine-protocol/decentralized-indexer.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.