> 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.md).
# Technology
## The Particle Chain
The Particle Chain powers chain abstraction by acting as the coordination engine behind Universal Accounts.
Upon the execution of a cross-chain transaction through a Universal Account, the Particle Chain processes, relays, and manages each operation associated with the completion of this transaction. Through an intricate network of Modular Nodes, including Relayers, Bundlers, and Watchtowers, alongside its native Universal Inter-Blockchain Communication Protocol, the Particle Chain handles end-to-end cross-chain operation management and execution, enabling the Universal Liquidity leveraged by Universal Accounts.
Furthermore, the Particle Chain acts as a central storage layer and source of truth for state parity across all Universal Account instances. Upon the deployment of a new Universal Account, its state is immediately synchronized with associated instances present on other chains through the usage of the L1's Master Keystore Hub.
The Particle Chain is intrinsically modular, retaining its sovereignty while outsourcing key functions like validation and data availability to specialized ecosystem actors. We also offer a high-performance EVM execution environment, ensuring seamless compatibility and maintaining developer friendliness.
---
# 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://doc.particle.network/particle-network/modular-l1-design.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.