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
When users asymmetrically add or remove liquidity they incur slippage because they execute a swap and then pool symmetrically. This removes the total value they own but they are unaware. Multiple investors have complained about this but we have not yet clearly indicated it, which is a good sign that the project would not be ready for larger whales to pool asymmetrically after a mainnet.
Describe the solution you'd like
Post a text warning for any asymmetric liquidity adds or removals indicating that the user will execute a swap followed by a symmetrical add or withdrawal. Note that this will incur swap fees and slippage.
Describe alternatives you've considered
We could also actually show users how each step works so they can see how much they'd give up in slippage prior to a swap. (Would take more time)
Additional context
let's get this done before mainnet
The text was updated successfully, but these errors were encountered:
Is your proposal related to a problem?
When users asymmetrically add or remove liquidity they incur slippage because they execute a swap and then pool symmetrically. This removes the total value they own but they are unaware. Multiple investors have complained about this but we have not yet clearly indicated it, which is a good sign that the project would not be ready for larger whales to pool asymmetrically after a mainnet.
Describe the solution you'd like
Post a text warning for any asymmetric liquidity adds or removals indicating that the user will execute a swap followed by a symmetrical add or withdrawal. Note that this will incur swap fees and slippage.
Describe alternatives you've considered
We could also actually show users how each step works so they can see how much they'd give up in slippage prior to a swap. (Would take more time)
Additional context
let's get this done before mainnet
The text was updated successfully, but these errors were encountered: