A new version of the FTX crypto exchange will go live on Nov. 21, featuring an improved matching engine aimed at addressing complaints from users about the performance of the current one.
“We’ll be rolling out a whole new order matcher, lower latency API pathways, a whole slew of other features,” FTX CEO Sam Bankman-Fried tweeted today.
Crypto exchanges, like other asset trading desks, use matching engines to match buy and sell orders. This process is what facilitates the buying and selling of crypto tokens on exchanges.
FTX’s matching engine has long been the subject of complaints from users. These complaints have been about the high latency and low throughput of the platform’s matching engine. Latency in the context refers to how fast the matching engine can match the buy and sell orders of users. Higher latency means slower trade execution which can be detrimental for users as profitable trading positions can be lost due to high latency.
According to Bankman-Fried, these improvements will double FTX’s order throughput while reducing the latency by 50%. He stated that these upgrades have been in the works for most of the year and are almost ready for release on the platform.
FTX suffered a downtime last month due to what Bankman-Fried described as web interface-related issues. The glitch prevented users from accessing the crypto exchange’s website in the immediate aftermath of the September U.S. consumer price index report going live.
© 2022 The Block Crypto, Inc. All Rights Reserved. This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
About Author
Osato is a reporter at The Block who likes to cover DeFi, NFTS, and tech-related stories. He has previously worked as a reporter for Cointelegraph. Based in Lagos, Nigeria, he enjoys crosswords, poker, and attempting to beat his Scrabble high score.
Source: https://www.theblock.co/post/175868/ftx-rolling-out-v2-of-the-exchange-with-new-matching-engine-in-november?utm_source=rss&utm_medium=rss