# Fluid Lite ETH Vault

Fluid Lite generates high yields by using lending protocols to amplify two main sources of returns:

* **ETH Proof of Stake rewards** (stETH Vault)
* **Stablecoins lending rates** (USD Vault)

Fluid Lite intelligently routes positions across multiple lending markets, currently **Compound, Aave V3, Spark, and Morpho,** to achieve the best possible APRs.

### stETH Vault: weETH-ETH Leverage Strategy

This vault takes **ETH or stETH**, then automatically converts deposits into the optimal mix of **wstETH and weETH**.&#x20;

It then:

* Supplies this collateral across multiple lending markets.
* Borrows ETH.
* Swaps borrowed ETH back into wstETH/weETH.
* Loops this process to create a leveraged staking position.

Through this continuous loop the base Ethereum staking yield is amplify.

This vault earns **weekly KING rewards** from weETH collateral. These are converted to ETH and distributed to users weekly.

<figure><img src="/files/510ujFkjoLylyzD0z0F6" alt=""><figcaption><p>A simplified view of Fluid’s leveraged ETH yield strategy.</p></figcaption></figure>

### **Long Term Steady Yields**

Ethereum’s proof of stake rewards will be generated in perpetuity! Unlike other DeFi yields that require emissions of DAO tokens, or secondary incentives, staking rewards are a consistent and reliable source of yield, arguably the best DeFi yield on the market! This makes Fluid Lite ideal for both short and long term holding.


---

# 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://lite.guides.instadapp.io/getting-started/fluid-lite-eth-vault.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.
