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
After the sent has been made, we need to take the transaction receipt and show the information about the status of the swap to the user, telling how much confirmations are needed, and a link to the etherscan / swingby explorer
The text was updated successfully, but these errors were encountered:
I'm putting this on hold as I need some clarifications regarding how the waiting status is going to be threatened on the side of the nodes. Relevant information about how the status is generated can be found in this diagram:
From what I understood: we have a missing status that's currently now inside the "Waiting" status. It has to be split into: "waiting for tx to be executed" and "awaiting transfer" or something like this. Now when the transaction is not executed on the blockchain and when it is executed on the blockchain but it's waiting to be taken by the swingby nodes to process the swap, they are the same status: "Waiting".
We need to discuss internally what the approach we are going to do is gonna be: either to add the missing status directly on the frontend (which will add a lot of technical debt, as the current implementation is based 100% on the status of the nodes). Or we do the "proper" way which should be updating the status from the nodes.
After the sent has been made, we need to take the transaction receipt and show the information about the status of the swap to the user, telling how much confirmations are needed, and a link to the etherscan / swingby explorer
The text was updated successfully, but these errors were encountered: