# DA Layer integration case studies

This section provides an overview of how the GlitchD 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 Layer 1 (L1) network while storing the full transaction data on the GlitchD 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 L1:** Preserving the cryptographic commitment to the transaction data, which allows for verification and auditing on the L1 network.
* **Managing Data Storage on the DA Layer:** Offloading the actual transaction data to the GlitchD DA Layer, thereby optimizing storage efficiency and scalability.

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

<figure><img src="https://3437597252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ7KRTq1pTZaELn1mvmb2%2Fuploads%2FAIaP3BU84eM2xidmio93%2FFrame%2051%20(3).png?alt=media&#x26;token=b9c0205c-898d-4a85-b017-d71de3b2b849" alt=""><figcaption><p>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.