> For the complete documentation index, see [llms.txt](https://fatexdao.gitbook.io/fatexdao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fatexdao.gitbook.io/fatexdao/what-is-fatexdao/fatexfi-is-not-a-dex.md).
# FATExFi is not a "DEX"
### Why does it look like a "dex" if it's not?
The DAO is *not* building a DEX directly, we are using the traditional “dex” — yield-farm, liquidity pool DApp model to circumvent the angel investment process, one of the many advantages of a DAO. to build capital and support using the cheap and rapid network the Harmony team has succeeded in creating.
### Ok... What is it?
FATExFi is a digital asset depository that is pooling capital for, and from, DAO members to build a profitable, commercial FinTech & DeFi investment & banking institution.\
\
FATExDAO & its DEX/Dapp was never intended to just be a fork yield-farm/dex in the traditional sense - it repurposes a dex into:
* It is a depository for members' digital assets that are pooled into a collective "DeFi" commercial enterprise.
* Collectively via the FATE governance token - DAO members participate in all decisions and build an equity position to benefit from the DAO's focus:
* Create financial services and products that have large-scale commercial applications via DeFi/DLT/tokenization tech.
* Produce wealth/value through innovations that increase economic activity in an equitable, inclusive, borderless, and ESG-aligned manner.
* This is significantly different from almost any other DeFi project by its own measure.
### How do we do that?
We want to minimize the number of FATE tokens in public circulation. At the moment, FATE is an intangible asset, that has immense potential value - that will be realized - but given the enormity of the FinTech industry and the DAO's plan to lead and capture a significant piece of the DLT-tokenization impact on each sector of traditional finance - the proformas' themselves are hard to believe - it is best to accomplish the first phase of monetization via FxD, demonstrate the ability and potential of FATExDAO before a significant portion of FATE tokens are allowed to be acquired.
* Building long-term members who hodl FATE and contribute capital with long-term, steady, sustainable FATE reward distributions - which has been, and will continue to be maintained.
### **What is important:**
**The DAO treasury's primary focus is not to provide liquidity for DeFi trading, but to build & hold capital for FinTech & digital banking products & services that produce revenue, which will be legally distributed to its members.**
We are the first DApp to offer PAXG as an alternative to BTC, ETH, or a stablecoin, as primary liquidity pair, not for novelty or apparent uniqueness.
* CapEx used to build the prototypes, team, and Dapp framework/infrastructure necessary to create profitable FinTech products/services asap.
* The focus is on the future value of FATE and its derivatives, not "APR" equated from the emission schedule rewards.
\
\
Please read & note the statements in the [**Disclaimers Section**](/fatexdao/legal-ip-disclaimers/disclaimers-1.md) of these documents found [here](/fatexdao/governance/non-defi-profit.md).\
---
# 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:
```
GET https://fatexdao.gitbook.io/fatexdao/what-is-fatexdao/fatexfi-is-not-a-dex.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.