Monthly Initiative Update:

• Summary of Achievements:
  • Updated the module templates and documentation with a tutorial for ERC-7579 modules (https://docs.zenguard.xyz/getting-started/building-7579-validator) for developers with a demo guide. This is currently being reviewed by Rhinestone and Safe - Product. Rhinestone will push it to the official 7579 spec site.
  • Added two more modules using the 7579 standard to our module collection. We are also tracking the module list here.
  • We have made progress in setting up workshops at two universities and one community, Hyderabad DAO, to introduce the developed modules and onboard developers. We have also proposed an additional talk on modular smart accounts using Safe.
  • Collaborated with a few projects on module development and onboarding (Coinshift, HQ, and QuestBook). We are tracking all demos, developer onboarding, and module development progress here: https://notes.zenguard.xyz/module-development.
  • Updated the audit dashboard, registry, and module template to support the 7579 standard (https://github.com/zenguardxyz/module-template-7579/tree/feature/registry-support).
    • Demo of the updated audit dashboard flow for 7579 modules: https://youtu.be/A7qqQ1nXi74.
  • Updated the docs for module auditing based on 7579 and circulated the demo to auditors. We are tracking the module auditor onboarding here: https://notes.zenguard.xyz/module-auditors.
  • As part of Safe {Wallet} user adoption (M3), we have deployed one module app on the mainnet (Base), with the rest tracked on the Sepolia testnet. Demos of Safe App modules for the Safe user community are being circulated here: (https://www.notion.so/zenguardxyz/ZenGuard-Modules-438d1daeb29f468d9e2d33ba4c039c26).
  • We are currently working to get user adoption in the Base community through the Safe Faucet Module as part of the Onchain Summer Buildathon by June 30.
  • As part of milestone 4, we are working with Coinshift and QuestBook to build and provide APIs and leverage the Safe {Core} SDK to interact with the modules on existing and new Safes.
    • Coinshift use case
    • QuestBook use case
• Milestones Reached:
  • Milestone 1: * Completed based on the proposed revised scope for M1.
  • Milestone 2: Made progress on more auditor reachouts and audit dashboard updates for new module standards.
  • Milestone 3: Made progress on the module App deployments, local and builder TG community reachouts for adoption.
  • Milestone 4: Made progress in working with a few projects to understand the usecases and API requirements to integrate the modules in their existing infra.
• Challenges/Blockers Faced:
  • We have proposed a rescope for milestone 1 based on the previous reported challenges and blockers.
  • For M2, Our module auditing interaction with auditors is affected by the external audit timeline for the Safe 7579 adapter and regular updates to the codebase.
  • Note: For M3, we are yet to publish a dune analytics dashboard or other ways to track all the user onboarding, and transactions on modules since we deployed the apps.

Milestone Progress Snapshot [%]:

Provide a snapshot of progress for each milestone as of end of reporting period; May 31, 2024.

*Targeted completion % is derived from the proposal timeline, understanding that some milestones may have been blocked from progression for valid reasons. These blockers are reflected in our reporting sheets.

Follow-Up Details

On explaining the size of rescoping for Milestone 1 as it pertains to developer onboarding…

1. The timeline to complete the initial onboarding to introduce devs to the onboarding docs while simultaneously upgrading the module standard was small.
2. Introducing the Safe ecosystem documentation and new modular standards, along with the necessary infrastructure, took longer to collaborate with new developers than we initially anticipated. This was a key factor we underestimated when scoping the project at the beginning.
3. We also focused on internal development of module and working with projects rather than independent devs to add quality output.
4. We are currently targeting the communities through workshop which will add more exposure to module ecosystem rather than individual onboarding (Although we are yet to find out on the outcome quality)

We are happy to still update our goals of the m1 based on the outcome of these workshops in the coming weeks.

CES Comment:

• Note the rescoping of Milestone 1 (doc linked again here) to 15 ind. devs and 3 projects
  • If approved, would be completed and relieve this milestone which was due May 15th