Why High-Frequency Traders Rapidly Cancel Limit Orders
Summary
The document discusses why high-frequency traders submit and quickly cancel limit orders. One explanation is routine event-driven market making: algorithms update quotes as order-book events change their estimate of fair value, producing frequent cancellations relative to fills. Other answers describe possible strategic uses, such as probing order-book responses, exploiting other algorithms’ reactions, or investigating exchange latency, while stressing that deliberate manipulation is not necessarily widespread.
The examples include order-book imbalance signals and an anecdotal account of fleeting displayed size influencing other algorithms and creating short-lived scalping opportunities. The discussion also mentions execution delays or call auctions as possible ways to reduce speed advantages. These claims are mixed in evidential strength: the accepted explanation is general, while several hypotheses are personal observations or speculation. The document does not establish how prevalent such behavior is today or whether slower traders are systematically exploited.
Key ideas
- Event-driven market makers update quotes as order-book events change their estimates of fair value.
- Rapid quote revisions can create a high cancellation-to-fill rate without implying manipulation.
- Displayed liquidity may influence algorithms that react to order-book size or imbalance.
- Quote stuffing and deliberate exploitation are proposed explanations, but the discussion does not establish their prevalence.
- Execution delays and call auctions are suggested as ways to reduce speed advantages.
Tags
Full text
# Why do high frequency traders use rapidly cancelled limit orders? # Why do high frequency traders use rapidly cancelled limit orders? In reading about the various practices and strategies of high frequency traders, one of the most mysterious to me is "fleeting orders," or orders that are cancelled almost immediately after they are sent (see Hasbrouck and Saar (2011)). Why do HFTs use these orders? Some of those trying to explain the practice claim it gives HFTs an informational advantage. How? What information do they get and how do they use it? Update I am hoping for someone with actual experience in HFT to answer and verify some of the hypotheses laid out by academics. In particular, one hypothesis is that rapidly cancelled limit orders bring forth market orders on the other side, which are then executed at a less favorable price also placed by the HFT. In other words, HFTs are gaming the system to exploit sub-optimal behavior by slower traders. Is there any evidence of this still occurring, now that the practice of fleeting orders is widespread and well known? This explanation would also imply that it is relatively simple to avoid being taken advantage of, thus weakening the policy implications. Is there some reason that slower traders prefer sending market orders only after seeing a limit order meeting their price target? ## Answer by Louis Marascio (score 21, accepted) https://quant.stackexchange.com/a/1854 All HFTs are event driven. In the most basic sense, they have some model that is a function of order book events. For every order book event the model calculates some micro price that is the HFTs perceived fair value. This is often a function of the current bid, ask, depth, last n trade prices, inventory, etc. Given the most up to date view of fair value, the HFT will be adjust orders in the market. As you can imagine, the rate of events for order book data is very high. This results in a very high scratch rate (cancel to fill ratio) because the HFT is adjusting their orders at a rate similar (but not equal to) the event arrival rate for a given stock. The likelihood that there are shenanigans going on is non-zero. However, the use of said shenanigans is not wide spread, IMO. ## Answer by stevegt (score 8) https://quant.stackexchange.com/a/3070 My favorite culprit is quote stuffing, which can be used for a lot of things, including mapping the topology of the exchange servers themselves. The general idea is to look for bottlenecks which can then be lagged with more targeted quote-stuffing to create arb opportunities. Nanex's flash crash analysis covers this to some extent: http://www.nanex.net/20100506/FlashCrashAnalysis_Intro.html The only thing I've heard or thought of to deal with this arms race is either built-in execution delays or going back to session-based call auctions rather than continuous. In either case, a 1 second delay or a 1 second call auction session would level the playing field in terms of speed of light (and might reduce data center rates in Brooklyn). ;-) ## Answer by Aravind (score 1) https://quant.stackexchange.com/a/7360 Based on my experience trading DJ Eurostoxx 50 (FESX), the HFTs place and delete the orders almost immediately to fool other algorithms which are based on limit order quantity at various prices. I have used a technique to scalp of a few ticks when such a phenomena occurs. For instance if the HFt places an order for 1000 lots at 2000 and immediately it disappears, but the market price moves up and down by a few ticks. This is because other algorithms are designed to operate on certain order imbalance etc. Hence if I see a huge order on bid side, I used to sell some lots and immediately scalp off a a couple ticks. I used to do this and make some money during such hours. This stuff mostly happened during dull hours. My 2 cents. ## Answer by AlgoQuant (score 0) https://quant.stackexchange.com/a/7364 For example, high frequency market makers use all the market microstructure to take decisions of how many stocks put in each side. This microstructure can be a 5 level data (ten prices, 5 bids and 5 asks with the quote amount or quantity) so they calculate and quantify the order book imbalance or other type of measure of the supply/demand of the order book. To modify the market they post some limit orders and send orders in different prices to try to balance the book order and also because they use this type of orders for the risk management of the strategy.
Shown in full with attribution under the source's licence. Licence: CC BY-SA 4.0 (Stack Exchange)
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.