We don't support creating requests from Safe Multisig Wallets or EIP-4337 Account Abstraction wallets
Possible Solution
@vrolland shared an image of old designs that were never implemented for handling signatures from gnosis safe multisig wallets.
The image tells me that the RN signature validation logic would need to change to support signatures from a multisig wallet.
Smart Contracts don't have a private key, and therefore cannot sign anything. However, we could change our signature validation logic to look at the configuration of the multisig (owners and threshold) and evaluate a composite signature as valid IF the signatures came from the owners, and the number of signatures exceeds the threshold.
I believe this signature validation logic would reside inside our SDK when we're retrieving requests and evaluating if they're valid or not. In other words, it would be written in TypeScript and would be executed off-chain by either a frontend or backend.
For inspiration on how this logic could be implemented, we can look at the Gnosis Safe code that implements EIP-1271:
We kind of support account abstraction already if there's an EOA that controls the smart contract wallet. The EOA will sign as the Payee Identity, and the smart contract wallet will receive the funds.
Problem
We don't support creating requests from Safe Multisig Wallets or EIP-4337 Account Abstraction wallets
Possible Solution