Call 1 (Andre) - A few notes from the ZenGuard initiative discussion

1. Concerns on the Safe{Core} Protocol not being production ready and not in active development.

• Yes, ZenGuard registry and module manager is an extension of pre-production ready Safe{ Core } Protocol implementation. We have currently developed publishing, and audit attestation verification on top of the registry. This will also be compliant with the future version of the implementation. We are also referencing the Rhinestone registry and readiness.
• The modules registered on the ZenGuard registry will be compliant irrespective of the registry upgrades.

1. Portability of the currently developed modules onboarded to the ZenGuard marketplace.

• The modules developed and all the module types (Plugins, Hooks, Function handlers, Sig verifiers) are compatible with Safe Account 1.3.0.

• Our approach for module development is always developing a module that is directly compatible on Safe Account and then porting it as a module type to enable it via the Module manager on ZenGuard.

  • For example: The Safe2Link module developed has 2 versions.

    1. A module that is developed as a normal Safe module independent of the manager. This is enabled directly as Safe App: http://safe2link.xyz.

       **Source code: https://github.com/zenguardxyz/safe2link**

    2. A module type that is developed as a plugin depends on the manager. This is enabled through the ZenGuard marketplace app: https://safe2link.zenguard.xyz. **Source code: https://github.com/zenguardxyz/safe2link-plugin**

• The same dev approach will be used for future modules. The audit will also be carried on for both versions but onchain attestation is applied for the one listed on ZenGuard.

Call 2 (Andre, John, Lorny, Amy)

1. Other module standard implementation and adoptions.
   1. As there have been a few developments in the module standards ( ERC-6900 and ERC-7579) implementations and the Safe Account adoption for this. We may update our module developments adhering to these standards once there is an adopter/ manager support for these standards (Discussions needed with 7579 authors and the Safe team)
2. More clarity is needed on how a few milestone metrics will be achieved