> 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/core-modules.md).

# Core Modules

<figure><img src="/files/Ctg4pIn9tTMcN3kXjuKX" alt=""><figcaption></figcaption></figure>

Within this modular L1, the following modules support the design and ongoing coordination of Universal Accounts:

* **Master Keystore Hub**: Particle Network acts as the central hub coordinating smart contract deployments and updates across all networks, automatically synchronizing settings between each Universal Account instance and ensuring complete state parity across networks. Account settings are stored on Particle Network to be used as a central source of truth across every instance. The Particle Chain then facilitates cross-chain messages to either deploy new instances abiding by these settings or update existing instances as these settings change.
* **Decentralized Messaging Network (DMN)**: On Particle Network, Relayer Nodes use a Messaging Protocol to monitor whether UserOperations on external chains have been executed successfully, and then settle the execution status on the Particle Chain. This network of decentralized Relayer Nodes, tasked with monitoring external chain events and the settlement of state events, is called the Decentralized Messaging Network.
* **Decentralized Bundler**: While current implementations of ERC-4337 account abstraction Bundlers are centralized and as such censorable, Particle Network has designed and implemented a fully decentralized Bundler for high-volume UserOperation processing. Within this implementation, the Bundler takes transactions from a public UserOp mempool, upon which they're processed by Operators participating in Particle Network's custom Bundler Nodes before relaying them.

<figure><img src="/files/uFFp3cDGupBmrTfj6l1Y" alt=""><figcaption></figcaption></figure>


---

# 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/underlying-architecture/core-modules.md?ask=<question>&goal=<endgoal>
```

`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.