# Flex Improvement Proposal (FIP)

The Flex ecosystem is designed to be dynamic and responsive to community needs. Flex Improvement Proposals (FIPs) provide a structured process for suggesting, discussing, and implementing changes. This guide outlines the technical steps and mechanisms involved in the FIP process, from submission to on-chain voting and implementation.

**Overview of the FIP Process:**

1. Proposal submission: Proposals are submitted on the Flex page on Discourse.org. 
2. Community moderation: Proposals undergo moderation by the Flex Core Team and Flex Contributors - community is also welcome to voice their opinions on the listed proposals. 
3. On-chain voting: Proposals that pass moderation are voted on by FLEXE token holders on the Flex Snapshot.org page.
4. Implementation: Approved proposals are implemented within the ecosystem.

**Detailed technical steps**

1\. Proposal submission

Proposals are submitted as entries on Discourse.org. A submission should include:

* Title: A concise title.
* Abstract: Summary of the problem and solution.
* Conclusion: Summary and call to action.

2\. Community moderation

Proposals are moderated on Discourse.org through:

* Discussion: The core team, contributors, and community can provide feedback and participate in the discussion. The final decision regarding moderation rests with the core team.
* Revisions: Proposer revises based on feedback.
* Moderation vote: Community moderators review and approve proposals for voting.

3\. On-chain voting

Proposals approved by moderation are moved to Snapshot.org for on-chain voting:

* Announcement: Proposal announced and voting period set.
* Voting period: Flex token holders vote during the specified period.
* Vote calculation: Votes are tallied and results are announced.

4\. Implementation

Approved proposals go through:

* Planning: Detailed planning and scheduling.
* Development: Coding and testing the changes.
* Deployment: Deploying changes to the ecosystem.
* Monitoring: Ongoing monitoring and issue resolution.

#### Technical specifications and mechanisms

Proposal submission and formatting

Proposals are formatted in Markdown and submitted on Discourse.org. Each proposal must follow a standard template to ensure consistency and clarity. Here’s an example template:

```markdown
# Proposal Title

## Abstract
Brief summary of the proposal.

## Conclusion
Summary of key points and call to action.
```

Community moderation process:

* Initial review: Proposals are initially reviewed for completeness and adherence to guidelines.
* Discussion phase: Community members discuss and provide feedback.
* Revisions: Proposers make necessary revisions.
* Final moderation: Community moderators conduct a final review and vote to move the proposal to the voting stage.

On-Chain Voting Mechanism:

Voting is conducted on Snapshot.org, leveraging the decentralized nature of the blockchain. 

Implementation and Monitoring:

Once a proposal is approved, it undergoes a rigorous implementation process:

* Planning: Detailed planning to outline the steps, resources, and timeline required for implementation.
* Development: Coding and testing the proposed changes. This involves writing smart contracts, modifying existing code, and conducting thorough testing.
* Deployment and testing.
* Monitoring: Continuous monitoring post-deployment to ensure stability and address any issues that arise. 

The Flex Improvement Proposals (FIPs) process is a robust and democratic mechanism for suggesting and implementing changes within the Flex ecosystem. By involving the community at every stage, from proposal submission to on-chain voting and implementation, Flex ensures that its development is aligned with the needs and preferences of its users. This process not only enhances the ecosystem but also fosters a collaborative and engaged community. 

**Whether you are a developer, a token holder, or an active community member, your contributions through FIPs can help shape the future of the Flex ecosystem.**

{% hint style="info" %}
We invite developers, researchers, and enthusiasts to work with our contributors for this section. [Start contributing here. ](https://app.deform.cc/form/21842244-e1c1-479f-a8b3-3877903ecd44)
{% endhint %}