Support Gnosis Safe Account Type

[jennypollack]

Gnosis SAFE provides the ability to control a contract account with multiple keys. Introducing this as an account type in the extension could open up a lot of possibilities.

We'll develop this in three stages:

1. Single Signer: SAFE contract controlled by a single key (1 of 1)

• batch transactions are cheaper on gas, happen in perfect order in single tx
• makes lots of extensions possible: account recovery, state channels, limits, allowances, etc
• communicating that your key controls a separate contract
• user needs to publish a contract, which is expensive

2. Two-Factor: SAFE contract controlled by two keys.

• Can customize rules around how many keys are required to sign tx
• Can use phone as second factor for tx signing
• Increased security

3. Multi-Sig: SAFE contract controlled by an arbitrary number of keys

• Max security
• Usecases for teams, etc
• Have to gather tx signatures off-chain – poses a UX challenge

[bdresser]

Some outstanding questions from last week's meeting:

• Should we make a MetaMask deployer dApp to create the SAFE contracts, or keep it inside the extension?

  • Deployer dApp is already its own project for testing purposes.
  • Faster to develop outside MetaMask.
  • Larger attack surface if we host it outside the extension.

• The contract account can’t be derived from the user’s hd-keyring, so it may look like a loose account that needs to be re-added. Is there a good way to circumvent this?

  • Is there a good word to encompass import, validation, and “watching” (re-adding the contract’s address multiple times is bad/confusing UX)

• We need to alert to the dApp that they are interacting with a SAFE account, if so, how do we propose to do this?

[bdresser]

@cjeria @danfinlay

[emilianobonassi]

+1