Open pcaversaccio opened 8 months ago
hell yes
would like to pick this up - I'd say the end version should be a combination of the 2 references: a contract that allows for sequential signatures, provided either as calls to a approve(proposalID)
method or as EIP-712 signatures.
anything else you'd like to see?
would like to pick this up - I'd say the end version should be a combination of the 2 references: a contract that allows for sequential signatures, provided either as calls to a
approve(proposalID)
method or as EIP-712 signatures.anything else you'd like to see?
Thanks for the ping. So the situation is the following: Vyper will release soonish a new breaking version (see the beta version here) that allows for stateless and stateful modules. I'm in the process of refactoring the π snekmate contracts for this release (you can follow the process in this PR: https://github.com/pcaversaccio/snekmate/pull/207). These new language features will power a lot of the multisig features I have in mind. But until Vyper 0.4.0
is shipped and I have not refactored all contracts, there will be a feature freeze. So it could be a few weeks before we can start with the multisig.
The multisig I envision should be more agnostic and flexible. The 2 references are a good starting point, but still too limited to make it competitive with existing multisig contracts managing hundreds of millions of dollars. Our goal is to eventually have a system of contracts like that of Safe (see here).
Oh I see, thanks for the insight. I'll wait it out until 0.4.0
drops and then look into making this contribution. Feel free to ping me when time comes!
Would love to help out as well in whatever way possible.
It's time for Vyper to catch up with Solidity on the multisig front, and π snekmate plans to offer its own Vyper-based multisig wallet that is capable of reaching mainstream adoption.
References