Research Strategy for Developing a Robust MT5 Price Continuation Expert Advisor

I. Executive Summary
This report outlines a comprehensive research strategy for developing a MetaTrader
5 (MT5) Expert Advisor (EA) based on a price continuation hypothesis. The EA aims
to achieve fast and long-term growth through consistent profit securing and
stringent loss prevention, utilizing entry signals derived from last high/low
breakouts, moving average crossovers, or Relative Strength Index (RSI) indicators.
A defining characteristic of this strategy is an aggressive 1-pip trailing stop
loss, activated upon achieving 1.5 pips in profit.

The strategy's inherently high-frequency, small-profit nature necessitates extreme

precision in execution, meticulous accounting for transaction costs, and rigorous
validation methodologies to ensure real-world viability. Key recommendations
include fixing identified look-ahead biases in signal generation, adapting profit-
securing mechanisms for optimal growth, implementing dynamic position sizing that
compounds profits responsibly, and establishing a robust risk management framework
with layered drawdown controls and emergency stops. Furthermore, the success of
such a high-frequency system hinges on utilizing high-quality tick data for
backtesting and optimizing the trading environment for minimal latency.

II. Introduction to the Price Continuation Strategy

The core of this Expert Advisor (EA) is predicated on the price continuation
hypothesis, which posits that short-term price movements tend to persist in their
current direction. This market belief forms the foundation for capturing
incremental gains as prices extend beyond established levels or continue along a
prevailing trend.

Detailed Breakdown of the EA's Proposed Trading Logic

The EA's operational framework is designed around specific, quantifiable conditions
for market engagement and exit:

Entry Conditions: The EA is engineered to identify potential price continuation

opportunities through a combination of technical indicators. These include entries
based on breakouts from recent high or low price levels, signals generated by the
crossovers of various moving averages, and indications from the Relative Strength
Index (RSI). The provided code snippets, such as SureEa_V2.txt and

[Link] , illustrate the foundational elements for detecting these signals.

Profit Target: A fixed profit target of at least 1.5 pips is stipulated for each
trade. In the context of MT5, where 1 pip typically equates to 10 points for 5-
digit brokers, this translates to a 15-point profit objective. It is important to
note that the TpPoints parameter in the provided code snippets (SureEa_V2.txt
shows 150 points, and

[Link] shows 200 points) suggests a larger default take profit than the user's
stated 1.5 pips, a discrepancy that requires careful consideration during
optimization.

Aggressive Trailing Stop Loss: A critical component of the strategy is an

aggressive 1-pip (10 points) trailing stop loss. This mechanism is intended to
activate promptly once a trade achieves 1.5 pips (15 points) in profit. This rapid
adjustment aims to secure gains and mitigate risk. The SureEa_V2.txt code,
however, sets

TslPoints at 20 (2 pips) and TslTriggerPoints at 30 (3 pips), which is less

aggressive than the specified requirement. The user's explicit preference for a 1-
pip trailing stop after 1.5 pips profit will be prioritized in the strategy's
development.
Challenges and Opportunities Inherent in High-Frequency, Small-Profit Strategies
The defined profit target (at least 1.5 pips) and the aggressive 1-pip trailing
stop loss after 1.5 pips profit are hallmarks of a scalping strategy. Scalping
involves capturing numerous small price changes over very short durations, often
executing dozens or even hundreds of trades within a single day, with positions
held for mere seconds to minutes. This strategic choice carries significant
implications for the EA's development and operational viability.

The EA's classification as a scalping strategy means it will inherently generate a

very high volume of trades. This high frequency, while offering numerous
opportunities for small gains, also means that every fractional cost associated
with trading—including spreads, commissions, and slippage—will accumulate rapidly.
These cumulative transaction costs can significantly erode the narrow profit
margins targeted by each trade. For instance, if a trade aims for 1.5 pips profit,
and the round-trip transaction cost is 0.5 pips, then one-third of the potential
gross profit is consumed by costs before any net gain is realized. This substantial
impact on net profitability underscores the paramount importance of minimizing
these costs and ensuring ultra-fast, precise execution for the strategy to remain
viable.

Furthermore, the aggressive 1-pip trailing stop, activated after only 1.5 pips in
profit, is designed to lock in gains very quickly and prevent profitable trades
from turning into losses due to pullbacks. This mechanism is highly effective for
stringent loss prevention and consistent profit securing on an individual trade
basis, as it rapidly reduces exposure to market reversals. However, this extreme
tightness also means that the strategy will frequently exit trades prematurely,
potentially cutting off larger winning trends. This trade-off can limit the overall
upside potential and lead to a higher frequency of trades with smaller average
profits, which in turn further magnifies the impact of transaction costs.
Therefore, a delicate balance must be struck between immediate profit protection
and allowing trades sufficient room to develop into more substantial gains for
long-term growth.

III. Core Trading Logic: MQL5 Implementation and Refinement

The successful development of this MT5 EA requires meticulous attention to the
implementation and refinement of its core trading logic, ensuring both signal
integrity and dynamic trade management.

A. Advanced Entry Signal Formulation

The EA's entry signals are based on last high/low breakouts, moving average
crossovers, and RSI signals. The accurate and unbiased formulation of these signals
is paramount.

Last High/Low Breakouts

The SureEa_V2.txt and

[Link] snippets incorporate

FindSignificantHigh() and FindSignificantLow() functions to identify price

extremes, which are then used as entry points for pending orders. These functions
utilize iHighest() and iLowest() to determine the highest or lowest price within a
specified window of historical bars, followed by additional checks to confirm their
significance.

A critical issue identified in the FindSignificantHigh() and FindSignificantLow()

functions within SureEa_V2.txt is the presence of a

look-ahead bias. Specifically, the conditions

iHigh(_Symbol, Timeframe, i + j) >= high and iLow(_Symbol, Timeframe, i + j) <= low
access price data from future bars (i + j) relative to the bar currently being
evaluated (i). In a live trading environment, such future data would not be
available, rendering any decisions based on it invalid. This flaw can lead to
artificially inflated backtest results, creating an illusion of profitability that
will not be replicated in live trading, directly undermining the objective of fast
and long-term growth. Similarly, the

findLow() function in [Link] contains a typo (

== 1 instead of == i) in its iLowest comparison, which must also be corrected to

ensure accurate pivot identification.

To rectify this, the future-looking i + j checks must be removed from both

FindSignificantHigh() and FindSignificantLow() functions. The logic should rely
solely on the

iHighest() and iLowest() functions to identify pivot points, ensuring that the
confirmation of a significant high or low only occurs after the relevant bars have
fully closed in the past. For real-time trading, a significant high or low can only
be confirmed once the pattern is fully formed using historical data, often with a
slight delay. After implementing these corrections, a complete re-backtest with the
revised logic is essential to establish a true and unbiased baseline performance.
This underscores the necessity for continuous vigilance against subtle biases
throughout the strategy development and optimization process.

Moving Average Crossovers

Moving Average (MA) crossovers are widely used technical analysis tools for
identifying trend direction and potential entry or exit points. A "Golden Cross,"
where a shorter-period MA crosses above a longer-period MA, is typically
interpreted as a bullish signal, while a "Death Cross" indicates a bearish signal.
MQL5 provides the

iMA function, which can compute various types of moving averages (e.g., Simple
Moving Average, Exponential Moving Average) over specified periods, facilitating
their integration into the EA's logic.

While MAs are fundamental indicators, their inherent lag can present challenges for
a scalping strategy that targets very small profits. Scalping thrives on rapid,
micro-price movements. Indicators with a built-in lag, such as traditional MA
crossovers, may generate signals too late to capture these fleeting opportunities
or may produce numerous false signals (known as "whipsaws") in choppy, short-term
market conditions. Each false signal, regardless of its magnitude, incurs
transaction costs (spread, commission, slippage), which can quickly erode the thin
profit margins characteristic of scalping. To make MA crossovers a viable component
of this EA, research should focus on utilizing extremely short MA periods (e.g., a
5/8/13 EMA combination as suggested for scalping ), combining MAs with volatility
filters to avoid non-trending conditions , or employing them as a higher-timeframe
filter to confirm the overall trend direction, while faster, more responsive
indicators trigger the actual entries on lower timeframes.

RSI Signals
The Relative Strength Index (RSI) is a momentum oscillator that quantifies the
speed and change of price movements, typically fluctuating between 0 and 100.
Readings above 70 are generally considered overbought, suggesting a potential price
pullback or sell signal, while readings below 30 indicate oversold conditions,
hinting at a possible price rebound or buy signal. Divergences between price action
and RSI can also serve as signals for potential trend reversals. MQL5's
iRSI function allows for easy integration of RSI values into the EA's decision-
making process.

The primary challenge in integrating RSI into a price continuation strategy lies in
its fundamental nature as a mean-reversion indicator. RSI's overbought/oversold
signals typically suggest that price is extended and due for a reversal or
correction. Directly entering a "continuation" trade based on an overbought RSI
(e.g., buying when the market is already overbought) would be logically
inconsistent with the EA's core price continuation hypothesis, as it implies a
counter-trend move is imminent. To effectively leverage RSI within a continuation
framework, research should explore its use as a

filter to prevent entries at extreme exhaustion points. Alternatively, in a strong

prevailing trend, a temporary oversold RSI (for a buy signal) or overbought RSI
(for a sell signal) could indicate the completion of a healthy pullback, after
which the main trend is expected to resume. For scalping, shorter RSI periods
(e.g., 2-3 days) can provide more frequent and responsive signals , but these
require extensive backtesting to validate their effectiveness.

Synergy of Multiple Entry Signals

Combining multiple indicators can significantly enhance signal quality, reduce
false signals, and improve the overall robustness of a trading strategy. This
approach can involve using one indicator to confirm the broader trend and another
for precise entry timing, or employing multiple indicators to build a confluence of
evidence for a trade.

For a small-profit scalping strategy, reducing whipsaws is critically important due

to the cumulative impact of transaction costs. Individual indicators, when used in
isolation, are prone to generating false signals in volatile or choppy markets. For
a strategy targeting only 1.5 pips profit, each false signal translates directly
into transaction costs (spread, commission, slippage), which can quickly erode
profitability. Therefore, the selection of indicators for confluence must be highly
strategic. Simply adding more indicators without careful consideration can lead to
"false confirmations" if they are based on similar underlying principles. The
objective is to select complementary indicators that measure different aspects of
market dynamics, such as trend strength, momentum, volatility, or
support/resistance levels. For this scalping EA, the multi-indicator combination
should aim for high-probability trades. This could involve using a higher-timeframe
moving average or a volatility filter (e.g., Average True Range) to ensure the
market is in a clear trend or exhibits sufficient volatility for continuation.
Pivot breakouts can then provide the directional bias, while a short-period RSI
might confirm short-term momentum or indicate temporary exhaustion before the
continuation of the main trend. Volume confirmation, where available, could further
validate breakouts and trend strength, adding another layer of robustness to the
entry signals.

B. Dynamic Profit Securing Mechanisms

The EA's ability to consistently secure profits is crucial for achieving long-term
growth. This involves a combination of fixed targets and dynamic stop-loss
adjustments.

Fixed Take Profit (1.5 pips)

The EA's design includes a fixed Take Profit (TpPoints) for each trade, calculated
as entry + TpPoints * _Point for buy orders and entry - TpPoints * _Point for sell
orders. While a 1.5-pip profit target is characteristic of scalping strategies,
which aim for "many small profits" , achieving "fast and long-term growth" from
such small per-trade gains presents a significant challenge.
To generate substantial overall growth from minimal per-trade profits, the EA must
execute an exceptionally large number of trades. This high trade frequency,
however, amplifies the impact of transaction costs (spreads, commissions, and
slippage) on the net profitability of the strategy. Even a minuscule fraction of a
pip in additional cost per trade can accumulate rapidly, turning otherwise winning
trades into break-even scenarios or even net losses. For instance, if the average
transaction cost per round trip is 0.5 pips, and the target profit is 1.5 pips,
then 33% of the potential gross profit is immediately absorbed by costs. The
viability of this strategy therefore hinges on rigorously minimizing all
transaction costs and ensuring a consistently high win rate and positive
expectancy.

Aggressive Trailing Stop Loss (1-pip after 1.5 pips profit)

The SureEa_V2.txt code includes a

TrailStop() function, which activates when a position's profit exceeds

TslTriggerPoints (30 points, or 3 pips) and then moves the stop loss to TslPoints
(20 points, or 2 pips) away from the current price. Additionally, the
ModifyToBreakEven() function moves the stop loss to the open price once the profit
reaches twice the original stop loss distance. The user's requirement for a more
aggressive 1-pip trailing stop after 1.5 pips profit is a key differentiator.

Aggressive trailing stops are designed to "reduce risk quickly, lock in profits,
and prevent holding through a pullback". They are particularly effective for
capturing immediate momentum and ensuring that losses are typically small, while
generating many small winners and occasional larger ones. This approach is highly
beneficial for stringent loss prevention and consistent profit securing on
individual trades, as it rapidly removes risk exposure. However, the extreme
tightness of a 1-pip trailing stop can lead to frequent premature exits, preventing
trades from developing into more substantial gains and potentially limiting overall
long-term growth. This also increases the total number of trades, thereby further
magnifying the cumulative impact of transaction costs.

Optimizing the TslPoints and TslTriggerPoints parameters is crucial to balance

profit protection with growth potential. Research should explore adaptive trailing
stop techniques, such as those based on the Average True Range (ATR). An ATR-based
trailing stop dynamically adjusts its distance based on prevailing market
volatility, allowing for wider stops in calm markets and tighter stops in highly
volatile conditions, which can help reduce premature exits while still protecting
profits. This adaptive approach could offer a more optimal balance between securing
consistent small profits and allowing for sustained growth.

Table: Comparison of Profit Securing Mechanisms

Mechanism Trigger Condition Action Taken Primary Benefit Primary Drawback
Suitability for Scalping
Fixed Take Profit Price reaches predefined target (e.g., 1.5 pips) Trade
automatically closes Guarantees minimum profit, removes emotional bias Limits
upside potential, susceptible to market noise around targetHigh, ensures quick
exits, but must outweigh costs
Break-Even Modification Profit reaches a multiple of initial Stop Loss (e.g., 2x
SL) Stop Loss moved to trade's open price Eliminates risk of loss on
individual trade, protects capital Can lead to premature exits if price pulls back
to entry High, crucial for risk-free trades, but frequent hits reduce overall
profit
Aggressive Trailing Stop Loss Price moves in profit by a set amount (e.g., 1.5
pips) Stop Loss trails price by a fixed distance (e.g., 1 pip) Locks in partial
profits, protects against reversals, reduces risk quickly Can lead to premature
exits, limits large trend capture, increases trade frequency High, but requires
careful optimization to avoid excessive whipsaws
Export to Sheets
C. Adaptive Position Sizing for Growth
To achieve both "fast and long-term growth" and "stringent loss prevention," the EA
must employ a sophisticated and adaptive position sizing methodology.

Risk-Percentage Based Lot Sizing

The CalculateLotSize() function in SureEa_V2.txt and

[Link] calculates the trade's lot size based on a predefined

RiskPercent of the account balance. This is a fundamental money management

technique, ensuring that the potential loss from any single trade, if the stop loss
is hit, does not exceed a specified percentage of the total capital.

Dynamic Lot Sizing for Compounding

For an EA aiming for "fast and long-term growth," compounding profits by
dynamically increasing trade size as the account equity grows is essential. The

LevelMultiplier in SureEa_V2.txt offers a basic mechanism for increasing lot size

with multi-level entries. However, while critical for growth, dynamically
increasing lot size also significantly amplifies risk during losing streaks,
potentially leading to faster account depletion.

If the EA increases its lot size proportionally with account equity, a winning
streak will indeed lead to rapid growth. Conversely, a subsequent losing streak
will result in progressively larger losses per trade, accelerating drawdowns and
directly conflicting with the objective of "stringent loss prevention". To
effectively balance aggressive growth with robust risk control, the EA should
implement more sophisticated compounding mechanisms. This includes

conservative compounding, where the LevelMultiplier is carefully optimized to

avoid overly aggressive, high-risk "martingale" behavior. Furthermore,

equity-curve based scaling can be employed, adjusting position sizes not just on
absolute equity but on the performance of the equity curve itself, reducing lot
size during drawdowns and increasing it during periods of strong performance.

Volatility-adjusted sizing, particularly using Average True Range (ATR), ensures

consistent risk exposure across varying market conditions; wider stops in volatile
markets would lead to smaller lot sizes, and vice-versa, thereby maintaining a
consistent risk per trade in monetary terms. Finally, while the

Kelly Criterion offers a theoretically optimal approach to maximizing growth, it

can be too aggressive in practice, often leading to recommendations for a more
conservative "half-Kelly" approach.

Table: Dynamic Position Sizing Methods

Method Description Calculation Basis Key Advantages Key Disadvantages MQL5
Implementation Considerations
Fixed Percentage of Account Risks a fixed percentage of total equity on each
trade. (Account Size * Risk %) / (Entry - SL) Simple, adapts to account
growth/shrinkage, consistent risk exposure. Ignores market volatility and
asset-specific risk.
Use AccountInfoDouble(ACCOUNT_EQUITY) and SymbolInfoDouble for tick/point values.

Volatility-Based (ATR) Adjusts trade size based on market volatility. Account Risk
/ (ATR * Multiple) Standardizes risk across assets, adapts to market
conditions. Requires accurate ATR calculation, parameter Multiple needs
optimization.
Calculate ATR using iATR function. Integrate into CalculateLotSize.

Equity Curve-Based Adjusts position sizes based on the performance of the

trading account's equity curve. Varies (e.g., scale up/down based on MA
crossovers of equity curve) Maximizes gains during uptrends, minimizes risk
during downturns. Can be complex to implement, may lag market reversals.
Requires tracking historical equity, calculating its moving average, and adjusting
lot size.

Kelly Criterion (Fractional) Mathematically optimal for maximizing long-term

growth. W - ((1 - W) / R) (W=Win Rate, R=Win/Loss Ratio) Maximizes expected
growth rate of capital. Very aggressive, requires highly accurate historical win
rate and payoff ratio, can lead to large drawdowns.
Calculate historical win rate and average win/loss. Apply fractional Kelly.

IV. Stringent Loss Prevention and Robust Risk Management

Effective risk management is paramount for the long-term viability and growth of
any algorithmic trading strategy, especially one characterized by high-frequency,
small-profit trades.

A. Comprehensive Drawdown Control

The provided SureEa_V2.txt EA already incorporates robust drawdown control
mechanisms through

MaxDailyDrawdown and MaxEquityDrawdown parameters, enabled by the

UseEquityProtection flag. The

CheckDailyDrawdown() function monitors the current balance against the

m_dailyStartBalance, which is reset daily, while CheckEquityDrawdown() tracks the
overall equity against the m_maxEquity (the highest equity achieved). If either of
these predefined percentage limits is breached, the

m_tradingEnabled flag is set to false, and all pending orders are closed via
CloseAllOrders().

These drawdown limits are not merely technical safeguards; they serve as a critical
imperative for both capital preservation and maintaining trader discipline. Beyond
preventing catastrophic capital loss, explicit automated drawdown limits are
crucial for ensuring long-term adherence to the strategy. In the absence of such
automated controls, even a statistically sound scalping strategy could lead to
emotional decision-making, such as "revenge trading" after losses, overtrading, or
abandoning the strategy prematurely during inevitable losing streaks. A large
drawdown can have a significant psychological impact, making it difficult to stick
to the trading plan. Therefore, these limits directly contribute to the "long-term
growth" objective by enforcing disciplined capital management. The current
implementation in

SureEa_V2.txt is well-structured. Future enhancements could explore dynamic

drawdown limits that adapt to prevailing market volatility or the strategy's recent
performance , or incorporating "End of Range Security Zone" checks for additional
protection during periods of extreme market movement.

B. Emergency Stop Functionalities (Kill Switches)

The CloseAllOrders() function in SureEa_V2.txt , triggered by drawdown limits or
time filters, acts as a basic emergency stop. However, a truly robust algorithmic
trading system requires additional, independent "kill switches" to safeguard
against unforeseen circumstances, such as black swan events, critical system
failures, or extreme market disruptions that might bypass standard risk controls.
Algorithmic trading, despite its automation, is not immune to risks like "technical
failure, market volatility, and regulation". Scenarios like "Flash Crashes" and
general "System Failures" are explicit concerns. Relying solely on internal EA
logic for emergency stops can be insufficient if the EA itself malfunctions or if
external market conditions are so extreme that they render normal stop-loss
triggers ineffective. The principle of "Emergency Controls: Employ kill switches
and circuit breakers for major disruptions" is a fundamental best practice.
Therefore, the research strategy must include the implementation of:

Manual Kill Switch: A simple input parameter in the EA that, when toggled,
immediately closes all open positions and pending orders, and permanently disables
the EA from placing new trades. This provides human oversight and intervention
capability.

Time-Based Kill Switch: Automatically closing all trades and disabling further
trading before high-impact news events or significant weekend market gaps. The
existing time filter in

SureEa_V2.txt that closes orders could be extended and hardened for this specific
purpose.

External Monitoring and Kill Switch: While not directly coded within the primary
EA, the overall trading system design should consider external monitoring tools or
a separate, independent utility EA. This external component could act as a "circuit
breaker," designed to monitor the primary EA's behavior and account metrics, and
intervene by closing positions or disabling trading if erratic behavior or extreme
market conditions are detected. This layered approach provides an additional safety
net against unforeseen system or market anomalies.

C. Accounting for Transaction Costs

For a scalping strategy targeting only 1.5 pips profit, meticulously accounting for
transaction costs is not merely good practice; it is a critical determinant of
profitability. These costs can easily erode the small profit target, turning
winning trades into break-evens or even net losses, posing a significant challenge
for high-frequency strategies.

The primary types of transaction costs include:

Commissions: These are fees charged by the broker, typically per lot traded or per
million notional value.

Swaps: These are overnight interest charges or credits for holding positions open
past a certain time (usually server midnight). For a pure scalping strategy where
trades are typically closed intraday, the impact of swaps is generally minimal.

Slippage: This refers to the difference between a trade's expected price and its
actual execution price. Slippage is common during periods of high volatility or
when placing large orders with insufficient liquidity, and it can be either
positive (better price) or negative (worse price).

The CalculateLotSize() function in SureEa_V2.txt and

[Link] calculates lot size based on

RiskPercent and slPoints, but it does not explicitly factor in commissions or an

estimate of slippage in its monetary risk calculation. For a strategy aiming for
1.5 pips profit, each trade incurs a spread (the difference between the bid and ask
price ), and often commissions. Even a small cumulative cost per trade (e.g., 0.5
pips round trip) means a substantial portion (e.g., 33%) of the target profit is
consumed by costs, directly impacting "consistent profit securing" and "fast
growth."

To accurately assess and achieve profitability, the research strategy must:

Refine Lot Size Calculation: Modify the CalculateLotSize() function to explicitly

include estimated round-trip commissions and an average historical slippage factor
in the risk calculation. This ensures that the

net risk is accurately controlled and that profit targets are realistic after
accounting for all trading costs.

Broker Selection: Prioritize brokers that offer "minimal spreads" and "low
commissions". The choice of broker significantly impacts the net profitability of a
scalping strategy due to the high trade frequency.

Order Types: Where appropriate, utilizing limit orders instead of market orders can
help mitigate the risk of negative slippage by ensuring execution only at the
desired price or better.

Backtesting Accuracy: Ensure that backtests properly account for variable spreads,
commissions, and realistic slippage models for a truly accurate performance
evaluation.

Table: Impact of Transaction Costs on Profitability

Cost Type Description Calculation Method (Example) Estimated Impact on 1.5-pip
Target
Spread Difference between Bid and Ask price. Variable, inherent in price
quote. Directly reduces gross profit. E.g., 0.5 pip spread consumes 33% of 1.5
pip target.
Commission Fee charged by broker per trade.
Per lot traded, or per million notional value (e.g., $3.5/lot round-turn).

Adds fixed cost per trade, reducing net profit.

Slippage Difference between expected and actual execution price.
Variable, depends on volatility, liquidity, order size.

Can turn profitable trades into losses, or reduce expected profit. Highly impactful
in volatile markets.
Swap (Rollover) Overnight interest paid/earned for holding positions.
Per lot, per day (triple on Wednesdays for FX).

Minimal for intraday scalping, but relevant if trades extend overnight.

D. Minimizing Latency and Optimizing Execution
Achieving "fast and long-term growth" with a small-profit scalping strategy places
immense demands on execution speed and latency. This environment often resembles a
competitive "race to zero" against other market participants, where milliseconds
can determine profitability.

For high-frequency strategies like scalping, "lightning-fast trade execution" is

essential. High-Frequency Trading (HFT) firms, which operate in a similar domain,
execute thousands of trades in milliseconds, relying on advanced algorithms,
powerful computers, and ultra-low-latency connections. While a retail EA cannot
match the sheer speed of institutional HFT , every millisecond of latency and every
fraction of a pip of slippage directly impacts the strategy's profitability.

To address these technological and infrastructural demands, the research strategy

must incorporate:
Importance of Forex VPS: A Virtual Private Server (VPS) is highly recommended for
running EAs. It ensures 24/7 uninterrupted operation, stable performance, and
significantly reduces latency by hosting the trading platform close to the broker's
servers. The proximity of the VPS server to the broker's data center is a critical
factor in minimizing network latency and speeding up order processing.

Broker Selection Criteria: Thorough due diligence in broker selection is paramount

for high-frequency strategies. Key criteria include:

Minimal Spreads and Low Commissions: Directly impacts profitability due to high
trade frequency.

Execution Model: Prioritize No Dealing Desk (NDD) brokers that use Straight Through
Processing (STP) or Electronic Communication Networks (ECN) to source liquidity
directly from providers, which generally offers faster execution compared to
Dealing Desk (DD) brokers.

Multiple Liquidity Providers and Level II Market Depth: These features indicate
better liquidity, which helps reduce slippage, especially for larger orders.

Proven Fast Execution Speed: Look for brokers with documented fast execution
speeds.

MQL5 Code Optimization: Optimizing the MQL5 code itself for faster execution is
crucial to minimize internal processing delays between signal generation and order
placement. This involves identifying performance bottlenecks, using efficient data
structures, minimizing memory usage, limiting global variables, avoiding string
concatenation, utilizing precompiled libraries, optimizing loops, vectorizing
operations, and reducing unnecessary function calls.

High-Quality Tick Data: The absolute necessity of using high-quality tick data for
backtesting cannot be overstated. This granular data, capturing every individual
quote or trade, is essential for accurately simulating real-world execution
conditions, including variable spreads and slippage, which are critical for the
viability of a scalping strategy. Backtesting on lower resolution data (e.g., 1-
minute bars) can produce "WAY OFF" results compared to live trading, leading to
misleading profitability assessments.

V. Research and Validation Methodology for MT5 EAs

The development of a robust and profitable MT5 EA requires a systematic and
rigorous research and validation methodology to ensure its long-term viability.

A. Data Collection and Preparation

The reliability of any backtest, and consequently the EA's projected profitability,
is fundamentally dependent on the quality and granularity of the historical data
used. For a high-frequency, small-profit scalping strategy, this dependence is
amplified, as low-quality data can lead to entirely misleading results.

The critical role of high-quality tick data cannot be overemphasized. Tick data
captures the most granular level of market activity, including every individual
quote or trade, along with their precise timestamps, prices, and volumes. For
scalping, which aims to profit from minute price fluctuations, this level of detail
is paramount. It allows for highly accurate simulation of trade timing, realistic
modeling of slippage, and precise calculation of fill prices, all of which are
impossible to achieve with aggregated bar data (e.g., 1-minute bars). Using lower
resolution data for optimization can lead to results that are "WAY OFF" when
compared to backtests on tick data, especially for instruments with wider spreads,
potentially showing "huge profits that were not really there". Therefore, the
research strategy must prioritize obtaining and utilizing the highest quality tick
data available, often from third-party providers, to achieve 99% modeling quality
in MT5 backtests.

Furthermore, data synchronization and time zone considerations are vital. The
historical data used for backtesting must be precisely synchronized to the broker's
server time zone to avoid discrepancies in trade execution times and to accurately
reflect market conditions. Any misalignment can introduce subtle errors that
compromise the integrity of the backtest results. The necessity of high-quality
tick data forms the bedrock of realistic backtesting and is a non-negotiable
prerequisite for developing and validating a viable scalping EA.

B. Rigorous Backtesting and Optimization

A single backtest, no matter how impressive its results, is insufficient to
guarantee long-term profitability or to prove the robustness of a trading strategy.
The pervasive risk of overfitting (also known as curve fitting or data snooping
bias) is a primary reason why strategies that appear highly profitable in backtests
often fail in live trading. Overfitting occurs when a strategy is excessively
optimized to the noise present in historical data, making it ineffective when
exposed to new, unseen market conditions. It is considered "the worst type of bias"
because its consequences are immediately apparent in real-world execution. Warning
signs of overfitting can include a "very smooth equity curve," a "straight line in
a log chart," or an exceptionally high Sharpe ratio (e.g., greater than 1.5) in
backtests.

To mitigate overfitting and ensure the EA's long-term viability, a multi-layered

validation approach is essential:

Walk-Forward Optimization (WFO): WFO is a robust methodology designed to reduce

overfitting by simulating a realistic trading scenario. It involves iteratively
optimizing strategy parameters on a historical "in-sample" (training) data segment
and then testing those optimized parameters on a subsequent, previously unseen
"out-of-sample" (testing) segment. This process is repeated by moving the
optimization and test segments forward in time, providing a more realistic
assessment of how the strategy would adapt and perform over different market
regimes. WFO also helps identify the optimal frequency for re-optimizing strategy
parameters in a live environment.

Out-of-Sample (OOS) Testing: This is a fundamental component of robust validation,

involving the explicit withholding of a portion of historical data (e.g., the most
recent 10-30%) that is not used during any stage of strategy development or
optimization. The strategy's performance is then evaluated on this genuinely unseen
data. A significant degradation in performance on the OOS data, compared to the in-
sample period, is a strong indicator of overfitting. The OOS period should be
selected to be as challenging as possible to truly stress-test the strategy.

Robustness Checks: Beyond WFO and OOS testing, various Monte Carlo simulations and
other robustness tests should be employed to stress-test the strategy against minor
perturbations and variations in market conditions. These can include:

Randomizing Trade Order: Shuffling the sequence of historical trades to see if

profitability is dependent on a specific order.

Randomizing Starting Bar: Testing the strategy's behavior when initiated at

different historical points.

Randomizing Strategy Parameters: Introducing small, random variations to the

optimized input parameters (e.g., indicator periods, constants) to assess the
strategy's sensitivity. A robust strategy should not be overly sensitive to minor
parameter changes.

Randomizing History Data: Introducing small, random changes to historical price

data (Open, High, Low, Close) to determine if the strategy is overly dependent on
specific historical patterns or noise.

The goal of these checks is to determine how well the strategy "copes with changing
conditions" and to identify if its profitability relies on specific historical
sequences or overly precise parameter values. For a scalping EA, which often
operates on short-term market microstructure, the risk of overfitting to noise is
exceptionally high. Therefore, the validation process must be exceptionally
rigorous, aiming to "break your system in the testing process" before the live
market does.

VI. Conclusions and Recommendations

The development of an MT5 EA for a price continuation strategy targeting fast and
long-term growth with consistent profit securing and stringent loss prevention,
particularly with aggressive 1.5-pip profit targets and 1-pip trailing stops, is
fundamentally a pursuit of a high-frequency scalping system. This classification
carries profound implications for every stage of the research, development, and
validation process.

Key Conclusions:

Scalping's Demands: The strategy's core mechanics align with scalping, which
necessitates extremely high precision, ultra-low latency, and meticulous accounting
for transaction costs. The viability of achieving "fast and long-term growth" from
minimal per-trade profits is highly sensitive to these operational efficiencies.

Bias as a Critical Threat: The identified look-ahead bias in the existing

FindSignificantHigh() and FindSignificantLow() functions, along with the typo in
findLow(), represents a fundamental flaw. Unaddressed, these biases will lead to
artificially inflated backtest results and inevitable failure in live trading,
directly undermining the user's objectives.

Indicator Suitability: While last high/low breakouts are suitable, the inherent lag
of traditional Moving Average crossovers and the mean-reversion nature of RSI pose
challenges for a pure price continuation scalping strategy. Their integration
requires careful filtering or re-contextualization to avoid false signals and
ensure alignment with the core hypothesis.

Trailing Stop Trade-off: The aggressive 1-pip trailing stop, while excellent for
immediate profit protection and loss prevention, can severely limit overall growth
by prematurely exiting trades and preventing larger winning runs. This necessitates
exploring adaptive solutions.

Compounding's Double-Edged Sword: Dynamic position sizing, crucial for compounding

and achieving rapid growth, simultaneously amplifies risk during losing streaks. A
responsible approach is essential to prevent accelerated capital depletion.

Transaction Costs are Paramount: For a strategy targeting such small profits,
commissions, spreads, and slippage are not minor details but critical determinants
of net profitability. Ignoring them will lead to a significant divergence between
backtested and live performance.

Infrastructure is Key: The "race to zero" in scalping demands a highly optimized

trading environment, including a low-latency VPS and a broker with superior
execution and minimal costs.
Actionable Recommendations:

Immediate Code Rectification:

Fix Look-Ahead Bias: Prioritize the immediate correction of the look-ahead bias in
FindSignificantHigh() and FindSignificantLow() functions in SureEa_V2.txt by
removing any future-looking data access (e.g., iHigh(..., i+j)).

Correct Typo: Rectify the typo in findLow() in [Link] by changing iLowest(...)

== 1 to iLowest(...) == i.

Re-backtest: Conduct a complete and thorough re-backtest of the EA with the

corrected code to establish a true and unbiased baseline performance.

Refine Entry Signal Logic:

Confluence and Filters: Implement a multi-indicator confluence approach that

strategically combines the chosen entry signals. For instance, use Moving Averages
as a higher-timeframe trend filter, while breakouts or short-period RSI signals
provide precise entries. Incorporate volatility filters to avoid choppy market
conditions.

RSI Re-evaluation: If RSI is retained, re-evaluate its role to ensure it

complements a price continuation strategy, perhaps by identifying healthy pullbacks
within a trend rather than outright reversals.

Optimize Profit Securing Mechanisms:

Adaptive Trailing Stop: Implement an adaptive trailing stop loss mechanism, such as
one based on Average True Range (ATR). This will allow the stop distance to
dynamically adjust to market volatility, potentially reducing premature exits while
still protecting profits effectively.

Fixed TP Optimization: Thoroughly optimize the 1.5-pip fixed take profit target in
conjunction with the refined trailing stop to find the optimal balance between
profit capture and trade frequency.

Implement Adaptive Position Sizing:

Conservative Compounding: While utilizing the LevelMultiplier for multi-level

entries, ensure its value is conservatively optimized to avoid excessive risk
amplification.

Equity-Curve or Volatility-Based Sizing: Integrate advanced position sizing methods

like equity-curve based scaling (adjusting lot size based on overall account
performance) or ATR-based sizing (adjusting based on market volatility) to achieve
responsible compounding and consistent risk exposure.

Enhance Risk Management Framework:

Refine Lot Size Calculation: Modify the CalculateLotSize() function to explicitly

account for estimated round-trip commissions and average historical slippage. This
ensures that the calculated lot size accurately reflects the net risk per trade.

Layered Emergency Stops: Implement additional emergency stop functionalities beyond

automated drawdown limits, including a manual kill switch and time-based closures
before high-impact news events or weekend gaps. Consider external monitoring
solutions for ultimate system resilience.
Prioritize Infrastructure and Data Quality:

High-Quality Tick Data: Obtain and utilize the highest quality historical tick data
for all backtesting and optimization processes. This is non-negotiable for
simulating realistic execution conditions for a scalping strategy.

Dedicated VPS: Deploy the EA on a high-performance Forex VPS strategically located

near the chosen broker's servers to minimize latency and ensure 24/7 uninterrupted
operation.

Broker Selection: Select a broker with demonstrably low spreads, minimal

commissions, ECN/STP execution, and proven fast execution speeds to maximize net
profitability.

MQL5 Code Optimization: Continuously optimize the MQL5 code for faster execution by
identifying and addressing performance bottlenecks.

By meticulously addressing these recommendations, the development of the MT5 EA

will shift from a potentially flawed concept to a rigorously validated and robust
trading system capable of achieving its objectives of fast and long-term growth,
consistent profit securing, and stringent loss prevention in real-world market
conditions.

Sources used in the report

[Link]
Scalping Trading Strategy Explained: Best Indicators & Tips - Samco
Opens in a new window

[Link]
How Algorithmic Trading is Reshaping Markets – Insights from Octa Broker
Opens in a new window

[Link]
Examining Different Trailing Stop Techniques - Investopedia
Opens in a new window

[Link]
How to Evaluate an Algo Trading Strategy? - [Link]
Opens in a new window

[Link]
The Aggressive One-Bar Trailing Stop Loss for Locking in Profit ...
Opens in a new window

[Link]
What is scalping in trading and how to apply it to your strategy ...
Opens in a new window

[Link]
RSI Overbought and Oversold Signals Explained - LuxAlgo
Opens in a new window

[Link]
What is the Moving Average Crossover and How to Use It - Blueberry Markets
Opens in a new window
[Link]
MQL5 Tutorial - Simple Moving Average Crossover Robot - YouTube
Opens in a new window

[Link]
Look-Ahead Bias In Backtests And How To Detect It | by Michael Harris | Medium
Opens in a new window

[Link]
RSI Strategy for MT5 - MyCoder
Opens in a new window

[Link]
"Caution! This strategy may use look-ahead bias, which can lead to unrealistically
profitable results." : r/TradingView - Reddit
Opens in a new window

[Link]
Master the 1 Minute Scalping Strategy Using EMA Crossovers! - Opofinance Blog
Opens in a new window

[Link]
RSI Trading Strategy (91% Win Rate): Backtest, Indicator, And Settings -
[Link]
Opens in a new window

[Link]
The 5-8-13 EMA Scalping Strategy Explained In Under 5 Minutes! - YouTube
Opens in a new window

[Link]
Scalping EA | Custom Trading Strategies Automation - Nordman Algorithms
Opens in a new window

[Link]
Top 5 Best Scalping EAs for MT4 in 2025 - Telegram Signal Copier
Opens in a new window

[Link]
EarnForex/ATR-Trailing-Stop - GitHub
Opens in a new window

[Link]
MQL5 TUTORIAL - BUY TRAILING STOP explained (in 4 min) - YouTube
Opens in a new window

[Link]
AI Trading Tutorial - MQL5 Adaptive Moving Average With Trailing Stops - YouTube
Opens in a new window

[Link]

[Link]
Are there any Real EAs that actually produce profits on Live
Opens in a new window

[Link]
how to close a position - Stop Loss - Expert Advisors and Automated Trading - MQL5
programming forum
Opens in a new window

[Link]
Forex Signals with TP/SL - Apps on Google Play-www
Opens in a new window

[Link]
Profitable strategies for EAs - StrategyQuant Forum Topic
Opens in a new window

[Link]
How To Use The MT5 Strategy Tester For Backtesting (EA Testing Explained) - YouTube
Opens in a new window

[Link]
5 Position Sizing Methods for High-Volatility Trades - LuxAlgo
Opens in a new window

[Link]
Trading Indicator Library - LuxAlgo
Opens in a new window

[Link]
MSA: Equity Curve Crossover Trading - Adaptrade
Opens in a new window

[Link]
Order Risk Management EA MT5 | Advanced Technical Analysis
Opens in a new window

[Link]
Algorithmic Trading in MQL5: Risk Management - Greaterwaves Academy
Opens in a new window

[Link]
Coding a Simple but Profitable Bracket Strategy for MT5 (mql5 Tutorial) - YouTube
Opens in a new window

[Link]
Stop Loss exact implementation - MQL5
Opens in a new window

[Link]
Dynamic ATR Trailing Stop Trading Strategy: Market Volatility ...
Opens in a new window

[Link]
Converting Lot Sizes to Monetary Investment Amounts in MQL5 | MetaTrader 5 -
YouTube
Opens in a new window

[Link]
How to Calculate Lot Size for Trade in mql5 ? - YouTube
Opens in a new window

[Link]
cTrader Commission Calculator | Trading Tools - FxPro
Opens in a new window
[Link]
Trade Cost Guide | Commission Calculator | Forex - Noor Capital UK Limited
Opens in a new window

[Link]
Swap Rollover Fee Calculator | FX Swap Rates | Trading Tools | FxPro
Opens in a new window

[Link]
Trading Costs & Charges | Forex Commissions & Swap Rates - Baxia Markets
Opens in a new window

[Link]
DAX Index Starts Week Strong as Trade Progress and ECB Optimism Lift Euro Stocks
Opens in a new window

[Link]
How should I estimate slippage? : r/algotrading - Reddit
Opens in a new window

[Link]
Reinvest gains for compounding? : r/Bogleheads - Reddit
Opens in a new window

[Link]
Equity Curve Position Sizing: Meaning, Definition And Example ...
Opens in a new window

[Link]
Fxview Trading Calculators | Calculate Your Trading Costs
Opens in a new window

SureEa_V2.txt

[Link]
DrawDown Limiter MT4 | Buy Trading Utility for MetaTrader 4 - MQL5
Opens in a new window

[Link]
MT5 Drawdown Safety Expert Advisor Programming Tutorial - YouTube
Opens in a new window

[Link]
Navigating the Ups and Downs: How to Stay Positive During Trading Drawdowns - ATFX
Opens in a new window

[Link]
How to optimize maximum drawdowns when backtesting a Forex trading strategy
Opens in a new window

[Link]
Back-testing in Metatrader 5 with 99% Modelling Quality - Tickstory
Opens in a new window

[Link]
Reliable backtesting in MetaTrader - StrategyQuant
Opens in a new window
[Link]
cTrader Tick Data vs m1 bars - ClickAlgo Forum
Opens in a new window

[Link]
How to optimize your MQL4/MQL5 code for faster execution. | by Faizur Rahman -
Medium
Opens in a new window

[Link]
MT5 Every Tick vs. Every Tick based on real ticks : r/Forex - Reddit
Opens in a new window

[Link]
I Programmed a Slippage Calculator for MT5! Free mql5 Code - YouTube
Opens in a new window

[Link]
Getting good results using MT5 strategy tester to optimize my EA. One month forward
out-of-sample test also done to confirm optimized settings.. Why does it tank on
the very next month? : r/algotrading - Reddit
Opens in a new window

[Link]
Robustness Tests and analysis - StrategyQuant
Opens in a new window

[Link]
Why is Strategy Tester so unreliable? - MQL5
Opens in a new window

[Link]
Out of Sample Testing for Robust Algorithmic Trading Strategies - Build Alpha
Opens in a new window

[Link]
What is a Walk-Forward Optimization and How to Run It? - Algo Trading 101
Opens in a new window

[Link]
Walk-Forward Matrix - StrategyQuant
Opens in a new window

[Link]
Scalping Strategies: Mastering Quick Profits in the Market - Investopedia
Opens in a new window

[Link]
Best MetaTrader5 VPS Hosting - 100% UpTime - ForexVPS
Opens in a new window

[Link]
Execution Speed Forex Broker Testing Results - Updated 2025 - CompareForexBrokers
Opens in a new window

[Link]
Why use a VPS with MT5? - BlackBull Markets
Opens in a new window
[Link]
How to Start High-Frequency Trading (HFT) Quickly and with ...
Opens in a new window

Sources read but not used in the report

Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window
Opens in a new window

Thoughts