# Governance Approach

## **From Centralized to Decentralized** <a href="#from-centralized-to-decentralized" id="from-centralized-to-decentralized"></a>

‌Flurry will begin with centralized control of the protocol (such as adding/ removing new types of yield-farming strategies, assigning risk factors to different strategies, etc) and migrate to complete community and stakeholder control over time.‌

**$FLURRY** will serve as the governance token of the Flurry Protocol. $FLURRY holders will participate in protocol governance through a decentralized voting process. Among other decisions, token holders will be able to vote on adding/removing new yield farming strategies and assigning risk factors to different strategies.

## Phased Approach <a href="#phased-approach" id="phased-approach"></a>

### **‌*****Phase 1***

‌Flurry Financial team will initiate yield-earning strategies.

### *Phase 2* <a href="#phase-2" id="phase-2"></a>

‌Launch of initial voting functions for $FLURRY token holders. Flurry Financial team and early $FLURRY holders will select best yield-earning strategies as the process to decentralization begins.‌

### *Phase 3* <a href="#phase-3" id="phase-3"></a>

‌Continued distribution of $FLURRY governance tokens to Flurry users, as voting functions are further developed and rolled out. The Flurry Financial team becomes less involved in decision making processes.‌

### *Phase 4* ‌ <a href="#phase-4" id="phase-4"></a>

Fully decentralized governance by $FLURRY token holders.‌


---

# 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.flurry.finance/flurry-finance/governance/governance-approach.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.