YI GOLD
Menu
Start 7-Day Demo
YI GOLD · MT4 / MT5

Complete Website & EA User Guide

Follow the chapters for your first setup. Afterwards, use the contents or keyword search. Your website login, broker trading account and EA device authorization are three separate things.

Updated 2026-10-27 · Current account center and client 1.23; the download page and your actual interface take precedence.

Emails, accounts, balances, invoices and authorization codes in account-center screenshots are demonstration data, not real performance or trades. EA panel images come from offline testing and do not prove a live connection. Never transfer funds using a tutorial example.

01 Before you start: accounts, devices and requirements

  1. Prepare your broker’s Windows desktop MT4 or MT5, a gold trading account, reliable internet and an always-on PC or VPS. Mobile and web terminals cannot load EX4 / EX5 files. Complete installation, authorization and pause checks on demo before considering a real account.
  2. Your website email and password access the account center. Your broker login, password and server access MetaTrader. The EA authorization code connects your own terminal to the website account. The website does not need your broker trading password; an email is not a trading account number.
  3. Each subscription binds one trading account and one active terminal. Accounts have separate expiry dates and risk settings. Do not run the same account on multiple VPS devices or install a publisher/another EA instead of the YI GOLD client.
  4. Funds remain at your broker. Connectivity, spreads, slippage, margin and broker restrictions affect execution. An online panel does not promise an immediate trade; historical performance does not guarantee returns.

03 Registration: email, password, invitation and terms

  1. Choose the 7-day demo or registration entry. Enter an email you control long term. Use a 12–128 character password and repeat it exactly. Prefer a unique password stored in a trusted password manager; avoid accidental spaces or full-width characters.
  2. An invitation code is required. An invitation link may prefill it. A normal entry may display the default YIGOLD code, but a displayed hint does not fill the input: type the valid code currently shown. Keep the intended referral source and do not create duplicate accounts to bypass trial limits.
  3. Read the terms, privacy policy and risk disclosure, confirm you are at least 18 and accept the checkbox. Registration is complete when the account center opens successfully. If submission fails, read the inline error before trying again.
  4. The current flow does not require an email verification step before opening the account center. If the email already exists, sign in instead. For lost access, use contact/support; never send support your password.
Registration and required invitation code · Enlarge screenshot

04 Sign-in, password changes and two-factor verification

  1. Sign in with your website email and password. A six-digit authenticator code is needed only after enabling two-factor verification. Do not enter the EA’s eight-digit code or the authenticator secret here. Avoid remembered sessions on shared PCs and sign out afterwards.
  2. Open Security in the account center. To change your password, enter the current password, the new password and its confirmation. The new password is also 12–128 characters. Submission revokes other sessions, so other devices must sign in again. Complete a forced password change before continuing.
  3. To enable two-factor verification, enter your current password and start authenticator setup. Add the displayed secret to your own authenticator, then confirm with its current six-digit code. The secret can generate future codes: conceal it in every screenshot or shared recording.
  4. Store recovery information securely and enable automatic phone time. Once enabled, the page shows its status. For a lost device or recovery, contact support; do not repeatedly register or disclose current codes or session cookies.
Sign-in: website credentials and authenticator · Enlarge screenshot
Security: password change and 2FA entry (demo) · Enlarge screenshot

05 Overview, adding an account and account states

  1. Overview shows account count, active subscriptions, connected clients and next steps. In Accounts, choose Add, select MT4 or MT5 and enter the numeric login from the terminal. The broker server appears after first connection. Identical login digits at different brokers do not make them the same account.
  2. Check platform, full login, server, expiry, last seen and risk scale on each card. The sample 12345678 is illustrative. If you added the wrong account, first check positions and pending actions, then follow unbinding; do not delete files to force rebinding.
  3. Unsubscribed means that account has no purchased service; Expired needs renewal; Close only restricts new openings; Client offline means the site has not received a fresh connection. Cached balance/status may be stale offline: also inspect the broker terminal.
  4. Subscribe, Confirm authorization, Risk, Reset device, Pause/Resume and Unbind act on the selected card. Check its login before proceeding. Website account count is not a broker position count.
Account overview (demo data) · Enlarge screenshot
Account cards and independent status (demo) · Enlarge screenshot
Choose platform and add trading login (demo) · Enlarge screenshot

06 Free demo: when the clock starts

  1. The trial covers one demo trading account, never a real account. First add the login, download and install the EA, allow requests and confirm terminal authorization. Eligibility uses the actual account type reported by the client.
  2. Once connected, explicitly choose Start Demo in the trial steps. Seven full days run from that activation, not a homepage visit or file download. Check the trial account, displayed expiry and EA authorization state afterwards.
  3. A demo account can have its own single-account group but cannot join multi-account group control. Renaming an account does not make it a demo: the broker account type reported by the client controls eligibility.
  4. After trial or when moving to real trading, subscribe the appropriate account. A demo trial does not authorize every account. Review positions and opening permissions before expiry; do not assume expiry automatically closes positions.
Trial steps and activation entry (demo) · Enlarge screenshot

07 Subscriptions, renewal and subscription credit

  1. Open Subscription or Subscribe/Renew on the account card. Check platform and full login, choose monthly, quarterly or annual and review the quote. It applies only to that account. Current prices, available plans and terms come from the live quote, not a fixed tutorial price.
  2. Check billing months, amount and account before creating the invoice. Subscribe each account separately: renewing A does not extend B. After renewal, verify the new expiry on the account card rather than relying on a payment screenshot.
  3. If referral subscription credit covers the whole invoice, select full credit payment. If insufficient, follow the chain payment flow. Do not assume you can combine partial credit with an arbitrary transfer. Credit is not withdrawable or broker trading capital.
  4. Invoice history shows the linked account, amount, status and expiry. Open the existing invoice and refresh before creating or paying another. If the wrong account is selected, stop before payment.
Per-account subscription and invoices (demo) · Enlarge screenshot
Billing cycle and quote review (demo) · Enlarge screenshot

08 USDT TRC20 invoices: verify before paying

  1. Chain payment first asks you to bind your own sending wallet. Enter its TRON address and bind it to reveal the payment address. If using an exchange or unsure about the sending address, check with support first. Never enter a seed phrase, private key or exchange password.
  2. Verify USDT TRC20 network, the current invoice’s receiving address, the exact amount including decimals, bound sender wallet and deadline together. Copy from the live invoice, never from this guide, chat or an old screenshot. Blockchain transfers are difficult to reverse.
  3. In your wallet, select the correct network, check transaction fees/resources and the final received amount. Do not choose ERC20, BEP20 or another chain, round the amount or subtract fees yourself. This guide does not initiate payment; its invoice screenshot has no usable receiving address.
  4. Keep the transaction hash and time, then refresh the same invoice. Chain confirmations and site settlement can take time. PENDING does not mean failure and is not a reason to pay twice. Success should show PAID and update the selected account.
  5. For expiry, wrong amounts/networks or delayed settlement, do not send several additional amounts. Submit the invoice ID, transaction hash, network and time to support. A new invoice requires a new address/amount check.
Invoice: bind sender first; no real receiving address (demo) · Enlarge screenshot

09 Risk parameters: units, scope and verification

  1. Choose Risk on the intended account. Record previous values, edit one field at a time and save. Settings belong to that account; screenshot values are examples, not recommendations. Wait for client synchronization and inspect current/pending scale and EA logs. A saved setting is not a completed trade.
  2. Risk scale changes requested strategy volume, subject to contract specifications, volume step, free margin and order/total caps. Some scale changes wait for a later strategy cycle. Do not delete state or reinstall to force an update.
  3. Total gold volume adds buy and sell lots together; it is gross exposure, not their net difference. Spread points use the broker symbol’s Point quote unit, not dollars or a universal pip value.
  4. Daily loss checks realized P/L since the broker server’s midnight for this client’s Magic and gold symbol, including available commission and swap. It is not all account trading loss and excludes open floating loss. MT4’s available account-history range can affect the calculation; keep history available.
  5. Reaching a risk cap normally prevents new openings; it does not guarantee an immediate full close or a maximum possible loss. Gaps, disconnections and existing positions can still increase loss. No threshold guarantees profit.
FieldMeaning and limits
Risk scaleRequested strategy-volume factor, not a return multiplier. Pending values require client/cycle confirmation.
Maximum total lotsGross gold buy + sell cap; both hedge sides count.
Maximum order lotsCap for an additional order; oversized requests are not guaranteed to split.
Maximum spread points(Ask − Bid) / Point. With Point=0.01, 50 points is a 0.50 quote difference; unit example only.
Maximum daily lossRealized daily P/L for this client’s gold trades, broker-server day; excludes floating loss.
Panel font size (local EA)Display only, roughly 11–22; does not change lots, risk or language.
Account risk form; examples are not recommendations (demo) · Enlarge screenshot

10 Download: platform, language, release and integrity

  1. In Client, choose the client language, then download MT4 or MT5. Website and EA languages are independent. MT4 uses EX4 and MT5 uses EX5; these files are not interchangeable.
  2. Check release version, notes and SHA-256. On Windows PowerShell, Get-FileHash -Algorithm SHA256 -LiteralPath 'actual downloaded file path' prints its hash. Compare the whole hash to the site, not just the filename.
  3. If a download is blocked, verify the domain and source first; do not install a same-named file from a chat group. An unavailable language is labeled unavailable. Renaming a file extension does not convert platforms.
  4. Account risk settings are managed on the website; the current EA’s main local input is panel font size. Installation needs no seat_account.txt file or private Master password. Keep version and hash for troubleshooting.
Platforms, releases and six-language downloads (demo) · Enlarge screenshot

11 MT4: install, attach and permit trading

  1. Log into the intended broker account in the correct MT4 terminal. Confirm connectivity and gold quotes. Choose File → Open Data Folder, open MQL4 → Experts, create YIGold and copy the EX4 there. Open the data folder from the actual terminal; it may differ from its installation directory.
  2. Refresh Expert Advisors in Navigator. If missing, check extension and folder before restarting that specific terminal. Do not close all terminals merely to refresh when other trading programs or positions exist.
  3. Show the broker’s gold symbol, such as XAUUSD, XAUUSDm or GOLD, in Market Watch. Open its chart and drag the client onto it. Allow live trading in the EA’s Common settings, check Tools → Options → Expert Advisors and add the WebRequest whitelist described next.
  4. Enable the top AutoTrading control only after checking account, risk and authorization. Keep one active client instance per account; do not attach it to several gold charts. The current client needs no customer strategy tuning. Do not enable DLL imports without a specific need.
  5. The panel image is an offline test illustration, useful only for its layout. Check Experts/Journal for actual connectivity, authorization, symbol and errors. Keep today’s account history visible because MT4 realized daily P/L depends on available history.
MT4 data-folder installation diagram (not a terminal screenshot) · Enlarge screenshot
MT4 panel, offline test; not proof of live readiness · Enlarge screenshot

12 MT5: install EX5 and check the position mode

  1. Use File → Open Data Folder in the intended MT5, then MQL5 → Experts → YIGold, and copy the MT5 EX5. Refresh Expert Advisors in Navigator and attach the client to the broker’s gold chart. MT5 cannot execute EX4; source files or archives are not substitutes for EX5.
  2. Allow algorithmic trading in the EA properties and add the WebRequest address in Tools → Options → Expert Advisors. Check account, server, language and release before enabling the top Algo Trading button. Panel font size does not change positions or risk.
  3. Per-order mapping and group locking involve independent buy/sell positions. Verify the broker’s account position mode and gold hedging support. A netting account is not equivalent to a hedging account. If compatibility is uncertain, test on demo and contact support first.
  4. Inspect Toolbox → Experts and Journal. A screenshot of the expected layout does not prove your connection. Avoid other EAs, manual changes or a second terminal altering managed positions. For an unknown order outcome, reconcile actual positions before triggering anything again.
MT5 data-folder installation diagram (not a terminal screenshot) · Enlarge screenshot
MT5 panel, offline test; not proof of live readiness · Enlarge screenshot

13 WebRequest whitelist and terminal availability

  1. In MT4 / MT5 Tools → Options → Expert Advisors, enable WebRequest for listed URLs and add https://yigold.vip . This is the EA’s actual non-www service address. Opening www.yigold.vip in a browser does not grant the terminal permission.
  2. Save and wait for the next connection. Include https:// and avoid spaces, nonstandard punctuation or an individual API path. If a proxy, firewall or VPS outbound rule blocks HTTPS, check outbound 443 and DNS resolution.
  3. Keep the terminal logged in, network connected, client attached and automated trading allowed. Closing the website does not stop the EA. Closing the terminal, disconnecting, disabling AutoTrading/Algo Trading or EA permissions can also prevent protective reductions and closes.
  4. This setup needs no arbitrary DLL permission or remote VPS access for strangers. Record both the HTTP status and terminal GetLastError when troubleshooting; they are different code systems.
WebRequest setup diagram (not a terminal screenshot) · Enlarge screenshot

14 Terminal authorization: eight digits and device checks

  1. After attachment and connection, the EA creates an authorization request. On the website, open Confirm authorization for the matching trading account, refresh the list and check that login, broker server and terminal are the device you just installed.
  2. Confirm the correct pending request. If entering manually, use the EA’s eight-digit code. It is valid for about ten minutes. Wait for a new code on the original terminal if expired; never use the tutorial sample or publish a code in a group.
  3. Keep the terminal online after confirmation. Verify that the website’s last connection and the EA’s license/expiry update. Signing into the website, seeing a request or submitting confirmation does not replace checking final authorization.
  4. Use Reset device only for a genuine device move or reinstall. First check positions, execution state and the new device’s identity, then confirm its new code. Do not repeatedly reset for an ordinary disconnection or authorize unknown requests.
Confirm your own terminal (sample code is invalid) · Enlarge screenshot

15 Every EA panel field and readiness checks

  1. Check the account suffix and gold symbol first, then connection, license and expiry. The website may format dates in browser local time; where the EA labels expiry UTC, compare in UTC. A timezone difference alone is not an authorization failure.
  2. Buy/sell “actual / target” compares real positions with synchronized targets. Volume steps, risk limits, sessions, target changes and fill synchronization may temporarily differ. One number alone cannot establish a missing order.
  3. Service status, last synchronization and group state show freshness. Group running/paused/locked and the local new-trade pause are distinct. Resuming one does not automatically remove the other restrictions.
  4. The local panel font-size input only changes readability and is bounded by the current client (roughly 11–22). Adjust for overlapping text, not to alter trading. TESTER/OFFLINE on the illustration explicitly means offline testing.
FieldMeaning and limits
ConnectionConnection, authorization or risk state; inspect logs for errors.
LicenseAccount entitlement, not proof of a fill.
ExpiryCheck timestamp and any UTC label.
Account suffixMasked display; match it to the terminal’s full login.
Gold symbolActual broker symbol; suffixes can differ.
Strategy serviceCloud/strategy availability, not broker fill confirmation.
Last syncUse for freshness, considering timezone.
Buy actual/targetActual buy positions versus target lots.
Sell actual/targetActual sell positions versus target lots.
Group stateRunning, paused and locked are distinct.
New tradesCheck local pause separately from cloud pause.
Skipped buy cycleMatches the current buy basket ID.
Skipped sell cycleMatches the sell basket ID, not a permanent switch.
MT5 panel, offline test; not proof of live readiness · Enlarge screenshot

16 Pause, resume and skip the current cycle

  1. The panel’s Pause new trades locally blocks additional exposure while normally allowing managed reductions/closes. Toggle again to restore local opening eligibility. Website account pause and group pause are cloud controls that require a connected client.
  2. Skip current cycle records the current buy and sell basket IDs, potentially skipping both directions. It does not permanently disable the EA or close existing positions. With no current basket, it does not preselect a future cycle to skip.
  3. When a new basket begins, the old skip ID no longer matches. Do not treat the button as an arbitrary undo of the current skip. Resuming still requires authorization, risk, market and cycle-admission conditions and does not guarantee catching up missed trades.
  4. To retain protective management, do not replace Pause new trades with closing the terminal or disabling AutoTrading/Algo Trading. If you need reductions or liquidation, use explicit closing controls and verify actual fills and remaining positions.

17 Synchronization, first-entry admission and missed trades

  1. The private strategy trades, the cloud computes account-eligible targets and the client executes plans using local order mappings. Target volume is not filled volume. Latency, contract rules, spread and limits can make a follower differ from the source.
  2. The current client handles missed cycle/first-entry admission conservatively and does not promise mid-cycle catch-up. If newly installed and online with no positions, check strategy, skipped-cycle and risk states, then wait for an eligible new cycle. Repeated restarts do not legitimately force a missed entry.
  3. Partial fills, partial closes, remaining volume and order tickets need reconciliation. A successful send or submitted web command is only the start, not proof of broker completion. For unknown outcomes, inspect actual positions and logs before any repeat.
  4. Do not edit client state/mapping files or let another EA use the same management identity to change positions. Manual closes can affect later mapping/synchronization. Pause additional risk and preserve evidence for support if anything is inconsistent.

18 Group control: totals, coverage and account filters

  1. Start with balance, equity, floating P/L and coverage. Header totals and command scope are different: totals may include all active subscribed accounts, while commands follow the current group or temporary selection.
  2. Check fresh, stale and excluded accounts and last synchronization. Offline clients, old releases or unsupported currencies can be excluded from a consistent total. Incomplete coverage is not a live total of all assets. Check the displayed currency/cent-account conversion rules.
  3. Find accounts using login search, status filters, pagination and page size. Open details for platform, full login, server, gold symbol, balance/equity, EA/lock state, expiry, risk and client release.
  4. Commands are asynchronous and execution varies by network/broker; a batch can partly succeed and partly skip. Inspect scope and risk before submitting, then verify each account’s result rather than relying on changed summary totals.
Group totals, scope and controls (demo) · Enlarge screenshot

19 Create groups, move members and use temporary selection

  1. Choose New group, enter a recognizable name (up to 40 characters), select accounts and save. An account belongs to only one custom group. Adding one from another group moves it; it does not duplicate membership.
  2. Manage group changes membership or deletes the group. Deleting a group is not a position-close command and must not be used to stop trading or liquidate. Trial accounts can only have their own single-account group.
  3. Temporary checked accounts override the current group and may persist across pages. Read Scope and account count before acting. Clear selection to restore group scope, then verify no previous checkboxes remain.
  4. Learn the confirmation flow on demo without real positions. Seeing only two rows does not mean a command affects only two accounts. The preflight target list defines its scope.
Group editor and members (demo) · Enlarge screenshot

20 Group start, pause, net lock and unlock

  1. Start allows selected accounts to resume strategy execution and may permit immediate openings. Pause blocks further strategy exposure; it does not close all positions. The current Pause flow can submit directly after preflight, while other consequential actions show confirmation. Do not assume every click asks twice.
  2. Net lock requests opposite gold exposure to hedge net volume, not remove every position. It requires compatible hedging support and still consumes margin, spread, fees and possibly swap. Locking is neither risk-free nor proof of a realized stop-loss.
  3. Unlock handles lock hedges and resumes strategy, potentially opening again immediately. Review direction, lock state, free margin and preflight warnings first; do not click without understanding the account’s position mode.
  4. Clients must be online, authorized and compatible. Individual accounts may fail or skip. Inspect command details per account and actual terminal positions before any further action; do not repeatedly click to repair an unknown outcome.
Preflight confirmation; no trade executed (demo) · Enlarge screenshot

21 Group manual opens: fixed lots and equity margin budget

  1. Choose scope, buy or sell, then sizing mode. Fixed lots request the same amount for each target account, not a total divided across the group. Two accounts at 0.01 request 0.02 in total; that example is not a recommendation.
  2. Equity percentage means each account’s margin budget as a percentage of equity, not percentage loss at a stop. It sets no price stop and guarantees no maximum loss. Broker contract and margin specifications determine resulting lots.
  3. Preflight lists targets, eligible/skipped counts, estimated lots per account and warnings. Final broker checks still apply. MT4 can skip if required margin specifications are unavailable; estimates are not fills.
  4. Check side, mode, value and logins before confirming. Distinguish requested from filled volume and inspect command details and terminal positions afterwards. Never increase lots just to test whether a connection works.

22 Seven close actions and stopping the EA

  1. Close buys handles gold buys; Close sells handles gold sells. Each side offers all, profitable or losing positions. Selection uses the client-visible position state at execution; P/L can change between submission and execution.
  2. Ordinary close actions keep strategy execution enabled, so eligible positions may open again. If the objective is to stop and clear gold exposure, understand and choose the explicit Close all and stop EA action instead of repeatedly using ordinary side closes.
  3. Close all affects every gold position in the target account scope, potentially including manual or other-strategy gold positions. Do not treat it as limited to this client’s Magic. Other symbols are outside this gold command scope. Check scope and warning first.
  4. Slippage, closed markets, rejects, partial fills or offline clients can prevent completion. Inspect per-target results and actual remaining gold positions, plus EA stop state. A disabled button is not proof that all positions closed.

23 Command history, partial success and unknown outcomes

  1. Open History and identify the recent command by time, action and scope. Details show account, status, effective lots, result code and explanation. Keep the command ID for support.
  2. PENDING means queued, EXECUTING in progress, SUCCESS a successful result, FAILED failure and SKIPPED omission. PARTIAL_SUCCESS means only some targets succeeded. Submitted never means every broker fill completed.
  3. Offline clients, expiry, trial rules, old releases, risk caps and broker rejects can affect targets. Read the actual reason before addressing it. Reconnection does not promise arbitrary later execution of an old command.
  4. If the webpage errors but a terminal may have received the instruction, preserve ID, time and positions and reconcile the original outcome. Blind repetition can add exposure or duplicate closing intentions.
Command history and result details (demo) · Enlarge screenshot

24 Referrals, rewards and credit ledger

  1. Copy your personal registration link from Referrals. Check its language and code before sharing. The recipient should register with that link/code; a later chat claim does not establish attribution.
  2. The page shows referral statistics, current reward rules, available subscription credit and ledger. Rates and eligibility follow the displayed rules; an invitation does not promise immediate credit. Example amounts are not real income.
  3. Ledger entries can include referral rewards, subscription debits and administrative adjustments. Check signs and references. Credit only pays website subscriptions, cannot be withdrawn and does not become broker margin.
  4. For discrepancies, send support the code, relevant necessary user/invoice references and time. Do not publish both parties’ emails, wallets or login credentials.
Referral link and subscription credit (demo) · Enlarge screenshot

25 Support tickets, logs and screenshot privacy

  1. In Support, enter a clear subject (up to 150 characters) and message (up to 5,000), submit and check replies in the list. Explain your intended action, observed outcome, start time and whether positions or unknown orders remain.
  2. Include MT4/MT5, EA release, necessary account identification, broker server, gold symbol, time with timezone, error code and command/invoice ID. Matching Experts and Journal logs are more useful than a button screenshot alone.
  3. Locate logs through the terminal/data folder and save a short excerpt before/after the event, preserving encoding and time. Never send strategy secrets, passwords, cookies, API keys, seed phrases, authorization codes or authenticator secrets.
  4. Redact personal details and payment addresses while retaining the actual error. Server retention is limited, so save local evidence promptly. Submitting a ticket does not automatically restore trading; continue observing the terminal and controlling new exposure.
Support form and replies (demo) · Enlarge screenshot

26 Troubleshooting and error codes: identify the layer

  1. First distinguish website sign-in, EA networking, licensing, risk limits and broker execution. HTTP 401, MT4/MT5 runtime errors and MT5 trade return codes are separate systems; matching digits do not imply the same meaning.
  2. No trades after setup: check account/server, unexpired authorization, gold symbol, fresh sync, pauses/skips, an eligible new strategy cycle, open market and limits. No positions alone does not establish a fault. Do not test by removing every risk cap.
  3. After reconnection or reinstall, reconcile old positions and original commands. Never repeat unknown outcomes. When network or permissions are disabled, software protection may not execute: inspect actual broker positions and existing protection too.
  4. The table gives common directions, not a diagnosis without context. Preserve full logs and version, consult the website code reference and official documentation and send original errors to support.
Code/stateWhat to inspect
5200 / 5201 / 5202 / 5203MQL network: invalid URL, connection, timeout, HTTP request failure; whitelist, DNS, HTTPS and logs.
HTTP 401Invalid session/authorization; distinguish website and EA credentials, do not delete state and resend.
10014 (MT5)Invalid volume: symbol minimum, maximum, step and requested amount.
10018 (MT5)Market closed: broker gold sessions and server time.
10019 (MT5)Insufficient margin: free margin, leverage, contract and lots.
10027 (MT5)Terminal automated trading disabled: Algo Trading and EA properties.
4756 (MT5)Send failed: accompanying broker return code, Experts and Journal.
OFFLINE / EXPIRED / CLOSE_ONLYCheck fresh sync, license expiry and opening/pause restrictions respectively.

27 Upgrade, move VPS, reset a device and unbind

  1. Before upgrading, record release, login/server, positions, cloud/local pause states and unfinished commands. Download the official platform/language file and verify its hash. Resolve unknown trade outcomes before repeated removal/reinstallation.
  2. Replace the intended EA file in a planned maintenance window, preserving authorization/order-state files. Check release, connection, position mapping and risk afterwards. Do not “clean” Common Files, mappings or caches used to prevent duplicate execution.
  3. For a VPS move, ensure old and new terminals do not execute the same account simultaneously, then reset/confirm the new device code. With open positions, plan protection continuity: between stopping the old terminal and readiness of the new one, software management has a gap.
  4. Unbind stops new openings and releases the account after positions close. It is not instant liquidation or a refund. Reconcile pending actions and gold positions, then wait for final state; removing an account does not resolve a trade inconsistency.

28 Other website pages: strategy, performance, data and tools

  1. Strategy explains synchronization, not customer control of the private strategy. On Performance, inspect coverage, historical reconstruction/live-record labels, drawdown and risk, rather than extrapolating one return number to your own account.
  2. Data, System status and Methodology explain provenance and freshness. Missing/unverified data does not mean zero risk. Healthy service status does not prove your VPS, broker or every account is healthy.
  3. Lot/risk tools require your broker’s real contract, minimum lot, step, Point, contract size and leverage. Gold suffixes and cent accounts may use different specifications. Calculator estimates never replace final broker checks.
  4. Read Security, Privacy, Terms and Risk before purchase. Contact leads to support. Languages preserve the same account and data; switching website language does not change the broker account or automatically change the EA language.

29 First-use checklist and daily review

  1. Before first use complete: email/invitation registration → correct login/platform → trial/subscription → risk settings → official download/hash → data-folder installation → WebRequest/trading permissions → eight-digit confirmation → connection, license, expiry and symbol checks.
  2. Observe a complete eligible strategy cycle on demo, including opening, position changes and exit; reconcile real positions and command results. A visible panel or a single fill does not verify every function.
  3. Daily review login/server, network/fresh sync, expiry, actual/target gold positions, pause/lock state, caps and unfinished commands. Repeat after renewal, restart or upgrade; pay particular attention to trading switches after VPS updates or broker maintenance.
  4. On anomalies, control new exposure, preserve logs and reconcile actual positions/original outcomes before contacting support. Do not edit mappings, blindly resend, expose credentials or assume closed software means closed positions.

Official platform references

MetaTrader 4 · Open Data FolderMetaTrader 5 · Settings / WebRequestMetaTrader 5 · Expert AdvisorsMQL5 · Runtime error codes