-
-
Notifications
You must be signed in to change notification settings - Fork 30
Open
Description
When creating a MetaMaskSmartAccount abstraction, the caller must provide a signer, so the abstraction can perform signatures.
In some cases, the caller may not have the signer available, but may still be able to derive value from the abstraction. For instance Multisig accounts with distributed signers, or a backend account deployer.
The signer argument in the toMetaMaskSmartAccount should be optional. If this argument is not specified, any function call that requires a signer should throw an error with a useful message indicating that the function is not available without a signer, and how the caller may specify the signer in order to perform signing operations.
Related to #62
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels