-
Notifications
You must be signed in to change notification settings - Fork 212
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
As a trader, I need to swap one token for another #5073
Comments
Looks like the dapp doesn't currently do this, it just loads the price when you select an asset. It could be annoying when you're entering a number and the rate constantly updates and changes your inputs, so my proposal is to debounce the price update until after you stop typing for a certain duration. Then, update whichever input that you didn't most recently type into to reflect the new exchange rate |
Looks like slippage is a bit buggy as well. It doesn't update the "receive at least" when you modify it. |
@samsiegart wrote:
After I added 25 RUN / 25 USDC of liquidity, I was able to swap 1 RUN for 1 USDC with 5% slippage tolerance. I would close this except that I don't see an UI for this part:
|
@rowgraus , as noted above, @samsiegart and I both tested basic "I need to swap one token for another" stories. I presume the "I would like to know how much my trade will impact the price in the pool" part is not critical. To make it easier to see that not all of the details in the description have been tested, I made it into a checklist and checked the parts that we tested. In at least one case (#5019) the unfinished parts are tracked in other issues. Feel free to open issues for the other sub-items... or if you prefer, go ahead an re-open this. |
re-opening for smart wallet integration |
hey! it can be done! some rough edges:
one user's journey:
|
I think changes to the smart wallet API mean this doesn't quite work any more. |
I think this is no longer planned. If it is, @otoole-brendan please re-open and update the body with what's left to do. |
The text was updated successfully, but these errors were encountered: