> For the complete documentation index, see [llms.txt](https://hash-network.gitbook.io/hashnetwork/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hash-network.gitbook.io/hashnetwork/core-concepts-and-architecture/hash-network-layer-3-stack.md).

# Hash Network Layer 3 Stack

The Hash Network Layer 3 stack is a modular architecture designed to capture value across its DePIN and Value layers. Operating on an L2 rollup, it integrates critical components to enhance security, scalability, and user control, with near-zero transaction fees using a native token. This stack also centralizes the provenance of decentralized content, ensuring efficient and secure operations.

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

**Execution Layer:** Utilizing Arbitrum Orbit for high-throughput execution, ensuring dApps run efficiently at scale with reduced costs.

**Settlement Layer:** Leveraging Arbitrum Nova for secure and efficient transaction settlement, enhancing overall network reliability.

**Data Availability Layer:** The Eigen Layer ensures robust data availability, maintaining integrity during disruptions and guaranteeing reliable access to decentralized content.


---

# 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://hash-network.gitbook.io/hashnetwork/core-concepts-and-architecture/hash-network-layer-3-stack.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.
