Nasdaq ISE, GEMX, MRX, PHLX and BX options exchanges. Order-by-order (orders, implied orders and two-sided quotes per option series).
Venues covered (5): Nasdaq ISE, Nasdaq GEMX, Nasdaq MRX, Nasdaq PHLX, Nasdaq BX Options
Venue
Nasdaq ISE, GEMX, MRX, PHLX and BX options exchanges
Asset class
US Options
Wire format
Options Depth of Market 2.1: big-endian binary messages over MoldUDP64 multicast, one feed format shared by the five Nasdaq options exchanges (PHLX adopted it when its migration finished in December 2025). SoupBinTCP is used for replay only.
Messages
System Event, Derivative Directory, Trading Action, Add Order (short / long), Add Quote (short / long), Single Side Executed / Executed with Price, Order Cancel, Single Side Replace (short / long), Single Side Delete, Single Side Update, Quote Replace (short / long), Quote Delete, Trade, Net Order Imbalance (NOII), End of Replay Sequence
Book
Order-by-order (orders, implied orders and two-sided quotes per option series)
Sequencing
MoldUDP64 sequence per channel; A/B duplicates skipped; gaps reported. Glimpse snapshot recovery code is present (shared with our ITTO handler) but incomplete and untested, so a book is complete only if the handler starts before the first order event of the day.
Validation
Validated 2026-11-20 in our production handler framework (MD) on Nasdaq's public sample captures for ISE, GEMX and MRX (November 2025) and PHLX (December 2025, from the start of the day): 20 captures, 5.2 million messages. Against a decoder we wrote independently from the 2.1 specification, all 2.6 million reference top-of-book states appeared in order, every final order book was identical (426,151 price levels) and option symbols built from the directory messages matched, with zero errors. The public samples contain no executions, cancels, trades, imbalance messages or implied orders; those were tested on a synthetic session built from the specification, with identical books. BX Options is the same format but has no 2.1 sample. Exchange-direct input: our production handler does not yet take live UDP multicast, so this handler runs on captures in our test tools today; live multicast input and gap recovery are in development.
Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.
This handler is not running in our public stack. It is built for clients with their own exchange connectivity and licences; live multicast input is in development.