# Data Availability

## Zulu Data Availability Strategy

As an L2 network, Zulu must provide users with the means to securely retrieve their assets from L1 by validating their assets through historical transactions, even in instances where L2 services are inaccessible.&#x20;

This precautionary measure is in place to prevent the locking of users' assets in L2 during periods when L2 services are unavailable. The optimal solution involves storing all transactions on the Layer1 verification network.&#x20;

However, drawing from the developmental history of Ethereum, we learn that while placing transaction data on the Layer1 network achieves the highest level of security, an excess of transaction data can overwhelm the network.&#x20;

Consequently, Ethereum itself addressed this Data Availability (DA) issue through the upgrade of [EIP4844](https://eips.ethereum.org/EIPS/eip-4844).

In the context of the Bitcoin network, storing all transactions directly on Bitcoin is not considered an ideal approach. Zulu's strategy involves placing actual transaction data on networks specifically dedicated to DA, such as [Avail](<https://x.com/AvailProject/status/1786317935633703304 >).&#x20;

Zulu follows a modular design, a technical direction widely embraced in the blockchain industry that plays a crucial role in enhancing the operational efficiency of the system.

<figure><img src="/files/Vllfr5c3WOUyFNrsAPPJ" alt=""><figcaption><p>Zulu Modular Design</p></figcaption></figure>


---

# 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.zulunetwork.io/tech-approach/data-availability.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.
