> For the complete documentation index, see [llms.txt](https://web3-gate.gitbook.io/web3-gate/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://web3-gate.gitbook.io/web3-gate/roadmap-of-project.md).

# Roadmap of project

## Phase 1:

* Brainstorming on the product's core concept
* Articulating the project's objective and vision
* Assembling a motivated team to work on the project
* Establishing the project's social networks and community
* Whitepaper and Website release 

## Phase 2:

* Development of functions in the dApp of W3Gate
* Creating a brand new web-wallet in the dApp
* Partnership with the Pinksale Finance for a fairlaunch
* Collecting badges (KYC, SAFU, Audit, DOXX) for the security
* Release of the dApp ready to use for everyone
* Initial marketing through KOLs, ads and AMAs

## Phase 3:

* Pinksale Finance presale as a fairlaunch
* Launching on UniSwap after the presale
* DexTools ads and trending tools for a marketing
* CoinMarketCap and CoinGecko listing for a new investors
* Partnerships and brand ambassadors to let more people know about project

## Phase 4:

* Main marketing campaign to increase the number of users
* Worldwide adoption and partnerships in global scale
* Listing on Top centralized exchanges
* Increased number of holders and continuous improvements 
* Second Part of the Roadmap release


---

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

```
GET https://web3-gate.gitbook.io/web3-gate/roadmap-of-project.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.