> 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.md).
# Underlying Architecture
The Particle Chain is an Avalanche L1. Its architecture aims to achieve fast finality, high transaction throughput, and short block times. It relies on three core modules **(the Master Keystore Hub, Decentralized Bundler, and Decentralized Messaging Network**) to achieve chain abstraction. These, in turn, are supported by **Aggregated Data Availability** and **Dual Staking** modules to ensure network security.
The chain's high-level architecture is diagrammed below:
Some core components that are key to this architecture are:
## VMs compatibility
By integrating the EVM, SVM, and MoveVM, we simplify full-chain interoperability with chains across all of the aforementioned VMs. The unified execution environment further reduces the ecological adaptation threshold, allowing flexible modular combinations with key areas such as cross-chain messaging and DeFi.
## Universal Signatures
Serving MPC nodes on non-Smart Contract Platform chains, Universal Signatures provides support for underlying virtual accounts, enabling interoperability with accounts on heterogeneous chains, such as Bitcoin.
## Universal IBC
Building upon existing cross-chain messaging components, we abstract an optimistic cross-chain messaging module powered by our Decentralized Messaging Network that can simultaneously connect Cosmos ecosystems, EVM chains, Solana, Bitcoin, and other chains. This component supports rapid settlement and is crucial for a transparent user experience.
---
# 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.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.
