Community-Funded Project Flow
For Clubs, Projects, and Working Groups.
Used when a member proposes a long-term, team-based initiative that requires funding. These efforts are typically ongoing, involve multiple contributors, and focus on building or maintaining specific community run parts of the DAO’s ecosystem.
Proposal Review Process
1. Submit to Core Team All project proposals must be submitted using the DAO’s official form: 🔗 Submit Project Proposal
Include:
Requested budget (Sets the scale and feasibility of the project)
How it supports the DAO’s mission (Demonstrates strategic alignment and value)
Project goals and overview (Provides a clear description of what the project aims to achieve)
Expected team size and roles (Outlines the human resources needed to execute the project)
Simple roadmap with milestones (Lays out the plan for reaching key objectives)
✅ If complete and aligned: Moves to Core Team vetting 🔁 If incomplete: Sent back with notes ❌ If misaligned or not viable: Rejected
2. Core Team Vetting The Core Team reviews the proposal for clarity, alignment, and feasibility.
If approved, the proposal is added to the public board (if not already visible) and prepped for vote
✅ If approved: Moves to vote and veto window 🔁 If edits are needed: Sent back to proposer
3. Core Team Vote + Community Veto (Simultaneous)
The Core Team creates the proposal and votes on Realms.
Community veto window opens at the same time (66% required to block)
Community members may leave comments during the voting period
Funding
If approved, any allocated funds are sent to a separate wallet in Realms, where they await Core Team approval for deployment once terms are finalized.
If the Core Team determines the proposing team or team lead is ready, Phase 1 funding can be deployed immediately as part of the initial proposal. This covers the first stage of execution and milestone work.
✅ If passed and no veto: Proceed ❌ If vetoed or rejected: Proposal is closed 🔁 A revised version may be submitted as a new proposal and must go through Core Team vetting again
4. Finalize Terms
The budget, timeline, milestones, and check-in expectations are finalized in coordination with the Core Team before the project moves into execution.
✅ Once finalized: Project moves into execution
Execution Process
Recruit Team The project lead assembles a team to carry out the roadmap.
Any member who hasn’t already must complete the DAO Contributor Form: 🔗 Submit Contributor Form
The Core Team must approve the final team before funding is released
⏸️ If team is incomplete or not approved: Project is paused until updated
Deploy Phase 1 Funding The first round of funds is released based on the agreed-upon roadmap and milestone structure.
Check-ins Progress updates required
❗ If off-track: Funding paused or project ended
Weekly Sync Updates
Project leads, a selected team member, or the overseeing Core Team member must post brief weekly updates in the 🔄┃weekly-sync forum. These serve as transparent reports to the community and should reflect information that can be shared publicly.
Suggested format:
Wins – What got done
Progress – Current tasks and milestone movement
Blockers – Any delays or issues
Notes (Optional) – Anything else worth sharing
No major updates? That’s okay! Still post a quick check-in. You can share what you're waiting on, any blockers, or simply confirm that you're on track. Even short updates help fulfill transparency requirements.
Projects that go off-track, exceed their budget, or fail to report in a clear and transparent way may be paused, marked inactive, or lose future funding.
Last updated