# Structure

### User Roles

In a DAO, users will have two core roles:

* **Voters:** holding [25,000 BAFEX](/bafex/tokenomics/staking/for-dao.md) in staking;
* **Initiators:** holding 100,000 BAFEX in staking.

Proposers may also take part in the vote, in case they are not the initiator of the vote.

***

### Voting Mechanisms

Voting will take place On-Chain, using the DAO smart contract, which records addresses, the number of votes (1 BAFEX = 1 vote), and the time of voting.

Voting is conducted in two stages:

1. **Signal Request** (optional): The community expresses a preliminary opinion (sentiment indicator). **Deadline**: 2-3 days.
2. **Official Vote** (Snapshot Proposal): Vote on fund transfers, protocol parameter changes, fee adjustments, staking APY, etc.

***

### Voting params

* **Voting period:** 7 days (enough for large holders and active participants to react, but not too long).
* **Quorum threshold:** **10% of the total number of BAFEX in circulation** (minimum 10,000,000 BAFEX must participate in voting in any form).
* **Approval threshold:** 50% + 1 vote of those participating (i.e., mandatory majority “for”).
* **Execution Delay:** After the vote is completed, the DAO contract puts the proposal into a "waiting for execution" state for 2 days (timelock - protection against rash instant decisions). After this period, any BAFEX holder can call the execute function, and smart contracts automatically make changes if this is not provided for by the development.

***

### Voting question categories

* **Changes in fees and economic parameters:** adjustments to the base marketplace fee, APY for staking, and the reward structure in liquidity pools.
* **Use of the ecosystem development fund:** allocation of funds for grants, marketing campaigns, and legal support.
* **UI personalization and languages:** localization of new markets (adding languages, displaying UI from themes to fully customized solutions).
* **Technical upgrades:** smart contract updates (Escrow, Staking, DAO), transitions to new blockchain networks (e.g., adding Arbitrum or Solana), and adding new features to the platform.
* **New partnership integrations:** establishing strategic alliances that could impact development direction and tokenomics.
* **Update to governance thresholds:** changing the minimum number of BAFEX required to vote or initiate proposals.
* **Core Council:** voted twice a year, five people from the team, and five people elected by the community.


---

# 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://bafex.gitbook.io/bafex/dao-governance/structure.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.