-
Notifications
You must be signed in to change notification settings - Fork 35
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
Cancelation realloc and current member state check/retain #104
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Will change this to be ProposalVoteV2 |
programs/squads_multisig_program/src/instructions/proposal_vote.rs
Outdated
Show resolved
Hide resolved
programs/squads_multisig_program/src/instructions/proposal_vote.rs
Outdated
Show resolved
Hide resolved
@vovacodes @bguillaumat the updates slated here for the realloc introduce some duplications, but mainly because i'm not sure what we're thinking for the future. Since this is already an edge case, i'm thinking we maybe change the account contect to ProposalCancel, and use that in the proposal_cancel_v2 ix. Then we can rip out all of the approve/reject from it. Lmk. |
Cancellation is blocked if new threshold exceeds space when proposal was first created. It's an edge case, but this will block the ability to cancel and thus reclaim rent. We propose adding a proposal_cancel_v2 for this specific realloc, but that requires a system_program account, thus adding a new account context.