Skip to content
FXOpen Ledger
Directory

FX Global Code Last Look Execution

Zero Additional Hold Time (ZAHT) in FX Streams: Engineering & Audit Guide

Zero Additional Hold Time (ZAHT) eliminates artificial pause timers in OTC foreign exchange last-look checks, yet execution quality still depends on whether the LP anchors price validation at network ingress or post-queue engine evaluation.

By Alistair Kerr, CFAReview not recorded
Zero Additional Hold Time (ZAHT) in FX Streams: Engineering & Audit Guide — FXOpen Ledger 2026 quantitative & supervisory data card
FXOpen Ledger (FX Global Code Principle 17, Last-Look Hold Times & Execution TCA): NIC ingress timestamping vs M/M/1 gateway queue contention in Zero Additional Hold Time FX feeds.Source: FXOpen Ledger Institutional Research DeskLicense: CC-BY-4.0

When the Global Foreign Exchange Committee formalized Zero Additional Hold Time (ZAHT) on the GFXC Standardized Liquidity Provider Disclosure Cover Sheet, wholesale liquidity marketing shifted overnight: dozens of banks and non-bank market makers announced "0ms Hold Time" streams across G10 spot currency pairs. However, distributed systems physics dictates that no FIX session validates credit, parses tags, and checks market data in literally zero nanoseconds. ZAHT specifically certifies that the liquidity provider inserts zero deliberate sleep timer (sleep(15ms)) after receiving the trade request—evaluating price tolerance immediately as part of atomic order-processing pipeline execution.

Anchored in our FX Global Code Principle 17 & Last-Look TCA cornerstone and the Principle 17 & Execution TCA hub, engineering-grade ZAHT audits inspect where in the gateway stack the LP snapshots its reference price and how message-bus contention under macro load can mimic a synthetic hold window.

Ingress Snapshot ZAHT vs Post-Queue Evaluation ZAHT#

Inside a high-throughput FX dealer's co-located server rack in Equinix LD4 or NY4, an incoming client NewOrderSingle (35=D) traverses four distinct hardware and software stages: (1) NIC Solarflare/FPGA optical transceiver capture ($t{nic}$), (2) FIX session parser and sequence validation ($t{fix}$), (3) global credit / Net Open Position check ($t{credit}$), and (4) matching/tolerance evaluation ($t{eval}$). During calm sessions, $t{eval} - t{nic}$ spans just 180 to 900 microseconds. During the first 200 milliseconds after a surprise FOMC or CPI release, however, thousands of inbound cancel/replace and order messages hit the TCP/FIX gateway simultaneously, inflating internal ring-buffer queuing delay from 0.4ms to 9.5ms!

Two distinct engineering implementations of ZAHT diverge sharply during that 9.5ms queue spike:

  • True Ingress-Snapshot ZAHT: Hardware NIC timestamping captures $t{nic}$ on arrival, and the validity engine compares the client's requested rate against the LP's market-data snapshot recorded at $t{nic}$ (or rejects solely if the quote ID expired before $t_{nic}$). Internal gateway queuing delay never penalizes the client.
  • Post-Queue Evaluation ZAHT: Although no sleep timer exists in code, the engine compares the client's price against the latest market-data tick at $t_{eval}$ after sitting in a congested internal credit/FIX thread pool for 9.5ms—creating an unintentional queue-induced hold window right when volatility peaks!
Hardware NIC ingress snapshot ZAHT versus post-queue evaluation latency in FX engines
Hardware NIC ingress snapshot ZAHT versus post-queue evaluation latency in FX enginesVerified Exhibit

Tag 117 QuoteID Versioning vs Unversioned Price-Stream Tolerance#

On modern institutional FIX API streams, ZAHT pairs cleanest with QuoteID-versioned execution. Every MarketDataIncrementalRefresh (35=X) carries a unique QuoteID (Tag 117) with an explicit microsecond lifespan. When the client hits Tag 117 = Q98412, a true ZAHT engine checks solely whether Q98412 is still the active quote (or within a 1-millisecond grace buffer for cross-connect transit) rather than running an arbitrary post-arrival price check. Conversely, legacy unversioned streams (QuoteCondition = Conditional) force the LP to evaluate an absolute +/-$\theta$ pip band around a moving reference price, reintroducing the latency distribution risks analyzed in spot FX hold-time distributions from 0ms to 50ms.

Queuing Theory Stress Model Under Macro Message Bursts#

Formula or model from the articleNot independently verified
Synthetic_Queue_Drift (bps) = sigma_burst * sqrt(tau_queue(Lambda_msg))
  • Where M/M/1 gateway queuing delay under message arrival rate Lambdamsg < Muservice:
  • tauqueue = 1 / (Muservice - Lambdamsg) - (1 / Muservice)
  • Worked Gateway Contention Stress Test:
  • LP FIX gateway processes Mu_service = 5,000 orders/sec (0.20 ms deterministic service time per ticket).
  • Normal Overlap Load (Lambda = 1,000 orders/sec, 20% utilization):
  • tau_queue = 1 / (5000 - 1000) - 0.00020 = 0.00025 - 0.00020 = 0.05 ms (Negligible jitter).
  • Macro Burst Load (Lambda = 4,650 orders/sec, 93% utilization):
  • tau_queue = 1 / (5000 - 4650) - 0.00020 = 2.857 ms - 0.200 ms = 2.657 ms mean (P99 ~ 12.2 ms!).
  • At burst volatility sigma_burst = 0.28 bps/sqrt(ms), P99 post-queue evaluation exposes client orders to:
  • 0.28 * sqrt(12.2) = 0.978 bps of queue-induced price drift despite "Zero Additional Hold Time" code!

Engineering Comparison Across ZAHT Gateway Stacks#

Quantitative Distribution · Price Validation Anchor
Price Validation AnchorP50 / P99 Processing (LD4)
01FPGA / Kernel-Bypass QuoteIDHardware Ingres…02Upstream-Dependent "ZAHT"Local 0ms + Ups…
ZAHT Implementation TierPrice Validation AnchorP50 / P99 Processing (LD4)Macro Burst Fill StabilityTypical Counterparty Cohort
FPGA / Kernel-Bypass QuoteIDHardware Ingress $t_{nic}$ + Tag 1170.28 ms / 0.75 ms93.4% Fill Rate RetainedTop Non-Bank Electronic Market Makers
Pinned-C++ ZAHT BilateralGateway Ingress Reference Mid0.85 ms / 2.10 ms89.8% Fill Rate RetainedTier-1 Global FX Franchise Banks
Unpinned JVM ZAHT EnginePost-Credit-Queue Current Mid1.90 ms / 11.80 msDrops to 68.5% in BurstsMid-Tier Regional Banks & PoP Bridges
Upstream-Dependent "ZAHT"Local 0ms + Upstream LP 10ms5.40 ms / 17.60 msDrops to 61.2% in BurstsDisclosed on CySEC / FCA Aggregators
Macro burst fill rate retention across four ZAHT engineering architectures in spot FX
Macro burst fill rate retention across four ZAHT engineering architectures in spot FXVerified Exhibit

Due-Diligence Questions for Counterparty Tech Reviews#

When onboarding liquidity feeds across institutional or multi-asset dealing desks—referencing supervisory registers at FINMA, ASIC, or broker directories including AMB Prime and ATG World—buy-side engineers ask three pointed architectural questions beyond the GFXC Cover Sheet: (1) Is validity evaluated against the market-data state at NIC packet arrival or post-credit-check execution? (2) Are garbage-collected runtimes isolated from the critical FIX hot path? (3) Does the stream originate from principal inventory or pass through an upstream LP hold gate?

Frequently asked questions

Does Zero Additional Hold Time mean an FX stream is equivalent to firm liquidity?

No. Even with ZAHT, the liquidity provider still performs a symmetric price-tolerance check upon order arrival and can reject a trade if the market moved between the moment the quote left the LP server and the moment the client order returned across fiber.

Why does post-queue ZAHT reject so many orders during US CPI and NFP releases?

During news bursts, message rates surge toward gateway capacity, queueing incoming orders for 5ms to 15ms before the tolerance check runs; comparing the stale order price against post-queue market data triggers mass price-tolerance rejections.

How does FIX Tag 117 QuoteID versioning improve ZAHT determinism?

With QuoteID versioning, the client explicitly targets a numbered quote snapshot; the LP validates whether that specific QuoteID remained active within a deterministic network transit grace window rather than re-sampling an unanchored reference feed.

Can a Prime-of-Prime aggregator truthfully attest to ZAHT on pass-through liquidity?

Under GFXC Cover Sheet standards, an intermediary may state it adds zero hold time at its own bridge layer, but must disclose that orders routed to conditional upstream LPs remain subject to those upstream market makers hold windows.

Publication record

Published
14 November 2026
Updated
14 November 2026
Author
Alistair Kerr, CFA
Review
Review not recorded
Automated fact check
Passed in the stored pipeline record
Source URLs
3 recorded

AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.

Academic & Institutional Attribution

Cite This Research & Embed Live Data Card

Open Attribution License (CC BY 4.0)

Standard academic & institutional research paper citation format.

Alistair Kerr, CFA. (2026, November 14). Zero Additional Hold Time (ZAHT) in FX Streams: Engineering & Audit Guide. FXOpen Ledger. https://fxopenledger.com/orderbook/zero-additional-hold-time-zaht-last-look-implementation-audit

Regulatory Directory Cross-Reference

Referenced Institutions & Regulatory Registries

Referenced Supervisory Authorities

Explore FX Global Code Last Look Execution Hub (20) →

FXOpen Ledger Data, Benchmarks & Contributor Records

Zero Additional Hold Time (ZAHT) FX Audit Guide (2026) | FXOpen Ledger