# Vote

**※The process of voting against a proposal will be similar to the process of voting for a proposal.**

**Step 1**

* On the recent proposal list screen, click on the proposal users wants to vote for → Redirect to the proposal details information.
* Condition

  * Only proposals with *Active* status can be voted on.
  * To make a successful vote, users need to have at least a certain amount of GT that differs among each type of proposal. For details, please refer to the **“Proposal Type”** Table.                                                                                                                                                                                                         

     ![](/files/q8m6XhXS2F1wRZ2sp87g)

**Step 2**

* The system will automatically record that you vote for all available GT/FRTS amounts in your account. You will not have to pay a fee (FRTS) to make a vote transaction.
* Click on the "Vote for" button → “Vote for proposal” pop-up will be displayed.

**Step 3**

* Click on the “Confirm” button to confirm the vote.                                                                                                                                                                      ![](/files/EBpO6AHw2YpBmOLj7d21)

**Step 4**

* The network will confirm the transaction. After the transaction is confirmed → Voting is done successfully

**Note:**

* Users can vote for multiple proposals.
* User's can only vote once per proposal.
* Each vote will count all the GT that the user owns (including the amount that was locked when creating the proposal and the available amount).
* The GT used for voting is not locked. The available GT is still used for transactions.

**Voting Process**

**※** The voting process for all types of proposals will be similar. However, each type of proposal will have different parameters such as proposal creating conditions, voting time, and success conditions. For details, please refer to the “Proposal Type” Table.

<table><thead><tr><th width="102">Period</th><th width="621">Description</th></tr></thead><tbody><tr><td><strong>1</strong></td><td><p><strong>Pending</strong>: When a governance proposal is created, it enters a 2 day review period. The FRUITS Organization considers to approve or reject the proposal. <strong>Active</strong>: Proposal is approved by FRUITS Organization</p><p><strong>Rejected</strong>: Proposal is rejected by FRUITS Organization.</p></td></tr><tr><td>2</td><td>Proposals with <strong>Active</strong> status will enter Voting period.</td></tr><tr><td>3</td><td><p><strong>Queued</strong>: if the proposal meets the approval conditions, it will be in the queue for execution.</p><p>Or <strong>Defeated</strong>: The opposite of “Queued” - the proposal failed to meet the approval conditions.</p></td></tr><tr><td>4</td><td><p><strong>Executed</strong>: FRUITS Organization designates proposal execution.</p><p>Or <strong>Expired</strong>: If after 30 days of waiting, FRUITS Organization has not specified execution, the proposal expires and the result is not valid.</p></td></tr></tbody></table>

**※** **Note**: At **Pending, Active, Defeated** status, the proposal creator can cancel the proposal. The system will cancel the result of the proposal at that time.

&#x20;&#x20;


---

# 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.fwallet.net/app-fruits-wallet/governance/vote.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.