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

# Hash Network Layers

The Hash Network Layers form the core architecture of the ecosystem, designed to ensure decentralized, secure, and efficient content access and management. This multi-layered structure is divided into the DePIN Layer and the Value Layer. The DePIN Layer handles the physical infrastructure through Gateway and Guardian Nodes, facilitating decentralized content delivery and network security. The Value Layer supports the economic and operational functions via smart contracts, ensuring the provenance, permanence, and prioritization of content. Together, these layers provide a robust and scalable foundation for the Hash Network

### DePIN Layer (Decentralized Physical Infrastructure Network)

The DePIN Layer forms the physical backbone of the Hash Network, comprising:

* **Gateway Nodes**: Manage decentralized content access and caching.
* **Guardian Nodes**: Ensure the integrity and security of transactions within the network.

### Value Layer

The Value Layer includes a suite of smart contracts that automate and secure network functions:

* **Provenance Smart Contract**: Manages the verification and traceability of content.
* **Permanence Smart Contract**: Ensures long-term content availability and redundancy.
* **Prioritization Smart Contract**: Organizes and prioritizes content based on relevance and recency.


---

# 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/editor.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.