> For the complete documentation index, see [llms.txt](https://docs.lifty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lifty.io/product/roadmap.md). # Roadmap ## **May 2021** MVP of an NFT marketplace launched on BNB Chain ## **Aug 2022** * High performing marketplace operating on BNB Chain, Ethereum, and Polygon * NFT portfolio: support of any NFT collection * Launchpad for INOs and IDOs * NFT Gaming analytics portal * Store: mint any NFT token or collection on any of supported chains. Create your custom storefront ## Q4 2022 * Gamer dashboard: portfolio, ROI, achievements, public profile * Smart money following and gem locator * New marketplace features and support of new chains * New games in the analytics portal ## Q1-Q2 2023 * NFT Gaming social network and rating system * Recommendation system * DAO implementation on the Launchpad * Promotion & publishing tools for Games * NFT price evaluation system ## Q4 2023 **No. 1 portal for NFT Gamers and Games** “Steam for NFT Gaming”. The main hub for all games and gamers where they can find all the actual and relevant data, exchange their items and ideas. --- # 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://docs.lifty.io/product/roadmap.md?ask=&goal= ``` `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.