-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix!: new validator creation not persisting to cometbft #149
Conversation
current issue: 81166e2 fixes the issue (new validators now get pushed into cometbft consensus) with test_node.sh (still need to fix in the new add val test) However: when you set the power of a validator, it now persist in the valUpdates forever. We ONLY want to update if it is a new validator. Since staking handles it usually
Working on a cache mechanism so abci.ValUpdates are only submitted on new vals vs existing updates |
32e6d77 looks to fix this in manual testing (start network, set val[0] to 18, add pending val, set pending val to 2, wait, query comet consensus, remove pending val, query comet consensus just has val[0] at 18). |
* fix jail test (unbonding or unbond) * use idx 0 since it fails anyways * bump ictest to latest main * rm remove val test from monolith tester * test: `TestPOARemoval` * fix test * touchups * `ictest-gov` * abic refactor * working local: val-add and jail
return err | ||
} | ||
|
||
if val.Status == stakingtypes.Bonded { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: add note this is to make ABCI events happy so we always control the key (which changes over blocks) & persist adding new validators to the network
moved to #160 |
ref #156
ref: found by ethos
Summary
Despite PoA depending on x/staking for it's EndBlock actions, it does not seem it is persisted when changing Power amounts for new validators -> CometBFT consensus
Issues