# Data Request Life Cycle

In the SEDA protocol, data requests follow a structured life cycle to ensure the data's accuracy and reliability. This process has two main phases: **Execution** and **Tally**.

* **Execution Phase:** During this phase, data is collected by the SEDA overlay network. Overlay Nodes fetch data from multiple predefined sources, specified in the DR, and can perform computations such as aggregation and transformation. To enhance reliability and prevent data manipulation, the network uses a replication factor, which defines how many Overlay Nodes are involved in each request.
* **Tally Phase:** After data collection, the network enters the tally phase. Here, SEDA Chain Validators aggregate and validate the execution reports from Overlay Nodes. They compare these reports based on the Tally instructions specified in the DR, and if a majority align, consensus is reached on the final data output.

**Actors Involved:**

* **Data Requestors:** Initiate data requests to obtain off-chain information.
* **Overlay Nodes:** Fetch and process the data, generating execution reports.
* **Chain Node Validators:** Aggregate and validate execution reports to ensure consensus.
* **Data Providers:** Supply the data requested by the Overlay Nodes.

This life cycle ensures that data requests are processed with integrity and trust. By involving multiple actors and reaching a consensus, the SEDA protocol provides reliable access to off-chain data for any blockchain network.


---

# 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.seda.xyz/home/tech/seda-architecture/seda-network-architecture/data-request-life-cycle.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.