# Zero Additional Hold Time (ZAHT) FX Audit Guide (2026)

> Technical engineering audit of Zero Additional Hold Time (ZAHT) in OTC foreign exchange streams: ingress snapshot timestamping vs queuing latency.

Canonical: https://fxopenledger.com/orderbook/zero-additional-hold-time-zaht-last-look-implementation-audit
Last updated: 2026-11-14T19:53:38.055Z

**Publication:** FXOpen Ledger
**Category:** FX Global Code Last Look Execution
**Published:** 2026-11-14T14:35:25.915Z
**Author:** Alistair Kerr, CFA (CFA, Former G10 Prime Brokerage & OTC Liquidity Desk Head)
**Reviewer:** Not recorded

## Answer-first summary

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.

## Key takeaways

- Zero Additional Hold Time (ZAHT) confirms the absence of artificial sleep timers, but post-queue validity checks can still suffer 8ms-12ms synthetic hold delays during macro TCP bursts.
- True institutional-grade ZAHT pairs hardware PTP ingress timestamping with FIX Tag 117 QuoteID versioning, retaining 93.4% fill rates during peak volatility vs 68.5% on post-queue JVM engines.
- Under M/M/1 queuing math, pushing a 5,000-msg/sec FIX gateway from 20% to 93% utilization spikes mean queue wait 53x and exposes post-queue checks to ~0.98 bps of burst drift.
- Intermediary bridges claiming "0ms local hold" while passing orders upstream to conditional LPs inherit the upstream LP full hold distribution and reject profile.

## Related financial entities

- **GFXC Standardized Liquidity Provider Disclosure Cover Sheet** (GFXC-LPDS) — license: Standardized disclosure template mandated by the Global Foreign Exchange Committee to establish transparency on last-look hold times, symmetry, and pre-hedging.
- **Global Foreign Exchange Committee (GFXC)** (GFXC) — license: Global forum of central banks and market participants maintaining the FX Global Code of conduct for wholesale foreign exchange markets.
- **Minimum Quote Life (MQL) ECN Rule** (ECN-MQL) — product: Electronic matching engine rule requiring resting maker limit orders to remain executable for a mandatory millisecond threshold before cancellation is permitted.

## Analysis

When the Global Foreign Exchange Committee formalized **Zero Additional Hold Time (ZAHT)** on the [GFXC Standardized Liquidity Provider Disclosure Cover Sheet](/pairs/gfxc-lp-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](/orderbook/fx-global-code-principle-17-last-look-tca-institutional-guide) and the [Principle 17 & Execution TCA hub](/topics/fx-global-code-last-look-execution), 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](/pairs/fxpb-designation-notice) 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](/api/figure?type=flow&title=Ingress-Anchored%20ZAHT%20vs%20Queue-Exposed%20Validity%20Check%20Architecture&subtitle=Why%20TCP%2Fcredit%20queue%20contention%20during%20NFP%20bursts%20creates%20synthetic%20hold%20drift%20if%20unanchored&steps=1.%20Optical%20NIC%20Capture%3A%3AHardware%20PTP%20stamps%20t_nic%20%28100ns%20precision%29%20at%20rack%20ingress%7C2.%20FIX%20Ring%20Buffer%3A%3ACalm%3A%200.15ms%20%20%20Macro%20burst%3A%204.5ms-9.5ms%20thread%20contention%7C3.%20Credit%20%26%20Quote%20ID%3A%3AVerify%20quote%20version%20active%20at%20t_nic%20%2B%20NOP%20credit%20headroom%7C4.%20Tolerance%20Gate%3A%3AIngress-anchored%20check%20prevents%20queue-induced%20reject%20spikes&metrics=CALM%20ZAHT%20ENGINE%3A%3A0.45%20ms%3A%3AMedian%20NIC-to-NIC%20Processing%7CBURST%20QUEUE%20JITTER%3A%3A%2B7.8%20ms%3A%3AUnpinned%20JVM%20Thread%20Contention%7CQUOTE-ID%20MATCHING%3A%3ADeterministic%3A%3ATag%20117%20QuoteID%20Versioning%7CFALSE%20REJECT%20DROP%3A%3A-61.0%25%3A%3AIngress%20Snapshot%20vs%20Post-Queue)

## Tag 117 QuoteID Versioning vs Unversioned Price-Stream Tolerance

On modern institutional [FIX API](/software/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](/orderbook/spot-fx-hold-time-latency-distributions-zero-to-fifty-ms).

## Queuing Theory Stress Model Under Macro Message Bursts

```formula
Synthetic_Queue_Drift (bps) = sigma_burst * sqrt(tau_queue(Lambda_msg))
Where M/M/1 gateway queuing delay under message arrival rate Lambda_msg < Mu_service:
tau_queue = 1 / (Mu_service - Lambda_msg) - (1 / Mu_service)

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

| ZAHT Implementation Tier | Price Validation Anchor | P50 / P99 Processing (LD4) | Macro Burst Fill Stability | Typical Counterparty Cohort |
| :--- | :--- | :--- | :--- | :--- |
| FPGA / Kernel-Bypass QuoteID | Hardware Ingress $t_{nic}$ + Tag 117 | 0.28 ms / 0.75 ms | 93.4% Fill Rate Retained | Top Non-Bank Electronic Market Makers |
| Pinned-C++ ZAHT Bilateral | Gateway Ingress Reference Mid | 0.85 ms / 2.10 ms | 89.8% Fill Rate Retained | Tier-1 Global FX Franchise Banks |
| Unpinned JVM ZAHT Engine | Post-Credit-Queue Current Mid | 1.90 ms / 11.80 ms | Drops to 68.5% in Bursts | Mid-Tier Regional Banks & PoP Bridges |
| Upstream-Dependent "ZAHT" | Local 0ms + Upstream LP 10ms | 5.40 ms / 17.60 ms | Drops to 61.2% in Bursts | Disclosed on [CySEC](/supervisors/cysec) / [FCA](/supervisors/financial-conduct-authority-uk-121) Aggregators |

![Macro burst fill rate retention across four ZAHT engineering architectures in spot FX](/api/figure?type=bars&title=Macro%20Volatility%20Fill-Rate%20Retention%20Across%20ZAHT%20Engineering%20Tiers&subtitle=Realized%20sweep%20fill%20percentage%20during%20top-decile%20volatility%20minutes%20%28EUR%2FUSD%20%26%20USD%2FJPY%29&steps=FPGA%20Ingress%20QuoteID%3A%3A93.4%25%20burst%20fill%20rate%20%20%200.75ms%20P99%20gateway%20latency%7CPinned-C%2B%2B%20Ingress%3A%3A89.8%25%20burst%20fill%20rate%20%20%202.10ms%20P99%20gateway%20latency%7CJVM%20Post-Queue%20ZAHT%3A%3A68.5%25%20burst%20fill%20rate%20%20%2011.80ms%20P99%20queue%20contention%7CPass-Through%20Bridge%3A%3A61.2%25%20burst%20fill%20rate%20%20%2017.60ms%20P99%20upstream%20wait&metrics=M%2FM%2F1%20UTILIZATION%3A%3A%3C%2050%25%20Cap%3A%3AInstitutional%20Gateway%20SLA%7CINGRESS%20FILL%20GAIN%3A%3A%2B24.9%25%3A%3AFPGA%20vs%20Post-Queue%20JVM%20in%20Bursts%7CCOVER%20SHEET%20CHECK%3A%3AQuestion%204%3A%3AGFXC%20ZAHT%20Attestation%20Field%7CGC%20PAUSE%20ELIMINATION%3A%3AZero-Alloc%3A%3AOff-Heap%20C%2B%2B%2FRust%20Standard)

## Due-Diligence Questions for Counterparty Tech Reviews

When onboarding liquidity feeds across institutional or multi-asset dealing desks—referencing supervisory registers at [FINMA](/supervisors/finma), [ASIC](/supervisors/asic), or broker directories including [AMB Prime](/dealers/amb-prime) and [ATG World](/dealers/atg-world)—buy-side engineers ask three pointed architectural questions beyond the [GFXC Cover Sheet](/orderbook/gfxc-liquidity-provider-cover-sheet-last-look-audit-metrics): (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.


## Source URLs

- https://www.globalfxc.org/docs/disclosure_cover_sheets_lp.pdf
- https://www.globalfxc.org/docs/last_look_guidance.pdf
- https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mifid-ii

## Citation

- APA: Alistair Kerr, CFA. (2026). 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
- Canonical article: [Zero Additional Hold Time (ZAHT) in FX Streams: Engineering & Audit Guide](https://fxopenledger.com/orderbook/zero-additional-hold-time-zaht-last-look-implementation-audit)
- Site research index: [FXOpen Ledger](https://fxopenledger.com/llms-full.txt)
