Skip to content
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

Migrate Lockdrop and Vesting LP vaults to CL pools #71

Conversation

pr0n00gler
Copy link
Collaborator

No description provided.

@pr0n00gler pr0n00gler changed the title [WIP] Migrate Lockdrop and Vesting LP vaults to CL pools Migrate Lockdrop and Vesting LP vaults to CL pools Jun 30, 2023
@pr0n00gler pr0n00gler marked this pull request as ready for review June 30, 2023 08:17
@quasisamurai quasisamurai force-pushed the fix/migrate-from-xyk-to-cl-pairs-vaults branch from 754aea0 to 8bdec04 Compare July 7, 2023 15:34
@pr0n00gler pr0n00gler requested a review from swelf19 September 1, 2023 09:15
info: MessageInfo,
new_owner: Option<String>,
new_lockdrop_contract: Option<String>,
new_oracle_usdc_contract: Option<String>,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think we use a pool, not an oracle

address: String,
height: u64,
) -> StdResult<Uint128> {
let pool_contract: String = match pool_type {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of matching pool type, you could pass only one appropriate pool_address in argument.

@pr0n00gler
Copy link
Collaborator Author

@pr0n00gler pr0n00gler merged commit 3394002 into feat/migrate-from-xyk-to-cl-pairs Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants