This repository was archived by the owner on Nov 15, 2023. It is now read-only.
Moving MAX_UNLOCKING_CHUNKS to become a runtime parameter
#10759
Conversation
This file contains hidden or 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
Contributor
|
seems to overlap mostly with #10670 @georgesdib can you DM me in element to coordinate more on future contributions? Thanks! |
Contributor
Author
I will close this PR as indeed it overlaps as you mention, thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Part of #9864, one little step at a time at making pallet-staking "bounded".
Fixes part of paritytech/polkadot-sdk#323.
Summary of changes below:
MAX_UNLOCKING_CHUNKSfrom being a constant to becoming a runtime parameterMaxUnlockingChunks.StakingLedger.BoundedVec.Polkadot companion: paritytech/polkadot#4811
@kianenigma