# Roseon.DeFi

**Roseon.DeFi** is a decentralized yield farming application, the DApp (Decentralized Application) will serve as our decentralized liquidity provider, swap and DeFi aggregator. Roseon.DeFi will come with 3 main features:&#x20;

**Vaults**

Roseon.DeFi’s Vaults is a yield optimizer platform focused on providing DeFi users with auto-compounded yields at optimal intervals, with pooling gas costs through efficient smart contract codes using complex yield optimization strategies. Roseon.DeFi uses a proprietary dynamic harvesting optimizer to enable the highest APYs on our vaults.&#x20;

**Swap**&#x20;

Roseon.DeFi’s Swap is a DEX aggregator that gets queries for the best prices from various DEXs. Roseon Farm Swap splits trades across multiple DEXs to ensure the best prices and lowest slippage possible. Trades with Swap also become non-front-runnable and non-arbitrable.&#x20;

**Liquidity Pools**

Liquidity pools are one of the foundational technologies behind the current DeFi ecosystem. They are an essential part of automated market makers (AMM), borrow-lend protocols, yield farming and synthetic assets. Liquidity pools are the backbone of many decentralized exchanges (DEX), such as Uniswap, Pancakeswap and Sushiswap. Roseon.DeFi will have its own AMM and will allow its users to participate in the ecosystem as liquidity providers (LP) to earn trading fees from the trades that happen in their pool, proportional to their share of the total liquidity. <br>


---

# 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://roseon.gitbook.io/roseon/whitepaper/roseon-ecosystem/roseon-aggregator.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.