1. Which goals does the strategy look to drive progress in?

Foster vibrant ecosystem (Goal 1): SafeDAO benefits from a vibrant ecosystem built on shared components and standards. SafeDAO supports and empowers new and existing projects integrating with the Safe Protocol or initiatives supporting the usage of Safe Protocol.

2. Which metrics and KPIs could initiatives under this strategy be measured against?

Disclaimer: KPIs should always be considered in relation to each other and not in isolation. For instance, the number of modules developed should be evaluated in conjunction with their quality. We would always prefer two high-quality contributions over five low-quality ones.

• Quality level of proposed modules (via individual assessment)
• Usage of modules, e.g. value driven through modules / transaction volume / number activation / percentage of Safes with modules activated
• Integration of modules (actual traction and individually assessed via former cases/benchmarks)
• Developer satisfaction score (for improvements, via rating mechanism)

3. Outline the execution strategy or thesis

Developers are encouraged to create new modules focusing on new use cases, robust implementation, and thorough auditing. Creation of libraries and further developer tooling. Execution should have a strong emphasis on boosting the security of the module ecosystem, possibly through sponsored auditing. Prioritizing the development of Safe modules is crucial for the ecosystem’s growth, as it enhances Safe’s core functionality and drives onchain compatibility. For non-module-related development efforts, there is an alternative source of funding through the SAFE grants program.

4. What are some example initiatives that would fall under this strategy

• Creating new modules, e.g. recovery module, passkeys, security guard
• Make existing modules more accessible for developers and end users
• Porting existing modules

5. Detail around existing data or evidence to support this thesis

The Zodiac toolkit by Gnosis Guild is utilized by 239 entities, and has 19 active GitHub contributors, indicating its significant engagement and adoption

6. Detail around any risks associated with this strategy

• Curation and quality control: Risk of subpar module development without proper quality control
• Discovery problem and fragmentation

7. If this strategy succeeds, what is the happy case?