> 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/unyfy-protocol/dark-pool.md). # Dark Pool ### Manipulation resistance for small cap tokens Dark pools in traditional finance are used for minimizing price impact. The [Unyfy](https://unyfy.xyz/) team sees the role of dark pools in crypto in an entirely different light. Rather than using its properties to protect institutional traders in big cap markets, we aim to protect community members in small cap markets. The Unyfy Dark Pool is the backend infrastructure that powers the protocol. As the token becomes high volume, DeFi scavengers such as MEV and snipers will be out there, and just providing the litpool in groupchat is not going to prevent this. An elegant solution therefore is making the primary medium of token exchange a darkpool, and filter out the small orders into GroupFi.

Observers should have no bearing on the distribution of liquidity across prices. There could be large orders right above or below the mid-price with enough liquidity to absorb adversarial pump and dumps. As such, bots who attempt to manipulate the market do so at a significant risk to their treasuries. --- # 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/unyfy-protocol/dark-pool.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.