Modify vesting schedule post-calico #4862
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
arajasek
requested review from
Kubuxu,
magik6k and
whyrusleeping
as code owners
|
Needs ✅ from @whyrusleeping |
magik6k
approved these changes
Nov 16, 2020
whyrusleeping
approved these changes
Nov 17, 2020
There was a problem hiding this comment.
these numbers are slightly different than i'd expect, but i'm guessing @zixuanzh has some reason for this
|
What do you mean? This should be as transparent as possible with no room for meddling. |
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.
There was an accounting mistake in the vesting table. It was reported but not fixed because of timeline and fixing it earlier will mean a spike in collateral for miners. This PR upgrades the vesting table to more closely match the actual multisig vesting.
Fixes #4660