> For the complete documentation index, see [llms.txt](https://docs.fang.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fang.finance/introduction-and-faqs/welcome/introduction.md). # Introduction Fang Finance is a multi-DEX yield optimizer on Ethereum. It supports only SuperNova, to begin with, leveraging the ve(3,3) flywheel. {% hint style="info" %} ## **The company was founded by a team of passionate OGs from the Tomb fork community on Fantom, initially with Snake Finance on Sonic.** {% endhint %} Our **treasury** will strategically invest in these areas, creating new utilities for the $FANG token and driving long-term value for our ecosystem. This multi-faceted approach ensures that $FANG remains relevant and resilient in the ever changing DeFi landscape. ## Why peg to $ETH? By pegging $FANG to $ETH, we aim to create a highly liquid, mirrored asset that benefits from the growth and adoption of the Ethereum network as well as the crypto space in general, while also benefiting its users with more stability. --- # 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.fang.finance/introduction-and-faqs/welcome/introduction.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.