Remove MultisigWallet in favor of gnosis/MultiSigWallet #328
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've decided to remove our own
MultisigWallet
from OpenZeppelin.Our recommendation going forward is to use gnosis/MultiSigWallet. We have not performed a formal audit yet, but have informally reviewed the code in the past and consider it of excellent quality. We are aware that it has been through several audits, and will perform and publish our own soon.
This resolves the month-old issue #251, after a decision to prioritize it in light of last week's hack on the Parity multisig wallet.
Besides Gnosis' implementation being more tested and audited than our own, there was a function definition missing in our MultisigWallet which caused the contract to be abstract and thus impossible to deploy.