0.7 entrypoint was unfinished when we started 4337 implementation. Currently it seems ready to be used and it should be possible to use it with the Safe SDK. We need to test and support both versions in the SDK.
Proposed solution
Update the safe-modules-deploymentsto the latest version, having compatibility for 0.2.0 or 0.3.0 versions of the Safe module.
We should keep 0.6 entrypoint by default (which is supported by 0.2.0 version of the Safe module). The API is not supporting v0.7 UserOperations yet.
From the supported entrypoints we receive from the bundler we need to detect which one is 0.6 or 0.7.
When we load a Safe that is already deployed, the SDK needs to be able to select the correct module that the Safe is using.
AddModulesLib was renamed to SafeModuleSetup. Everything will still work if unchanged, but would be good to align naming convention to avoid future breaking changes.
The API service won't be compatible with 0.7.0 yet. We can add compatibility to the SDK setting the specific module address manually. We should test this approach to anticipate the differences in the SafeOperation object.
Context / issue
0.7 entrypoint was unfinished when we started 4337 implementation. Currently it seems ready to be used and it should be possible to use it with the Safe SDK. We need to test and support both versions in the SDK.
Proposed solution
safe-modules-deploymentsto the latest version, having compatibility for 0.2.0 or 0.3.0 versions of the Safe module.AddModulesLibwas renamed toSafeModuleSetup. Everything will still work if unchanged, but would be good to align naming convention to avoid future breaking changes.Additional context
safe-modules CHANGELOG
The API service won't be compatible with 0.7.0 yet. We can add compatibility to the SDK setting the specific module address manually. We should test this approach to anticipate the differences in the SafeOperation object.