> 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/1.-depin-layer-decentralized-physical-infrastructure-network.md).

# 1. DePIN Layer (Decentralized Physical Infrastructure Network)

The DePIN Layer is the backbone of the Hash Network, facilitating decentralized content access through a network of gateways. It consists of two main components:

* **Gateway Nodes:** These are critical entry points for data, handling requests, and ensuring seamless and secure communication between clients and the network. Gateways are geographically distributed to reduce latency and ensure high availability. They integrate advanced caching mechanisms like NGINX and Varnish to store frequently accessed content, optimizing performance and providing a faster, more reliable user experience. Additionally, Gateway Nodes are scalable and can handle increased traffic by adding more nodes and distributing the load efficiently.

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

* **Guardian Nodes:** These nodes play a pivotal role in maintaining network integrity by overseeing and validating transactions and operations. Acting as trusted entities, Guardian Nodes ensure that the decentralized infrastructure remains secure, trustworthy, and resilient against malicious activities.


---

# 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/1.-depin-layer-decentralized-physical-infrastructure-network.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.
