# Network Layer

The network layer is the foundation of all privacy in Invinos. It is responsible for protecting how your device communicates with the outside world. In most systems, this traffic flows through centralized Internet Service Providers (ISPs) or VPN services — entities that can log, analyze, and potentially sell or hand over your metadata. Invinos eliminates these intermediaries by using a decentralized, peer-based VPN tunnel system that routes all internet traffic through anonymous relays.

Each packet is encrypted multiple times (multi-hop routing), passing through several randomly selected relays before exiting to the open internet. At no point can a single node see both the origin and destination of the data. DNS queries are also resolved anonymously, preventing domain-level surveillance. Padding is added to disguise packet sizes and timings, mitigating traffic analysis attacks.

This layer ensures that websites, applications, and blockchain services can’t infer where you are, what device you’re using, or what other traffic might be associated with your session. It's always-on, persistent across modules, and the first defense in Invinos' privacy stack.


---

# Agent Instructions: 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:

```
GET https://invinos.gitbook.io/invinos/system-architecture-overview/core-design-layers/network-layer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
