# How to create a teaDAO proposal One of the governance goals is to foster a sense of engagement between the community and the ***tea*** protocol. It should be up to the entire communi’tea, to work together, to carry ***tea*** forward, ensuring it is resilient for developers, sustainable for open-source maintainers, and useful to all other users. ## Who can make proposals? Anyone with a ***tea*** protocol account can submit ideas, and proposals, respond to posts, and provide feedback on the Governance Forum. ## How is voting power determined? stTEA is used to determine a project’s voting power. This implies that a project needs to possess staked TEA either through delegation or staking to be eligible to participate in the governance process. ## Step-by-step guide to creating a DAO proposal 1. **Find an opportunity:** The first and most important step is identifying ways the protocol can be improved. For example, say you want to improve the project registration workflow that requires you to commit your project’s constitution file manually, potentially allowing bad actors to open pull requests trying to claim your project as their own. You could create a proposal to automate this process or modify it to prevent bad actors from claiming your projects as their own. 2. **Draft a proposal:** After identifying an opportunity, draft a detailed proposal outlining the problem, your solution, and the potential benefits. Be sure to include any data or research that supports your idea. This can be done using the template provided [here](https://docs.google.com/document/d/1z3lQ3vGpkZjronPrZquq8bhVPBot29K33U3nQBxPAzg/edit?usp=sharing). Always remember to add \[DRAFT] to your proposal’s title and the `draft` tag to your proposal. 3. **Community discussion**: After drafting your proposal, share it with the community via [discord](https://discord.tea.xyz/) or [X](https://twitter.com/teaprotocol) for discussion. This is a critical step as it allows for feedback, questions, and potential improvements to your proposal. The discussion phase is open-ended and continues until a clear consensus or the proposal is withdrawn. 4. **Iteration**: Review the community's feedback and implement the recommendations that improve your proposal and align with its goals. 5. **Submitting for mod review**: You’re getting close. In this step, all you need to do is change the \[DRAFT] in your proposal’s title to \[REVIEW] and add the `review` tag. 6. **Mod review**: Mods will review the \[REVIEW] proposals to see that they are within the power of DAO and meet the requirements such as matching up with the template , having quality community engagement, etc. 7. **Getting on-chain**: Proposals that pass will be created into formal votes on-chain by mods. ## Timeline of a DAO proposal ### On Testnet * Week 1 is for Proposals * During this time, if a Proposer feels like their proposal is ready for a vote, they can append \[REVIEW] to the start of their proposal’s title * Week 2/Monday, the moderator will start a Thread called “*REVIEW Proposals — Cycle {n}*” in the [forum](https://forum.tea.xyz), with links to all the proposals marked as \[REVIEW] * The Moderator can also start their review now, and post basic template fixes, or more concerted feedback on the individual Proposals, that need to be fixed for the Proposal to be considered in the Voting Round. If those notes are not incorporated, the Vote will not be considered. * Week 2/Tuesday, the deadline for new submissions is closed. * The Moderator will review all the proposals in the *Roundup* thread for completeness, and update the Thread with the Proposals that will be moving for a Vote * Proposers whose proposals were not included can expect the moderator to outline why their proposal was not included in this cycle’s Voting Period. Proposers ***must*** update their Proposal to \[DRAFT]. * The Moderator will create an on-chain vote for all Proposals by the end of the next 5 days. Which can be viewed in the [forum](https://forum.tea.xyz) or the [app](https://app.tea.xyz). * The following 5 days are used for voting, and all \[VOTE] proposals can be voted on [app.tea.xyz](https://app.tea.xyz). * While this is ongoing, community members can still participate in Discourse Proposals. * At the end of the 5 days, voting closes, and the results of the votes are handed off to the ***tea*** Association for enactment. ### On Mainnet A ***week*** in the context of Governance is defined from Wednesday 19:00 UTC — Tuesday 19:00 UTC the next week. On mainnet, * The first 3 weeks will be reserved for the submission of Proposals * During this time, if a Proposer believes their proposal is ready for a vote, they can append \[REVIEW] to the start of their proposal’s title * Week 3/Monday, the moderator will start a Thread called “*REVIEW Proposals — Cycle {n}*” in the [forum](https://forum.tea.xyz), with links to all the proposals marked as \[REVIEW] * The Moderator can also start their review now, and post basic template fixes, or more concerted feedback on the individual Proposals, that need to be fixed for the Proposal to be considered in the Voting Round. If those notes are not incorporated, the Vote will not be considered. * Week 3/Tuesday, the deadline is closed. * The Moderator will review all the proposals in the *Roundup* thread for completeness, and update the Thread with the Proposals that will be moving for a Vote * Proposers whose proposals were not included can expect the moderator to outline why their proposal was not included in this cycle’s Voting Period. They ***must*** update their Proposal to \[DRAFT]*.* * The Moderator will create on-chain votes for all Proposals by the start of Week 4. Which can be viewed in the [forum](https://forum.tea.xyz) or the [app](https://app.tea.xyz). * Week 4 is used for Voting, and all \[VOTE] proposals can be voted on via [app.tea.xyz](https://app.tea.xyz). * While this is ongoing, community members can still participate in Discourse Proposals. * At the end of Week 4, voting closes, and the results of the votes are handed off to the ***tea*** Association for enactment.