From XAUUSD to BTCUSD: A Complete Migration Guide for TrendCandleEA

How to transform the XAU configuration of TrendCandleEA into the BTC configuration — parameter by parameter, with the reasoning behind every change.

1. Introduction

TrendCandleEA ships with several ready-to-use configurations, one per market. The XAU configuration is calibrated for gold (XAUUSD) on the M30 timeframe. The BTC configuration is calibrated for Bitcoin (BTCUSD) on the same M30 timeframe.

Both share the exact same engine — the same signal logic, the same filter framework, the same position management. Only the input values differ.

This article is a step-by-step migration guide. It explains:

• Why the XAU configuration, applied to Bitcoin without modification, produces poor or erratic results.
• Which inputs must change, and by how much.
• Which inputs must be left untouched, and why.
• How to verify your setup before running it live.

By the end of this guide, you will be able to take the XAU configuration, apply every documented change, and end up with a fully working BTC configuration — with no guesswork.

2. Why the XAU Configuration Cannot Be Used As-Is on Bitcoin

At first glance, XAUUSD and BTCUSD look similar on a chart: both are quoted in US dollars, both trend strongly for weeks, and both respond to macro news. But under the hood, they are fundamentally different instruments. A configuration tuned for one will behave very differently on the other.

Concretely, if you take the XAU configuration and run it on BTCUSD without any change, three problems appear immediately:

1. The spread and slippage filters block almost every trade. The XAU configuration caps the spread at 60 points. On BTCUSD, normal spread is 10 to 30 times higher — so the EA simply never trades.
2. The Stop Loss is too tight. The XAU configuration adds a 1 000-point buffer to the SL. On Bitcoin, that buffer is roughly 10 USD — a meaningless distance given BTC's typical M30 range. Trades get stopped out by pure noise.
3. The signal filters were tuned for gold's rhythm. Gold trends smoothly with few pullbacks. Bitcoin trends violently, with frequent liquidation cascades and fakeouts. Filters that work on gold leave Bitcoin either over-exposed or fully blocked.

The BTC configuration solves all three problems by rebuilding the filter stack from scratch for Bitcoin's specific behaviour.

3. The Three Fundamental Differences Between XAUUSD and BTCUSD

3.1 Price Level

At the time of the backtest, XAUUSD traded around 4 500–5 500 USD per ounce. BTCUSD traded between 62 000 and 93 000 USD per coin. The absolute price level is roughly 15× higher on Bitcoin.

3.2 Volatility

A typical daily range on XAUUSD is about 1 % of price. A typical daily range on BTCUSD is 3 to 5 %. In absolute terms, Bitcoin moves 30 to 60 times more than gold on a normal day. This is why every point-based parameter must be scaled accordingly.

3.3 Market Structure

Gold trades 23 hours a day, 5 days a week, with a well-defined session pattern (Asian range, London breakout, New York continuation). Bitcoin trades 24/7, with no session boundaries, and is subject to exchange-specific events (weekend liquidation cascades, funding rate flips, whale movements). The result: gold trends are smooth; Bitcoin trends are punctuated by violent reversals.

4. The Point Paradox — The Single Most Important Concept

Before changing any parameter, you must understand one thing: on BTCUSD, one point is not worth the same as one point on XAUUSD.

Both symbols typically use 2 decimal places, so _Point = 0,01 in both cases. But the value of one point in USD depends on the contract size, which is defined by the broker, not by the price.

For a common broker setup:

• XAUUSD: 1 lot = 100 ounces → 0,01 lot = 1 ounce → 1 point (0,01 USD) = 0,01 USD of P&L per 0,01 lot.
• BTCUSD: 1 lot = 1 BTC → 0,01 lot = 0,01 BTC → 1 point (0,01 USD) = 0,0001 USD of P&L per 0,01 lot.

In other words, one point on BTC is worth 100 times less than one point on gold, at equal volume. So to risk the same dollar amount, the Stop Loss on BTC must be 100 times wider in points than the equivalent SL on gold.

5. Migration, Group by Group

The following sections walk through every group of inputs in the same order they appear in the EA's input window. For each parameter, the change is given alongside its justification.

5.1 General Group

5.2 Matrend Group

5.3 Higher Timeframe MA Group

5.4 ADX Group

The other ADX parameters ( InpAdxTimeframe , InpAdxPeriod , InpAdxMin ) are left at their defaults. Since the filter is disabled, they have no effect.

5.5 Candle Quality Group

5.6 Session Filter Group

Unchanged. The session filter remains disabled ( InpUseSessionFilter = false ). Bitcoin trades 24/7; a session filter would only reduce opportunities without improving quality.

5.7 RSI Group

The other RSI parameters ( InpRsiTimeframe , InpRsiPeriod , etc.) are left at defaults. Since the filter is disabled, they have no effect.

5.8 MACD Group

Other MACD parameters are left at defaults, as the filter is disabled.

5.9 Squeeze Momentum Group

5.10 Bollinger Bands — 5 Timeframes Group

5.11 Bollinger Modality A — Median Line Group

5.12 Bollinger Modality B — Outer Band Touch Group

Other Modality B parameters are left at defaults, as the filter is disabled.

5.13 Smart Money Concept (SMC) Group

5.14 ZigZag Filter #1 Group

5.15 ZigZag Filter #2 Group

5.16 Candle Filter Group

5.17 Volume Filter Group

5.18 Volumes Indicator Filter Group

Unchanged. The iVolumes-based filter remains disabled ( InpUseVolumesIndFilter = false ). It is redundant with the Volume Filter group already enabled in section 5.17.

5.19 Virgin Price Filter Group

Other Virgin Price parameters are left at defaults, as the filter is disabled.

5.20 Money Management Group

Unchanged in the backtest. The BTC backtest used InpLotMode = LOT_FIXED with InpFixedLot = 0,01 , exactly as the XAU backtest. Both use the same lot size, which keeps the comparison rigorous.

Recommended for live trading: switch to LOT_RISK_PCT with InpRiskPercent = 0,5 and InpMaxLot = 1,0 . Bitcoin's volatility means a fixed lot can become disproportionately risky as price rises.

5.21 Exit Modes Group

Unchanged. The BTC configuration uses InpMode_TP_EgalSL = true (Mode 2 — Fixed TP = SL distance), exactly as the XAU configuration.

5.22 Mode Settings Group

Unchanged. The relevant parameters for Mode 2 are already covered by the SL buffer set in section 5.16. Other mode parameters (MODE 1, MODE 3, MODE 5) remain at their defaults and have no effect since only Mode 2 is active.

6. Summary Table — Every Changed Input

The table below consolidates all changes documented above. It can be used as a checklist when configuring the EA manually.

Thirty-one inputs changed between the XAU and BTC configurations. All other inputs remain identical.

7. What Stayed the Same

It is equally important to know what did not change — and to avoid the temptation to modify these parameters "just to be safe". They were validated as-is during the BTC backtest.

• All indicator periods (EMA 50, EMA 200, BB 200, ATR — where ATR was explicitly changed to 2, all others): these are measured in bars, not in points. Bar counts are market-agnostic.
• All Bollinger deviations (2,0 for Modality A, 0,5 for Modality B): these are standard deviation multipliers, unit-less.
• All threshold values (RSI 65/35, Stochastic 80/20, IBS 70/30): these are oscillator levels, independent of price.
• All ratios ( InpMinBodyRatio = 0,50 , InpMinBodyAtrMult = 0,60 , InpCloseNearExtremeRatio = 0,33 ): relative measurements, valid on any market.
• Volume multiplier (1,20 × 20-candle average): relative, not absolute.
• Risk / money management parameters (Mode 2, fixed lot 0,01 for the backtest): identical between the two backtests to keep the comparison rigorous.

8. Verification Checklist Before Running

Before running the BTC configuration on live or demo, verify the following points. Each one addresses a common source of error.

1. Verify your broker's BTCUSD specifications. In MetaTrader 5, right-click BTCUSD in the Market Watch → Specification. Note the Digits (should be 2), Point (should be 0,01), Contract size , and Spread .
2. Verify that all 31 changed inputs are correctly set. Cross-check against the summary table in section 6.
3. Verify that InpMagic = 1004 . If you run XAU and BTC configurations on the same account, the two magic numbers must differ.
4. Verify that InpTradeComment = BtcTrendCandle . Open a demo position and check the position comment in MT5 — it should read BtcTrendCandle , not XauTrendCandle .
5. Verify that InpSlBufferPoints = 10 000 . A common mistake is to leave it at 1 000 (XAU value), which would produce an SL that is 100 times too tight.
6. Verify that InpMaxSpreadPoints = 6 000 . With 60, the EA would never trade on BTC.
7. Verify that InpUseVirginCloseFilter = false . With it enabled, almost no BTC trade would pass.
8. Verify that InpUseSqzFilter = true with InpSqzMode = RELEASE_RECENT . This is the volatility gate specific to BTC.
9. Verify that InpUseVolumeFilter = true with InpVolumeTimeframe = M15 . Volume confirmation is specific to the BTC config.
10. Run 1 week on a demo account before going live, to observe the trade frequency and verify that the configuration matches expectations.

9. Common Mistakes to Avoid

10. Results Comparison — XAU vs BTC

The table below compares the two configurations over the exact same 9-month period, on the same broker, with the same EA build.

Both configurations deliver positive expectancy with very controlled drawdown. The BTC configuration trades less often, has a higher win rate, a higher Profit Factor and a much lower drawdown — but a lower absolute return over the same period, because it trades roughly half as often. The BTC config is also the only one of the two that traded in both directions during the test window.

11. Conclusion

Migrating from the XAU configuration to the BTC configuration is not a matter of scaling a few points-based parameters. It requires a full recalibration of the filter stack, driven by Bitcoin's specific market behaviour: higher volatility, longer trends, more frequent fakeouts, and a fundamentally different microstructure.

Thirty-one inputs change between the two configurations. Thirty-one others remain untouched. The summary table in section 6 is designed to be used as a direct reference during configuration.

Traders who already run the XAU configuration successfully can add the BTC configuration alongside it, provided they respect the two golden rules: a distinct InpMagic (1004 instead of 1003) and a distinct InpTradeComment ( BtcTrendCandle instead of XauTrendCandle ).

Always validate on a demo account before going live, and always use risk-based position sizing.

Thank you for reading. Feedback, bug reports and suggestions are welcome in the comments section.

Useful Links

• Download TrendCandleEA on the MQL5 Market
• Download MetaTrader 5 & the Strategy Tester