Open jennypollack opened 6 years ago
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?
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?
We need to alert to the dApp that they are interacting with a SAFE account, if so, how do we propose to do this?
@cjeria @danfinlay
+1
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)
2. Two-Factor: SAFE contract controlled by two keys.
3. Multi-Sig: SAFE contract controlled by an arbitrary number of keys