OBJECTIVE:
Create a decentralized Rewards System for $CODE for all contributors of Developer DAO with the goal of creating synergy between Guilds and Projects, and fostering the following characteristics:
–Open and transparent
–Should encourage consistent contributions
–Should allow flexibility to the contributors
–Should enable ownership
–Should be sustainable
REQUIREMENTS:
A Tokenomics Team should be assembled to maintain and improve the Rewards System.
The initial proposal is that Guild Leaders and Ops Team can assume this function, and work to create an independent group before the end of Season 1. The goal should be ensuring the core characteristics are maintained, and the following actions are considered:
- It will design rewards of $CODE with inclusive collaboration as a core value: This means testing rewards for accessibility, diversity, teamwork, and mutual generosity.
- It will review rewards regularly: In Season 1 this should be done monthly. Later a seasonal review probably would be enough.
- It will keep it simple: Making reward recommendations easily understandable by contributors helps them focus on what the DAO needs. Complex rewards lead to “hacks”.
- It will calibrate rewards to reasonable levels.
TASKS TO BE REWARDED WITH $CODE:
–Community Operations: Participation in leadership roles in Guilds and Projects and any other official DAO role.
–Project Tasks Completed.
–Bounties (to be designed and updated by Tokenomics Team)
TASKS REWARDED WITH OTHER FORMS:
–Assistance to Town Halls, and conferences (POAPs)
–Voting (POAPs)
TASKS NOT TO BE REWARDED:
–Assistance to regular meetings
–Proposal Creation and/or Development
REWARD TYPES:
–Fixed: Monthly rewards of $CODE allocated to contributors according to a predefined amount by Tokenomics Team. Generally used to reward non-quantifiable and/or permanent contributions done by DAO officials.
–Project allocation: Defined by the Flow of Rewards (below)
–Project Profits: Earnings in completed projects with a profit will be split 50/50 with the DAO and the team.
–Unique Rewards: Rewards allocated by participation in Bounties, Hackathons, contests and similar events.
–Other Rewards: Tokenomics Team is encouraged to create and support other types of rewards.
FLOW OF REWARDS:
-
The Tokenomics Team will have the responsibility to define a total budget of $CODE to spend for the complete Season. This should take into account:
–Obligations acquired by Ops Team, Tokenomics Team, and approved DDIPs.
–Fixed allocations of previously approved DDIPs.
–Guild Operations -
The allocation of $CODE for Guild Operations will be split evenly between all Guilds, and sent to each Guild Treasure.
(ALTERNATIVE: Allocation for Guild Operations will be based on the number of projects each Guild has under its umbrella) -
Each Guild would need at least 3 members in charge of the Treasure to be able to receive $CODE.
-
Each Guild would be able to decide on its own how to allocate $CODE to each project, based on the opinions and vote of its members.
-
Each Project would decide how to allocate $CODE to its members based on tasks completed.
PROJECT OBLIGATIONS:
For Projects to be able to be considered in the allocations of $CODE by the Guild, they need the following:
–Should have a defined Champion(s) and defined allegiance to one Guild
–Should have a defined roadmap and deliverables approved by the Guild.
–Should have regular meetings
–Should have 3 defined KPIs at the beginning of the Season, approved by leaders of the Guild.
–Should be on compliance in at least one KPI