-
Notifications
You must be signed in to change notification settings - Fork 14
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
Stake display after unstaking with P7 #265
Comments
This is fixed in #214 and released in CCDscan backend 1.9.1. |
The fix is now out on Testnet as well |
@limemloh , I have just checked this again in more detail, and the stake displayed on CCDscan still doesn't look right. For my testnet account |
Checking the account using concordium-client:
|
Thanks for the clarification. I will close the issue again, and double check when the fix is out. |
Bug Description
CCD scan displays incorrectly the stake after P7 and produces a wrong information message when stake is in cool-down. It seems to display stake = active + inactive stake, instead of just active stake. The message says that "Stake will be reduced to Ͼ XXX in YYY days", when the stake has already been reduced and will be unlocked in YYY days. See screenshot attached.
Steps to Reproduce
Unstake some CCD, wait for the next pay day.
Expected Result
The new stake should be displayed after the pay day, because a stake change is immediately effective (well, at the next pay day), i.e., stake displayed = active stake.
There should probably also be a new line for the total stake in cool-down, i.e., inactive stake.
It is unclear what the expected message should be. Since there can be a queue of inactive stake to be unlocked on different days, this is inconvenient to display. Maybe the message should be removed altogether, until we can properly revise CCD scan.
Actual Result
The stake displayed = active + inactive stake, i.e., effective stake + CCD in cool-down.
There is no mention of how much stake is in cool-down.
Versions
CCD scan version 1.5.41/1.8.19
The text was updated successfully, but these errors were encountered: