MQL5 Market validation — safe first-time initialization of a trading EA without user interaction
Li Chin Fatt:
- Is there an officially supported mechanism to establish trustworthy first-install initialization during unattended Market validation?
- If an EA safely refuses new trading operations until explicit first-time enrollment is completed, is that design compatible with Market automatic validation?
Market Rule IV(6) is on-point:
The Seller shall not integrate and apply any third-party sales, accounting, license control and update management systems (including the ones using WebRequest features) in Products (emphasis added).
Would such mandatory safety enrollment be considered a prohibited functionality restriction under Market Rules IV.7 or V.5, even when it is unrelated to licensing or account eligibility?
The Seller shall not collect users' personal data by means of Products or implement additional custom limitations on the functionality of MQL4/MQL5 applications (emphasis added).
Could MetaQuotes please clarify:
-
Is there an officially supported mechanism to establish trustworthy first-install initialization during unattended Market validation?
-
If an EA safely refuses new trading operations until explicit first-time enrollment is completed, is that design compatible with Market automatic validation?
-
Would such mandatory safety enrollment be considered a prohibited functionality restriction under Market Rules IV.7 or V.5, even when it is unrelated to licensing or account eligibility?
1. No.
2. No.
3. Yes.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Hello,
We are preparing an MT5 Expert Advisor for the MQL5 Market. Before implementing its next version, we would like clarification about safe first-time initialization during automatic Market validation.
The proposed next version would maintain persistent trading-state records using native MQL5 SQLite functionality, without DLLs or external licensing services.
For safety, a missing database cannot automatically be interpreted as a fresh installation, because previously committed trading records might have been lost.
A genuine first installation therefore requires an explicit account-holder confirmation and checks of the observable broker state before enabling new trading risk.
Our concern:
MQL5 Market automatic validation runs unattended in the Strategy Tester with default inputs. There is no real account holder available to confirm that the installation is genuinely new.
We do not wish to use tester-only bypasses, automatically pre-approved declarations, artificial trades, or relaxed risk controls to pass validation.
Could MetaQuotes please clarify:
Is there an officially supported mechanism to establish trustworthy first-install initialization during unattended Market validation?
If an EA safely refuses new trading operations until explicit first-time enrollment is completed, is that design compatible with Market automatic validation?
Would such mandatory safety enrollment be considered a prohibited functionality restriction under Market Rules IV.7 or V.5, even when it is unrelated to licensing or account eligibility?
We are looking for a supported design approach before developing and submitting the product.
A response from MetaQuotes staff or a reference to official documentation would be particularly helpful.
Thank you.