# 2.6 Organizational Model

![Wicrypt organizational model - high level summary
](https://165368761-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUlL6Z5XcXIxjYKLCkpNg%2Fuploads%2F7PEeh99bxAq4KfAQPn7O%2FWicrypt%20organisational%20model%20-%20high%20level.jpg?alt=media\&token=64ac7201-c696-4316-9e0e-2f95285eef1d)

Technical layer of Wicrypt is quite simple, the network is built atop two layers: 

* Layer 1 - decentralized hotspot hubs (micro nodes), powered by the custom firmware

* Layer 2 - connected clients (mobile phones, laptops, PCs, Smart TVs, Smart Watches and IoTs)

The network is not controlled by any central authority. Anyone can become a host by acquiring a supported hotspot hub router (micro node), installing the Wicrypt firmware and creating a WiFi zone. Anyone within the created WiFi range and a proper device (e.g. laptop or phone) can gain access to the internet and become a Wicrypt user by connecting with the hub.

In future, all Wicrypt nodes will be also connected with a decentralized storage network powered by Filecoin, allowing them to act as cloud storage devices as well.

\
From a business perspective, Wicrypt network is powered by a native token called Wicrypt Network Token ($WNT). The tokens are used to incentivise hosts for creating and managing WiFi zones, (especially in hardly accessible regions) and as means of user-oriented bonuses such as cashbacks and airdrops.


---

# 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://whitepaper.wicrypt.com/2.-introduction-to-wicrypt/2.6-organizational-model.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.