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
Swaps that fail are not recognized by the GUI. This has been a change from mm1.0; in mm1.0 there wasn't a clear way to tell that a swap had failed.
In mm2.0 however, using the my_swap_status API call, there is a way to find out if something has failed.
As an example, I tried to swap 1 CHIPS for KMD. On the taker side (the HyperDEX app), the order stays in the Open Orders screen, with a matched label:
However, when I open one of the 2 failed swaps in the screenshot, I see this ugly error message:
The app should be able to recognize that the swap has failed, by issuing a my_swap_status call and look for events that are labeled [...]Failed, like the following example (this is the maker side of the same swap):
Swaps that fail are not recognized by the GUI. This has been a change from mm1.0; in mm1.0 there wasn't a clear way to tell that a swap had failed.
In mm2.0 however, using the
my_swap_status
API call, there is a way to find out if something has failed.As an example, I tried to swap 1 CHIPS for KMD. On the taker side (the HyperDEX app), the order stays in the Open Orders screen, with a
matched
label:However, when I open one of the 2 failed swaps in the screenshot, I see this ugly error message:
The app should be able to recognize that the swap has failed, by issuing a my_swap_status call and look for events that are labeled
[...]Failed
, like the following example (this is the maker side of the same swap):The type of this event ends with Failed.
So 2 things need fixing here:
The text was updated successfully, but these errors were encountered: