Sequence number of message block.

See Naming Convention on Appendix D.

Extra contract symbol. Some contract symbols might contain more than 35 characters. Clients should append this field to ContractSymbol (Offset 11) to get the complete contract symbol.

Denominator for the deal price fields in the market. For most markets, this is the same as `OrderPriceDenominator`.

Feed identifier.

Indicates if GTC is allowed in the market.

Collection of Hedges.

Minimum increment premium price for this market.

Minimum increment quantity for this market.

Indicates if Market is only tradable via ICE Block Trade. This also means the screen trading is not allowed for the market.

This field is true if messages has been received within bundle (see BundleMarker).

Is a flag allows the user to specify that the product is interested to user.

Indicates if the contract is tradable.

Processing latency in microseconds.

Indicates whether leg deals are suppressed.

Collection of Legs.

Unique identifier of the market.

See Appendix C for the list of makret types and IDs.

Maximum price. `OrderPriceDenominator` should be applied to this field.

Indicates MIFID-II market.

Minimum price. `OrderPriceDenominator` should be applied to this field.

Minimum quantity for this market.

Number of messages in message block.

Number of cycle (days, hours, MWh, etc.) for a contract.

Day of the month. Last date that the option market can be traded and should be removed from the system.

Month range 1-12. Last date that the option market can be traded and should be removed from the system.

4 digit year. Last date that the option market can be traded and should be removed from the system.

Denominator for the order price fields in this market.

Indicates whether the Block Minimum can be overridden for the market.

Date-time of the message received.

Contains the Strategy Code for defined market where applicable. See Appendix E for list of codes.

Date-time of the message sent.

Each message is assigned a sequence number that increases monotonically on the server side. To save bandwidth, the sequence number is a field in the block header, instead of every message. The sequence number for the first message is used in the header, and the client is expected to derive the sequence numbers for subsequent messages in the block. In the case of a heartbeat which includes only header in the block, the expected next sequence number is used.

The session number is used so that a client can easily detect when a new session has started after the daily maintenance window or failure on the server side. It should stay the same for a given multicast channel until a new session has started. It should be noted that the same number can be used by different multicast channels.

Denominator for the settlement price fields in the market. For most markets, this is the same as `DealPriceDenominator`.

Strategy Symbol.

Indicates Test Market.

See Appendix A on trading status codes.

Unique identifier of the underlying market.

Denominator for `UnitQuantity`. This field will be `0` for most of the markets.