# The ve(3,3) Flywheel

It is in veBEAM holders' best interests to vote for the reward pools that have the most trading fees and bribes, and through their votes more $BEAM emissions are directed to the most productive pools (boosting liquidity providers' farming APRs). \
\
Additionally, as veBEAM holders are the only stakeholders with access to the trading fees of Beam, it is in users' best interests to continually grow their veBEAM position through providing liquidity or buying on the open market.

This aligns the incentives of veBEAM holders with liquidity providers, as well as traders (as higher farming APRs attracts more liquidity, which reduces slippage on trades).\
\
**The ve(3,3) flywheel is as follows:**\
1.) Emissions are distributed to liquidity pools based on veBEAM holders' votes\
2.) Incentives / APRs attract farmers to provide liquidity to these liquidity pools, increasing TVL\
3.) Higher TVL = higher trading fee revenue\
4.) Higher trading fee revenue means more rewards for veBEAM holders to claim for the week (increasing voting APR)\
5.) Higher rewards means more demand to buy and lock veBEAM to increase weekly reward share\
6.) More demand for $BEAM = higher $BEAM price\
7.) Higher $BEAM price = higher liquidity pool APRs when emissions are distributed next week\
8.) Flywheel repeats


---

# 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.beamdex.xyz/protocol-overview/beams-ve-3-3-ecosystem/the-ve-3-3-flywheel.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.
