The purpose of this proposal, to be separate from Co-Creation Sprint - Delegation Discussion Thread is to summary the discussion about the roles of delegates into a concrete proposal, therefore when the OC / AC committees form, they can use these key findings from delegates as a consideration.
Shout-out to @alexsotodigital for the feedback and for initiating the idea of Support Squad which now has become part of the Delegate Contribution Program (DCP).
After analyzing delegate feedback from the Miro board, we came up with 4 Strategic Pillars that align with the goals Scroll aims to achieve in this phase, which mainly focus on price performance and increasing volume.
The Strategic Pillars include:
-
Ecosystem Vitality (Onchain Growth & Liquidity)
-
Network Resilience & Security
-
Data Transparency & Open Analytics
-
SCR Token Utility & Economic Flywheel
There were originally 11 roles in total. However, from the meaningful feedback from delegates, there is broad agreement that the role of delegates needs to evolve in the DCP to be more than just voting or providing rationale and feedback, and that there should be clear delegate responsibility for each role, aligned with Scroll, to ensure the work actually moves Scroll forward.
Following the feedback “Fewer roles, but better defined,” adjustments were made by using a 2-system model as suggested by Alex, resulting in 8 roles in total. A poll was then created to answer:
Which specialized roles do delegates feel are most critical to launch first in the Delegate Contribution Program?
From the result of 4 people who voted, delegates ranked Program Coordinator as the highest priority role for Scroll.
Final Ranking (Highest → Lowest Priority)
| Rank | Role | Avg priority score |
|---|---|---|
| 1 | Program Coordinator | 2.0 |
| 2 | Biz-Dev | 4.0 |
| 3 | Scribe | 4.5 |
| 4 | Content | 4.75 |
| 5 | Growth | 4.75 |
| 6 | Analyst | 5.0 |
| 7 | Weaver | 5.0 |
| 8 | Community | 6.0 |
We do think the sample size is still too small to jump to a strong conclusion about which roles are the most critical. However, it does show that delegates generally agree on this set of roles.
We believe the next step is to run an experiment, where at least one delegate contributes to each role for two months, and explore the actual workload involved. This would help determine whether we should:
a) stop the role,
b) continue the role as is, or
c) add more people to that role.
Running this experiment would raise several open questions for the DAO:
-
How can we measure the impact of contributions in a fair and consistent way?
-
What are the expected time commitment, duration, and capacity requirements for each role (e.g., hours per week, commitment period, and number of delegates per role)?
-
What eligibility and role-allocation rules should apply (e.g., verification requirements and whether a delegate can assume multiple roles)?
-
What accountability mechanisms should exist if a delegate fails to fulfill the responsibilities of a role?