Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status of Gnosis Safe and MultiSigWallet #103

Closed
guylando opened this issue May 3, 2019 · 4 comments
Closed

Status of Gnosis Safe and MultiSigWallet #103

guylando opened this issue May 3, 2019 · 4 comments
Labels

Comments

@guylando
Copy link

guylando commented May 3, 2019

It is a little unclear on what should be used right now to deploy a new multisig ethereum wallet.
safe-contracts version 1.0.0 was released 29 days ago so does that mean that it should be used instead of MultiSigWallet? On the other hand the MultiSigWallet repository keeps getting commits which makes it unclear if MultiSigWallet is deprecated or not.

Sources:

  1. It was told here that efforts are moved to gnosis safe instead of MultiSigWallet Use gnosis multisig wallet with mist/ethereum wallet gnosis/MultiSigWallet#102
  2. Gnosis safe version 1.0.0 was released 29 days ago without any article post about it at that time https://github.com/gnosis/safe-contracts/releases/tag/v1.0.0
  3. An article published few days ago tells to upgrade to gnosis safe version 1.0.0 which addressed latest security audit vulnerabilities https://blog.gnosis.pm/formal-verification-a-journey-deep-into-the-gnosis-safe-smart-contracts-b00daf354a9c
  4. MultiSigWallet had 25 commits since last release which means it keeps getting developed gnosis/MultiSigWallet@v1.5.0...master
  5. The description of gnosis safe google chrome extension says it is beta until the formal audit is done however the formal audit is already done so why is it still beta? https://chrome.google.com/webstore/detail/gnosis-safe-mainnet-beta/iecodoenhaghdlpodmhooppdhjhmibde

Questions:

  1. What is the status of MultiSigWallet? Is it deprecated?
  2. What is the way to deploy a new gnosis safe contract? Previously MultiSigWallet contract was deployed using the MultiSigWallet gui: https://wallet.gnosis.pm
  3. Can https://wallet.gnosis.pm be used to interact with gnosis safe contract? if not then what is the new gui/web to interact with gnosis safe multisig wallet?
  4. It says here: https://safe.gnosis.io/ that "Personal edition" is limited while the "Team edition" is an upgrade of MultiSigWallet. Does the term "Team edition" means that it is not free? Why does it say that it is not available if version 1.0.0 was released 29 days ago?
  5. Is the gnosis safe chrome extension still beta even though the formal audit is done? https://chrome.google.com/webstore/detail/gnosis-safe-mainnet-beta/iecodoenhaghdlpodmhooppdhjhmibde

The bottom line is: if we deploy a multisig wallet TODAY then what should we use (contract/interface)?

Thanks!

@rmeissner
Copy link
Member

Hey,

1.) The MultiSigWallet will be deprecated, but this doesn't mean that there will be no commits to that repository, since we will continue to provide security updates. But there we be no new features implemented.
2.) and 3.) One of the reasons why we say "will be deprecated" is that there is now web interface for the safe-contracts that has the functionality of wallet.gnosis.pm yet. We are working on that and the current state can be seen in the https://github.com/gnosis/safe-react repository. So currently you need to use either the mobile apps or create the Safe yourself by interacting with Ethereum directly.
4.) The naming of the "Team edition" should not imply any payment. Also it should be said that this name is by all means NOT final. For the "Personal edition" we make the assumption that all owner keys are managed by a single person. This allows us optimise certain flows and provide additional functionality which would be complicated otherwise (e.g. paying transactions with tokens). Both versions share the same contracts, but the version that is tailored towards teams (where the ownership of the Safe is shared between different persons) is not ready yet (as mentioned above).
5.) We are currently in the progress of pointing all clients towards the audited contract. Once this is done the description of the clients will be updated.

To your last question: If you want to share access of the MultiSig between different people, I would currently still point you to our old "wallet.gnosis.pm". If the MultiSig is managed by a single person that owns a mobile phone, I would recommend using the Safe mobile app.

If you want we can notify you as soon as the react version is ready, just shoot us an email to safe@gnosis.pm

Cheers

@guylando
Copy link
Author

guylando commented May 6, 2019

Thanks for the detailed and informative answer!

A little follow up:

  1. If we create a multisig wallet today with wallet.gnosis.pm then will you make some easy migration button or similar in the new gnosis safe web interface you are creating so that we will be able to easily migrate when gnosis safe is ready?
  2. Any place where we can look at timeline/roadmap for gnosis safe? looks like this: https://github.com/gnosis/safe-contracts/projects/1 was not updated for 2 months.

Thanks for your time.

P.S sent an email as you recommended.

@lukasschor
Copy link
Member

Hey Guy,

Saw your email, we will keep you updated on the progress of the "Team Edition".

  1. We definitely want to make it as easy as possible to migrate from the old multisig wallets to the new Gnosis Safe contracts. We will be evaluating different options in that regard. This won't be part of the very first release, though.
  2. We are using Zenhub to track the progress of all Safe-related projects: https://app.zenhub.com/workspaces/gnosis-safe-5c1b98250e13551e8aae81eb/board?repos=100974407,146720563,156711728,96440096,120428054,102186072,122183817,126045032,123913364,134711860,122971363&showPipelineDescriptions=false
    However, we are still working on giving a better overview of future release plans and timelines.

@guylando
Copy link
Author

guylando commented May 6, 2019

Thanks! closing

@guylando guylando closed this as completed May 6, 2019
fdarian pushed a commit to fdarian/safe-contracts that referenced this issue Jan 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants