LMEX Markets on LD4: what we are launching with

LMEX Markets is moving the matching engine off Colima-on-Mac onto bare-metal hardware in LD4, the Equinix-hosted data centre in Slough. This post covers what changes for you, what stays the same, and what to expect during the cutover window.

If you are a beta account holder, also read the [Migration Guide](/migrate) for the active steps you need to take.

Why LD4

Three reasons.

**Latency.** LD4 is the canonical low-latency venue for institutional trading in Europe — the major colocation point where prop firms, market makers and the institutional FIX flow live. Cross-connect latency to other tier-one venues is single-digit microseconds. Running the matching engine on Mac dev hardware is fine for beta; for serious flow it is not. Bare metal at LD4 means microsecond-class internal latency and the ability to take cross-connects from clients who want them.

**Throughput.** The dev stack tops out long before the kind of throughput a multi-asset perpetual exchange needs in normal conditions. Bare metal — same engine code, same data structures, just real hardware underneath — moves the ceiling by an order of magnitude. We have benchmarked the migration target at sustained five-figures-per-second order throughput with sub-millisecond match latency.

**FIX gateway.** Institutional buy-side, prop firms and brokers expect FIX 4.4 over TCP. We have written the FIX acceptor; it lands with the LD4 cutover because the latency budget for a FIX session only makes sense on bare metal in the same rack.

What changes for you

### Crypto, equity, commodity and indices traders

Almost nothing. The same perpetual contracts, the same order types, the same WebSocket channels, the same trading interface. URLs do not change. Funding rates settle on the same schedule. Margin rules are identical. The improvements are under the hood — faster fills, deeper books at the same notional, better stability under load.

### Forex traders

The forex book gets a meaningful liquidity uplift because the LD4 cross-connect to Massive (our forex price source) drops the propagation budget. Expect tighter spreads during the European session and more depth at any given level.

### Algo and high-frequency traders

This is the big one. Three things go live at cutover:

**FIX 4.4 over TCP** — a full FIX session with heartbeats, sequence recovery, resend. Translates to the same binary submit/cancel path as the REST and WebSocket surfaces. Sub-millisecond round-trip from a same-rack cross-connect; ~500-microsecond round-trip from a managed colocation cabinet.

**Stable rate limits.** REST submit caps move from "best effort" to a guaranteed envelope per account — 100 req/s standard, higher on request for institutional accounts.

**WebSocket guarantees.** We commit to per-connection broadcast lag SLAs at LD4. The dev stack tries hard but does not promise.

### Institutional traders

If you are evaluating LMEX Markets for institutional flow, this is the moment to start a conversation. The FIX gateway brings us inside the standard buy-side integration matrix; the LD4 location brings us inside the European institutional trading footprint. Contact us via the [help centre](/help) for an institutional onboarding pack.

VIP tier system goes live

Until now, every account has been trading at a flat introductory rate. At cutover the [published VIP tier ladder](/fees) goes live with automatic tier assignment from your 30-day perpetuals volume:

- General User: 0.01% maker / 0.06% taker, $5 per side per forex lot

- VIP 1 → VIP 5: see the fee schedule

Your tier is recomputed daily from the rolling 30-day window. You do not need to do anything to qualify — volume on the platform counts automatically. Forex ECN-style commission applies in parallel (your perp volume qualifies you for forex discounts, and vice-versa).

The amber "Effective LD4 launch" caveat at the top of the fees page comes down on cutover day.

Tick-data audit + liquidation replay

Every tick that contributes to a mark price gets captured to immutable storage at LD4. This unlocks two things:

- **Liquidation enquiries**: if your position is liquidated, support can replay the exact tick stream the engine consumed at the moment of liquidation. Disputes get resolved with the actual data, not screenshots.

- **Regulatory record-keeping**: a 7-year retention window on every order, fill and price tick — the floor for derivatives venues in most jurisdictions.

This works invisibly during normal trading. It only becomes relevant when you need it.

What stays the same

- All URLs (lmexmarkets.com, the trading interface, the API endpoints)

- All API keys (no rotation required; you may rotate proactively if you want)

- Account balances and open positions (these live in the same database, just behind a different engine binary)

- Symbol set (the markets you trade today, you will trade tomorrow)

- Funding settlement times (00:00, 08:00, 16:00 UTC)

- The 0% LMEX Markets share of funding payments

Cutover window

The migration runs in a single maintenance window of roughly 30 minutes. During the window:

- Trading is halted; the maintenance banner at the top of the platform shows the live status

- Deposits and withdrawals are paused

- WebSocket subscriptions return a Lagged event on resumption; clients should re-fetch state

- Open orders persist; they are restored at resume

We will announce the exact window via the maintenance banner at least 48 hours in advance.

What to do before cutover

If you are a beta account holder, please:

1. **Verify your email** if you have not already (the green check on your /account page)

2. **Enable 2FA** before any sensitive operation — withdrawals and API rotation will be gated on it

3. **Save your backup codes** from the 2FA panel

4. **Update any bots** to handle the WebSocket Lagged event gracefully (most should already; check anyway)

5. **Read the [Migration Guide](/migrate)** for the full checklist

After cutover, log in once and verify everything looks right. Open a [support ticket](/help) if anything is unexpected.

What is on the roadmap after LD4

The LD4 cutover is a milestone, not an endpoint. Next on the build queue:

- **MCP server** for AI-agent trading (read-only v0.1 first, then order submission)

- **Sandbox / testnet** for safe integration testing

- **Backup-data-centre failover** — LD4 is our primary; a secondary venue lets us survive single-DC events

- **More forex pairs** as the LD4 cross-connect to Massive proves out

- **Equity index perpetuals** (SPX500, NAS100, US30, GER40) once the LMEX-upstream feed lands

We will write each up as it ships.

Ready to trade everything, 24/7?