`SafeECDSASignerLaunchpad` has unclear support for multi-owner accounts about safe-modules HOT 4 CLOSED

Correct me if I'm wrong, but would you say that the expected outcome would be to:

1. evaluate the security implications of the current setup? (Basically, what you said in the standup where we a single owner has full control of the multisig)
2. propose changes to the API to adjust for potential multi-owner use cases?

Bang on!

Something that came to me while writing the issue: IIRC, the current launchpad contract was your experiment to make Passkey signers work with 4337, and we never defined any formal requirements (product, technical, etc) for the contract. Perhaps this is the moment to do this, sync with Niharika and formalize the requirements, etc

from safe-modules.

Correct me if I'm wrong, but would you say that the expected outcome would be to:

1. evaluate the security implications of the current setup? (Basically, what you said in the standup where we a single owner has full control of the multisig)
2. evaluate with the product team what the requirements are for multi-owner use cases
3. propose changes to the API to adjust for potential multi-owner use cases?

from safe-modules.

This is blocked on product decision on what must be supported for SDK passkey support.

from safe-modules.

We found a general solution with the shared signer, which would work for arbitrary ownership structures, so this is once again unblocked.

from safe-modules.