# Flywheel Rooster Protocol incorporates powerful ve(3,3) flywheel mechanics, a proven model that creates a self-reinforcing cycle of liquidity growth and governance participation: * **Emission Control:** veROOSTER holders can use their voting power to direct emissions toward specific liquidity pools. * **Enhanced Rewards:** veROOSTER holders are incentivized with trading fees and additional rewards for directing emissions effectively, creating strong alignment between token holders and liquidity growth. * **Positive Feedback Loop:** As pools attract more liquidity through emissions, trading volume and fees increase, further rewarding veROOSTER holders and encouraging more token locks. This well-established flywheel design aligns the interests of all participants—traders, liquidity providers, and veROOSTER voters—fostering sustainable ecosystem growth and reinforcing the protocol's utility and value.\ \ The ve(3,3) flywheel will go live after ROOSTER TGE. ## **Epoch Mechanics** Rooster Protocol's flywheel will operate on a weekly epoch cycle: * **Epoch Duration:** A 7-day period, starting every Thursday at 00:00 UTC and ending Wednesday at 23:59 UTC. * **During each epoch:** * LPs who provide liquidity receive ROOSTER token emissions, distributed proportionally to the votes their pools accumulate. * Participants can lock ROOSTER tokens to become veROOSTER voters, who determine the emissions distribution for the next epoch. * veROOSTER voters are rewarded proportionate to their votes with: * 100% of the protocol trading fees generated in the current epoch. * Additional voter incentives allocated by participating projects. * All votes, emissions, fees, and incentives are calculated and distributed at the epoch's conclusion. --- # 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://rooster-protocol.gitbook.io/docs/overview/flywheel.md?ask= ``` 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.