仕事が完了した

実行時間30 日
開発者からのフィードバック
Wonderful client. Patient and great communication. Looking forward to more projects together!!
依頼者からのフィードバック
Paul (MQL5) is fantastic! Delivered perfectly, offered great suggestions & exceeded expectations with clear communication & positivity

指定

Objective: To Create an EA based on an EMA cross Strategy that utilizes martingale account management strategy with multiple profiles to better manage risk                     and  scale safely

Strategy Concept: This strategy was created around Volatility Index 75  on the 5 minute chart. It was Observed that this Index tends to  frequently form very          strong trends with short periods of consolidation. On applying a 10 period EMA offset at 0 And a 10 Period EMA offset at 500 , it was observed          that there tends to be on average at least a 1,000,0000 point movement in price in  a single direction after 1 or a few crosses  of EMA lines.          After applying a martingale strategy that increases lot size on every 'x' points in cumulative losses per martingale run, the risk of ruin          returned positive figures. The system uses a mix of dynamic and fixed stop loses, take profits and trailing stops to mitigate loses and          maximize profit. These levels are based on the EMAs as well.

Targeted pairs/index/Commodities: Volatility Index 75 , others(build to be able to be tested on currency pairs though doesn't have to be effective with)

Parameters: 

EMA1_period ;   EMA2_period ; EMA1_offshift  ; EMA2_offshift ;  EMA1_Method ;  EMA2_Method ;  EMA1_Apply2 ;  EMA2_Apply2 ; fixedTakeProfit ;    fixedStopLoss ; floatingTakeProfit ;   floatingStopLoss ;  floatingStopLoss_Type; 

(martingale)

no_of_Steps ; initial_step_size ; continue_after_final_step ; continue_type ; multiply_on_loss_amount ; multiply_on_loss_rate_factor;

Specification:

     1.After User enters parameter and initializes the bot, an alert should be issued informing user of the dollar amount that would be at risk per  martingale cycle. this can be  calculated as:

       amount at risk per run =  (Initial Step Size *multiply_on_loss_amount )[1+ ( Σ n * (multiply_on_loss_rate_factor))]   where ,  1 < n   < = (no_of_Steps

                   Formula in text was assuming  1 unit  = 100     points

     2. If EMA1 is Lower than EMA2 then Open a sell position 

else

If EMA1 is higher than EMA2 then Open a buy position

    3. If EA opened position but EMA lines cross line in other direction, close position and open other opposing position type( close buy and open sell).

     4.  On loosing a specified number of points ; ( >=  multiply_on_loss_amount ), The following position should open with

lot size  = initial step size * multiply_on_loss_rate_factor * number of current step    

     5. If the Accumulated  loss for current run is equal to or exceeds the previously calculated amount at risk per run then the EA must alert the user and  either   stop the EA, continue the martingale run  or restart the martingale run. (The purpose of the  continue_after_final_step ; continue_type ;  parameters)

     6. On opening a position the stop levels would be according to the  fixedTakeProfit ;   fixedStopLoss parameters. As price moves away from he entry   point if  the user selects a value equal to or above zero (=> 0) for the  floatingStopLoss  a trailing stop would be applied using either of 2 methods.  

If   floatingStopLoss_Type   = continuous ; then a regular trailing stop with the specified number of point will be applied to price

                        If   floatingStopLoss_Type   =  jump ; then for each specified number of units/points change in price (non-absolute) the stop loss jumps to             that many points bellow or above current price (jumping again only after price went up or down by the           specified amount of units once

     7. The floating TP is equal to the EMA2 Line if Line value is greater than  fixedTakeProfit  for a buy position and less than the fixedTakeProfit for a sell    position. If floating stop is enabled it would be based on the maximum value for The floating Tp(maximum relative to direction of trade)

     8. The EA would not consider other trades made manually or by other EAs. 

     9. The EA should update the user via comment :

the current step number ; the current martingale run number (since initiating) ; the accumulated loss on current run; the next lot size          run continuation type.

 


As an example, take point 1 , EMA1( the turquoise line  set at offset = 0)  crosses EMA2 which is offset at 500. If the initial step size is 0.01 then a   sell position is opened with SL set at fixedStopLoss . In this case even if the user was using a floating stop loss it would automatically default  to the fixed stop loss as the distance between the EMA 2 line and EMA1 line is below the permitted stop loss level.

At point 2 though the previously opened sell position has not reached the Fixed stop loss and the floating stop loss was unable to activate, the  position is closed and a buy position is opened. If the multiply_on_loss_amount is exceeded for the current step of the martingale run then the  opening lot size for the buy order 

initial step size multiply_on_loss_factor  *( current step number).  (Assuming we index steps in martingale run  starting at 1) . 

        Additionally for point 2  lets consider the yellow rectangle. If the stop levels for the buy position opened at point  2 is represented by the long sides  of the rectangle then price would've reached the stop loss before the moment , on close, that the EMA1 would below the EMA 2. The trade would  close at the price marked by the triangle however the sell position would open at point three where the EMAs cross after the close

For Point 4 , the previous sell position would be closed and a buy position simultaneously opened at the crossing of the EMA lines. The floating Stop  Loss ,if selected as a value  => 0,  would begin at the EMA2 line and dependent on the  floatingStopLoss_Type selected would either trail behind price  for each point movement, jump between prices as current price increases every  floatingStopLoss  units  or be equal to EMA2 so long as that value is  less than the  fixedStopLoss

    

Notes:

Use points not pips as unit of price measurement though that may be simplified by rebasing for user input. Formula in text was assuming  1 unit  = 100      points

  This would be the first version of the EA. I plan to use the same developer to apply more features in the future. features would include panels, buttons ,     a partials mechanism with multiple TPs, reporting to a website ect.

  I am aware the current method of calculating the next lot size becomes inefficient really quickly would like to discuss if other more efficient models           not posted here 

 Use this set as the initial starting parameters:

EMA1_period  = 10 ;   EMA2_period = 10  ; EMA1_offshift = 0  ; EMA2_offshift =  500;  EMA1_Method = exponential;  EMA2_Method = exponential ;    EMA1_Apply2 = close ;  EMA2_Apply2 = close ; fixedTakeProfit = 10,000 ;    fixedStopLoss = 5,000 ; floatingTakeProfit = no ;   floatingStopLoss = 0 ;     floatingStopLoss_Type = jump; 

(martingale)

no_of_Steps = 3 ; initial_step_size =0.005 ; continue_after_final_step = yes ; continue_type = restart ; multiply_on_loss_amount = 5,000 ;  multiply_on_loss_rate_factor = 1 ;


応答済み

1
開発者 1
評価
(8)
プロジェクト
11
18%
仲裁
8
38% / 38%
期限切れ
1
9%
2
開発者 2
評価
(6)
プロジェクト
9
11%
仲裁
5
40% / 20%
期限切れ
2
22%
3
開発者 3
評価
(45)
プロジェクト
91
13%
仲裁
34
26% / 59%
期限切れ
37
41%
4
開発者 4
評価
(11)
プロジェクト
11
0%
仲裁
5
20% / 60%
期限切れ
2
18%
5
開発者 5
評価
(850)
プロジェクト
1457
72%
仲裁
122
29% / 48%
期限切れ
356
24%
パブリッシュした人: 3 articles
6
開発者 6
評価
(273)
プロジェクト
402
27%
仲裁
40
40% / 50%
期限切れ
1
0%
7
開発者 7
評価
(72)
プロジェクト
80
10%
仲裁
38
8% / 58%
期限切れ
6
8%
8
開発者 8
評価
(152)
プロジェクト
228
80%
仲裁
22
27% / 50%
期限切れ
11
5%
パブリッシュした人: 24 articles, 1882 codes
9
開発者 9
評価
(362)
プロジェクト
435
54%
仲裁
20
55% / 15%
期限切れ
30
7%
仕事中
10
開発者 10
評価
(21)
プロジェクト
28
36%
仲裁
7
14% / 71%
期限切れ
2
7%
11
開発者 11
評価
(298)
プロジェクト
477
40%
仲裁
105
40% / 24%
期限切れ
81
17%
取り込み中
パブリッシュした人: 2 codes
12
開発者 12
評価
(271)
プロジェクト
553
50%
仲裁
57
40% / 37%
期限切れ
227
41%
仕事中
13
開発者 13
評価
(568)
プロジェクト
641
41%
仲裁
25
48% / 36%
期限切れ
46
7%
仕事中
14
開発者 14
評価
プロジェクト
0
0%
仲裁
0
期限切れ
0
類似した注文
Gold Precision Pro 30 - 100 USD
I want the indicator to be built professionally and carefully because the strategy is strong, but it requires advanced and clean programming. The indicator should work mainly on XAUUSD M15 and should generate more than 2 high-quality signals per day, ideally around 2 to 4 signals maximum, without flooding the chart. The logic must not be random. Each signal must be based on: HTF Bias from H1/H4, Liquidity Sweep
FINAL EA STRATEGY DOCUMENT (Chandelier Exit + EMA Breakout System) ------------------------------------ CORE INDICATOR - Chandelier Exit (MAIN LOGIC) - ATR Period: Editable (Default 22) - ATR Multiplier: Editable (Default 3) IMPORTANT: - ATR must NOT be shown as a separate indicator - ATR must be used ONLY internally inside Chandelier Exit - All SL & trailing must strictly follow Chandelier Exit line
Super scalper 30 - 200 USD
Articles 1 How to create Requirements Specification for ordering a trading robot 28 MetaQuotes 225 289 Table of Contents Prerequisites for ordering a trading robot Why is it important to have a well-prepared Requirements Specification? Requirements Specification examples What is contained in the Requirements Specification? Where do I get Requirements Specification if I can't create it? Terms to use How to write an
i have a tradingview simple indecator of 40 lines of code ,i want it to convert it into mt5 EA strategy details given below AUTOMATED TRADING STRATEGY Multi-Lot Execution & Dynamic Trailing Stop Logic System Architecture & Operational Rules Trading Bot Strategy Profile Entry Conditions Buy Logic • • • Wait for Buy Signal candle. Confirmation: Future candle must break the signal high. Execution: Open 2 orders of 0.01
Situation: Please contact me privately so I can provide the source code for review. Thank you. Project Overview: I have developed a high-frequency trading (HFT) EA that performs consistently in demo environments and passes most prop-firm requirements. While short live phases showed profitability, the results were not reproducible over time. My primary goal is stable live performance on retail accounts , not just
"I need an MT5 EA based on price action — liquidity sweep + hammer/shooting star reversal strategy. TREND: Identified by HH/HL for uptrend, LL/LH for downtrend on selected timeframe. No trade in ranging conditions. BUY SETUP: In uptrend, price retraces to swing low zone, wicks below it (liquidity sweep), hammer forms (lower wick min 2x body, closes above swept low). Buy stop entry at hammer high. SL below hammer
EA SPECIFICATION SHEET OBJECTIVE: Build a transparent, non-martingale, non-grid breakout EA for XAUUSD that trades only high‑quality breakouts during London + New York sessions. 1. TRADING INSTRUMENT - XAUUSD only - MT4 platform - 5‑digit ECN broker 2. CORE STRATEGY LOGIC (BREAKOUT + CONFIRMATION) A trade is allowed ONLY when ALL conditions are true: - Candle closes beyond previous high/low (no wick breakouts) -
I am looking to develop a custom Expert Advisor (EA) for MetaTrader (MT4/MT5) based on a defined technical analysis strategy and flexible risk management rules. The EA should operate on a chart and timeframe that I manually specify, with the ability to adapt its behavior dynamically when the timeframe is changed. Core Strategy Logic The EA will execute trades based on predefined technical analysis zones
I need a professional MT5 Expert Advisor (EA) built with clean, modular code. This is an advanced strategy combining liquidity concepts, controlled DCA, hedge protection, and strict risk management. Core Requirements: Entry Logic (ALL must align): Liquidity sweep (Previous Day High/Low breakout and return) EMA50 and EMA200 trend alignment Higher timeframe bias (H1 or H4) RSI confirmation Bollinger Band entry Filters
I need a professional MQL5 developer. BEFORE I SHARE ANY DETAILS: 1. You must sign a PERPETUAL NDA with no expiration date 2. NDA includes €100,000 penalty for any breach 3. I require full .mq5 source code ownership 4. Developer must have 500+ completed jobs, 4.9+ rating Budget: €1500 EUR Duration: 14 days Start your application with "RULER" to prove you read this

プロジェクト情報

予算
30 - 100 USD
締め切り
最高 10 日