Skip to content

signer should be optional when calling toMetaMaskSmartAccount #163

@jeffsmale90

Description

@jeffsmale90

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions