> For the complete documentation index, see [llms.txt](https://docs.glitchd.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glitchd.network/glitchd-products/data-availability/da-layer-integration-case-studies/integration-guide-for-op-stack-rollup-with-glitchd-da-layer.md).
# Integration Guide for OP Stack Rollup with GlitchD DA Layer
### Prerequisites and Initial Configuration
To initiate an OP Stack rollup, follow the steps provided in the [official documentation](https://docs.optimism.io/builders/chain-operators/tutorials/create-l2-rollup). OP Stack documentation covers all procedures necessary for deplying the rollup, however, please note that the following adjustments are necessary for switching the network to Holesky testnett:
* **Change the Network Chain ID:** Modify the chain ID from Sepolia to Holesky.
* **Modify the Batcher’s Destination L1 Address:** Update the batcher’s destination L1 address to separate transactions from the default destination address on the Holesky network.
The above two updates can be made after creating the `getting-started.json` file.
### Service Configuration for DA Layer Integration
Once all OP services are started, proceed with the following steps:
**1. Start the Light Client:** Initialize the light client service, which will handle storing L2 transaction batch data to the DA Layer.
**2. Stop the Batcher Service:** Temporarily halt the batcher service to apply the necessary configuration changes.
**3. Update the Batcher Configuration:** Modify the `--l1-eth-rpc` parameter in the batcher’s configuration to point to the light client’s RPC URL.
**4. Resume the Batcher Service:** Resume the batcher service to continue processing transactions.
[As illustrated in the Light Client diagram](https://docs.glitchd.network/glitchd-products/data-availability/da-layer-integration-case-studies), the light client performs the following functions:
* Stores L2 transaction batch data to the DA Layer.
* Saves versioned hashes on L1.
* Returns the versioned hashes to the batcher.
### Testing the Integration
A test OP Stack L2 network is available for experimentation:
* **Chain ID:** 42444
* **L2 RPC Node:**
* **Batcher transactions on the Holesky network can be found at the following link:**
By comparing the initial transactions with subsequent ones, particularly focusing on the input size, it becomes evident that the input size is significantly smaller in later transactions. This reduction occurs because the transactions contain only the versioned hashes of the data stored on the DA layer.
By adhering to these steps and configurations, the integration of the DA Layer solution with an OP Stack rollup can be successfully accomplished. For any questions or issues, please consult the documentation or contact our team.
---
# 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.glitchd.network/glitchd-products/data-availability/da-layer-integration-case-studies/integration-guide-for-op-stack-rollup-with-glitchd-da-layer.md?ask=&goal=
```
`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.