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
Treat the validator updates from the application as an unordered set #3181
Comments
sounds related to #3073 |
Proposal for atomic application:
Also we should consider if we need |
all updates except the validator removals
do validator removals here
|
pls. see pull request #3222 |
Seems like NewValidatorSet(valList) does not check for duplicates in the validator list valList and we end up with a validator "set" including same validator multiple times. I'm not sure if all checks are in place when running in a real setup so valList does not contain duplicates. Will check. |
Merged! Thanks @ancazamfir ! Will add follow up notes to #3166 |
When the application updates the validator set it calls updateValidators() with an 'updates' parameter, a list of changes that is then parsed in order, one entry at a time, making updates for the corresponding validator. i.e. the list is treated as a transaction list.
For example [add v1, rem v2, add v3] is different than [rem v2, add v1, add v3] and the call with one will produce different results than with the other.
This is an issue for gaia that requires these updates to be instead interpreted as a set.
The text was updated successfully, but these errors were encountered: