SOS and MVP
Viewing this alongside the OpCo proposal, this appears to be part of a broader template for streamlining proposals that feed into the OpCo entity under strict timelines. This makes sense and seems like the natural maturation of the DAO. That said, some initiatives are short-term sprints with urgent timelines. How does the SOS framework plan to handle these?
This may be an edge case given the existing grant groups and events budget which likely address most immediate decision-making and spending. However, in case I’m wrong, how can we ensure agility/flexibility from this system? This is likely a conversation for the SOS, once that proposal is posted.
Competition
The technology focus of Arbitrum is exactly what’s needed here. Arbitrum’s product is its network, applications, and tech-suite that’s powered by decentralization and scalability. Furthering itself in this domain will naturally allow it to win against competitors. Earlier in this discussion, others noted that the proposal could benefit from stronger language on Arbitrum’s unique identity. Building on that point, I think the proposal needs to address the competitive landscape more directly.
The MVP does touch on Arbitrum becoming the default option for applications and developers, though it’s possible that a more direct focus on competition would help frame Arbitrum’s unique value proposition. The L2 ecosystem is dominated by a few players, and there are other DAOs with the resources to compete even if they lack mindshare. It’s important for the DAO to recognize that, and articulate where Arbitrum will lead and how it will continue to compete. As many delegates have stated already, they’re concerned about the DAO’s ability to be agile and flexible in times of need. This competitive language may be what the proposal needs to signal that the DAO will still retain the ability to be flexible in response to a competitive market.
The rollup ecosystem is not just a vague collection of networks sharing the market; rather, these rollups are actively competing with one another. I agree with @L2Beat’s points that there are overlooked areas the DAO should start exploring. For example, with this Arbitrum-specific view, it might be time to start looking into getting Arbitrum-specific assets or Arbitrum-specific onramps rather than relying on competitors (like Coinbase) who will likely be preferential to their own rollups moving forward. Part of a mission statement is the acknowledgement of competition, and gaining a competitive mindset. It may be time for Arbitrum to clearly articulate its competitive stance, as this perspective could influence how funding initiatives are prioritized in the future. Acknowledging competition means that the DAO would become less frivolous with spending and actually award true winners in select vectors to win in its own market as a rollup.
Token
Finally, I think that there is a missing component to many of the recent conversations on Arbitrum: the ARB token. The token plays an integral role in the governance of the network, and so it stands to reason that there should be some additional mention of it within the mission statement. While it can be argued that defending Arbitrum means defending the ARB token, this connection isn’t obvious. This isn’t to suggest the token should dominate the DAO’s focus, but it deserves a clear mention in the mission statement.
TLDR; Overall, I think the proposal could benefit from stronger competitive language and a clearer mention of the ARB token, but we’re in support.
Concluding thoughts: Blockworks Advisory will be voting FOR this proposal on Snapshot.