LMEX LIVE
BTCETHSOLBNBXRPDOGESUITONTAOHYPEAAPLTSLANVDAMSFTMETACOINHOODOILBRENTGOLDSILVERCOPPERXLEURNM
★ LD4 MIGRATION GUIDE

What to do before, during and after the LD4 cutover.

A short checklist for beta accounts moving to the LD4 bare-metal venue. Read the launch announcement for the why; this page covers the what-to-do.

The exact cutover window — date and time — is announced 48 hours in advance via the maintenance banner at the top of the trading interface and on the status page. This page covers the process; subscribe to the trading interface for the timing.

Before the cutover

Five things to do whenever you next log in. None of them take more than a few minutes; all of them are useful even outside the migration.

1
Verify your email
Open the /account page in your dashboard. If the amber "Verify your email" banner is showing, click Resend Email and follow the link. Without a verified email, withdrawals and API-key rotation will be blocked at cutover.
2
Enable two-factor authentication
Find the Two-Factor Authentication panel on /account. Scan the QR with Google Authenticator, Authy, or any TOTP app. Enter the 6-digit code to confirm.
3
Save your 2FA backup codes
When 2FA enables, 10 backup codes appear once. Save them in a password manager or print them — they are your only way back into the account if you lose your device. We cannot show them a second time.
4
Test your API integration against the WebSocket lagged event
During the cutover, all WebSocket subscribers receive a Lagged event on resumption. Your bot should re-fetch any state it cares about (order book snapshot, account detail, open orders) when this fires. Test by killing and restoring your connection deliberately.
5
Bookmark the status page
The /status page shows live engine, relay, aggregator, dashboard and LMEX-feed health. We will update it in real time during the cutover.

During the cutover window

What happens at each step, in real time. Reference timeline only — exact wall-clock times depend on the announced window.

T−48hMaintenance banner activates on the trading interface, announcing the exact cutover window.
T−1hBanner level escalates to "warn". Final reminder.
T−15mNew deposits and withdrawals paused. In-flight trades complete normally.
T−5mNew order submission paused. Existing open orders remain on the book and will be restored at resume.
T+0Engine cutover begins. Dashboard shows "Maintenance — be back shortly." WebSocket connections close cleanly.
T+~30mNew engine binary live on LD4 bare metal. Open orders restored. WebSocket reopens. Banner returns to "info" with a "Back online" confirmation.
T+1hBanner cleared. Normal trading resumes. Status page shows all-green.

After the cutover

Once trading resumes. Most traders will not notice anything except slightly better fills.

1
Log in and verify your balance
Your USDT balance, open positions and order history should look identical to pre-cutover. If anything looks wrong, screenshot it and open a support ticket immediately.
2
Reconnect your bot
Your API key and secret are unchanged. If your bot dropped during cutover, restart it — it should connect, receive a clean state, and resume.
3
Verify VIP tier on /account
The VIP tier ladder is now live. Your tier is computed from your trailing 30-day perpetuals volume; the API Credentials and Fees panels reflect your current tier.
4
(Institutional) Request FIX credentials
If you are an institutional account using FIX 4.4, contact support for your session credentials. The FIX gateway goes live at cutover.

Migration FAQ

Answers to the questions we expect. Anything not covered — open a support ticket.

Will my API keys change?
No. Your existing per-account API key and secret continue to work. You can rotate them proactively from the API Credentials panel if you want a fresh pair, but rotation is optional.
Will my open orders survive the cutover?
Yes. Open orders are persisted before the cutover window and restored once the new engine is live. Order IDs are preserved.
Will my open positions and balance survive?
Yes. Positions and balances live in the database, not the engine binary. The cutover swaps the engine; the data is untouched.
What about funding payments during the cutover window?
The cutover is scheduled to fall between funding settlements (which happen at 00:00, 08:00 and 16:00 UTC). The engine settles any pending funding before halting trading.
Will the URL change?
No. The trading platform stays at the same URL. The API endpoints stay at the same URL. The WebSocket endpoint stays at the same URL.
My bot uses REST polling — anything to change?
Rate limits move from "best effort" to a guaranteed envelope (100 req/s standard). If your bot is polling more aggressively than that, you need to throttle. Otherwise no change.
My bot uses the WebSocket — anything to change?
One thing: handle the Lagged event on reconnection. The new engine will close existing WebSocket connections during the cutover; on reconnect your client receives a Lagged event indicating it should re-fetch any state. Most well-written clients already do this; verify yours does.
Will the fees go up at cutover?
No. The General User rate at cutover is identical to the current introductory rate (0.01% maker / 0.06% taker). What changes is that VIP tier discounts now apply automatically based on your volume — so for many traders the rate goes DOWN.
How long is the cutover window?
Approximately 30 minutes for the engine swap, with a 1-hour total window to allow for any delayed verification. The exact window is announced 48 hours in advance via the maintenance banner.
What if something goes wrong with my account after cutover?
Open a support ticket via the help centre with a screenshot and a brief description. Account-affecting issues are triaged within 30 minutes during the cutover window and the following 24 hours.
Questions about the migration?

Anything not covered above — open a ticket in the help centre. Account-affecting issues during the cutover are triaged within 30 minutes.

Open Help Centre →Check System Status →Go to Account →