This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Multiple vesting schedules per account #7699
Closed
raoulmillais
wants to merge
12
commits into
paritytech:master
from
raoulmillais:multiple-vesting-schedules-per-account
Closed
Multiple vesting schedules per account #7699
raoulmillais
wants to merge
12
commits into
paritytech:master
from
raoulmillais:multiple-vesting-schedules-per-account
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
raoulmillais
added
A3-in_progress
Pull request is in progress. No review needed at this stage.
J0-enhancement
An additional feature request.
labels
Dec 9, 2020
raoulmillais
force-pushed
the
multiple-vesting-schedules-per-account
branch
2 times, most recently
from
December 9, 2020 16:36
7a0f325
to
7fb4540
Compare
raoulmillais
force-pushed
the
multiple-vesting-schedules-per-account
branch
5 times, most recently
from
December 14, 2020 15:15
1728aca
to
b76844e
Compare
Needs a companion PR |
- Add config value for max vesting schedules (currently not honoured)
- Check for too many schedules when adding schedules instead of erroring if there is one - Update storage with only remaining schedules (incomplete ones) after updating the lock - Update module genesis building to support multiple vesting schedules in genesis config (sum unvested balances so far before adding vesing schedule and set lock to total unvested balance across all schedules) - Update vesting_balance to return None if there are no vesting schedules, or sum up the vested_at for all vesting schedules - Update tests for api change - Add new tests for more than one schedule (disjoint and concurrent)
- ADds missing docs for `vested_transfer` and `force_vested_transfer`
- test happy path
raoulmillais
force-pushed
the
multiple-vesting-schedules-per-account
branch
from
January 13, 2021 12:46
b76844e
to
cc08dbe
Compare
I suppose unfortunately this will not be finished, correct? |
kianenigma
added
A5-stale
Pull request did not receive any updates in a long time. No review needed at this stage. Close it.
and removed
A0-please_review
Pull request needs code review.
A3-in_progress
Pull request is in progress. No review needed at this stage.
labels
Feb 19, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A5-stale
Pull request did not receive any updates in a long time. No review needed at this stage. Close it.
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 implements allowing multiple vesting schedules per account in the vesting pallet. This will ultimately fix #7101
Please be gentle I am new to both rust and substrate! :)
Task List
Support multiple vestings per account:
VestingInfo
to account →Vec
ofVestingInfo
VestingInfo
toVec
ofVestingInfo
Support consolidating vestings in account
valid/invalid combinations for algorithm
Companion polkadot PR
See companion PR for substrate#7040