# Scroll DAO Monthly Update — September, 2026 **URL:** \ **Category:** General\ **Tags:** monthly-update\ **Created:** [September 24, 2026, 3:27pm UTC](https://forum.scroll.io/t/scroll-dao-monthly-update-september-2026/1500 "2026-09-24T15:27:25Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Jane](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@Jane](https://forum.scroll.io/u/Jane)\ **Post date:** [September 24, 2026, 3:27pm UTC](https://forum.scroll.io/t/scroll-dao-monthly-update-september-2026/1500/1 "2026-09-24T15:27:25Z")
This month, we discussed Scroll’s consumer AI strategy, how Compass fits into that direction, and what the proposed changes could mean for the chain, SCR, USX, and the DAO. The chain transition and migration plans outlined below are still under discussion and will require further governance review. ## 1. Background Our 2026 priorities are to build products that reach users directly and drive more on-chain activity. We first explored AI as a way to improve operations, marketing, and business development. Through that work, we saw a larger opportunity in consumer-facing products. Compass is the first product to put this direction into practice, supported by an API that routes user requests to suitable AI models. Delegates asked why AI is the right focus and whether Scroll should prioritize RWA instead. We see potential in RWA, but our current focus is on problems the team has experienced first-hand and can address with its existing capabilities. ## 2. Compass: App and API **Compass App** Previously called PocketPal, Compass is an iOS app for digital nomads and travelers. It combines offline AI agents, eSIM purchases, and VPN services to help users navigate unfamiliar places and stay connected. The app is available on the App Store, and the team is currently promoting it through Instagram. **Compass API** Alongside the app, the team is developing an API that routes everyday tasks to suitable AI models at a lower cost. The planned design includes ZK-based verification and USX for payment settlement. Delegates asked how the API would compete with established services such as OpenRouter. We discussed our proprietary video models and efforts to source lower-cost models with comparable quality. ## 3. Proposed Chain and Token Changes To support this direction, the team outlined a proposed transition to a permissioned chain and the deployment of SCR and USX contracts on Ethereum mainnet. The mainnet deployment is intended to maintain transparency and liquidity as the role of the chain evolves. The intended token roles are: - **SCR:** Governance token for both the chain following the proposed transition and USX. - **USX:** Payment asset within Compass and a yield-generating stablecoin. SCR holders would govern USX parameters, including how yield is distributed among users, stakers, and the protocol. The indicative timeline discussed was: - **Mid-November–December 2026:** Deploy SCR and USX contracts on Ethereum mainnet. - **By the end of 2026:** Seek a governance vote on the proposed transition to a permissioned chain. - **Early 2027:** Target the chain transition, with migration details and timing subject to further review. These dates are not final. Delegates stressed that the migration will require careful planning and execution. ## 4. The DAO’s Role The proposed changes raise a broader question: what should the DAO be responsible for as Scroll’s direction evolves? Delegates pointed to limited recent proposal activity and asked how the new direction relates to earlier decentralization plans. The DAO’s future structure is still being developed, and we are asking delegates to help define its scope and decision-making responsibilities. A delegate suggested that the DAO could retain a role through periodic or optimistic voting, with SCR serving as the governance token for both the chain and USX. The distribution of USX yield was discussed as one concrete area for governance. ## 5. Next Steps Before the October call, the team will run an anonymous survey on DAO roles and governance responsibilities. The results will inform a draft DAO structure proposal for discussion at the next call. The team will also propose a new monthly call time to make participation easier across regions. Please share your views on the DAO’s future role and which decisions should go through governance. ---
**Author:** ![alexsotodigital](https://sea2.discourse-cdn.com/flex002/user_avatar/forum.scroll.io/alexsotodigital/32/325_2.png) [@alexsotodigital](https://forum.scroll.io/u/alexsotodigital)\ **Post date:** [September 28, 2026, 10:15pm UTC](https://forum.scroll.io/t/scroll-dao-monthly-update-september-2026/1500/2 "2026-09-28T22:15:07Z")
Hey @Jane. GM. After watching the call and reading the recap, I think I can articulate my concern more precisely. 🎯 Before we design new delegate roles or governance processes, **I think we first need to define the governance domain itself**. You mentioned during the call that “everything has to go through your decision / your vote.” Historically, that has not really been the case (and I don’t necessarily think it should be)… Foundation/Labs needs room to operate, but then we need a clear boundary: **what can Foundation/Labs decide autonomously, and what decisions are actually reserved for SCR governance?** Without that distinction, asking delegates to ‘help design the DAO’ puts us in a difficult loop. We can propose structures, roles, and processes (and some of us have done so before through things like [The Case for Holacracy as a Governance Model for Scroll](https://forum.scroll.io/t/the-case-for-holacracy-as-a-governance-model-for-scroll/1264), [the Support Squad pilot](https://forum.scroll.io/t/proposal-support-squad-pilot-weaver-scribe-model/1112?utm_source=chatgpt.com), [the DCP discussion around delegate roles](https://forum.scroll.io/t/rfc-the-role-of-delegates-in-delegate-contribution-program-dcp/1391?utm_source=chatgpt.com), etc.) but unless there is clarity about the authority those structures would actually have, we are designing mechanisms before knowing what they are supposed to govern. I also think there is a **communication and authority gap** between delegates and Foundation/Labs that needs to be addressed. I appreciate you (@Jane) taking a more active role as a bridge, but right now I honestly don’t know who delegates are supposed to engage with when a question requires an actual strategic commitment from Scroll. **I cannot even tag Raza on the forum** , and I am not clear on who has the authority to say: “Yes, Foundation/Labs commits to this.” If the people determining Scroll’s strategic direction are not part of the governance conversation, it is difficult to know whether these monthly calls are 1. spaces for genuine institutional co-design **or** 2. spaces where delegates brainstorm and provide feedback that Foundation/Labs can later choose whether or not to use. Both can be useful, but they are very different relationships. For example, Raza publicly posted **“[I killed Open Campus](https://x.com/razacodes/status/2095861549873410049?s=20)”** and explained the shift by saying that scroll had spent years building distribution for other founders and that “now we’re building it for ourselves” around something the team controls end-to-end. Scroll’s account [amplified that direction](https://x.com/Scroll_ZKP/status/2095564500472824041?s=20) as a shift toward “building around your own” incentives. If something that was presented as an ecosystem initiative could disappear or be fundamentally repurposed when the strategic thesis changed, then that makes it especially important to understand **what in the new Scroll is actually durable beyond the current decisions of Raza/Foundation/Labs, and what can be created, changed, rebranded, or sunset unilaterally.** > If the new Scroll can function successfully as a company building Compass + AI infrastructure, why does it need a DAO? For example, saying that the DAO could decide how USX yield is distributed may be a perfectly reasonable governance domain… but why is decentralizing that decision valuable compared with having the USX team define the policy? **This changes what being a ‘delegate’ means.** If the emerging model is closer to a company surrounded by a network of trusted, experienced contributors, that could also be legitimate. Delegates could potentially function as a kind of verified talent pool ([another initiative that fell through](https://forum.scroll.io/t/verified-delegates-cohort-1/1430)) that can take on scoped projects when Foundation/Labs needs governance research, ecosystem work, analytics, facilitation, communications, etc. But if that is the model, the relationship should be explicit: **what work is needed, who commissions it, what authority comes with it, and how is it compensated?** I am hesitant to enter another open-ended process where delegates are asked to “help figure out the DAO” without clarity on whether Foundation/Labs wants feedback, actual governance, or professional contributor work; and without knowing what commitment exists on the other side. So before another governance design exercise, these are the questions I would most like Foundation/Labs to answer 🙏 - What exactly belongs to the DAO’s governance domain? - What can Foundation/Labs decide, change, or sunset without DAO approval? - When the DAO votes, is that decision binding on Foundation/Labs or ultimately advisory? - Who has the authority to make commitments on behalf of Foundation/Labs in these conversations, and how can delegates communicate directly with them? - What specific contribution is expected from delegates beyond voting, and how will substantial contributor work be commissioned and compensated? _In a few words,_ I worry we will once again spend significant community time designing a governance system without knowing whether the organization behind Scroll is actually committed to operating within it. Peace out ✌ ---
**Author:** ![Jane](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@Jane](https://forum.scroll.io/u/Jane)\ **Post date:** [October 22, 2026, 11:53am UTC](https://forum.scroll.io/t/scroll-dao-monthly-update-september-2026/1500/3 "2026-10-22T11:53:15Z")
Thank you for taking the time to share such detailed feedback. I agree that we need to be clearer about the DAO’s role before designing new delegate roles or processes. When I said during the call that “everything has to go through your decision and your vote,” I was referring to parts of the proposed transition that directly affect SCR holders, such as the migration of SCR. These are not changes that the Foundation should decide and implement on its own. We need to explain the plan and its implications clearly, discuss them with delegates and SCR holders, and take them through the appropriate governance process. At this stage, I believe the immediate priority is to focus on execution and establish a stable operating foundation for Scroll’s next phase. The Foundation is responsible for operating the products and executing the strategy, including the roadmap and day-to-day work across Compass and the broader product stack. During this phase of strengthening our operational foundation, the DAO can gradually develop into a governance body that provides an additional layer of oversight and accountability for major decisions affecting SCR holders, while the Foundation remains responsible for product execution. I will continue to help connect delegates with the team. When a discussion requires an organizational decision or commitment, I will work internally to bring the relevant decision-maker into the conversation. My aim here is to clarify the order of priorities: focus on execution now, while continuing to use the appropriate governance process for decisions that directly affect SCR holders, and return to the broader DAO structure when Scroll is in a stronger position to define it well.