# Why should you choose FlyPad?

> FlyPad is built for BNB Chain traders, creators, and communities who want real
>  yield, real liquidity, and real burn pressure behind every token launch.

It turns BNB into productive capital and turns every trade into a flywheel for the
 ecosystem.

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

There's a variety of benefits that comes alongside joining the FlyPad ecosystem;

{% stepper %}
{% step %}

### Trenchers earn yield while they trade, no matter the trades

Users wrap BNB into FLYBNB and earn up to 10 percent APY from aster.
&#x20;Yield is claim based and earned by wallets and liquidity pools.
{% endstep %}

{% step %}

### Liquidity pools bolstered by yield as well

Any pool that uses FLYBNB as liquidity earns the same 10 percent APY on its
&#x20;FLYBNB balance.
\
This makes every launched token start with productive liquidity.
{% endstep %}

{% step %}

### v3 Single Sided Liquidity, v2 fees

Tokens launch with PancakeSwap v3 single sided liquidity using the 0.25
&#x20;percent fee tier (same as v2).

\
This gives better price impact, better routing, and more control over fees.
{% endstep %}

{% step %}

### Flywheel Design with the $FLY Token

The ecosystem token is burned through trading, fuelled by yield, supported
&#x20;by buybacks, and rewarded through airdrops.

\
Wrap BNB → earn yield → launch tokens → trade → burn → rewards → more
&#x20;activity → more yield → repeat.
{% endstep %}
{% endstepper %}


---

# 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.flypad.app/getting-started/why-should-you-choose-flypad.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.