# Governance Process

AWE Network is a decentralized, community-driven ecosystem that enables governance participation through a structured proposal and voting process. The governance process ensures that all network decisions, from protocol upgrades to ecosystem initiatives, are made transparently and efficiently.

## **Proposal and Voting Process Flow**

<figure><img src="https://2494829985-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKPzJzyJFmAFMJBOSKIiV%2Fuploads%2Fvyu9goz2xnAgebcWuZ0s%2FIdeation%20Phase%20(1).png?alt=media&#x26;token=2be27c8b-f2e9-487f-8772-f94688fa8def" alt=""><figcaption></figcaption></figure>

### **Step 1: Ideation Phase**

To submit a proposal, community members must first initiate a discussion in the **AWE Governance Hub**. The proposal should be well-structured, clearly articulated, and categorized correctly.

When posting in the **AWE Governance Hub**, select the appropriate category and add a prefix to your proposal title:

* **AWE Funding Proposal** **(AFP):** Proposals related to allocating funds from the community treasury (grant programs, ecosystem development, strategic acquisitions)
* **AWE Governance Proposal (AGP):** Proposals related to governance structures, framework modifications, quorum adjustments, or security council updates.
* **AWE Community Proposal (ACP):** Proposals for offchain initiatives, such as nominating committee members or modifying non-contractual governance mechanisms.

After posting, community members are encouraged to **discuss, comment, and refine the proposal**. The default Ideation Phase lasts **5 days**. If additional discussion is needed, the proposer may extend this phase for up to **an additional 5 days**.

### Step 2: Temp Check

Once the Ideation Phase concludes, the proposer must summarize the refined proposal in the same thread, incorporating community feedback. A poll is then held to ensure community alignment.

At this stage, the proposal receives an official identifier (e.g., **AFP-1, AGP-1, or ACP-1**).

A **2-day final review period** follows, allowing for final feedback before moving forward to voting.

### **Step 3.1: Offchain Voting on Snapshot (ACP Only)**

*Relevant only for AWE Community Proposals (ACPs).*

If an ACP gains significant community support in the Governance Hub, it proceeds to **Snapshot for an offchain vote**.

* The voting period lasts **5 days**.
* Quorum: **0.5% of AWE supply** **(10M AWE)**
* A simple majority vote is required for the proposal to pass.

This step ensures consensus before implementing community-driven changes that do not require smart contract execution.

### **Step 3.2: Onchain Voting on Tally (AFPs, AGPs Only)**

For proposals that involve smart contract modifications or governance framework updates, the next step is **onchain voting via Tally**.

* Any wallet with **at least 0.2% of AWE supply** (4M AWE) **in voting power** can submit an onchain proposal via governance contracts on Base through the Tally interface.
* After the proposal is submitted, there is a **3 day waiting period** before the start of onchain voting.
* Quorum: **10% of AWE supply** (200M AWE)
* Proposals will require a **detailed description** and the **executable code** so that the proposed changes are executed automatically if passed.

{% hint style="info" %}
Join and Delegate your AWE tokens on [Tally](https://www.tally.xyz/gov/awe-network).
{% endhint %}

### **Step 4: Voting Period**

The offchain voting period lasts for **5 days** on Snapshot.

The onchain voting period begins **3 days** after proposal submission and lasts for 10 **days** on Tally. During this period, only **wallets with delegated voting power** can cast votes.

Users can choose between:

* **For** ✅
* **Against** ❌
* **Abstain** ⚪

### **Step 5: Passing Thresholds & Timelock**

For a proposal to pass, it must meet the following requirements:

* **Quorum:** At least **10% of AWE supply** must be cast as votes.
* **Outcome:** More **For** votes than **Against** votes.
* **For AGPs (governance changes):** Requires a **higher margin of support**, where **For votes > 2x Against votes**.

If a proposal **fails to meet quorum** or **does not pass**, it is rejected, and no execution occurs.

If the proposal passes, it moves into the **Timelock Phase**:

* **AFPs, AGPs are subject to a 7-day timelock before execution.**
* This ensures ample time for review, allowing the community to prepare for changes.

### **Step 6: Execution**

Once the **7-day timelock** concludes,

* Any user on the **Base network** can trigger the execution after the timelock expires.
* Once executed, the **proposal’s executable code is implemented automatically**.