> For the complete documentation index, see [llms.txt](https://doc.particle.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.particle.network/particle-network/modular-l1-design/underlying-architecture/aggregated-da.md).
# Aggregated DA
Within modular blockchain architectures, the most commonly outsourced component is Data Availability (DA). Particle Network is no exception, although it takes a unique approach to the implementation of external DA layers.
Due to the intensive task of coordinating cross-chain transactions across the entire blockchain ecosystem and simultaneously maintaining state across every Universal Account, Particle aims to maximize security and stability to build a truly robust blockchain. In the context of DA, this is achieved through the aggregation of multiple providers. These providers are:
* Celestia
* Avail
* NEAR DA
With each DA solution bringing unique benefits and performance priorities, leveraging only one would fail to meet the requirement of maximal security and stability. Therefore, Particle Network leverages random deterministic redundancy for each block, posting data between different DA layers accordingly. This model significantly enhances availability and stability through increased redundancy, as well as decentralization.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.particle.network/particle-network/modular-l1-design/underlying-architecture/aggregated-da.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
