Conversation

SBF
@SBF_FTX
2) Over the next month, we'll be rolling out a bunch of improvements to FTX's matching engine. In fact we've already started.
6
266
SBF
@SBF_FTX
3) We'll be rolling out a whole new order matcher, lower latency API pathways, and a whole slew of other features. These have been in the works for most of the year. They're almost ready to release.
7
185
SBF
@SBF_FTX
4) Between a month ago and then, we should see at least: a) double the order throughput b) half the order latency
4
145
SBF
@SBF_FTX
5) We're planning to roll out some of the features over the course of the next month. But a bunch will come on November 21st, 2022. At that point, FTX: V2 will be live.
9
164
SBF
@SBF_FTX
Replying to
@SBF_FTX
7) And, finally, a huge thanks to our growing dev team: turning sleepless nights into higher order throughput and lower API latency.
54
303
Bhavya Madan
@BhavyaPnk
Replying to
@SBF_FTX
Some feedbacks: 1. Start allowing Replace/Update of orders, as of now we need to send a cancel and a new, creating 2 msgs for every time we like to update the order. Current replace methodology is not good and not usable without risks. This will cut a lot of msgs.
2
2
Bhavya Madan
@BhavyaPnk
Replying to
@BhavyaPnk
and
@SBF_FTX
2. It seems new orders and cancel orders go to different tunnels, and making it a possibility that msgs needn't be processed in the order they are sent. That's not industry standard. I would like to understand what value it adds to split them?