Overview

Below provides an overview of the proposal drafting, submission and approval process. Please treat this as a living document that will continue to evolve over time based on the Open Campus community’s input.

Below are the key steps that every proposal will have to go through, from ideation to implementation:

• Ideation: Submit your proposal and it will be reviewed and approved by an Administrator appointed by the Council. The Administrator will vet the proposal to ensure it meets the DAO’s objectives and mission. If the proposal is not approved, they will notify you, and you will be able to revise the proposal and submit it again.
• Comment Period: Tokenholders will have the opportunity to review, comment and discuss the proposals on Discourse for 7 days.
• Council Review: The Council will consider whether the proposal should be presented to the tokenholders for a vote. The Council will only consider implementing the proposal would cause the DAO to breach any laws, regulations or duties applicable to the DAO or the mission of the DAO. 
• Voting Period: Once the Council has determined to present a proposal for token holder voting, the proposal will be published on Snapshot and tokenholders will vote on it. The voting period will be open for a period of 7 days. If the proposal is approved, the proposal will move to the implementation phase. If not, it is archived for historical purposes.
• In Process: Approved proposals that are still being worked on will be tagged as "in process", and the Council should provide periodic updates to the community.
• Completed: Proposals that are fully implemented will be tagged as "completed" by the Council.
• Archived Proposals: Proposals that do not meet the threshold or are rejected during the Voting Period will be archived for historical purposes.

Proposal Structure

To provide structure and clarity throughout the proposal process, each proposal must follow the format below. The Council may specify any additional requirements for certain categories or types of proposals:

• Title
• Preamble: headers should include; Author, Status, Created Date
• Abstract: Detailed Summary
• Motivation
• Goal for Proposal
• Specification (technical details, if applicable);
• Proposed budget, anticipated fees and any other relevant forecasts
• Benefits
• Risks & Drawbacks
• Goal for Proposal

Proposals involving illegal activities, hate speech, or contradicting the DAO’s  mission or values will not be put forward for a vote.

How to deal with proposal conflicts?

To avoid conflicting proposals, if a proposed idea contradicts a proposal currently under consideration, the Council may withhold the second proposal from voting until a decision is reached on the first proposal.

If a proposal directly conflicts with an approved proposal, it should not be put forward for a vote for a period of three months following the implementation of the original proposal. This is put in place to minimize unnecessary expenditure of community resources.

Who can submit a Proposal?

A Proposal can be made on Snapshot by any EDU tokenholder who meets the proposal threshold of 1 EDU.

The holder verification requires the EDU to be held on on-chain wallets supported by Snapshot (i.e. MetaMask, WalletConnect, Coinbase, Portis, Stargazer, Kaikas) and out of CEX wallets.

Read here to understand the withdrawal process from Binance wallet: https://www.binance.com/en/fee/cryptoFee

How does a proposal get approved? 

A proposal will be approved during the Voting Period only if it achieves at least a simple majority of EDU tokens that casted a vote. In all other circumstances, the proposal will fail.

What is the voting process?

• Administrators post proposals to Snapshot after ensuring that each one has gone through the correct process.
• The voting for each proposal will be open for voting for 7 days (including the date that it was posted), closing on the 7th day. New proposals can be posted at any time as instructed by the Council. This is when the 7-day voting window opens as well. Following posting, an announcement will be made via the Open Campus Discord #governance channel. 
• EDU tokenholders vote on Snapshot. One EDU is equal to one vote. As votes cannot be divided into fractions and the total number of votes should not ever exceed the number of tokens minted, the number of votes will be rounded down if a fractional number of tokens is owned by the voter (i.e., 100.1 tokens will result in 100 votes, and so will 100.9 tokens).
• The voting options for a live proposal are “In favor” and “Against.” Voting “In favor” means the voter is in favor of implementing the proposal exactly as-is. Voting “Against” means the vote is against implementing the proposal exactly as-is — you may vote “Against” to encourage the author to resubmit the proposal after making changes.
• Proposals that receive a majority “In favor” vote are moved into implementation. Proposals that are rejected will have the chance to be resubmitted via the appropriate resubmission template if the author contacts an administrator to initiate this process. If by the vote close time, the live proposal has not gotten any votes or is tied, it will be tagged as “Stalled” and be eligible for resubmission.