Pricing

Subscription Management

SecurityStatus Messages

Security Status messages communicate static attributes of each instrument supported by the Venue and are delivered on successful connection to a CLOB Pricing session.

Should Whisperer be notified of changes for an Instrument, these messages will also be used to deliver intra-day updates. Typical scenarios are value/trade date rolls & changes in trading status (open/halted).

The usage of specific fields is elaborated below:

ContractMultiplier - This is aka Lot SIze. whilst there are a few FX venues to allow the client to trade standardised contracts (e.g. LMAX), this is primarily present for trading Futures on venues such as the CME. For most venues, the contract multiplier returned will be 1.0.
MinQty - This is the minimum allowed Order size for the Venue. given that the venue may be trading in terms of contracts, the client may safely assume that this quantity is expressed in ‘nominal’ units (e.g. contracts) and not in total units.

MarketData Messages

Incremental Processing

Whisperer delivers market data in the form of incremental updates, wherever possible. When a venue message is known to be a snapshot, this is reflected with MDFlags.IsSnapshot = TRUE and NoMDEntries[*].MDUpdateAction = New.

Standard incremental processing is expected, with clients making direct reference to NoMDEntries[*].MDUpdateAction and applying New/Change/Delete actions against each associated MDEntryID.

The population of the NoMDEntries group will vary with the MDUpdateAction as follows:

All: MDEntryID and MDUpdateAction are always provided.
New: all other available fields will always be provided.
Change: typically those fields that are changed will be provided. For performance reasons, Whisperer does not currently reference cached fields to replicate the coverage of the New.
Delete: by definition the entry is no longer valid, so there is no need to redeliver the state of the outdated entry.

Book Management

Please refer to Liquidity Representation for an overview of CLOB market data structures.

OrderDepth books are characterised by there being the possibility of many orders at each Bid or Offer price point. In order to ensure that this book is maintained correctly the Client must order it first by Price (best to worst), and then by Age (oldest orders first) for each given price.

PriceDepth books are a simplification of this since we know that they are an aggregated view of the raw OrderDepth data, so there is only ever a single entry for any given Bid or Offer price point. The same applies for other aggregated views - Spread, VWAP etc.

The MDEntryID is always used as follows for the two book types:

OrderDepth - MDEntryID provides a unique identifier of that individual Order, as and when the order is modified it's ID will change. Additional linkage information may also be provided by the venue so the market data consumer can track each individual order through it's entire lifetime. Whisperer currently delivers this in the NoEntryPassthruFields block, if available.
PriceDepth - here the MDEntryID represents a specific side/price level and so can be relied upon to give the correct book ordering. Typically it will be a string representation of either the price itself, or the level within the book (position number).

In order to ensure a consistent processing model across both book types, the client may implement an efficient equivalent of the following:

Collect the orders by price level (this is redundant for a PriceDepth book, which is already aggregated).
Sort prices for each side of the book best to worst.
For each price level sort MDEntryIDs smallest (oldest) > largest (newest).

Orders

The Orders workflow is always normalised and consistently implements the state transition model as outlined in the diagram below. Where Venue events are absent, synthetic equivalents are generated by Whisperer in their place. These messages are easily discernible by reference to the TradingFlags.IsSynthetic field.

It's worth remembering that while all inbound messages will adhere to the same state transition model, there will necessarily be Venue-specific variation in whether and how outbound ExecutionAck messages are handled.