Deduplicate session.validators #139
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change just deduplicates
session.validatorsstorage. It is required in v15 node, as that storage has 900 entries now - representing 900 slots. This PR does not affect v14 version, as deduplication does not affectsession.validatorsorder.Implementation is not ideal, as still there's some code duplication - ideally I'd like to see
api.query.session.vliadatorsonly once inpage-staking.Also, I analyzed if those v15 changes can impact other part of this repo, but they are not:
page-stakingthere are no other usages ofapi.query.session.vliadatorsapi-deriveusesapi.query.session.vliadators, but thankfully we don't use any of such calls