-
Notifications
You must be signed in to change notification settings - Fork 165
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
Add return value to WithdrawBalance #26
Comments
This sounds great to me. It's part of an open discussion, but this also sounds like a change that's inconsequential enough that we might not need to use the FIP process for it. Since it changes the actors API it will need to wait for the next major release (v3) of actors, but we're planning for that later this year. @whyrusleeping @dignifiedquire @momack2 should we use the FIP process for this, or just go straight to implementation. |
I would error on the side of creating a FIP for now, even if it is a simple one. |
Hi @anorth! I'm currently working to audit all open FIP discussion items so that we can triage existing issues and flag priorities that may have been missed. It looks like this issue was lost in the bundle of FIPs that were implemented prior to the Actors v5 launch. Is this the case? If so, we should reintroduce the idea and write a FIP draft. |
Thanks, sounds good to me
…On Sat, 7 Aug 2021 at 10:40 am, Kaitlin Beegle ***@***.***> wrote:
Hi @anorth <https://github.com/anorth>! I'm currently working to audit
all open FIP discussion items so that we can triage existing issues and
flag priorities that may have been missed.
It looks like this issue was lost in the bundle of FIPs that were
implemented prior to the Actors v5 launch. Is this the case? If so, we
should reintroduce the idea and write a FIP draft.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADMW6UX4X3EKKARHMOJSMDT3R6IHANCNFSM4TIMP64A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
This was implemented as FIP0020! |
Background
Both miner and market actors have
WithdrawBalance
methods.However, either method is actually an attempt to withdraw a specified amount, it could be successful even when the available balance is less than required amount, that means, the actual amount withdrawn is equal to or less than the amount specified in the method parameters, and the method always return
nil
, so that, there is no way to get how much amount actually withdrawn if we check the chain status and message info, e.g. from CLI or explorer.Proposal
Simply add a return value to the method to indicate the actual withdrawn amount.
This will improve the visibility and traceability of FIL flow. This is important especially for miners who need to have a very clear balance sheet and financial report.
The text was updated successfully, but these errors were encountered: