-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
💥 Vyper-Based Multisig Wallet #176
Comments
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 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: #207). These new language features will power a lot of the multisig features I have in mind. But until Vyper 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 |
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
The text was updated successfully, but these errors were encountered: