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

Users unable to pass approval step in LINK asym pool deposits #6775

Closed
purelycrickets opened this issue Apr 29, 2024 · 12 comments
Closed

Users unable to pass approval step in LINK asym pool deposits #6775

purelycrickets opened this issue Apr 29, 2024 · 12 comments
Labels
bug Something isn't working needs engineering Requires engineering input before bounty

Comments

@purelycrickets
Copy link

Overview

Currently in production, Users are unable to get past the approval section in an asym deposit of LINK into a pool. The user is continually prompted to approve and can continually spend gas on approvals without error messages or being able to move forward to their desired action.

References and additional details

Screen recording of the approval flow coninually prompting:
https://github.com/shapeshift/web/assets/94998097/21d6a13f-7c0d-43e8-b4b9-d6e3d8032207

Previous recording was too long to upload, heres a screenshot of the multiple approvals paid without the flow continuing:

Screenshot 2024-04-29 at 3 31 47 PM

Acceptance Criteria

Users are able to complete the desired flow of LINK asym deposits, or ShapeShift is able to handle errors experienced upstream in TC that could block users from coniuning their desired action.

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

@purelycrickets purelycrickets added bug Something isn't working needs engineering Requires engineering input before bounty labels Apr 29, 2024
@0xApotheosis
Copy link
Contributor

@purelycrickets did I hear you mention that you were able to replicate this on the THORSwap UI as well?

@gomesalexandre
Copy link
Contributor

gomesalexandre commented Apr 30, 2024

@purelycrickets I wasn't able to repro on THORSwap nor in the app - is this still happening?

link.mov

Gut feel if this was happening both with us and THORswap is there may have been an upstream issue re: inbound addresses rotation, it would help to see at least two of those Txids to see if they approved LINK for the same spender.

@gomesalexandre
Copy link
Contributor

Last one looks like it's not related to THOR and was probably inluded by mistake, but all the others look sane to me and approved the same contract as spender.

Unless this is reproducible in prod currently and after the THOR consolidation PR, I would probably disregard THORSwap having the same issue (doesn't look like anything's wrong here Tx-wise) and assume we had some shenanigans on allowance checks which are now fixed, close this, and possibly reopen if that ever happens again and ops can consistently repro @purelycrickets

@RussellJBennett
Copy link

This issue is persistent and repeatable. Every time. It is NOT resolved. Please acknowledge.

@RussellJBennett
Copy link

Screenshot 2024-05-01 at 19 02 35

@RussellJBennett
Copy link

I just tried to deposit LINK into the Pool again. I'm using a Trezor One to connect and transact.

Earlier just now, I deposited into the BTC/RUNE Pool without any issue. There is a conflict with only LINK when I try it. I've been successful before. My last LINK deposit was on 27 APR.
Screenshot 2024-05-01 at 19 09 51

@purelycrickets
Copy link
Author

purelycrickets commented May 6, 2024

I just tried to deposit LINK into the Pool again. I'm using a Trezor One to connect and transact.

Earlier just now, I deposited into the BTC/RUNE Pool without any issue. There is a conflict with only LINK when I try it. I've been successful before. My last LINK deposit was on 27 APR. Screenshot 2024-05-01 at 19 09 51

Hey @RussellJBennett are you trying on ShapeShift? It appears you are sharing screenshots from Thorswap, an app we have no control over the codebase of.

@RussellJBennett
Copy link

RussellJBennett commented May 6, 2024 via email

@purelycrickets
Copy link
Author

"If it doesn’t work in THORswap, why would we expect a different result in Shapeshift?"

Thorswap and ShapeShift are two separate front end interfaces. We manage ShapeShift, another team manages Thorswap. Both teams have integrated THORchain, however the code bases are different and we do not have the ability to control the code at Thorswap.

We believe the issue will be resolved if you attempt the action at ShapeShift. You may want to open up the issue with THORswap if you wish to see the issue fixed there as well.

@RussellJBennett
Copy link

Don't "believe the issue will be resolved if you attempt the action at ShapeShift" Test it. Then show me evidence it's resolved. I'm not interested in being a beta tester for ShapeShift's front end.

@RussellJBennett
Copy link

ShapeShift has resolved this issue. Please close my incident. Thx, Russell

@0xean 0xean closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs engineering Requires engineering input before bounty
Projects
Status: Done
Development

No branches or pull requests

5 participants