Co-Creation Cycle

Why Co-Creation?

Starting with a Co-Creation Cycle will provide everyone in the community with an opportunity to hear from those who have been building Scroll for the last few years, to lay out a vision of what we can accomplish together in the coming months, to onboard a wider community into the DAO, and to make sure there is a process to co-design our first steps towards a decentralized future.

Overview of the First Co-Creation Cycle

To effectively prioritize our growth and execution efforts, we have established four key priorities. Each priority focuses on a critical aspect of Scroll’s mission and provides structured guidance for achieving our goals. For each priority, we are including a point of focus, some guiding questions, and the desired outcomes that we hope to see following the co-creation period.

Priorities

The priorities are as follows:

  1. Ecosystem Growth (Growth)
    1. Focus: Identify what is driving growth across various protocols and projects, as well as what is currently under-explored that can help drive growth and innovation on Scroll.
    2. Guiding Questions: What unique strategies or projects can Scroll pursue that no one else is currently doing? What initiatives are others implementing that could benefit Scroll?
    3. Desired Outcomes:
      1. To have at least one grant program clearly defined that can be launched in the coming months,
      2. To have a ‘program of programs’ model outlined for how we will select subsequent grant programs, and
      3. To have a plan for tooling and data infrastructure to enable output, outcome, and impact evaluations.
  2. Global Community (Community)
    1. Focus: Determine where to direct resources and efforts globally to maximize impact and support local communities effectively.
    2. Guiding Questions: What is the best method for identifying which regions to prioritize? How can the DAO best support and empower local communities within these regions? How can we create a cohesive community of communities, ranging from local to global?
    3. Desired Outcomes: Source specific areas (at the level of a city or region) for community efforts to fund and/or to have an initial ‘community of communities’ strategy for the DAO and Foundation to pursue.
  3. Governance Iterations (GovIt)
    1. Focus: Address the most pressing challenges in governance and test cutting-edge approaches to improve decision-making processes and effective coordination.
    2. Guiding Questions: What are the biggest problems in current governance models? What experiments should we conduct to test new governance structures and methods?
    3. Desired Outcomes: Define specific questions or problem statements the community wants to have researched and/or source ideas for governance experiments for the Scroll ecosystem to explore in more detail.
  4. Further Explorations (Exploration)
    1. Focus: Provide a space for the community to suggest and explore areas that we might not be currently prioritizing, ensuring the community has a say in the overall direction of the DAO and protocol.
    2. Guiding Questions: What crucial aspects are missing from our current priorities or from web3 as a whole? What specific issues need addressing and what solutions can we explore?
      1. Desired Outcomes: Creating a feedback mechanism where the community can propose adjustments to existing priorities or to set new priorities altogether.

The first three priorities are the focus of the co-creation activities that will run for 7 weeks, while the fourth is meant to start a focused feedback loop from the community to the Foundation to help drive future priorities.

Commencing Co-Creation

While the Foundation team has laid out the aforementioned initial priorities, the goal is to both co-create the strategies to enact these (Growth, Community, GovIt) with the community, as well as to create the mechanism (Explorations) for how the DAO can propose new priority domain areas. You can think of the effort over these 7 weeks as an idea-and-proposal-oriented hackathon (no coding necessary).

The rough flow will be as follows:

  • Week 1 - Context setting
  • Week 2 - Sourcing initial ideas
  • Week 3 & 4 - Voting on community ideas (adding a week due to Devcon)
  • Week 5 - Proposal submissions
  • Week 6 - Reflection and refining
  • Week 7 - Voting on the initial proposals

This flow will apply to the first three priority areas (Growth, Community, GovIt). We are also keen to hear ideas on the Exploration front and will have both calls and forum threads relating to it, though we will let the cadence of voting emerge naturally for this priority area.

Desired Outcomes

The desired outcomes as outlined are meant to be something the community can specific hold us accountable for as far as the results of the 6 weeks of co-creation go. Let’s dive into each outcome in a bit more detail.

Growth

Have at least one grant program clearly defined that can be launched by the end of 2024.

  • We are very keen to seed and support a plurality of grant programs over time. Instead of the Foundation running a single grant program to fund everything from local meetups, to hackathons, to the development of new apps, to web3 public goods, to research, we want to have a series of programs that are each specialized. We are calling this a ‘program of programs’ model. While who specifically manages each program may vary, the Foundation will create some form of coordination amongst the various grant programs and will create shared infrastructure for tracking outputs, outcomes, and eventual impact.
  • The first grant program in the ecosystem is likely to be one that is managed by the Foundation itself. As such, we want input from the community on what topic(s) to fund from the get go. Successful proposals will address: what to fund, what kind of outputs get created as a result of the funding, what outcomes are generated as a result of the outputs existing, and an initial timeline for the pilot phase.
  • The Foundation is also open to working with community members and/or third-parties to run specialized grant programs. Successful proposals will address: what to fund, what kind of outputs get created as a result of the funding, what outcomes are generated as a result of the outputs existing, who will run the program, an initial budget, any additional success metrics that can help the community assess the efficacy of the program, and an initial timeline for the pilot phase.
  • Finally, successful proposals can also focus on:
    • The nature of required coordination and share infrastructure that can make for a successful pluralistic program of programs.
    • The tooling and data infrastructure required to meaningfully track outputs and to measure outcomes and impacts.

Community

Source specific areas (at the level of a city or region) for community efforts to fund and/or an initial ‘community of communities’ strategy for the DAO and Foundation to pursue.

  • Scroll is deeply committed to ensuring that our tech is accessible to as many people as possible and that our community is representative of global populations. As such, we will be introducing a system to have city and region specific pitches that the DAO will be able to vote on.
  • We hope to see at least one proposal from each continent (well, most continents - not sure if any scientists or penguins are running ETHAntartica). Particular emphasis will be placed on areas that are often underrepresented in web3.
  • We are specifically looking to learn more about which cities and regions around the world have groups of interested individuals, relevant use cases, and/or technical talent to build on top of Scroll.
  • Successful proposals can come from from well-established community organizations that have a track record of activities, as well as from newly formed groups that are building off of burgeoning interest. Activities, both existing and desired, can include but are not limited to:
    • Hackathons
    • Meetups or conferences
    • Educational efforts
    • Bridges from web2 to web3
    • Interest from local universities (professors or students)
  • Successful proposals will either focus on proposing specific activities, or will focus on outlining a community strategy for the Foundation to enact, or will focus on outlining what a Community Committee could look like in terms of focus, budget, and metrics to measure its success.

Governance Iteration (GovIt)

Define specific questions or problem statements the community wants to have researched and/or source ideas for governance experiments for the Scroll ecosystem to explore in more detail.

  • The Foundation team is eager to both directly research certain problems and to fund research projects that touch on the core challenges faced in governance within web3 and in digital communities broadly. To do this, we first need to source the problems that seem most pressing to community members and DAO practitioners across the space.
  • The research questions or problem statements that are sourced will help inform both the Foundation’s research agenda as well as potential topics that we issue grants for. These questions ideally build off of existing research (e.g. DAO Science) and will have clear and concise areas of exploration. These questions will also seed a running list of governance challenges, which we hope will help increase coordination across web3 ecosystems dedicating resources to advancing governance.
  • We are also interested in hearing ideas of specific governance experiments. What governance tools do you want to see the Foundation or DAO utilize? In what contexts?
  • Successful proposals will outline research agendas or will center around concrete governance experiments that the DAO and Foundation can implement.

Overview of Initial Proposals

Genesis Proposal

The first proposals of the DAO will be focused on the results of the Co-Creation Cycle. Some of the desired outcomes of the cycle are outlined below.

We hope to see at least one proposal emerge on a focused grant program (resulting from the Growth priority) that the DAO will vote on. Alternatively, a proposal on a program of programs model or on tooling and data infrastructure may be be voted on first.

We hope to see a series of proposals emerge in terms of community efforts to fund (resulting from the Community priority). Alternatively, a proposal outlining a community of communities model or articulating what a Community Committee can look like may be voted on first.

There may be at least one proposal emerging from the GovIt track on a focused governance experiment, though there is a chance that track mainly outputs problem statements as opposed to proposals to vote on.

Similarly, the Experimentations priority may not produce a voteable proposal during the co-creation phase and that is ok. If a strong proposal does emerge for a new priority, then it will be voted on as well.

Measuring Success

For each of the priorities, we want to outline some initial success metrics we will evaluate during Co-Creation Cycle #1.

Growth

  • Is there at least one Growth proposal that the DAO at large, delegates, and the Foundation team are excited about? (subjective - can be social ratification or treasury allocation)
  • Is there at least one proposal defining grant program or a program of programs strategy or a tooling and data infrastructure strategy? (quantitative)
  • Attendance of relevant calls (quantitative)
  • Engagement, primarily but not exclusive to the forum (quantitative)

Community

  • Is there at least one Community proposal that the DAO at large, delegates, and the Foundation team are excited about? (subjective - can be social ratification or treasury allocation)
  • Is there at least one proposal defining a community program or a community of communities strategy? (quantitative)
  • Attendance of relevant calls (quantitative)
  • Engagement, primarily but not exclusive to the forum (quantitative)

GovIt

  • Is there at least one GovIt proposal that the DAO at large, delegates, and the Foundation team are excited about? (subjective - can be social ratification or treasury allocation)
  • Is there at least one proposal outlining a list of questions to explore or proposing a concrete experiment to run? (quantitative)
  • Attendance of relevant calls (quantitative)
  • Engagement, primarily but not exclusive to the forum (quantitative)

Explorations

  • Is there any awareness of and engagement with the initial feedback mechanisms (calls and a dedicated forum post)? (quantitative and subjective)

Event & Calendar Outline Through December 2024

Scroll Foundation team is planning to host a series of calls throughout the first 6 weeks of co-creation. The calls will range from two 60-minute calls to three 90-minute facilitated sessions, hosted across multiple timezones.

For more information the exact schedule, refer to our Governance Calendar.

Week 1 - Context Setting, week of Oct 28th, 2024

  • Kick off / intro call (or twitter space) - Mon morning
  • Two 60-minute calls featuring other Scrollers, each with some context setting at the start of each - Tue morning and night. These will provide context in what we’ve already done and where we want to go

Weeks 2 & 3 - Sourcing Ideas, week of Nov 4th, 2024 & Nov 11th, 2024

  • Three 90-minute ideation, gathering general ideas with each call being focused on one of the three priorities. Each call is done in a different timezone
  • Sourcing of ideas

Week 4 - Voting on Ideas, week of Nov 18th, 2024

  • Two 60-minute calls to review the ideas that came up and address any questions
  • Voting happens in first half of the week
  • One 60-minute call to digest results

Week 5 - Sourcing Proposals, week of Nov 25th, 2024

  • Three 90-minute calls workshopping various ideas and proposals, scheduled across timezones
  • Proposals due Sunday December 1 at 23:59 UTC

Week 6 - Reflection & Refining, week of Dec 2nd, 2024

  • Four 60-minute calls to review proposals and give folks a chance to refine them before having a vote
  • Proposals due

Week 7 - Voting, Week of Dec 8th, 2024

  • Voting happens
  • Two 60-minute calls go over the results and next steps

Week of Dec 15th, 2024 onwards

  • Two weekly calls going forward across two timezones as the baseline interaction until more is added
  • Propose gov calendar through January at least, ideally through Q1 at least

What's Next