-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Gaia-7004 halt stack trace #1920
Comments
I think I figured out the situation which might cause this - it should be resolved by https://github.com/cosmos/cosmos-sdk/pull/1858/files Consider this situation:
I haven't been able to write a failing test for this one yet however |
Can you explain this in more detail? What's the sequence around the oldCliffValidatorAddr variable? In your scenario, after step 2 ("6" bonded power), is the cliff validator the one that became 10? Then, a new validator bonds 7 and kicks out "6", wouldn't "10" still be bonded? |
In this situation the cliff validator should be 10, however because the old cliff power wasn't updated correctly the protocol may think that the cliff validator actually the new validator which has a power of "6"
Correct, however if the "6" is being kicked out (which requests that this validator be unbonded) the protocol would panic because this validator was never bonded to begin with. the original cliff validator would remain bonded the whole time. here is a more verbose description of the same scenario. Again I haven't been able to write a test for this but I think this which actually panics, which leads me to think that the real scenario is not this one but maybe a close variant.
|
I think the postmortem also closes this? @cwgoes |
Let's close it cause no one seems to have a stored a blockchain for |
The text was updated successfully, but these errors were encountered: