Feature request: expose the user (EOA) wallet provider about safe-apps-sdk HOT 5 OPEN

don't care if EOA is actually a valid owner and

Why bother with the feature then? You can generate a random private key and sign the message

The author doesn't care but in my use-case this is essential and an huge UX improvement.
I do need signature from ALL safe account signees

from safe-apps-sdk.

I agree this would big an huge UI UX improvement for our use case.
Looking at the code they interact with the safe account using https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage

Maybe it wouldn't be too much of a hassle to use that feature to request the safe web app to interact with the EOA wallet on behalf of the Iframe.

from safe-apps-sdk.

don't care if EOA is actually a valid owner and

Why bother with the feature then? You can generate a random private key and sign the message

from safe-apps-sdk.

don't care if EOA is actually a valid owner and

Why bother with the feature then? You can generate a random private key and sign the message

Hi @mmv08. The purpose of the feature (back then) was to allow the Safe App to consume the wallet client (the connected wallet on the app.safe.global website). As mentioned on the description, one of the intended use cases was to be able to use the wallet client to sign a message mainly for authentication purposes within the developer's DApp.

I take back this part: i) don't care if EOA is actually a valid owner (just updated the description). Just wanted to be able to let the connected user sign a message without the need to interact with SignMessageLib (no need for all multisig owners to approve it).

from safe-apps-sdk.

ii) takes time to wait for all owners to approve the message and execute the Gnosis Safe: Sign Message Library and you won't like to wait that whole process just for interacting with the DApp.

Just FYI you can use offchain signatures which should be faster: https://docs.safe.global/safe-smart-account/signatures/eip-1271

from safe-apps-sdk.