> 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/untitled-3.md). # Industry (market) analysis and NIFTSY's place in it Since Envelop (hereinafter referred to as the Project) is initially built at the intersection of several markets (DeFi, NFT, DAO, DEX) and has the cross-chain feature, we will try to cover all segments very briefly and share the conclusions why we believe Envelop is not just a competitive product, but also a promising global solution for further Web 3.0 evolution over the next 5-10 years. This section is primarily intended for those who are familiar with the markets listed above, and want a brief, but comprehensive analysis to understand the trends within which the Project was organized and received development. --- # 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/untitled-3.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.