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

feat: single remove cl position and sfs new position msg #7095

Open
czarcas7ic opened this issue Dec 12, 2023 · 1 comment
Open

feat: single remove cl position and sfs new position msg #7095

czarcas7ic opened this issue Dec 12, 2023 · 1 comment
Assignees

Comments

@czarcas7ic
Copy link
Member

Background

Right now if a user wants to make a full range CL position a sfs position, the frontend does a multi message to remove the cl position, then calls the create full range position and sfs stake message. The problem is, the frontend can't know what the slippage will be on the position removal. Its usually small on the order of 1 unit, but we can't assume, and if we do then its possible the user will be left with one unit of an asset which is anoyying.

Suggested Design

Create a message that calls both of these messages in one. It uses whatever the output of the position removal as the position creation.

Acceptance Criteria

Message created and tested on localosmosis.

@MuhtasimTanmoy
Copy link

Can we have a high-level design based on the current architecture?

@czarcas7ic czarcas7ic self-assigned this Jun 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Needs Triage 🔍
Development

No branches or pull requests

2 participants