> For the complete documentation index, see [llms.txt](https://bafex.gitbook.io/bafex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bafex.gitbook.io/bafex/dao-governance/the-role-of-the-team-and-community.md).

# The role of the team and community

### Founder's rights and multi-signature

During the development and testing phase, any change to the multisig budget requires approval from at least 3 key team members. After 6 months of launch, the DAO community will elect 5 members who will have the right to vote on budget changes - increasing the number of required minimum votes to 6 out of 10(minimum 3 from each side, 3 from the team, 3 from the community). Holders of over 0.8% of the total issue will have the right to be elected.

This mechanism eliminates the possibility of unilateral changes and maintains a balance between decentralization and the need for prompt action in emergency situations.

Example: The DAO decided to change the Liquidity Pool by a majority vote - even with a 51%+ "FOR" vote, the consent of the majority of the team members will be required.

***

### Veto-mechanisms

The team has the right to **veto** any proposal only during the “Time Lock” period (48 hours after the end of the voting).

A veto is applied in cases of detecting critical errors in the code, security threats, or serious legal risks.

To remove the veto, a new community vote would be required with a quorum threshold of 20% of the total proposal and an approval threshold of 66% "Yes".

***

### Incentive programs and grants

* **Grants Program:** a fund for third-party developers who want to build DApps and supporting services on top of BAFEX. The budget is allocated from the ecosystem development fund (10% of tokens).
* **Compensation:** Active community members who participate in discussions and help improve the protocol can receive up to 5,000 BAFEX for valuable advice and solutions.