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.

Sign up for GitHub

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

Jump to bottom

Lagoon: strategy redemption (withdrawal) flow #891

Open
kenkunz opened this issue Jan 9, 2025 · 0 comments
Open

Lagoon: strategy redemption (withdrawal) flow #891

kenkunz opened this issue Jan 9, 2025 · 0 comments
Assignees
@kenkunz
Labels
enhancement New feature or request priority: P1 An important issue that must be fixed before the next release, but does nto require immediate focus. size: M An ordinary task that can be completed in a few days or in a week

Comments

@kenkunz
Copy link
Contributor

kenkunz commented Jan 9, 2025 •
edited
Loading

Goal

As a web visitor seeking to redeem funds from a strategy that uses a Lagoon vault, I want a usable and secure redemption flow that enables me to redeem vault shares, and receive in exchange an appropriate amount of denomination tokens (e.g., USDT, USDC) based on the current value of the shares. If the strategy currently has open positions in other token assets, the user may receive proportionate quantities of those tokens, totaling the current value of the redeemed shares (in-kind redemption).

Example redemption

Here's an example redemption flow for ETH-BTC long swing using an Enzyme vault:

ETH-BTC.long.swing.redeem.mp4

Acceptance criteria

TBD
@kenkunz kenkunz mentioned this issue Jan 9, 2025
Open
@kenkunz kenkunz self-assigned this Jan 13, 2025
@kenkunz kenkunz added enhancement New feature or request priority: P1 An important issue that must be fixed before the next release, but does nto require immediate focus. size: M An ordinary task that can be completed in a few days or in a week labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kenkunz kenkunz

Labels
enhancement New feature or request priority: P1 An important issue that must be fixed before the next release, but does nto require immediate focus. size: M An ordinary task that can be completed in a few days or in a week
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kenkunz