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

Force unlock message #2727

Closed
2 tasks
ValarDragon opened this issue Sep 13, 2022 · 0 comments · Fixed by #2733
Closed
2 tasks

Force unlock message #2727

ValarDragon opened this issue Sep 13, 2022 · 0 comments · Fixed by #2733
Assignees

Comments

@ValarDragon
Copy link
Member

Background

For Mars, we need to add a "ForceUnlock" message for LP's where they can break locks they own immediately. However permission for their address to use this needs to be given by governance, based upon contract audits.

Suggested Design

Design of force unlock:

  • There is a chain parameter for the addresses that are allowed to have force unlock for their own locks
    • (Governance can update this list through either param change proposal, or custom proposal type. I'd prefer param change)
  • We add a message called "ForceUnlock" which takes in a lock ID and amount, and asserts that:
    • lock owner = msg sender
    • lock is not superfluided
    • {partial unlocks that amount immediately}

Acceptance Criteria

  • Force unlock message exists
  • Above constraints are met
@osmo-bot osmo-bot moved this to Needs Review 🔍 in Osmosis Chain Development Sep 13, 2022
@mattverse mattverse self-assigned this Sep 14, 2022
Repository owner moved this from Needs Review 🔍 to Done ✅ in Osmosis Chain Development Oct 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants