-
Notifications
You must be signed in to change notification settings - Fork 2
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
migration to update a number of users total allocations #30
Conversation
this is what the execute msg will look like:
|
successfully executed on mainnet fork:
|
v1_1_0::migrate(deps) | ||
pub fn migrate(deps: DepsMut, _: Env, msg: MigrateMsg) -> Result<Response> { | ||
match msg { | ||
MigrateMsg::V1_0_0ToV1_1_0 {} => v1_1_0::migrate(deps), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The way we set version numbers in the cargo.toml meant the old test failed, it was checking for 1.1.0 but since the cargo is now set to 1.1.1 that is what gets set regardless of what migration you are doing, I cross-referenced to the other contract migrations, e.g. oracle contract and seems to be doing the same thing so just left it as is
LGTM |
A number of Labs members gave up a part of their allocations on the Labs fundraise, this migration is claiming back the required allocation portion to re-allocate investors. This was needed to be done as a migration because some of these allocations had already vested more than what they should have now had... and as a result terminating the position with existing vested amount is not sufficient