Skip to content
Research · Market Microstructure

Priority Ordering in Perpetual CLOBs: Measuring the Latency Tax on Takers

A closed-form model and two-million-path simulation of stale-quote optionality

15 min readStatus · pilotVenym Labs Research
Study record/Market Microstructure
Status · pilot

Summary

A closed-form model and two-million-path simulation of stale-quote optionality

Published
Filed under
Market Microstructure
Reading time
15 min read
Sections
11
Research by
Venym Labs Research
Research is not peer reviewedvenym.io/research/priority-ordering-in-perpetual-clobs-mea…

Abstract#

A taker facing a delayed view of a central limit order book does not merely receive an old price. The taker effectively grants faster counterparties a short-lived option: stale liquidity remains available when the market moves against its maker and disappears when it becomes favorable to the taker. This paper derives a minimal closed-form value for that asymmetry. If the efficient-price innovation over latency interval τ\tau is Gaussian with volatility σ\sigma basis points per square-root second, the one-sided stale-quote cost is L(τ)=στ/(2π)L(\tau)=\sigma\sqrt{\tau/(2\pi)} basis points per exposed fill. A seeded Monte Carlo with two million draws per latency point reproduces the formula within 0.16% across 10–500 ms. Under an illustrative—not estimated—σ=4\sigma=4 bps/s\sqrt{s}, model cost rises from 0.160 bps at 10 ms to 1.128 bps at 500 ms. The result supports the square-root scaling mechanism, not a claim about realized losses on any named venue. Public trade-level timestamps, quote-cancellation events, and queue positions are required to estimate an actual latency tax.

Hypotheses#

H1 — Strong analytical support expected. Under a driftless diffusion and one-sided adverse selection, expected stale-quote optionality scales with τ\sqrt{\tau} rather than linearly with latency.

H2 — Strong numerical support expected. A direct Monte Carlo should agree with the closed form to within 0.5% using two million independent paths per grid point.

H3 — Exploratory and not identifiable from available observations. At realistic venue-specific volatility and cancellation behavior, the latency tax can equal or exceed a one-basis-point fee advantage. The model can identify break-even boundaries, but the staging data cannot establish where a production perpetual CLOB sits relative to them.

Data Provenance#

This study deliberately separates measurements from assumptions. The primary analysis is SIMULATED with NumPy 2.x using fixed seed 20260710, two million independent Gaussian innovations at each of six latency points, and an illustrative volatility of 4 bps/s\sqrt{s}. The data source for every simulated output is the included script and its saved JSON result. Closed-form values are mathematical derivations, not observations or confidence intervals.

The daily staging snapshot was collected through Venym's operational databases and contained 944,150 funding-rate records, ten recent filled trades, and cross-exchange funding snapshots from Binance, Hyperliquid, and Asterdex. Those records provide market context only. They contain no synchronized order-book messages, cancellation acknowledgements, queue positions, or packet timestamps, so they are not used to estimate latency costs. The web research bundle supplied five contextual sources, including academic work on transaction ordering and general MEV references; none supplied a venue-level causal estimate suitable for reuse here.

Input or outputProvenanceReliabilityAppropriate interpretation
L(τ)=στ/(2π)L(\tau)=\sigma\sqrt{\tau/(2\pi)}Derived closed formRELIABLE conditional on assumptionsMechanism and scaling law
Monte Carlo valuesSeeded simulation, n=2,000,000n=2,000,000 per pointRELIABLE as implementation checkNumerical validation only
σ=4\sigma=4 bps/s\sqrt{s}Illustrative sensitivity parameterUNRELIABLE for any venueScenario, not estimate
Latency grid, 10–500 msDesigned sensitivity gridUNRELIABLE as market prevalenceComparative scenarios
Realized venue latency taxNot observedUNIDENTIFIABLERequires message-level data
Funding and ten fillsInternal operational snapshotRELIABLE as logged context; irrelevant to causal estimateMotivation only

Mechanism: Latency Creates an Option#

Suppose the efficient midprice at the taker's decision time is P0P_0. The taker sees or acts on a quote whose actionable state arrives after τ\tau seconds. During that interval the efficient price changes by

ΔPτ=στZ,Z∼N(0,1),\Delta P_\tau = \sigma\sqrt{\tau}Z, \qquad Z\sim\mathcal N(0,1),

where price changes are expressed in basis points. Consider a buy order hitting a stale ask. If the efficient price has risen, the stale ask is valuable to the buyer but costly to the liquidity supplier; fast cancellation races determine whether the quote survives. If the efficient price has fallen, the stale ask is unattractive to the buyer. A deliberately conservative abstraction values only the positive half of the innovation:

L(τ)=E[max⁡(ΔPτ,0)].L(\tau)=\mathbb E[\max(\Delta P_\tau,0)].

For a centered normal variable, the first partial moment is E[max⁡(Z,0)]=1/2π\mathbb E[\max(Z,0)]=1/\sqrt{2\pi}. Therefore

L(τ)=στ2π.\boxed{L(\tau)=\frac{\sigma\sqrt{\tau}}{\sqrt{2\pi}}.}

This is not a complete execution-cost model. It is the gross option value created by delayed state under maximal one-sided selection. A participation factor q∈[0,1]q\in[0,1] can represent the fraction of exposed opportunities in which fast agents or cancellation logic actually impose the asymmetry:

Lrealized(τ)=q στ2π+cimpact+cfees.L_{\text{realized}}(\tau)=q\,\sigma\sqrt{\frac{\tau}{2\pi}} + c_{\text{impact}} + c_{\text{fees}}.

Here qq, market impact, and fees are venue- and order-specific. They are UNIDENTIFIABLE from the staging snapshot.

The essential point is asymmetry. Symmetric stale prices could average to zero around the efficient mid. Selective survival does not.

Numerical Cross-Check#

The following exact experiment generated the reported results. It avoids fitted parameters and records both the analytic result and simulation error.

python
import numpy as np

rng = np.random.default_rng(20260710)
n = 2_000_000
sigma = 4.0
latencies_ms = np.array([10, 25, 50, 100, 250, 500])

for ms in latencies_ms:
    tau = ms / 1000
    moves = rng.normal(0, sigma * np.sqrt(tau), n)
    simulated = np.maximum(moves, 0).mean()
    closed_form = sigma * np.sqrt(tau / (2 * np.pi))
    error_pct = 100 * (simulated / closed_form - 1)
    print(ms, closed_form, simulated, error_pct)
LatencyClosed-form cost (bps)Simulated cost (bps)Relative error
10 ms0.1595770.159448-0.0808%
25 ms0.2523130.252356+0.0168%
50 ms0.3568250.356700-0.0350%
100 ms0.5046270.503857-0.1524%
250 ms0.7978850.797362-0.0655%
500 ms1.1283791.129356+0.0866%

H2 is supported as a code-validation statement: the maximum absolute discrepancy is 0.1524%, below the prespecified 0.5% threshold. This is not a statistical test of market behavior. The simulation was constructed from the same stochastic assumptions as the derivation, so agreement catches implementation errors but cannot validate Gaussian diffusion, independence, or selective cancellation in a live order book.

The Square-Root Law and Its Consequences#

Doubling latency does not double the modeled option value; it multiplies it by 2\sqrt{2}. Cutting latency from 100 ms to 25 ms halves the gross option value because the interval falls by a factor of four. This produces an important engineering implication: early latency reductions are valuable, but marginal returns decline in absolute time units.

For two traders with latencies τs\tau_s and τf\tau_f, the modeled difference is

ΔL=σ2π(τs−τf).\Delta L=\frac{\sigma}{\sqrt{2\pi}}\left(\sqrt{\tau_s}-\sqrt{\tau_f}\right).

At the illustrative volatility, moving from 250 ms to 50 ms reduces gross stale-quote exposure by 0.441 bps per selected fill. Moving from 50 ms to 10 ms reduces it by 0.197 bps. Neither number is an expected strategy return: fill probability, impact, fees, failed transactions, and the participation factor remain absent.

A one-basis-point fee rebate supplies a useful break-even sensitivity. Setting L(τ)=1L(\tau)=1 bp gives

σ∗(τ)=2πτ bps/s.\sigma^*(\tau)=\sqrt{\frac{2\pi}{\tau}}\text{ bps}/\sqrt{s}.
LatencyBreak-even σ∗\sigma^* for 1 bp gross option valueReliability
25 ms15.8533 bps/s\sqrt{s}RELIABLE algebra; UNRELIABLE venue application
50 ms11.2100 bps/s\sqrt{s}RELIABLE algebra; UNRELIABLE venue application
100 ms7.9267 bps/s\sqrt{s}RELIABLE algebra; UNRELIABLE venue application
250 ms5.0133 bps/s\sqrt{s}RELIABLE algebra; UNRELIABLE venue application

Thus H3 remains unresolved. The boundary is explicit, but whether a particular market crosses it depends on correctly sampled subsecond efficient-price volatility and the realized selection factor qq. Annualized volatility is not a safe substitute because microstructure noise, jumps, and serial dependence distort square-root-of-time scaling at millisecond horizons.

What a Real Measurement Requires#

A production study should reconstruct each order's information set at decision time and execution time. At minimum it needs synchronized exchange timestamps and local receive/send timestamps, full-depth book updates, trade prints, order acknowledgements, cancellations, and a defensible efficient-price proxy. The causal target for buy order ii could be

Ci=104Pifill−Mi,t+δMi,t+δ,C_i = 10^4\frac{P_i^{\text{fill}}-M_{i,t+\delta}}{M_{i,t+\delta}},

with the sign reversed for sells, where Mi,t+δM_{i,t+\delta} is a future midpoint after a fixed markout horizon. Latency buckets should be assigned before examining outcomes. A credible design would compare matched orders by symbol, side, size, spread, volatility, queue depth, and time of day, then report clustered uncertainty by market and session.

The study should also distinguish three channels: stale-state losses suffered by slow takers, queue-priority losses from arriving later, and adverse-selection losses imposed on slow makers. Combining them into a single average conceals who owns the option and when.

Discussion#

Robust findings#

The partial-moment derivation is exact under its assumptions. Gross one-sided stale-price optionality scales with subsecond volatility and the square root of latency. The simulation reproduces that result across the designed grid. The break-even expression also provides a transferable way to compare a fee advantage with latency exposure without inventing a live-market estimate.

Preliminary findings#

The scenario table suggests that hundreds of milliseconds can matter economically during high subsecond volatility. That statement is conditional. The illustrative 4 bps/s\sqrt{s} value was selected for sensitivity analysis, not inferred from Hyperliquid, Binance, Asterdex, or another venue. The 944,150 funding observations confirm a rich derivatives environment but say nothing about millisecond ordering or selective quote survival.

Not supported#

This paper does not support a claim that validators, sequencers, market makers, or any named venue extract a stated number of basis points. It does not show that faster execution is profitable after infrastructure expense. It does not estimate qq, impact, fill probability, or queue priority. It also does not establish a risk-adjusted strategy metric; no such ratio is reported because the available data cannot support one responsibly.

Limitations#

The model assumes driftless Gaussian innovations, constant volatility inside each latency interval, and a stark one-sided selection rule. Real perpetual books have jumps, discrete ticks, clustered volatility, hidden or aggregated liquidity, maker cancellation races, self-trade prevention, matching-engine batching, rate limits, and endogenous order submission. Clock error can be the same magnitude as the latency being estimated. The Monte Carlo validates code against a derivation built from identical assumptions, so it is not independent empirical confirmation. Internal funding observations and ten fills are not message-level microstructure data and cannot identify causal latency effects. Results should not be generalized to other exchanges or venues without re-validation, and especially not from Binance, Hyperliquid, or Asterdex funding snapshots to their execution engines. A credible estimate needs synchronized event data, multiple volatility regimes, prespecified markout horizons, and out-of-sample replication.

Conclusion#

Latency in a priority-ordered perpetual CLOB can be valued as optionality rather than treated as an abstract infrastructure metric. In the minimal model, the gross tax is στ/(2π)\sigma\sqrt{\tau/(2\pi)}, making volatility and square-root latency the sufficient inputs. Two million seeded paths per latency point reproduce the formula within 0.16%, satisfying the numerical hypothesis. The paper's original contribution is a compact break-even framework linking latency to basis-point economics while keeping parameter reliability explicit.

What this paper is: a reproducible pilot model and measurement blueprint. What it is not: evidence of realized extractable value on Hyperliquid or any other specific venue. The next step is not a more elaborate simulation; it is synchronized order-level data capable of estimating selective survival, queue loss, and post-fill markouts out of sample.

References#

  1. Daian, P. et al. (2020). “Flash Boys 2.0: Frontrunning in Decentralized Exchanges, Miner Extractable Value, and Consensus Instability.” IEEE Symposium on Security and Privacy.
  2. Adams, H. et al. (2024). “The Dark Side of the Mempool.” arXiv:2407.19572. Contextual source supplied by the research bundle.
  3. Zhang, K. (2024). Research on blockchain transaction ordering and extractable value. ÉTS Montréal. Contextual source supplied by the research bundle.
  4. Chainlink Education Hub. “Maximal Extractable Value (MEV).” Accessed through the 2026-07-10 research bundle.
  5. Venym Labs. scripts/analysis/2026-07-10-latency-tax.py and 2026-07-10-latency-tax-results.json, seeded reproducibility artifacts.
Venym Labs ResearchReturn to the archive

From research to a working system

A better question. A tested answer.

Bring the system, the constraint or the question. We will work out what the evidence needs to show.

New message
ToVconnect@venym.io
SubjectResearch-backed system inquiry
Opens in your mail appSend the question