The team working at the core of the Scroll + RnDAO research effort is excited to share the results from our in-depth investigation into the realities and possibilities of builder support at Scroll.
This report reflects the result of background research and interviews with program managers and builders about how Scroll can support and grow its builder base in the future.
We invite you to review and comment on the existing document, which is being finalized based on feedback in the coming weeks. We will also do a short presentation of results in Wednesday’s governance calls.
Project Proposal: Proposal: Research to inform a builder support strategy
Research Report: Notion
6 Likes
Hi, @Mecherodsim !
to address your question on the call, could you elaborate what exactly you had problems with linking in the post? so i can edit it.
Hi @Mecherodsim ,
Thanks for the in-depth analysis! Where can I find the Google Slide that was shared during the last call to present the findings? The results are pretty extensive, so I’d like to get a high-level overview first before diving in. I really liked the slides too!
Well done RNDAO crew, thanks for sharing.
Q: Is there a PDF of this that I can read? I find it hard top digest notion content, thanks!
The research team will share the link soon but by the way, the report includes a TLDR
Thank you for the thorough report. I have some comments and questions for the DAO:
-
Builders and founders need to trust community and program managers. Therefore, local nodes are key to onboard more people to the Open Economy.
-
We need to have proper documentation that developers truly engage with it due to its usefulness. Do we have any metric of what’s the dev perception of Scroll’s documentation?
On that same line, every node should have that dev documentation available in their local node language, so to facilitate an engaging developer experience. At the Mx node we will work on this too. Perhaps it could be a shared effort between the upcoming Argentinan node and us.
-
Same question for our APIs and systems. Do we have a list of those? Do we have any metrics regarding the usefulness and trustworthiness of dev resources? ARe they useful to foster interoperability?
-
Besides each local node’s strategies. How will the DAO and Foundation assist local nodes in providing technical expertise? A dedicated office hour or channel for technical expertise to tap into could be useful for all.
-
How are the DAO and the local nodes targeting the 3 major stages that builders need support in?
Open Zero focuses on discovery and validation and sprints into product building; Campus targets product building and launching.
The Mx node is targeting those projects that already have a product at least in MVP. How about other local communities?
-
How clear is the perception of goals, processes, and priorities of Scroll to:
a) Delegates?
b) Builders?
c) Node managers?
-
Things that builders are looking for Builder support programs that include training and education, incubation and acceleration programs, grant programs, VC introductions, talent access. On that regard, the Mx local node is focusing on:
→ gathering available educational material to guide web2 builders into the most straightforward path to web3 so they can be reached by our builder program
→ incubation and acceleration program for projects with at least an MVP.
→ Introduction to key stakeholders who could lead to new clients, partnerships and investment.
It would be great to weave synergies between the upcoming Argentinan node and the Mx node to deliver an educational program (from existing resources) to channel all our Spanish-speaking community into.
-
When is the Grants program projected to be launched?
-
Local nodes are the human connection and support. We need to include in our reports the understanding of local needs so that future research and decisions are based on both the global and local understandings.
Our nodes should provide support on Business challenges (legal and marketing that need local context) and on Distribution and Credibility (access to vertical-specific customers and partners, as well as marketing amplification and brand endorsement.
-
Post-funding continuity. The Mx local node is launching a Founder’s Circle where founders gather to share their insights and knowledge as well as support each other to reach their goals. That’s part of our community building strategy for long-term trust, engagement, and growth.
-
Regarding the weaknesses perceived of Scroll:
- Limited regional communication. The ES account will surely have a lot to share in the upcoming weeks with the nodes producing lots of updates and activities. We are glad that we can help this weakness become a strength.
- ThirdWeb has smart accounts that are available with zK through zKSync. Their docs say they support Scroll.
Do we have a list of providers that offer their services to the Scroll chain? Do we have a list of those who don’t but we want to? Local nodes coud help in BD.
- Things we can re-strategyze at the Mx local node for the next cohorts:
- Connection to investors
- Double down on tech support
- Organize and co-host educational programs with local communities where validation of products ideas that are native to Scroll can emerge.
- Find the verticals that are hot in MX so to focus on finding resources (Investors, Clients, Partners)
3 Likes
Thanks for sharing the results, congrats on the finished report. The notion page is a really nice overview.
I’d suggest now it’s important the research is taken into account for future initiatives, maybe this would be a good resource for the upcoming growth and community council?
1 Like