> For the complete documentation index, see [llms.txt](https://docs.unyfy.xyz/unyfy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unyfy.xyz/unyfy/overview/intro-to-unyfy.md). # Intro to Unyfy From Trader to Consumer With Unyfy, project founders and users can unify multiple aspects of their ecosystem right within group chats. Unyfy incorporates four critical layers - notifications, finance (encompassing darkpools, orderbook, liquidity pools, auctions, trading, staking, lending, borrowing, and referral systems), and execution (integrated with smart contract blockchains). Up until now, open defi protocols have predominantly functioned as an infrastructure for open, unrestricted financial markets, fostering a surge in financial and trading applications. This, however, has birthed several issues within the industry: rampant pump-and-dump schemes by traders, consolidation of power in the hands of centralized entities, substantial revenue leakages due to Miner Extractable Value (MEV), a disjointed user experience given the gap between traditional and web3 identities. These prevailing market dynamics significantly hinder the potential value tokens could bring to projects and their communities, stifling the realization of a more comprehensive and engaged ecosystem. Unyfy addresses the pervasive issues in the blockchain space through a cohesive protocol that unifies project ecosystem in any community venue. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.unyfy.xyz/unyfy/overview/intro-to-unyfy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.