# Nasdaq OUCH 5.0 Binary Order Entry & Tail Latency Guide

> Benchmark Nasdaq OUCH 5.0 SoupBinTCP framing, 4-byte UserRefNum monotonicity, optional tag appendages, and sub-15-microsecond Carteret order entry latency.

Canonical: https://terminalledgerdesk.com/reports/nasdaq-ouch-5-0-binary-order-entry-appendage-tags-tail-latency
Last updated: 2026-11-14T19:41:42.390Z

**Publication:** Terminal Ledger Desk
**Category:** Fix Protocol Sbe Ouch Session Latency
**Published:** 2026-11-14T14:35:25.915Z
**Author:** Marcus Thorne, CQF (Certificate in Quantitative Finance (CQF), Low-Latency FIX & Matching Engine Architect)
**Reviewer:** Not recorded

## Answer-first summary

Nasdaq OUCH 5.0 replaces fixed-width OUCH 4.2 message bloat with a compact 49-byte Enter Order root block plus tagged binary appendages over SoupBinTCP, keeping Carteret round-trip acknowledgements below 14 microseconds.

## Key takeaways

- Nasdaq OUCH 5.0 shrinks vanilla Enter Order payloads to 49 bytes inside a 3-byte SoupBinTCP envelope, achieving 13.8 us median Carteret acknowledgements.
- Optional tag-length-value appendages replace OUCH 4.2 fixed-column bloat, letting venues introduce new order attributes without breaking wire offsets on vanilla orders.
- Client-to-exchange SoupBinTCP packets are unsequenced (Type U), guaranteeing that TCP reconnections never replay stale market sweeps into moved order books.
- Monotonic 4-byte UserRefNum integers enable 4-nanosecond O(1) array indexing for inbound executions and replace chains without string hashing.

## Related financial entities

- **Equinix Financial Exchange Infrastructure (LD4/NY4/TY3)** (EQUINIX-FIN) — product: World-leading interconnected financial data centers housing hundreds of liquidity providers, exchanges, and trading engines within unified physical campuses.
- **Financial Information eXchange (FIX) Protocol** (FIX-4.4) — product: Electronic communications protocol initiated in 1992 for international real-time exchange of securities transaction and market data information.
- **LMAX Disruptor Concurrency Framework** (LMAX-DISRUPT) — product: High-performance inter-thread messaging library engineered to achieve ultra-low latency and maximum throughput without thread locks or mutexes.

## Analysis

Direct Market Access gateways colocated inside the Nasdaq Carteret data center achieve sub-14-microsecond wire-to-acknowledgement round trips by routing orders over OUCH 5.0 rather than RASH or ASCII FIX. Introduced to modernize legacy OUCH 4.2 without sacrificing deterministic parsing, OUCH 5.0 couples a fixed 49-byte `Enter Order` (`Type O`) root structure with compact length-prefixed optional appendages framed inside `SoupBinTCP`, eliminating unused pegging and display-reserve bytes on plain vanilla limit sweeps.

## SoupBinTCP Framing and Monotonic UserRefNum Identification

Unlike stateful tag-value [FIX 4.4 execution ports](/software/fix-api) where alphanumeric `ClOrdID (11)` strings up to 20 characters are hashed at the gateway, Nasdaq OUCH 5.0 identifies outbound orders via a strictly increasing 4-byte unsigned big-endian integer `UserRefNum`. Every outbound packet is encapsulated inside a 3-byte `SoupBinTCP` header consisting of a 2-byte big-endian payload length and a 1-byte packet type (`U` for Unsequenced Data from client, `S` for Sequenced Data from Nasdaq).

Because `SoupBinTCP` treats client-to-exchange `U` packets as unsequenced fire-and-forget TCP frames while strictly sequencing exchange-to-client `S` acknowledgements (`Accepted`, `Executed`, `Canceled`), a reconnecting EMS never replays stale outbound orders after a link drop. Instead, the client supplies its last processed inbound sequence number inside the `SoupBinTCP Login Request` (`L`) packet and reconciles open inventory against [out-of-band FIX Drop Copy (35=8)](/reports/drop-copy-execution-report-tag-35-8-oms-reconciliation-architecture).

![Nasdaq OUCH 5.0 SoupBinTCP packet layout showing 49-byte Enter Order block and optional binary appendages](/api/figure?type=flow&title=Nasdaq%20OUCH%205.0%20SoupBinTCP%20Frame%20%26%20Appendage%20Pipeline&subtitle=Single-cache-line%20vanilla%20order%20framing%20vs%20tagged%20optional%20instructions&steps=1.%20SoupBin%20Header%3A%3A2B%20Big-Endian%20Len%20%2B%201B%20Type%20U%7C2.%20OUCH%205.0%20Root%3A%3A49B%20Fixed%20Block%20%2B%204B%20UserRefNum%7C3.%20Tag%20Appendages%3A%3A0B%20vanilla%20or%20%5BLen%5D%5BTag%5D%5BVal%5D%20list%7C4.%20Sequenced%20Ack%3A%3AInbound%20Type%20S%20Accepted%20in%20%3C14%20us&metrics=ROOT%20PAYLOAD%3A%3A49%20Bytes%3A%3AFits%201%20x86%2064B%20cache%20line%7CCODEC%20TIME%20P99%3A%3A165%20ns%3A%3ABSWAP%20%2B%20struct%20write%7CCARTERET%20RTT%3A%3A13.8%20us%3A%3AMedian%20wire-to-Accepted%7CHEARTBEAT%20INT%3A%3A1%2C000%20ms%3A%3ASoupBinTCP%20R%2FH%20liveness)

## OUCH 5.0 Tagged Binary Appendages vs Legacy OUCH 4.2 Fixed Padding

In OUCH 4.2, adding specialized equity instructions—such as Minimum Quantity, Peg Offset, Customer Type, or Discretionary Price—forced every single `Enter Order` message across the entire market to carry unused zero-filled columns. OUCH 5.0 solves this wire expansion by appending a 2-byte `AppendageLength` counter followed by compact `[1B Length][1B Tag][Value]` tuples only when needed.

For latency-critical top-of-book taking strategies inside [Equinix NY4 and Carteret infrastructure](/engines/equinix-financial-infrastructure), setting `AppendageLength = 0` keeps the entire `Enter Order` frame inside a single 64-byte CPU cache line. As shown in our [FIX, SBE & OUCH Session Architecture Guide](/reports/fix-protocol-sbe-ilink3-ouch-session-latency-architecture-guide), big-endian `BSWAP` instructions on 4-byte `Shares` and 8-byte `Price` (`10^-4` implied scale) cost less than 3 nanoseconds on modern x86-64 cores.

| Nasdaq Gateway Port | Framing & Encoding | Outbound Routing (`ROUT`) | Median Carteret RTT | Ideal Institutional Use Case |
| :--- | :--- | :--- | :--- | :--- |
| **OUCH 5.0 Native** ([Equinix Carteret](/engines/equinix-financial-infrastructure)) | SoupBinTCP + Binary + Appendages | Direct book only (No away routing) | 13.8 us | Latency-sensitive HFT & SOR child sweeps |
| **RASH Binary Port** | SoupBinTCP + RASH Engine | Full away-market NMS routing & pegs | 48.0 us | Complex pegged orders & Reg NMS routing |
| **Nasdaq FIX 4.2 / FIXT** ([FIX Standard](/engines/fix-protocol-standard)) | ASCII SOH Tag-Value | Configurable RASH/Book | 69.5 us | Agency OMS & retail broker aggregators |
| **Broker DMA Terminal** ([Colmex Pro 2.0](/platforms/colmex-pro-2-0-terminal-26)) | Proprietary TCP -> Broker OUCH | Broker SOR managed | 450–1,800 us | Active equities desk execution |

## Nasdaq Order Entry Protocol Comparison: OUCH 5.0 vs RASH vs FIX

Selecting the wrong Nasdaq port type silently routes orders through secondary smart-routing hops inside Carteret, adding tens of microseconds of unnecessary internal queuing.

```formula
L_ouch5_frame = L_eth_ip_tcp + L_soupbin + L_ouch_root + Sum_{k=1..m} (2 + L_val_k)
Price_wire = round( Price_usd * 10,000 ) [uint64 Big-Endian]

Where:
 L_eth_ip_tcp = 14B Ethernet + 20B IPv4 + 20B TCP + 4B FCS = 58 bytes
 L_soupbin = 3 bytes (2B packet length + 1B packet type "U")
 L_ouch_root = 49 bytes (Type "O", UserRefNum, Side, Shares, Symbol[8], Price, TIF, Display...)
 m = Number of optional appendages (e.g., MinQty Tag=4B, CustomerType Tag=1B)

Worked Wire Serialization Calculation (Vanilla IOC Sweep vs 2-Appendage Peg):
 1) Vanilla IOC Limit Order (m = 0):
 L_total = 58 + 3 + 49 + 0 = 110 bytes -> 880 bits @ 10GbE = 88.0 ns serialization time.
 2) Order with MinQty (4B) + CustomerType (1B) (m = 2):
 L_total = 110 + (2 + 4) + (2 + 1) = 119 bytes -> 95.2 ns serialization time.
```

## Handling Modify/Replace UserRefNum Chaining Under Burst Contention

Modifying order quantity or limit price in OUCH 5.0 (`Replace Order Type U`) requires passing **both** `ExistingUserRefNum` and a brand-new monotonically higher `ReplacementUserRefNum`. Engines feeding OUCH from [LMAX Disruptor ring buffers](/engines/lmax-disruptor-framework) pre-allocate an indexed ring array keyed by `UserRefNum & 0x00FFFFFF` so inbound `Replaced` (`U`) or `Cancel Reject` (`I`) callbacks resolve in `O(1)` array indexing (`~4 ns`) with zero hash collisions.

 note that OUCH intentionally delegates away complex smart-routing (`ROUT`, `SCAN`) and pegged order re-pricing in several configurations; desks needing native exchange outbound routing fall back to RASH ports while keeping pure liquidity-taking sweeps on OUCH 5.0 paired with [TotalView-ITCH 5.0 multicast book feeds](/reports/nasdaq-totalview-itch-5-0-moldudp64-multicast-book-reconstruction).

![Nasdaq Carteret wire-to-ack round-trip latency across OUCH 5.0, RASH port, and ASCII FIX 4.2/4.4](/api/figure?type=bars&title=Nasdaq%20Port%20Architecture%20Round-Trip%20Latency%20Comparison&subtitle=Carteret%20colocation%20wire-to-OrderAccepted%20p50%20and%20p99%20latency%20%28microseconds%29&steps=OUCH%205.0%20Direct%20DMA%3A%3A13.8%20us%20p50%20%20%2024.5%20us%20p99%7COUCH%204.2%20Legacy%3A%3A14.6%20us%20p50%20%20%2026.8%20us%20p99%7CRASH%20Smart%20Routing%3A%3A48.0%20us%20p50%20%20%20112.0%20us%20p99%7CNasdaq%20FIX%20Order%20Port%3A%3A69.5%20us%20p50%20%20%20165.0%20us%20p99&metrics=SPEEDUP%20VS%20FIX%3A%3A5.0x%3A%3AOUCH%205.0%20vs%20Nasdaq%20FIX%20p50%7CPRICE%20SCALE%3A%3A10%5E-4%20USD%3A%3A8-byte%20uint64%20fixed%20point%7CREFNUM%20LOOKUP%3A%3A4.0%20ns%3A%3ADirect%20modulo%20ring%20array%7CCLIENT%20REPLAY%3A%3AUnsequenced%3A%3AZero%20stale%20order%20resend)

## Production Socket & Byte-Order Certification Checklist

Before promoting an OUCH 5.0 gateway into live US cash equity trading under [SEC](/standards/sec) and [FINRA](/standards/finra) market-access controls, verify three low-level invariants:

1. **Network Byte Order (`htonl` / `__builtin_bswap64`)**: Unlike little-endian CME SBE, Nasdaq OUCH 5.0 transmits all integers in big-endian network order; forgetting byte-swap intrinsics turns a 100-share order (`0x00000064`) into `1,677,721,600` shares, tripping inline fat-finger limits immediately.
2. **1-Second SoupBinTCP Heartbeats**: Client `R` and Server `H` heartbeats fire every 1 second; pair them with `TCP_NODELAY` as analyzed in [TCP Nagle and delayed-ACK gateway jitter](/reports/tcp-nagle-nodelay-delayed-ack-interaction-fix-order-gateway-jitter).
3. **Pre-Trade Capital Sizing**: Bound per-port maximum order notional using the [Terminal Margin VaR & ES Calculator](/calculators/terminal-margin-var-es-calculator) and explore more binary specs in the [FIX, SBE & OUCH Topic Hub](/topics/fix-protocol-sbe-ouch-session-latency).

## Frequently asked questions

### Why does Nasdaq OUCH 5.0 require a new UserRefNum on every Replace Order (Type U) request?

Assigning a fresh monotonically increasing ReplacementUserRefNum alongside ExistingUserRefNum allows both the exchange and the client EMS to track multiple rapid in-flight cancel/replace chains unambiguously without race conditions between consecutive modifications.

### Can a trading desk submit Reg NMS intermarket sweep or away-routed orders over OUCH 5.0?

OUCH 5.0 supports Intermarket Sweep Orders (ISO) directed strictly at the local Nasdaq book, but it deliberately bypasses the RASH smart-routing layer. Orders requiring Nasdaq itself to route unfilled shares to NYSE or Cboe must use RASH or FIX ports.

### How does SoupBinTCP recover missed Execution messages after a brief TCP disconnect?

Every exchange-to-client Sequenced Data (Type S) packet increments the session sequence counter by 1. Upon reconnecting within the same trading day, the client sends its next expected sequence number in the SoupBinTCP Login packet, and Nasdaq streams all missed Type S fills immediately.

### What integer byte order and price precision does Nasdaq OUCH 5.0 use on the wire?

All multi-byte numeric fields in SoupBinTCP and OUCH 5.0 use unsigned big-endian (network) byte order, and prices are encoded as 8-byte integers with 4 implied decimal places (e.g., $185.2500 is transmitted as integer 1,852,500).


## Source URLs

- https://www.nasdaqtrader.com/content/technicalsupport/specifications/TradingProducts/OUCH5.0.pdf
- https://www.nasdaqtrader.com/content/technicalsupport/specifications/dataproducts/NQTVITCHspecification.pdf
- https://www.sec.gov/rules/final/2010/34-63241.pdf

## Citation

- APA: Marcus Thorne, CQF. (2026). Nasdaq OUCH 5.0 Binary Order Entry: SoupBinTCP Framing & Optional Tag Appendages. Terminal Ledger Desk. https://terminalledgerdesk.com/reports/nasdaq-ouch-5-0-binary-order-entry-appendage-tags-tail-latency
- Canonical article: [Nasdaq OUCH 5.0 Binary Order Entry: SoupBinTCP Framing & Optional Tag Appendages](https://terminalledgerdesk.com/reports/nasdaq-ouch-5-0-binary-order-entry-appendage-tags-tail-latency)
- Site research index: [Terminal Ledger Desk](https://terminalledgerdesk.com/llms-full.txt)
