# The Reputation Stack

<figure><img src="https://1110142702-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEtcdATXDvC0WSePF1xED%2Fuploads%2FVTY5LCLoQIomBTzEgG3p%2Fnetwork-architecture.jpg?alt=media&#x26;token=0217baa9-a5d9-4267-ad29-bf9450028cf3" alt=""><figcaption></figcaption></figure>

## The Ranking and Reputation stack

* **Data Layer:** This enables any developer or application to bring their own data sets for compute. This involves two main operations - *Data sourcing and Pre-processing.* Any data source such as onchain attestations, blockchain transactions, open data repositories can participate for sourcing the data.  In addition, data analysis and data science communities can bring their own heuristics to form input data sets or reputation graphs as an input for the ranking and reputation compute. The output of the data layer is an `[i,j,v]` matrix, which is a context-specific reputation graph that will be computed by OpenRank protocol. Read an extensive overview of this in the next page.&#x20;
* **OpenRank Protocol** - A decentralized compute network to ensure verifiable, scalable and permissionless ranking and reputation compute. This layer computes the desirable algorithm (EigenTrust/Hubs and Authorities/Graph neural networks) on the reputation graphs committed by the data layer or clients and provides the converged ranking results (output). The compute nodes provide guarantees of computation and leverage a data availability layer for storing the input and output for any compute operation.
* **Apps and Clients using Rankings** - Developers, Protocols and Data scientists can utilize the verifiable rankings data to build desirable reputation, filtration, airdrop, search and discovery, feeds or gating strategies and applications. Rankings of one context can serve as input data for compute for another use case.


---

# 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://docs.openrank.com/the-reputation-stack.md?ask=<question>
```

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.