Market Microstructure

Orders are where trading systems stop sounding intelligent and start spending money. A model can narrate the market beautifully. It can explain momentum, liquidity, volatility regimes, inventory pressure, and the great moral tragedy of being early. None of that matters if the final system places the wrong limit order, sizes too aggressively, fills only in a fantasy simulator, or wins a backtest because it tried enough variants to accidentally find one that looked divine. ...

TL;DR for operators Structural filtering is useful, but not in the simple “delete noisy orders, get cleaner alpha” way. The paper tests three order-level filters — order lifetime, modification count, and modification timing — on BANKNIFTY January 2023 futures, then asks whether filtered order book imbalance better aligns with short-horizon returns.1 The diagnostic ladder is sensible: start with Pearson correlation, move to discretised OBI-return regimes, then use Hawkes excitation norms to examine whether imbalance regimes are followed by return regimes of the same sign. ...

TL;DR for operators Markowitz variance is usually treated as the clean mathematical backbone of portfolio risk. Olkhov’s paper asks a narrower and more awkward question: what if that familiar covariance formula is only what remains after trade-volume randomness has been quietly set to zero?1 The paper’s answer is mechanism-first. It constructs a buy-and-hold portfolio as if it were a synthetic single traded security. To do that, it rescales the observed market trades of each constituent so their normalised volumes match the investor’s actual holdings, then aggregates those normalised trade values and volumes into portfolio-level trade series. Once the portfolio has its own synthetic trade values $Q(t_i)$, volumes $W(t_i)$, and implied prices $s(t_i)$, its variance can be computed in the same market-based way as the variance of any single security. ...

TL;DR for operators Execution desks already know that volatility matters. The useful question is less poetic: which volatility, on what time scale, and what should the trading algorithm actually do about it? The paper by Patrick Chan, Ronnie Sircar, and Iosif Zimbidis extends the Gârleanu-Pedersen optimal trading framework from constant volatility to predictable returns, temporary transaction costs, persistent price impact, and multiscale stochastic volatility.1 That combination matters because it puts the model closer to the daily problem of a trading desk: alpha is changing, risk is changing, and the desk’s own trades are also moving the price. Delightful. The market is not merely adversarial; it is participatory. ...

TL;DR for operators Support levels are usually treated as chart objects: a line, a zone, a Fibonacci retracement, a moving average, perhaps a hand-drawn artefact with suspicious confidence. DeepSupp reframes them as latent market states: patterns in how price, volume, VWAP, and related features move together over time.1 The paper’s useful contribution is the pipeline, not the marketing-friendly phrase “AI technical analysis.” DeepSupp builds rolling Spearman correlation matrices from price-volume features, sends those matrices through a multi-head attention autoencoder, compresses them into latent embeddings, and then uses DBSCAN clustering to map dense market states back into median price levels. In plainer language: it tries to find support zones by learning how market relationships evolve, rather than by assuming that yesterday’s visual line still deserves respect. ...