> For the complete documentation index, see [llms.txt](https://docs.flurry.finance/flurry-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flurry.finance/flurry-finance/governance/usdflurry-governance-token.md). # FLURRY Governance Token ## Governance Users who **hodls FLURRY tokens** will be able to **participate in protocol governance** through a transparent decentralized voting process. They will be able to vote on adding, changing, or removing new yield farming strategies the protocol uses to deploy its vaulted stablecoins received in exchange for rhoTokens. Unlike rhoTokens, FLURRY is not pegged to any stablecoin and its value fluctuates relative to the rest of the crypto market, and the FLURRY token is not used for yield farming. Instead, it can be purchased on exchanges and staked back into the protocol, earning [additional FLURRY as staking rewards](https://docs.flurry.finance/flurry-finance/governance/pages/-MgsDvVpxr-VgEmoc27R#2.-flurry-reward). FLURRY is now available for purchase (see trading links [here](/flurry-finance/governance/usdflurry-governance-token/trading-flurry.md)). ### FLURRY Staking ([Snowball](/flurry-finance/user-guide/snowball.md)) * Once users earn FLURRY from holding rhoTokens, they can claim their FLURRY, and stake it back into smart contracts, compounding the FLURRY earned. The proportion of the staking pool equals the proportion of the rewards. Rewards are given on a discretionary basis, earliest adopters will earn the biggest shares. * Users can stake FLURRY in Liquidity Pools. ## Note As the phased approach from centralized to decentralized governance of the Flurry Protocol proceeds, users who hold $FLURRY will be able to exercise their vote on the protocol through updated functions on the user interface. Look for these as they come! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.flurry.finance/flurry-finance/governance/usdflurry-governance-token.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.