EdgeDriven Dollar Yen Portfolio
- Experts
-
Dan Mishima
Vantaggio supportato da prove concrete.
EdgeDriven Algo è un marchio di Expert Advisor (EA) che sviluppa sistemi di trading algoritmico, privilegiando robustezza e riproducibilità attraverso la verifica statistica. - Versione: 1.102
- Attivazioni: 5
EdgeDriven Dollar Yen Portfolio is a fixed, nine-module USDJPY Expert Advisor for MetaTrader 5 hedging accounts. One installation evaluates multiple H2 strategy modules under a common risk and execution framework with separate module ownership.
At a glance
-
USDJPY H2 portfolio — 9 fixed strategy modules
-
No Martingale or grid averaging
-
Protective stop-loss, break-even management and bar-count exits
-
3,418 historical trades from January 2014 through June 2026
-
Combined historical MT5 Profit Factor: 1.57
-
Historical reference tested in MetaQuotes-Demo real-tick mode
-
Development / Validation / Final Historical Holdout periods disclosed separately
-
No customer-side DLL, external indicator installation, license server or subscription required
Try before purchasing
Use the free Market demo to test the EA in MetaTrader 5 Strategy Tester before deciding whether to purchase. Test it with your own broker history and trading conditions, and compare the results with the disclosed reference evidence below.
EdgeDriven Algo. Edge, Backed by Evidence.
The results below are historical MT5 simulations, not live or Forward returns. Leveraged currency trading can cause substantial losses.
Why a portfolio?
Different modules can act at different times while one installation manages their ownership and operating controls. All nine modules still share USDJPY and account exposure, so correlation and simultaneous losses remain possible and the portfolio does not represent nine independent sources of future profit.
What is inside
The USDJPY-specific frozen composition combines price, momentum and volatility conditions on H2. Entries use pending stops, with protective stop-loss, break-even management and bar-count exits. Individual strategy recipes and relative weights are fixed. This is a separate nine-module implementation, not a symbol setting of the twenty-module Gold product.
Calculated volume rounds down to the broker step. Trades below minimum volume are skipped without increasing lot size or redistributing the skipped budget. Price, stop-distance, session, order-capacity and margin checks precede submissions.
Validation Process
- Development (2014–2022): portfolio construction and candidate selection. The top candidates were frozen before Validation was opened.
- Validation (2023–2024): portfolio-level narrowing and priority setting using Development and Validation only.
- Final Historical Holdout Confirmation (2025–June 2026): historical confirmation after portfolio membership and priority were frozen.
No membership, weighting or ranking changes, re-optimization or rescue were made after the Final period was evaluated. Combined history is descriptive; it was not the portfolio-combination selection score.
This phase separation applies to portfolio combination selection. Individual strategies had previous later-period exposure during formal qualification or research, so Final is not completely unseen data for those strategies. It is a historical confirmation stage, not live or forward performance, and does not guarantee future results.
Historical evidence: reference configuration
Version 1.102; USDJPY H2; MetaQuotes-Demo real-tick test mode; USD 10,000 initial capital; hedging account; leverage 1:100; ProductRiskScale=1.0; BaseRiskPercent=0.9; Compounding=false. All rows below use the same frozen production EX5.
| Period | Net profit USD | MT5 PF | Equity DD at maximal drawdown | Trades |
|---|---|---|---|---|
| 2014–2022: Development | 4,335.21 | 1.58 | 4.06% | 2,425 |
| 2023–2024: Validation | 1,068.23 | 1.69 | 1.87% | 565 |
| 2025–June 2026: Final Historical Holdout Confirmation | 325.72 | 1.32 | 1.85% | 428 |
| 2014–June 2026: Combined descriptive history | 5,729.16 | 1.57 | 4.06% | 3,418 |
The first three rows are separately initialized tests; Combined is a continuous test. Period names describe their assessment purpose and do not imply untouched individual-strategy holdouts. Final Historical Holdout Confirmation is not Forward or live trading. Combined is descriptive, not an additional independent sample. End date is 1 July 2026 exclusive.
PF is the official MT5 report value at displayed precision. The DD percentage is the percentage shown with MT5's maximal money equity drawdown, relative to the associated equity peak; it is not a percentage of initial capital or a loss limit. The native MT5 graph displays modeled Balance and Equity; it is not a reconstruction or a live account curve.
Losses are part of the evidence
The continuous history contains 93 positive and 57 negative calendar months. The worst posted-cash month was January 2015 at USD -212.10. Monthly cash sums posted profit, commission and swap; it is not a mark-to-market monthly return. July–December 2026 are outside the test, not zero months. Future losses can be worse.
Risk and reference settings
The reference settings allocate a nominal 0.1% of the stored starting balance per module entry before broker rounding. With Compounding=true the basis becomes current account balance. Other scales and compounding are not performance projections from the reference table.
USD 10,000 is an evidence setting, not a universal minimum or personalized capital recommendation. A USD 100 execution check skipped trades rather than exceed its budget at minimum lot. High-capital, low-leverage and doubled-spread checks are engineering evidence, not additional recommended risk profiles.
Risk Controls
Operational controls manage order handling; they do not prevent losses or guarantee execution.
Friday cleanup and weekend pause
Designed to avoid routine weekend position carry through scheduled Friday cleanup and a weekend trading pause. Execution remains subject to broker availability, terminal connectivity and market conditions.
From Friday 20:00 until Sunday 23:00, in broker server time, new entries are blocked. On incoming ticks during this window, the EA requests cancellation of its pending orders and closure of its open positions, retrying when trading is possible. Broker sessions, permissions, freeze levels and connectivity can delay or prevent completion. Different broker timezones change the corresponding UTC hours.
At Sunday 23:00 broker server time the weekend gate ends. Entries resume only when the normal H2 bar and signal rules, trading permissions and broker-session checks permit; a market reopening alone does not trigger an entry.
Reading weekday and hourly statistics
MT5 Entries by weekdays/hours counts entry deals. Profits and losses by weekdays/hours groups exit deals by their recorded closing time. Scheduled pre-weekend cleanup can therefore concentrate realized profit or loss in the Friday bucket, or the corresponding server-time hour/day. This is not evidence of a Friday-specific entry edge. The report clock and cleanup clock may differ, especially for the UTC-based Gold rule.
Protective stops and order checks
Entries carry a protective stop-loss. The EA manages break-even changes, pending-order expiry and bar-count exits under the fixed module rules. Before submission it checks broker volume steps and limits, stop/freeze distances, order capacity and available margin, including pending-order margin reservation. Below-minimum calculated volumes are skipped rather than increased. Accepted stops remain broker-side; software management requires a running terminal and quotes. Gaps and slippage can increase realized losses.
Restart and ownership
Management is restricted to the chart symbol and the reserved MagicBase range. Local state retains the starting-capital basis and last processed bar, while current orders and account history inform management after reinitialization. Keep one instance per ownership context and preserve terminal state. Tester reinitialization was exercised; this is not live reconnect, crash or VPS power-loss certification, and there is no cross-terminal duplicate-instance lock.
Economic news
This release does not implement an economic-calendar News Guard. It does not block entries or close positions around specified news events. No event, importance, currency or pre/post-event protection window is configured or claimed in the tester or live operation.
Operating requirements
- MetaTrader 5 hedging account; netting is not supported.
- One instance on the broker's USDJPY H2 chart, with synchronized H2 history.
- An exclusive MagicBase through MagicBase+8 range and sufficient account margin.
- A continuously running terminal or VPS, fresh quotes and trading permissions for managed actions.
- Broker server time governs Friday 20:00 cleanup and the weekend pause through Sunday before 23:00. Different server times can change behavior.
The EA evaluates the current chart symbol without an instrument-name refusal. Verify the chart before enabling entries. USDJPY is the recommended and performance-evidenced instrument; another symbol working in a technical test does not establish its trading suitability. No customer DLL, external indicator installation, license server or subscription is needed.
Inputs and operational limits
| Input | Default | Operation and limits |
|---|---|---|
| ProductRiskScale | 1.0 | Positive common multiplier. 1.0 is the verified reference; increasing it can increase loss and margin needs. |
| BaseRiskPercent | 0.9 | Positive, at most 100. Reference percentage divided equally across nine nominal entry budgets; not a drawdown cap. |
| Compounding | false | Stored starting balance when false; current account balance for new sizing when true. Reference evidence uses false. |
| TradingEnabled | true | Permits new entries. False retains management and does not cancel accepted pending orders. |
| EmergencyStop | false | Blocks entries and repeatedly requests owned pending cancellation and owned position closure when execution is possible. |
| MagicBase | 560506780 | Integer 1 to 2147483600. Owns MagicBase through MagicBase+8; default 560506780–560506788. Reserve this range exclusively. |
| SlippagePoints | 20 | Nonnegative requested deviation for market operations, in broker points; not a maximum-loss or fill guarantee. |
| AuditDiagnostics | false | Reserved in this release; leave false. It does not enable a separate diagnostic display. |
Use the verified defaults as the comparison baseline, then test your own broker conditions before use. Risk inputs do not enforce a guaranteed loss limit. Do not alter MagicBase while owned exposure remains.
Installation and support
Install the purchased product through MetaTrader's Market workflow. Before attachment, set TradingEnabled=false in the Inputs dialog while checking the account, chart, history, risk basis and exclusive Magic range. This setup setting differs from the compiled default true and is not a separate performance preset. Enable new entries only when you intend to allow orders and the Journal shows initialization.
Keep terminal state across reinitializations. On an update or VPS migration, prevent duplicate management from the previous instance and reconcile open positions and pending orders first. The stored capital basis is local and is not automatically transferred by this package.
Use the product comments or MQL5 messaging for support. Provide the product version, sanitized Journal messages and relevant symbol specifications. Never share credentials. Support does not provide personalized investment advice.
How to read the evidence gallery
The first image identifies the product; it is illustration, not a trading result. Images 3 and 4 contain actual English MT5 Strategy Tester screenshots: the Combined Backtest report and the native Balance / Equity graph. Only the surrounding brand frame and explanatory captions were added; report values and graph pixels were not redrawn. Period and risk panels are explanatory summaries. These are historical simulations, not live or forward results.
No product-linked live or demo-forward performance is presented here. A technical demo setup or restart test is not a Forward return record. Evaluate historical results together with modeling, costs and operating limits.
Frequently asked questions
Does this use Martingale or grid recovery?
No loss-recovery lot ladder or grid averaging is used. Each module checks its own fixed signal; sizing uses the configured capital basis and protective-stop distance. A module does not submit another entry while it owns a position. Different modules can still be exposed at the same time.
Is this the Gold product with another symbol?
No. This release uses a separately frozen nine-module USDJPY portfolio with H2 signal evaluation and its own production evidence. The Gold product uses twenty modules and H1/H4 history. A shared brand and general risk-engineering practices do not imply identical strategies or combined portfolio validation.
Does nine modules mean nine independent sources of profit?
No. All modules share USDJPY and account exposure. Correlation and simultaneous losses remain possible. No future profitability or independence is established.
Can I select modules or optimize their weights?
No. The membership and relative construction are fixed. ProductRiskScale changes the common sizing scale; it does not select components.
Which account and chart should I use?
Use an MT5 hedging account and your broker's USDJPY H2 chart, with sufficient synchronized H2 history. The recorded reference is USD-denominated at 1:100. Netting is not supported. The engine uses the current chart symbol and evaluates H2 internally, so attaching it to another instrument can produce orders there; those instruments are not recommended or performance-validated.
Is USD 10,000 the minimum deposit?
It is a tested reference, not a universal broker minimum. At low balances, minimum-volume constraints can cause skipped trades or no trades. Do not increase risk simply to force participation.
Does 0.9 mean a maximum 0.9% portfolio loss?
No. At scale 1 it is divided into nine nominal 0.1% entry budgets before rounding. Costs, gaps, slippage, simultaneous exposure and pending fills can increase realized loss. Historical drawdown is not a future limit.
Does TradingEnabled=false make the account inactive?
No. It blocks new submissions while owned management continues. Existing pending orders may fill. Turning terminal Algo Trading off can also prevent EA-managed actions, while accepted broker-side orders remain active.
What does EmergencyStop do?
It blocks entries and attempts to cancel owned pending orders and close owned positions. It requires incoming quotes, trading permission, an open session and broker acceptance. It is not guaranteed instant liquidation, and it does not close unrelated magic identifiers.
What happens while the terminal is offline?
Accepted protective stops remain broker-side and pending orders can fill. Software expiry, break-even moves, time exits and Friday cleanup require the terminal. Keep it connected; reconnection is not a guarantee of the intended exit price or time.
Are the later periods untouched OOS or live results?
No such claim is made. These are historical MT5 tests; prior strategy research exposure prevents a universal unseen-data claim. Combined history is descriptive, not another independent validation sample. No demo-forward or live return is presented.
Can I run this alongside the Gold product?
Only with distinct ownership ranges and sufficient shared account capacity. Their combined performance and joint risk have not been verified here. This product's state cannot coordinate duplicate instances across separate terminals.
Are DLLs, indicator files or external subscriptions required?
No. The production EX5 contains the required implementation. Use the purchased Market build, not private QA experts. Support is available through product comments or MQL5 messaging; never send passwords.
Evidence limitations and risk disclosure
Commission in these reference reports is zero; historical spread and reported swap are included. Broker costs, history, execution and time conventions can differ. Real-tick test mode is still a historical simulation, not proof of future fills.
Broker-side protective stops do not guarantee exit price or realized loss. Software pending expiry, break-even management, time exits and Friday closure depend on a running terminal and successful execution. Pending orders can fill while offline. Instrumented reinitialization in the tester is not live network, crash or VPS power-loss certification.
Historical simulated performance does not guarantee future results, broker universality or independence between modules. Leveraged trading can cause substantial losses.
Version notes
Trading release 1.102. This sales-package revision updates presentation, explanations, FAQ, brand assets and evidence organization. It does not change the frozen production MQ5, EX5, nine-module composition, relative construction or verified results.
