> For the complete documentation index, see [llms.txt](https://ola-foundation.gitbook.io/ola-documentations/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ola-foundation.gitbook.io/ola-documentations/ola-network-core-components-onis-and-massive/massive/2.-modular-design.md).

# 2. Modular Design

Blockchain networks can be broadly categorized into two types: monolithic and modular.

* **Monolithic blockchains** centralize all tasks, including data availability, consensus, settlement, and transaction execution, within a single network. While this structure offers simplicity, it often leads to scalability issues, especially during periods of high transaction volumes. Ethereum, for example, has faced challenges with high fees and slower processing speeds due to its monolithic design.
* **Modular blockchains**, on the other hand, separate these layers—execution, settlement, and data availability—allowing each to operate independently. This design results in a more efficient and scalable system, as different tasks can be processed in parallel.

Massive is a decentralized Zero-Knowledge Proof (ZKP) verification network that exemplifies the modular design approach. It is composed of several layers that optimize efficiency and scalability:

* **ZKRollup**: Handles off-chain computation to reduce the load on the main blockchain.
* **Data Availability (DA)**: Manages off-chain transaction storage, ensuring scalability without overloading the main chain.
* **ZKVaaS (Zero-Knowledge Verification as a Service)**: Conducts off-chain verification of transactions and states, maintaining security while minimizing on-chain activity.
* **L1**: Manages state updates and consensus, providing finality for verified transactions and maintaining the integrity of the network.


---

# 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://ola-foundation.gitbook.io/ola-documentations/ola-network-core-components-onis-and-massive/massive/2.-modular-design.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.