You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: