You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that this kind of user may be hard to find, but one current example is Ned, as shown in the recording of the bug. Ned's 14-week powerdown will finish at 11:09pm on 24 Jan 2019, so you should find another example after that.
Powerdown amount is more than current SP, which is impossible.
Cause and Fix
This bug is due to the floor operation in the calculation of weekly powerdown amount, as explained in details in steemit/steem#3237 Due to this, the entire powerdown may take 14 weeks. Thus when calculating 14-week powerdown amount, it should be at most the remaining withdrawal.
While I fixed that bug at steemd level, until the fix is applied in production, any client (e.g., busy) should user their own fix. Thus, I made the fix.
After the fix is applied, voting value and powerdown amount (0 SP since it's 11 vests) are shown correctly.
The text was updated successfully, but these errors were encountered:
This bug is due to the 14-week powerdown bug: steemit/steem#3237 and I made the fix for steemd and another fix for busy.
Expected behavior
A weekly powerdown amount can't exceed the remaining powerdown amount.
Actual behavior
A weekly powerdown amount may exceeds the remaining powerdown amount; thus, voting value can be negative.
How to reproduce
Note that this kind of user may be hard to find, but one current example is Ned, as shown in the recording of the bug. Ned's 14-week powerdown will finish at 11:09pm on 24 Jan 2019, so you should find another example after that.
Recording Of The Bug
Cause and Fix
This bug is due to the floor operation in the calculation of weekly powerdown amount, as explained in details in steemit/steem#3237 Due to this, the entire powerdown may take 14 weeks. Thus when calculating 14-week powerdown amount, it should be at most the remaining withdrawal.
While I fixed that bug at steemd level, until the fix is applied in production, any client (e.g., busy) should user their own fix. Thus, I made the fix.
The text was updated successfully, but these errors were encountered: