> 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/modular-nodes-introduction.md).
# Modular L1 Nodes
Users are able to support the Particle Chain's decentralization and security by running a node. "Modular Node" is a collective term for various types of nodes in the Particle Chain each serving different roles. \
\
Particle Network's modular design requires five types of Modular Nodes:
1. **Validator:** Responsible for validating transactions, settling the execution status of external UserOps, voting to generate blocks, and participating in the verification of fraud proofs submitted by Watchtower nodes.
2. **Relayer:** Acts as a message hub, monitoring and synchronizing the execution status of external chain UserOps and synchronizing Universal Account changes.
3. **Bundler:** Responsible for the specific execution of UserOps on external chains.
4. **DA Aggregator:** Integrates and encapsulates various DA networks such as Celestia, Avail, Near DA, and EigenDA, providing upper layers with a unified data publishing and verification interface.
5. **Watchtower:** Monitors the work of other nodes, ensuring node liveness, and provides execution proofs and possible fraud proofs for each block generated per epoch.
### Operating Conditions
The Particle Chain is an open and permissionless Layer-1, where any node operator can freely participate as long as they meet certain conditions.
The network will gradually open up, with more information to be provided later.
---
# 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/modular-nodes-introduction.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.
