-
Notifications
You must be signed in to change notification settings - Fork 15
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
Feat/3537 arbitrary via multi sig #3979
Conversation
5819a12
to
71cc9f1
Compare
f6bb1e2
to
2119e50
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Impressive work on adding Custom transactions
via Multi-sig
@Nortsova 🥇
Installed the Multi-sig
extension
Gave leela
and amy
Owner
permissions in General
for Multi-sig actions
Created a Custom transactions
multi-sig motion
Approved as leela
And as amy
And could see the incoming funds
after this motion was finalised
Then created another Custom transactions
via multi-sig that I have rejected
And nothing changed on the incoming funds page
Nice work!!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @Nortsova! All the code is looking good and it looks to be working as expected:
After installing the extension and giving permissions I could make the action, vote and finalize:
And there were incoming funds: (a tiny amount 🤣)
And cancelling also worked, without new incoming funds appearing:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really nice and simple 👌
Form looking all good ✔️
Removing a vote works ✔️
And finalization also goes through 😎
However, I just wanted to raise a question here
test
is the multi-sig motion and it doesn't have the correct description, should this be added?
is Generic action we don't have information about
for the actual contract call OK, or should it be something else?
Will preliminarily request changes, and if it's not in scope of this isssue, I'll just approve.
Overall, great job 💪
71cc9f1
to
7db7bd4
Compare
2119e50
to
78911fb
Compare
Nice catch, @bassgeta . Thank you for your help. Fix for Generic action is here now 🙌 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ef18af6
to
40d066f
Compare
The base branch was changed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-approving 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
40d066f
to
48851c7
Compare
Description
This issue covers the multi-sig flow of creating arbitrary transaction.
New saga needs to be added that should accept a target contract address and a list of arbitrary transactions, consisting of function name and a list of arguments. It should create a multi-sig motion to call makeArbitraryTransactions on the Colony contract.
Note
Please Review block-ingestor PR too - JoinColony/block-ingestor#306
Testing
Step 1. Install Multi-Sig extension http://localhost:9091/planex/extensions/MultisigPermissions
Step 2. Give leela and amy owner Multi-Sig roles:
Step 3. Create Custom transaction action ("Manage Colony" -> "Custom transactions")
Step 4. Create transaction with the following (or you can use beautiful approach of custom contract that Jakub described here: #3966 )
Contract address:
0xeF841fe1611ce41bFCf0265097EFaf50486F5111
ABI:
Step 5. Select
Decision Method:
Multi-Sig
Step 6. Submit form
Step 7. Ensure that Multi-Sig motion was created:
Step 8. Login as amy from incognito window and approve motion
Step 9. Finalize it
Step 10. Verify that you can see Incoming funds (that was minted because of the Contract call)
Step 11. Repeat Step 3 - Step 7.
Step 12. Remove your vote and reject motion
Step 13. Verify that there is no new income funds (means no Contract was called)
Contributes to #3537