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 he tries to update the slippage, the system says: “Must update slippage with delegate” because he was trying with the initiator address.
If you go to li.fi explorer says that the Destination wallet is: 0x0806e8bebd0ba58834fa2655e0613555945120d3 (the gnosis pay multi-sig).
The main issue here is that he can't import that seed or manually put the call data in the safe app and finally update the slippage, the user is unable to control it.
So, what are the options here?
Could the user expect a lower slippage? It doesn't seem like an option, I believe that the big slippage comes from Base (5k liquidity) instead of Gnosis (we already have 250k usdc there, so idk if it will go down enough to decrease it under 0,5%)
Forcing to receive NEXT assets? I think this option is also blocked since he doesn't control the destination address, but please lmk if I'm wrong.
I honestly don't know how to help him lol, any ideas?
**PS: note that the pop-up says
"New slippage tolerance (recommended): 0.6 %
Slippage tolerance is too low
Estimated: 4.66%
(use a larger amount or set tolerance higher)**
Describe the bug
User sent USDC from Base to Gnosis.
He used jumper and since he is trying to fund his gnosis pay card, he is using a Gnosis pay multi-sig in a limited environment.
https://connextscan.io/tx/0x2990b20457d62339f0bcf18f4fb8fc6eb1bb43d395518803580657e9cf87b929
When he tries to update the slippage, the system says: “Must update slippage with delegate” because he was trying with the initiator address.
If you go to li.fi explorer says that the Destination wallet is: 0x0806e8bebd0ba58834fa2655e0613555945120d3 (the gnosis pay multi-sig).
The main issue here is that he can't import that seed or manually put the call data in the safe app and finally update the slippage, the user is unable to control it.
So, what are the options here?
Could the user expect a lower slippage? It doesn't seem like an option, I believe that the big slippage comes from Base (5k liquidity) instead of Gnosis (we already have 250k usdc there, so idk if it will go down enough to decrease it under 0,5%)
Forcing to receive NEXT assets? I think this option is also blocked since he doesn't control the destination address, but please lmk if I'm wrong.
I honestly don't know how to help him lol, any ideas?
**PS: note that the pop-up says
"New slippage tolerance (recommended): 0.6 %
Slippage tolerance is too low
Estimated: 4.66%
(use a larger amount or set tolerance higher)**
Where did the user initiate this transfer?
Jumper
Link to ticket
https://app.intercom.com/a/inbox/qge2vd8z/inbox/shared/all/conversation/1583?view=List
@oncall
The text was updated successfully, but these errors were encountered: