The Lab

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 1.4.0

Table of Contents

Pricing

Supported Book Types

The Market Data feed will supports subscriptions to PriceDepth and TradeTicker  MDBookTypes.

Supported Instruments

Expand


Table Filter
totalrow,,,,,,,,,,,,
hidelabelsfalse
sparkNameSparkline
hidePanetrue
sparklinefalse
defaultlmax,ExecutionVenue&&client_role&&target_platform
isFirstTimeEnterfalse
cell-width250,250
hideColumnstrue
disabledfalse
enabledInEditorfalse
globalFilterfalse
id1688058897929_-1132640038
order0,1
hideControlsfalse
inversefalse,false
columnVenue
disableSavefalse
separatorPoint (.)
labelsVenue‚Hide columns
ddOperatorOR
datepatterndd M yy
updateSelectOptionsfalse
worklog365|5|8|y w d h m|y w d h m
isORAND
Table Excerpt Include
nameSupportedInstruments
merge-tablestrue
pageSupported Instruments
typepage


Please refer to Supported Instruments to view across all venues.

PartyIDs

Expand


Table Filter
hideControlstrue
inversefalse
sparkNameSparkline
hidePanetrue
isNewfalse
separatorPoint (.)
ddSeparatorstrue
defaultlmax
isFirstTimeEnterfalse
userfilterVenue
datepatterndd M yy
id1688058897931_-1543466278
worklog5|8|w d h m|w d h m
isORAND
order0

Table Excerpt Include
copytabletrue
namePartyIDs
pagePartyIDs
typepage


Please refer to PartyIDs to view across all venues.

Regulatory fields

Expand


Table Filter
hideControlstrue
inversefalse
sparkNameSparkline
hidePanetrue
isNewfalse
separatorPoint (.)
ddSeparatorstrue
defaultlmax
isFirstTimeEnterfalse
userfilterVenue
datepatterndd M yy
id1688058897933_-1738422776
worklog5|8|w d h m|w d h m
isORAND
order0

Table Excerpt Include
copytabletrue
nameRegulatoryFields
pageRegulatory Fields
typepage


Please refer to Regulatory Fields to view across all venues.

Passthru Fields

Expand


Table Filter
hideControlstrue
inversefalse
totalrow,,,,,
hidelabelsfalse
sparkNameSparkline
hidePanetrue
disableSavefalse
separatorPoint (.)
sparklinefalse
labelsVenue
defaultlmax
isFirstTimeEnterfalse
cell-width150
hideColumnsfalse
userfilterVenue
datepatterndd M yy
disabledfalse
enabledInEditorfalse
globalFilterfalse
id1688058952137_-351178729
updateSelectOptionsfalse
worklog5|8|w d h m|w d h m
isORAND
order0

Table Excerpt Include
copytabletrue
namePassthruFields
pagePassthru Fields
typepage


Please refer to Passthru Fields to view across all venues.

Details

Instrument Availability

Varies by region and session, please see attached CSV-s below for reference:

Pricing

TradeTicker

By default LMAX trade notifications are delivered with a 60 second delay, at no charge. The delay may be removed on a per-session basis, for an additional LMAX fee,  if the client wishes.

In the event where a trade is cancelled/busted on the LMAX Exchange, LMAX will publish a MarketDataIncrementalRefresh message with MDUpdateAction=Delete where the MDEntryID references the original trade now being cancelled.

Orders

Supported Products, OrderTypes and TimeInForce

Varies by region and session. LMAX will publish the security list on the FIX session after logon, please see attached CSV-s below for reference.  MF will send the client a SecurityStatus message for each FX currency pair from this list. The client will request market data and send orders.

Maker ESP

Whisperer will send the client a synthetic spot quote request for each instrument. The client will send MassQuotes in response, and LMAX will respond with fills (no last-look).

MassQuote
Publication

A subsequent MassQuote, if accepted, will replace the previous MassQuote and will cancel all the unmatched liquidity associated with the replaced MassQuote.

If an order within the new MassQuote equals the price and size of an unmatched order within the previous MassQuote, the previous order will keep priority on the order book and will adopt the new QuoteID.

A MassQuote supports a maximum of 6 quote entries for each side of the order book. A MassQuote will be rejected if the number of quote entries is greater than 6 on either/both side(s).

In order to withdraw a previous MassQuote, the client may either send an explicit QuoteCancel or send an “empty” MassQuote (with no prices and quantities).

In the event that a MassQuote is sent to replace a previous MassQuote, but is rejected (e.g. due to incorrect IDs, incorrect formatting, incorrect levels of depth), the initial MassQuote will still be active on the LMAX platform. It is advised that if a MassQuote is rejected, for any reason, and there is an existing MassQuote on the platform, a QuoteCancel or “empty” MassQuote is sent to remove the existing MassQuote.

Matching

Once the MassQuote message is submitted to a market, the individual Quote Entries are treated as single orders. The trades generated for each of the Quote Entries in the MassQuote order will be reported with an ExecutionReport Message.

The MassQuote is uniquely identified in the ExecutionReport by  the pairing of Price and ClOrdID fields:

  • MassQuote and QuoteCancel messages contain the QuoteID field that is used to uniquely identify the message. This field will be mapped to the corresponding ExecutionReport as ClOrdID (I.e. the QuoteEntryID is not used).
  • The Price field contains the price of a quote entry reported by this execution. 


Two types of MassQuote matches are possible:

  • Aggressive – when the MassQuote matches retail orders immediately;
  • Passive – MassQuote is applied to a market and waiting to be matched on the Order Book.

During trading, a given MassQuote may result in a combination of the two, e.g. The following ExecutionReports in sequence:

  • Aggressive full match for 1st price level submitted in the MassQuote.
  • Aggressive partial match against 2nd price level submitted in the MassQuote.
  • Passive match that fully fills the 2nd price level submitted in the MassQuote.

Orders

...

Iceberg Orders

Info
titleSupported LMAX platforms
Iceberg orders are supported on both LMAX Echange and LMAX Interbank.

...

  • ExecutionReports for Dark orders behave in the same way as ExecutionReports for non-Dark orders, with the addition of the MaxShow tag.
  • ExecutionReports for MassQuotes made up of Dark and non-Dark orders will include the MaxShow tag for executions against Dark Orders only. MaxShow will be omitted on ExecutionReports for executions against non-Dark orders.
  • Dark orders will not be disseminated on the MarketData stream.
  • Orders without the MaxShow tag will be treated as a normal Limit order.

Trade Sizes

Minimum Trade Size

The option to control trade sizes, using the LMAX Minimum Trade Size (MTS) functionality, is available through two methods, outlined below. The functionality is to ensure orders match, in full or partial, in a size equal to or larger than a pre-set minimum trade size.

...

Warning
titleMTS restrictions

For Takers, only Limit/Market IOC and FOK orders are supported with MTS; orders with a TimeInForce of DAY or GTC will be rejected.

MTS is not supported for Makers.

Full Amount

Full Amount trading, where orders are executed in whole, without partial fills, and against only one counterparty is available on LMAX through two methods, outlined below.

...

Warning
titleFA restrictions

For Takers, only Limit/Market IOC and FOK orders are supported for FA orders; orders with a Time in Force of DAY or GTC will be rejected.

For Makers, DAY and GTC orders are supported.

Maker ESP

Maker ESP is supported by LMAX with no Last-Look.

...

Supported instruments vary by region and session.

MF will send the client a synthetic spot quote request for each, as per the Instruments lists below (cryptocurrencies on LMAX Digital are also included in the FX currency pair list). The client will send MassQuotes in response, and LMAX will respond with fills.

MassQuote

Publication

A subsequent MassQuote, if accepted, will replace the previous MassQuote and will cancel all the unmatched liquidity associated with the replaced MassQuote.

If an order within the new MassQuote equals the price and size of an unmatched order within the previous MassQuote, the previous order will keep priority on the order book and will adopt the new QuoteID.

A MassQuote supports a maximum of 6 quote entries for each side of the order book. A MassQuote will be rejected if the number of quote entries is greater than 6 on either/both side(s).

In order to withdraw a previous MassQuote, the client may either send an explicit QuoteCancel or send an “empty” MassQuote (with no prices and quantities).

In the event that a MassQuote is sent to replace a previous MassQuote, but is rejected (e.g. due to incorrect IDs, incorrect formatting, incorrect levels of depth), the initial MassQuote will still be active on the LMAX platform. It is advised that if a MassQuote is rejected, for any reason, and there is an existing MassQuote on the platform, a QuoteCancel or “empty” MassQuote is sent to remove the existing MassQuote.

Matching

Once the MassQuote message is submitted to a market, the individual Quote Entries are treated as single orders. The trades generated for each of the Quote Entries in the MassQuote order will be reported with an ExecutionReport Message.

The MassQuote is uniquely identified in the ExecutionReport by  the pairing of Price and ClOrdID fields:

  • MassQuote and QuoteCancel messages contain the QuoteID field that is used to uniquely identify the message. This field will be mapped to the corresponding ExecutionReport as ClOrdID (I.e. the QuoteEntryID is not used).
  • The Price field contains the price of a quote entry reported by this execution. 

Two types of MassQuote matches are possible:

  • Aggressive – when the MassQuote matches retail orders immediately;
  • Passive – MassQuote is applied to a market and waiting to be matched on the Order Book.

During trading, a given MassQuote may result in a combination of the two, e.g. The following ExecutionReports in sequence:

  • Aggressive full match for 1st price level submitted in the MassQuote.
  • Aggressive partial match against 2nd price level submitted in the MassQuote.
  • Passive match that fully fills the 2nd price level submitted in the MassQuote.

Venue Checks


Venue Checks

Self-Match

Info
titleSelf-Match Prevention
Self-match scenarios (where two Client orders matched against each other) are possible, but may be disabled by the venue on a per-session basis. Please contact MarketFactory SUP to organise this, if required.


Warning
titleDuplicate ExecIDs
In the event of a self-match event, the ExecID value delivered to both sides of the trade will be identical.

Throttling

Info
titleMessage Rate Threshold
In order to manage the number of messages that the LMAX Platform can process at any given point, a Message Rate Threshold is imposed on each FIX session that acts as a limit to the number of messages the FIX session can send to LMAX in one second. If the Message Rate Threshold is breached, LMAX will force the session to disconnect by sending a Logout with a “Number of messages exceeds the threshold” message. LMAX will block any subsequent Logon attempts for 15 seconds. Message Rate Thresholds are determined by LMAX. They are based on the number of instruments and levels that each FIX session will price.

Volatility Bands

In order to protect Clients from pricing errors Volatility Bands are set per order book on LMAX. If the price difference between the previous accepted price and the new price is outside the volatility limit, LMAX will reject the order with an OUTSIDE_VOLATILITY_BAND message.

...

For Makers, If the Maker has not yet input an order during that Trading Day, the price will be compared to the last price accepted on the order book by other Makers.

PartyIDs

...

Table Filter
hideControlstrue
inversefalse
sparkNameSparkline
hidePanetrue
isNewfalse
separatorPoint (.)
ddSeparatorstrue
defaultlmax
isFirstTimeEnterfalse
userfilterVenue
datepatterndd M yy
id1643361205037_236752878
worklog5|8|w d h m|w d h m
isORAND
order0

Table Excerpt Include
copytabletrue
namePartyIDs
pagePartyIDs
typepage

Please refer to Whisperer Enterprise - PartyIDs for the full Enterprise table across all venues.

Regulatory fields

...

Table Filter
hideControlstrue
inversefalse
sparkNameSparkline
hidePanetrue
isNewfalse
separatorPoint (.)
ddSeparatorstrue
defaultlmax
isFirstTimeEnterfalse
userfilterVenue
datepatterndd M yy
id1643361219415_-1177202643
worklog5|8|w d h m|w d h m
isORAND
order0

Table Excerpt Include
copytabletrue
nameRegulatoryFields
pageRegulatory Fields
typepage

Please refer to or Regulatory Fields for the full Enterprise table across all venues.

Passthru Fields

None.

Instruments

LMAX-Exchange-TY3-Instruments.csv

LMAX-Exchange-NY4-Instruments.csv

LMAX-Exchange-LD4-Instruments.csv

LMAX-Exchange-Interbank-Instruments.csv

LMAX-Digital-Instruments.csv