# 1.1 History of creation

Nava DAO was created by a group of crypto enthusiasts in 2025. After analyzing existing crypto projects, referral programs, as well as decentralized organizations, DeFi, and GameFi sectors, we came to the conclusion that most sectors of the crypto and web3 sphere are either completely centralized or pseudo-decentralized organizations. 

The lack of comprehensive solutions for users, perceived decentralization, and unfair distribution of profits in relation to users led us to the idea of creating a fully decentralized web3 platform where each participant has the right to influence the future development of the company and claim a fair distribution of rewards. 

*Setting ambitious goals and plans for ourselves, we decided to challenge not only the unfair model of centralized management, but also pseudo-decentralized projects that position themselves as "community-managed" but are in fact ordinary companies pursuing only the personal interests of their creators and their inner circle.* 

**The priority task of the NAVA DAO development team is to create a web3 platform that combines referral programs, DeFi, and GameFi products into a single ecosystem managed by the community.** 

Furthermore, delving deeper into the issues of unfair profit distribution in projects, the absence of referral rewards, and the concentration of power in the hands of company managers, we were motivated to unite to create a fair model for distributing rewards, implementing referral programs, and establishing a fully-fledged DAO managed by the community. 

<br>


---

# 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://nava-dao-1.gitbook.io/nava-dao-white-paper/basics/markdown/1.1-history-of-creation.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.