Guide for the forthcoming LSCT Relay edition. Use these steps to prepare; the customer installer is not available yet.
The screenshots use synthetic example data. They illustrate setup; they do not certify a released installer or a broker connection.
Before you begin
Review the computer and account requirements. Prepare a Demo Hedging account, your permitted Telegram sources and a backup. Windows and processor compatibility, including ARM64, is awaiting final qualification.
No payment or registration is needed now. The steps below apply when the approved release becomes available. Download the application only from the official download page.
1. Your local account

Choose your username and an 8–128-character password, then confirm it. Read and accept the displayed terms yourself. This account is separate from your broker and Telegram.
Keep your password safely. No central recovery or default password is provided for this local account.
2. License file or trial

After the release and paid subscriptions open, choose Download device request and share that file with LSCT for your subscription. Use Import signed license for the signed file supplied after payment. No activation code is needed; no payment is requested for this preview.
When available, review device registration consent and choose Start seven-day trial. Its seven days begin at the first registration; downloading again does not restart them. Public trial registration is not available yet.
3. Telegram and sources

Save your own API ID, API Hash, phone number and full numeric source identifiers only in the local application. API Hash is not a bot token.
Saving does not connect Telegram or send a code. Connection and source-access verification are separate explicit actions.
4. Account and terminal

Select the correct terminal64.exe, account number, broker server and intended Demo or Live mode. Your device license allows account changes; each connection needs its own verification.
Review existing exposure before changing accounts. Scheduled entries need fresh broker time; your computer clock and a simulated schedule preview do not replace it.
Install the included broker-clock helper

The helper is included with LSCT. You do not need to buy a separate bot. It writes the latest confirmed broker quote time to a JSON file; it does not place, modify or close trades.
- In the app's MT5 setup step, find Set up broker time, select Get clock helper and check saved clock, then download LSCT_BrokerClock.ex5 from that step. This is a helper download inside the app, not a public application-installer download.
- In the intended MT5 terminal, choose File > Open Data Folder, then open MQL5 > Experts and copy the downloaded EX5 there. Preserve any existing version before replacement.
- In Navigator, refresh Expert Advisors and attach LSCT_BrokerClock to a separate chart. Keep an existing trading EA on its own chart. Leave ClockFile as LSCT_BrokerClock.json; use a different JSON name per terminal if several broker servers share the Common/Files folder.
- The clock helper needs no DLL, WebRequest or trade permission. Installing it does not require changing AutoTrading or the permissions of other EAs.
- Open Toolbox > Experts and copy the full path printed after LSCT broker clock file:. Paste it into Broker clock file in LSCT and save the MT5 step. Use that printed Common/Files path; do not guess a path under MQL5/Files.
- Select Get clock helper and check saved clock again. Keep MT5 and the helper's chart open and wait for a new broker quote. The server must match your saved profile, and both the file and quote must be fresh. A closed market may leave the check pending. A successful check confirms time reading only; it does not Start trading.
If the compiled EX5 download is unavailable in the app, download LSCT_BrokerClock.mq5 from the same step into Experts, open it in MetaEditor and press F7. Require zero compile errors and the resulting EX5 before attaching it. Do not use testing or debugging for this compilation step.
After changing the JSON path, save the MT5 profile and check it again. If the runtime is already connected, review existing exposure and reconnect explicitly to use the new path. Saving or checking the clock does not connect Telegram, start MT5 or change your account.
5. Risk and protection

Choose exact symbols, schedule, whole-setup and total-open risk limits. Select one or two protection triggers: source command, pip distance or progress towards profit; whichever occurs first.
Define thresholds and the symbol’s pip size yourself. Trailing starts after broker-confirmed protection and its configured condition. Saving settings is not proof of a moved stop.
6. Review and finish

Review configuration, license, clock, risk and protection. Finish setup after reading the summary; this does not start trading.
Once the approved release is available, connect deliberately and verify source names, message times, hold reasons, tickets and protection on Demo. Follow the checks below before considering Live. Completing setup or connecting does not automatically Start new entries.
Before considering Live
These checks remain part of release acceptance. After the approved release is available, repeat the relevant checks on your own Demo setup.
- Reception: confirm the source name, message and reception times, interpretation and any reason for withholding an entry.
- Protection: choose one or two triggers—source command, pip distance or progress towards profit. Confirm that the first selected trigger reached moves the stop as configured and that MT5 acknowledges it.
- Trailing and recovery: verify trailing after its configured condition, and review stop status, duplicate prevention and recovery after interruption.
- Live: use only a release qualified for Live and a license allowing it. Confirm the intended account and make a separate decision to connect and allow new entries.
A displayed setting or a successful connection does not prove that a stop was moved. Check the broker’s accepted result. Read the protection guide.