Currently, only the WebSocket servers for Spot and Perpetual Futures return an ID when subscribing to a channel (as stated in the gateio documentation).
However, the Delivery Futures WebSocket server does not send back an ID or the payload in the subscribe response => no mapping possible. This makes it impossible to properly create automated trading tools for the delivery futures on gateio!
Analyzing the code, it looks to me that currently an old implementation is used for the Delivery Futures. Is it planned to be migrated into this codebase in the near future? If not, I would recommend a small update to add the request-id to the response for subscribe and unsubscribe events.
Please let me know if I should open the issue in the old repository as well.
Currently, only the WebSocket servers for
Spot
andPerpetual Futures
return an ID when subscribing to a channel (as stated in the gateio documentation).However, the
Delivery Futures
WebSocket server does not send back an ID or the payload in the subscribe response => no mapping possible. This makes it impossible to properly create automated trading tools for the delivery futures on gateio!Analyzing the code, it looks to me that currently an old implementation is used for the
Delivery Futures
. Is it planned to be migrated into this codebase in the near future? If not, I would recommend a small update to add the request-id to the response for subscribe and unsubscribe events.Please let me know if I should open the issue in the old repository as well.