> For the complete documentation index, see [llms.txt](https://docs.toupee.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toupee.tech/what-toupee-tech-aims-to-solve.md). # What Toupée Tech Aims to Solve Toupée Tech endeavors to enhance the Solidly model by introducing pivotal innovations that offer: \ \ Adaptability: Through the integration of plugins, support for gauges involving any yield-generating asset becomes possible. This liberates Toupée Tech from dependency on any singular AMM technology, safeguarding against potential obsolescence. Furthermore, this expansion opens avenues for ecosystem incentives beyond the realm of DeFi, encompassing domains like web3 gaming and public goods. \ \ Stability: The establishment of an unalterable price floor for the primary token (WIG), grants DAOs that accumulate voting power the ability to assess their risk with a firm confidence in the token's minimum value. \ \ Flexibility: The era of protracted lockups for tokens secured in voting is concluded. Participants with voting power experience locked positions solely during active use, with the option to initiate a one-week unlocking phase. This empowers them to free their vote-escrowed tokens and depart the system. \ \ Sustainability: The issuance of call options to gauges introduces a balanced incentive system. Those engaging must also contribute. \ \ Liquidity: The bonding curve introduces a novel concept of Token-owned Liquidity (ToL), ushering in substantial liquidity and minimal slippage across the full spectrum of possible price points. This encompasses borrowing against tokens in vote escrow without liquidation risk, providing liquidity from a single side (eliminating impermanent loss), and establishing an immutable price floor for the primary token. --- # 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.toupee.tech/what-toupee-tech-aims-to-solve.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.