Release notes

Liquidity Manager


26.11.137

12 Nov 2026

What's new

  • We have added a new SnapshotType parameter to oneZero liquidity provider sessions. Set it to Incremental to receive prices as Market Data Incremental Refresh (35=X) deltas instead of full snapshots (35=W). The default is Full, so existing sessions are unaffected.
  • We have added Crypto.com as a liquidity provider, so its prediction-market prices can be streamed and orders routed to it.

Misc

  • We have reduced the time the FIX server takes to build each FIX message it sends and the CPU the liquidity manager spends parsing FIX messages from liquidity providers.

26.11.136

06 Nov 2026

Misc

  • We have introduced end-client identification on IS Prime and Match Trade orders that arrive through a FIX session, so these liquidity providers now see the end client's account instead of one shared account for the whole session.

26.10.132

23 Oct 2026

Misc

  • We have introduced faster ClickHouse log-file handling in the Liquidity Manager, which removes latency spikes when FIX message logging to ClickHouse is enabled.
  • We have aligned trace identifiers across our trade records, FIX drop copy and tracing: a trace id is now written as a 32-character hexadecimal value, so the id stored with a trade is the one used to look up that order's trace. Orders that still send the previous sender_unique trace id format in FIX tag 820 continue to be accepted.

26.10.131

21 Oct 2026

What's new

  • We have introduced the ability for the Liquidity Manager to ask a liquidity provider to resend messages missed during a disconnection (new trade session parameters ResendRequests and ResendRequestTimeout), so fills sent while the connection was down are no longer lost. We have also added the ReconnectOnSequenceGap quote session parameter, which rebuilds the order book by reconnecting when price updates are missed, and quote sessions no longer stop streaming when an LP ignores a resend request.

Bug fixes

  • We have fixed an issue where, with guaranteed delivery enabled for a gateway, a quick reconnect could leave the gateway without execution reports until it reconnected again, or cause some reports to be skipped.

Misc

  • We have added the io thread id and the currently running connection handler to the periodic TCP client statistics log line, to help diagnose a stuck network thread.

26.10.129

16 Oct 2026

Bug fixes

  • We have fixed an issue affecting clients using the CFH incremental quote feed (CFHI-QUOTES), where part of the price book could be missing and individual symbols could show a stuck bid or ask, in some cases producing a negative spread. Affected sessions no longer need to be restarted to clear the condition.

26.10.128

15 Oct 2026

Bug fixes

  • We fixed Liquidity Manager leaving a connector stop request unanswered when it was shut down before the connector had finished stopping; the request is now answered and Liquidity Manager exits.
  • We fixed crashes of Liquidity Manager and Matching Engine when a configuration client connected during shutdown or dropped its connection while a response was being sent
  • We fixed a rare LiquidityManager crash when an STP endpoint was removed through the configuration API. The same crash could happen in other components when a connection to the Data Collector was closed.

Misc

  • We have improved the speed at which incoming FIX messages are parsed, and we have tightened the validation of numeric, date and time fields so that values outside the FIX data types are refused instead of being silently reinterpreted.

26.10.125

01 Oct 2026

Bug fixes

  • We have fixed a rare crash in the Liquidity Manager that could happen when a client connected to its configuration API

Misc

  • We have built the FIX connector into the Liquidity Manager: connectors no longer depend on uploaded plugin files, and the plugin upload

26.9.120

19 Sep 2026

Misc

  • We have improved the Liquidity Manager's currency conversion so that a conversion the configuration cannot satisfy is reported once instead of on every margin and P&L recalculation

26.9.118

11 Sep 2026

What's new

  • We have added a new liquidity provider session parameter, MDBookType, which selects the market data view requested from the venue: top of book, price depth, or full order book. Where it is not set, market data subscriptions are
    unchanged.

26.9.117

11 Sep 2026

What's new

  • We have added a new LP session parameter ClOrdLinkIDTag, which sends the client's account, order id and group to the liquidity provider as a single <account_id>-<order_id>-<group> value on the configured FIX tag.
  • We have introduced propagation of the trading account and group from the MT4 Bridge and the MT5 Gateway, so orders opened on MT4/MT5 now carry the client's login and group through to the liquidity provider.

Misc

  • We have release minor changes to logging
  • We have improved startup diagnostics: when a configured host name cannot be resolved, the log now reports the DNS failure and the host name instead of a generic "invalid configuration" error.
  • We have improved Liquidity Manager logging: when a liquidity provider declines a market data subscription for a symbol that is not configured on our side, this is now reported as a warning rather than an error. 

26.8.115

27 Aug 2026

What's new

  • We have added a new CROSSx ECN liquidity provider connector, enabling crypto market-data consumption and Market/Limit (IOC/FOK) order routing over FIX 4.2.

Bug fixes

  • We have corrected the handling of text values that exactly fill their allotted storage — logins, symbol names, comments, group and account names, and MT server names. Such a value could previously lose its final character, or be stored differently, depending on which platform the component was running on. These values are now stored complete and identically everywhere.
  • We have fixed a crash where a liquidity provider session configured with an unreadable SSL certificate, CA file or private key would terminate the whole Liquidity Manager at connector start.

Misc

  • We have added four new Liquidity Manager configuration parameters that control the size of the internal per-worker queues and buffer pools: WorkerShardCapacity (default 1024), LpDataPoolCapacity (default 1024), TradeRequestPoolCapacity (default 512) and TradeRequestV2PoolCapacity (default 128).
  • We have improved how the xOpen Hub connector handles symbols that have no lot size configured. 

26.8.114

21 Aug 2026

Bug fixes

  • We have fixed an issue where the B-Book liquidity multiplier could be applied to the
    wrong price level. When a level moved between configured price bands without its own
    price or size changing, it kept the multiplier of the band it used to occupy — so the
    top of book could be advertised at the wrong size, in either direction. The same fix
    covers the infinite-quantity setting used by the "last layer" configuration, which was
    stale by the same mechanism.

26.7.113

14 Aug 2026

What's new

  • We have introduced an ability to encrypt LP session passwords in the Liquidity Manager configuration file.
  • We have greatly improved processing performance and reduced memory consumption

26.7.112

13 Aug 2026

Misc

  • We have increased the maximum length of Sender/Target CompID for LP FIX sessions from 32 to 64 characters.

26.7.110

31 Jul 2026

Misc

  • We have improved liquidity-provider resilience: when a PrimeXM/PXM feed sends a quote update or withdrawal for a price we are not currently holding, the affected instrument is now re-synced on its own instead of dropping and reconnecting the entire liquidity-provider session. This removes the continuous reconnect loop seen with the PXM feed and keeps all other instruments streaming uninterrupted.

26.7.109

30 Jul 2026

Bug fixes

  • We have fixed an issue where a FIX liquidity provider connector could stay disconnected after the LP sent a Logout (for example, rejecting a logon outside session hours) and only recovered after a manual restart. The connector now reconnects on its own.
  • We have fixed an issue where pointing an ExternalLoginFixTag, ExternalOrderIdFixTag, or ExternalGroupFixTag at a FIX tag that the liquidity provider connector already writes caused that tag to be sent twice in the same order message, which could lead the provider to reject the order or ignore the carried client account. The configured external value now takes precedence and the tag is sent exactly once.

Misc

  • We have improved the resilience of the logging pipeline: a single malformed log record can no longer stall log delivery. Records that the database permanently rejects are now set aside for later inspection while logging continues uninterrupted.

26.7.103

07 Jul 2026

What's new

  • We have added the ability to send a client's account group name in the Account field (tag 1) of orders forwarded to a liquidity provider. LPs that expect a string identifier now receive it directly, with a single configuration parameter and no duplicate tag

26.7.101

02 Jul 2026

What's new

  • We have introduced support for string-based trading account identifiers. Order flow now carries an alphanumeric account, order id, and group end-to-end (from the client FIX session all the way to the liquidity provider), instead of being limited to numeric logins.

26.6.100

26 Jun 2026

What's new

  • We have added automatic recovery for market-data subscriptions in the Liquidity Manager: when a liquidity provider rejects a symbol subscription, the LM now resubscribes automatically using a configurable exponential backoff, instead
    of leaving that symbol without quotes until the next full session reconnect.
  • We have added a new FXPrimus market-data (quotes) connector to the Liquidity Manager.

Bug fixes

  • We have fixed a Liquidity Manager bug where a Trade session would refuse to connect if the ApiData_<N>_NewOrderSingleTag (or sibling GroupTag / HeaderTag / TimeInForce) parameter exceeded 1024 characters — for example on configurations with many trading groups. The session now loads parameters of any length.

Misc

  • Minor logging changes

26.6.99

19 Jun 2026

What's new

  • We have extended outbound FIX tag obfuscation to cover integer-valued tags, so identifying values sent as integers (e.g. Account, PartyID) are no longer transmitted in clear text.

26.5.92

22 May 2026

Misc

  • Log files have daily rotation

26.5.89

12 May 2026

Misc

  • We have improved how the LiquidityManager recovers from corrupt persistent delivery files.

26.5.87

08 May 2026

Misc

  • We have improved diagnostics for components that persist data to Postgres

26.4.84

30 Apr 2026

Bug fixes

  •  We have fixed precious metal margin calculator 

26.4.82

17 Apr 2026

Bug fixes

  • we have fixed an issue when SEND_ORIGINAL_REQUEST_PRICE was set and markup for a symbol on Liquidity Manager was set, incorrect price would be sent to Liquidity Provider

26.4.79

09 Apr 2026

Misc

  • We are now treating suspended status as new (applicable for Exante connector)