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
The existing taker events only include information about the maker account and order, and not the taker.
The taker receives no event to confirm that their order was successfully placed and filled when it is successful. Consequently, it is impossible to send order status updates for taker orders on the WebSocket API, which most exchange APIs offer.
A future version of the move code should either include this information, or alternatively, if we go with #146, emit separate events to both the maker account and the taker account, including the fields that are relevant to the respective user.
The text was updated successfully, but these errors were encountered:
The existing taker events only include information about the maker account and order, and not the taker.
The taker receives no event to confirm that their order was successfully placed and filled when it is successful. Consequently, it is impossible to send order status updates for taker orders on the WebSocket API, which most exchange APIs offer.
A future version of the move code should either include this information, or alternatively, if we go with #146, emit separate events to both the maker account and the taker account, including the fields that are relevant to the respective user.
The text was updated successfully, but these errors were encountered: