# The Power of a MetaDEX Economy for Blast

With the upcoming launch of the [full-stack chain in Q4](https://blog.blast.io/vision/), Blast is laying the foundations for a new type of ETH L2 that can capture millions of users through seamless onboarding with fiat on/off ramps, zero-gas swaps, and automatic yield through a mobile experience.

Our vision is a rich protocol ecosystem that has a capacity to exponentially grow by tapping into a much larger user base beyond DeFi or crypto natives.

Traders will need deep liquidity to trade tokens and protocols will need liquidity to make that happen. Blast will benefit from a decentralised economy that can effectively meet these needs, and where **value distributed to users is unlimited.**

**Blast allows Fenix to supercharge revenue potential.** \
\
\&#xNAN;*Fenix has a powerful model that is not possible on other chains.* \
\
Usually DEXs rely on trading fees and/or protocol incentives to generate revenue. This is also true for Fenix, however, through Blast Native Yield there is an additional source of revenue that will allow Fenix to more efficiently build and maintain liquidity for protocols and core ecosystem assets, which will facilitate the best prices on swaps for traders.

<figure><img src="/files/TpcdCIEIIcVHQyMqCpcu" alt=""><figcaption></figcaption></figure>

Blast Native Yield is an improvement in L2 technology that allows liquidity deposits of USDB & ETH on Fenix to accumulate underlying yield. By redirecting this yield through the RISE as protocol and user incentives and to LPs in FNX pools, the power and capital efficiency of the MetaDEX design is increased significantly.

Through higher revenue potential that comes from Blast Native Yield, Fenix is improving the MetaDEX model with a goal to establish Blast as a highly attractive place for protocols to deploy and build liquidity amongst a highly competitive ETH L2 landscape.


---

# Agent Instructions: 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://docs.fenixfinance.io/fenix/a-metadex-supercharged/the-power-of-a-metadex-economy-for-blast.md?ask=<question>
```

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.