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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃挜 Vyper-Based Multisig Wallet #176

Open
pcaversaccio opened this issue Nov 8, 2023 · 5 comments
Open

馃挜 Vyper-Based Multisig Wallet #176

pcaversaccio opened this issue Nov 8, 2023 · 5 comments
Assignees
Labels
feature 馃挜 New feature or request help wanted 馃啒 Extra attention is needed
Milestone

Comments

@pcaversaccio
Copy link
Owner

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

@pcaversaccio pcaversaccio self-assigned this Nov 8, 2023
@pcaversaccio pcaversaccio added the feature 馃挜 New feature or request label Nov 8, 2023
@pcaversaccio pcaversaccio added this to the 0.0.5 milestone Nov 8, 2023
@pcaversaccio pcaversaccio added the help wanted 馃啒 Extra attention is needed label Nov 8, 2023
@sambacha
Copy link

sambacha commented Nov 8, 2023

hell yes

@pcaversaccio pcaversaccio modified the milestones: 0.0.5, 0.1.0 Mar 7, 2024
@DrasticWatermelon
Copy link

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?

@pcaversaccio
Copy link
Owner Author

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: #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).

@DrasticWatermelon
Copy link

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!

@pcaversaccio pcaversaccio modified the milestones: 0.1.0, 0.1.1 Apr 18, 2024
@f3rmion
Copy link

f3rmion commented Apr 24, 2024

Would love to help out as well in whatever way possible.

@github-staff github-staff deleted a comment from carlosfgti May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature 馃挜 New feature or request help wanted 馃啒 Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants