# How does AMBR generate revenue to backup high APY?

AMBR enables its holders to extensively compound their investment and returns, as the protocol auto rewards its holders with 0.02422% every 15 minutes with the compounding APY of 385,047.90%.

Seeing the size of this APY, one may wonder — how is such APY attainable?

AMBR leverages a number of revenue-generating mechanisms:

**The protocol will use Defi 3.0 Multichain Farming to increase the AIF exponentially at a rate of \~100% a year or more to better support** AMBR **price floor.**

Unlike others who have a static RFV fund that do not yield profit. We will use the AIF fund and the treasury fund to multi-chain farming. The AIF funds are bridged to other EVM-compatible blockchains - like Avalanche, Fantom, Solana, Metis, Polygon, etc. to farm at the highest APY farms and the profit returned to the AIF fund.&#x20;

AMBR seeks yield-generating opportunities across different protocols and chains. Not just stay at BSC, the money from Treasury will be bridged to Fantom, Avalanche, Ethereum or any emerging blockchains which have high profit yield farms and substantial APYs enabling AMBR to deliver **\~100% additional returns a year or more to better support AMBR price floor. That's why we are confident that we can support higher APY than other projects while still sustainable.**


---

# 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://hamza-ayaz.gitbook.io/amberprotocol/the-amber-protocol/how-does-ambr-generate-revenue-to-backup-high-apy.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.
