> For the complete documentation index, see [llms.txt](https://niftsy-protocol-niftsy-1.gitbook.io/niftsy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://niftsy-protocol-niftsy-1.gitbook.io/niftsy/key-documents/white-paper/roadmap.md).

# Roadmap. Part. #01

From November 2020 to February 2021, DAO NIFTSY was formed and work began on researching the NFT market. 

In March 2021, a minimal product was made and the team participated in the Binance hackathon. 

Currently, an Alpha version of the protocol is being worked on (until July 2021). 

After that, it is planned to refine the functionality of the Protocol and expand the Token functions, including - in connection with the IDO held in August-September. 

Next, the development of other elements of the Project starts: Oracle and Index, which together with the Protocol represent a closed ecosystem of work with NFT and their accounting/analysis system. 

Finally, the release of the full beta version of the Project is expected in June 2022.

![](/files/-MeVRdCTRWZDkG1D4bWB)

Above is a general road map. Let us try to look at it in more detail:

So, from November 2020 to February 2021, DAO NIFTSY was formed and work on NFT market research began. 

In March, a minimal product was made and the team participated in the Binance hackathon. 

Currently, an Alpha version of the protocol is being worked on (until July 2021). 

After that, it is planned to refine the functionality of the Protocol and expand the Token's functions, including - in connection with the IDO in August-September. 

Next, the development of other elements of the Project starts: Oracle and Index, which together with the Protocol represent a closed ecosystem of work with NFT and their accounting/analysis system. 

Finally, the release of the full beta version of the Project is expected in June 2022. <br>

During development, we also take into account the gradual integration of the Protocol and other elements of the Project into the various LDCs, as follows:

The initial version of the Protocol is built on EVM-enabled blockchains (Ethereum, BSC and others).&#x20;

This is followed by integration with L2-level solutions such as Polygon and others.&#x20;

And then there is gradual integration with other DDN/DDS. At the time of writing (in alphabetical order): first turn - **Ethereum** (release), **BSC** (release), **Polygon** (release), **Avalanche** (MVP), EvmOS (MVP), **Ziiliqa (**&#x61;t work), **Wax** (at work), **Near** (at work). Second line - L2.&#x20;

Finally, we are guided by the following principles in implementing the said Roadmap:

Initial implementation dates are written down, if the project attracts more crowdfunding for development, the specified dates can be shifted towards better positions.&#x20;

It all depends on which projects integrate the Protocol and/or are willing to invest their own energy, time and other resources into its development.&#x20;

Finally, it also depends on the implementation of the roadmaps of the projects themselves: for example, as of today we expect Ethereum to move to version 2.0. <br>

Knowing all this - let's move on to the final part.<br>


---

# 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://niftsy-protocol-niftsy-1.gitbook.io/niftsy/key-documents/white-paper/roadmap.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.