# Benefits of AvailDA

| **Cost Efficient** | Securely transition data availability off-chain, significantly cutting costs, and boosting L2 scalability and efficiency.                                                                                                |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Improved UX**    | Shifting data availability off-chain alleviates the burden on the Ethereum mainnet, leading to expedited transaction confirmation and reduced gas fees for users.                                                        |
| **Scalability**    | Designed to scale as user activity increases, allowing higher throughput without sacrificing performance or reliability.                                                                                                 |
| **Reliable**       | Cutting-edge solution for encoding, committing to, and verifying the availability of data, ensuring that it remains accessible and reliable even in the face of node failures, network disruptions, or malicious actors. |
| **Versatility**    | Turn-key data availability base layer equipped with SDKs, an attestation bridge, and data availability guarantees from peer-to-peer light clients designed for ZK and Optimistic rollups, all built by a proven team.    |


---

# 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.lumia.org/lumia/data-availability/what-is-avail-da/benefits-of-availda.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.
