-
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
DisputWindowPost executes successfully but without a reward! #11703
Comments
The reward comes from the Miner Actor's balance, and this Miner had no balance. It looks like they:
This is definitely an... interesting edge case. But there isn't really a way to "pay out" in this case because there simply isn't any FIL. |
Thank you for your reply. |
Closing in favor of #11715 (with a description of how this should be fixed). |
And thanks for reporting this! |
…miner has no balance to pay rewards (#11800) In #11703, a user came across an edge case where an SP: 1. Submitted a bad PoSt. 2. Terminated their sectors. 3. Withdrew all funds (after paying all fees). This left the SP's miner actor with a bad proof but without any funds to pay for disputes. On the other hand, given that the sectors have been terminated and termination fees were already paid we don't really care about fining the SP for the bad proofs anyways. But... we still don't want to submit dispute messages in this case because doing so isn't free and doesn't really serve a purpose. So add a check to fetch miner wallet balance and only send disputing messages if balance is non zero. fixes #11715
Checklist
Latest release
, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.Lotus component
Lotus Version
Repro Steps
https://filfox.info/en/message/bafy2bzacedeupksdrvt7ujn62xrk6peinaa27czhakkr3osyut2jzqym4pihq?t=1
Describe the Bug
Sending DisputWindowPost succeeded but no reward, the last DisputWindowPust succeeded with a reward, I'm wondering if the reward was canceled or if there was a problem with the lotus
Logging Information
The text was updated successfully, but these errors were encountered: