I’ve been following the Ecosystem Growth Council updates closely, and I appreciate the clarity around defining the four focus areas. However, I believe we now have an opportunity to turn these categories into a true long-term roadmap.
At the moment, the focus areas are directional, but they are not yet strategic in the operational sense. There is no indication of how long these priorities will remain in place, how heavily each one should be supported relative to the others, or how different councils should sequence execution over time. Without defined time horizons or allocation weightings, STRATEGY risks becoming intention rather than governance making it hard for founders to plan, and equally hard for councils to be evaluated on outcomes.
To solve this, I propose that Scroll converts the current focus areas into a three-to-five-year strategic plan, where each year includes a deliberate distribution of support across the verticals. For example, in the early phase, builder and founder support could intentionally receive the largest share: something in the 30–35% range, to rapidly widen the pipeline of teams building on Scroll. Liquidity and economic infrastructure could then scale progressively from around 25% in Year 1 toward 30–35% in later years as ecosystem activity increases. Community and local ecosystem growth could hold steady at roughly 20% across cycles to maintain grassroots expansion, while user retention and growth experiments remain a consistent 15% to drive recurring engagement. A small reserve perhaps 5% each cycle would remain flexible for emergent opportunities.
The exact numbers are less important than the structure. The goal is not to lock the DAO into rigid spending targets, but to define a long-term intention that councils execute against rather than reinterpret each term. Annual reviews could still adjust the weightings based on performance, or trends, but without deviating from the agreed long-term direction.
This kind of framework is how other ecosystems achieve sustained compounding impact: define the mission for years, then optimize execution annually.
If this direction aligns with where Scroll intends to go, I’m happy to formalize it further or collaborate with others on a draft that could be tested via community signaling.