Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/69231819-359c-8007-85e5-e9b0981ed9f1
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== ✅ Why HFTs Can’t Predict Flash Crashes (Even Though They Watch the Order Book) === ==== 1. The order book becomes sparse or incoherent faster than models can update ==== Flash crashes aren’t smooth declines. They involve: * sudden liquidity withdrawal * simultaneous cancellation of thousands of quotes * no one taking the other side * market makers backing off together When the order book collapses, all the signals used in microstructure prediction stop being statistically stable. This is like trying to steer a car when the wheels suddenly detach. ==== 2. Feedback loops amplify tiny moves beyond predictive ranges ==== HFT systems often share similar triggers: * inventory boundaries * volatility thresholds * risk-off cutouts * “kill switches” When volatility spikes beyond a certain threshold: 👉 they all pull liquidity at once 👉 the spread widens massively 👉 the price jumps through empty space This self-reinforcing loop becomes chaotic, not predictable. HFTs don’t fail individually— the entire ecosystem becomes reflexive, like a stampede. ==== 3. Order flow becomes dominated by cancellations, not submissions ==== Normal prediction uses: * limit order arrival rate * market order aggressiveness * replenishment behavior * queue dynamics In a flash crash, the dominant action is: CANCELLATION → not predictable like order flow. You can model arrivals; you cannot meaningfully model panicked simultaneous withdrawals with microstructure tools. ==== 4. Latency arbitrage changes regime under stress ==== During stable markets: * HFTs exploit small delays between markets * that contributes to predictability During crashes: * prices dislocate between venues * latencies spike * matching engines slow * data feeds desync The whole latency-arbitrage framework breaks, destroying the foundation of HFT predictions. ==== 5. Hidden toxicity measures spike unpredictably ==== Market makers estimate toxicity using: * VPIN * order flow imbalance * short-term volatility * trade classification But when toxicity goes vertical (say, from a large hidden parent order or an algo gone wrong), models blow up. Toxicity is predictable in normal conditions— catastrophic toxicity is not. ==== 6. Exogenous shocks are faster than the prediction cycle ==== Many flash crashes start with: * a fat-finger order * a broken execution algo * a huge liquidation * a news headline * a regulatory halt * a cross-venue liquidity cascade No amount of microstructure can predict an external shock occurring in milliseconds.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)