> For the complete documentation index, see [llms.txt](https://docs.viction.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viction.xyz/viction-data-availability/da-integration-use-cases.md).

# DA Integration Use cases

This section provides an overview of how the Viction Data Availability (DA) Layer integrates with Layer 2 (L2) rollups. The integration involves implementing a Light Client as an intermediary component. This Light Client encapsulates the necessary logic to enable rollups to maintain IDs (commitments to the transaction blob data) on the Viction network while storing the full transaction data on the DA Layer. The diagram below outlines each step of this workflow, offering a high-level understanding of the integration process.

The Light Client plays a crucial role in this architecture by ensuring the integrity and availability of transaction data. It achieves this by:

* **Storing IDs on Viction(L1)**: Preserving the cryptographic commitment to the transaction data, which allows for verification and auditing on the Viction network.
* **Managing Data Storage on the DA Layer**: Offloading the actual transaction data to the Viction DA Layer, thereby optimizing storage efficiency and scalability.

By providing this intermediary layer, the integration facilitates a seamless connection between L2 rollups and the Viction DA Layer, enhancing scalability without compromising data integrity or availability.

<figure><img src="/files/bzrpBOQCMI4k61H91WZk" alt=""><figcaption><p>Viction - Data Availability (DA) Layer Architecture</p></figcaption></figure>

**Note**: The current version of the Light Client is undergoing active testing and will be updated soon with new improvements.

<br>


---

# 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.viction.xyz/viction-data-availability/da-integration-use-cases.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.