-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Support lotus-miner actor withdraw
when owner address is a multisig
#5647
Comments
lotus-miner actor withdraw
when owner address is a multisig
Three options here:
|
for now we might as well include docs akin to #5342 (comment) |
I am waiting for this feature, and my customers are also very anxious. When will we release this feature? |
blocked by #1136 |
Would love to see progress on this! Needed by SPs @Reiers @ribasushi |
Hey @stuberman! I know the UX is not ideal, but you can withdraw the balance with a msig owner following this guide https://lotus.filecoin.io/tutorials/lotus-miner/msig-as-owner/#withdraw-balance-with-multisig-owner using the Else you can use regular Lotus by encoding and sending the right message, but the UX is not nice, so I deliberately left it out from the Docs: 1. Then propose from one msig member: Then approve with the rest of the msig signers: |
We can wrap the steps above and introduce the following
We set the encoding as |
thanks @alvin-reyes ! given that under
that might use a different method id - so id suggest to have some indicator on then cmd that this is for the |
Adding here the related slack discussion(s): |
Describe the bug
A clear and concise description of what the bug is.
To use a multi-signature wallet as the miner owner, use the command: lotus-miner actor control list | actor withdraw 0.001
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
success
Screenshots
If applicable, add screenshots to help explain your problem.
Version (run
lotus version
):1.4,2
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: