仕事が完了した

実行時間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%
仲裁
7
43% / 29%
期限切れ
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%
仲裁
4
25% / 50%
期限切れ
2
18%
5
開発者 5
評価
(844)
プロジェクト
1443
72%
仲裁
117
29% / 47%
期限切れ
355
25%
仕事中
パブリッシュした人: 3 articles
6
開発者 6
評価
(262)
プロジェクト
388
26%
仲裁
23
61% / 22%
期限切れ
1
0%
仕事中
7
開発者 7
評価
(72)
プロジェクト
80
10%
仲裁
35
9% / 54%
期限切れ
6
8%
8
開発者 8
評価
(152)
プロジェクト
228
80%
仲裁
19
32% / 42%
期限切れ
11
5%
パブリッシュした人: 24 articles, 1882 codes
9
開発者 9
評価
(310)
プロジェクト
370
51%
仲裁
16
50% / 0%
期限切れ
24
6%
取り込み中
10
開発者 10
評価
(21)
プロジェクト
28
36%
仲裁
3
33% / 33%
期限切れ
2
7%
仕事中
11
開発者 11
評価
(288)
プロジェクト
464
39%
仲裁
95
43% / 19%
期限切れ
75
16%
多忙
パブリッシュした人: 2 codes
12
開発者 12
評価
(270)
プロジェクト
551
50%
仲裁
57
40% / 35%
期限切れ
227
41%
仕事中
13
開発者 13
評価
(568)
プロジェクト
641
41%
仲裁
23
52% / 30%
期限切れ
46
7%
仕事中
14
開発者 14
評価
プロジェクト
0
0%
仲裁
0
期限切れ
0
類似した注文
1. Purpose and Objectives Goal: Develop an automated trading system that implements a Hedging Strategy to achieve consistent profits by hedging positions in response to market movements. Primary Objective: To minimize or remove directional market risk through offsetting long and short positions. To systematically recover losses from previous trades through controlled position sizing and incremental hedging. To
1)EA should determine trend using the candle stick,when price is above the open price of the candle ea should see it as bullish and when price is below candle stick ea see it as bearing.there should be a perimeter for user to determine which time frame candle stick ea uses to determine trend. 2)Breakeven and trailing will be in two forms (trend and non trend break even and trailing ),breakeven and trailing for trend
We are seeking an experienced professional to sanity check our vibe coding platform, which is 90% complete. The platform uses AI to generate code, links to a VM for compilation, error checking, and fixing. We need someone with expertise in MQL4 & MQL5 and AI coding development to ensure consistency and resolve any teething issues
I’m looking to connect with a developer who has a tested and reliable trading strategy , preferably one that has passed or been tested under prop firm conditions . Hi few questions Do you any trading strategy? Does your strategy pass prop firms? Is your strategy using algo? What platform you recommend to use for it? i will be waiting for a great developer to response to this offer
I am looking for an experienced MQL4 developer to create an advanced custom alert system for MT4. The alert must: draw lines on the chart when specific conditions are met send push notifications to the mobile app run as an EA on a single chart evaluate multiple internal conditions (full logic will be explained privately) This alert is part of a next-level, high-accuracy proprietary trading strategy . All details will
Description: I need a professional MT5 Expert Advisor for XAUUSD on the M5 timeframe. The EA should trade only when both SuperTrend(22) and Guard62/Range Filter confirm the same direction. Buy: when SuperTrend is green and price is above Guard62. Sell: when SuperTrend is red and price is below Guard62. Only one direction at a time — if a Buy is open, Sell will trigger only after Buy closes. Filters & Logic: ADX(14) ≥
I’m hiring an experienced algorithmic trading developer to build a production-grade bot. The system must implement a clear edge, strict risk management, reliable execution, and verifiable reporting. Target Platforms (choose one or both) MT4/MT5 EA (MQL4/MQL5), broker: ____ (e.g., IC Markets/Exness), leverage: ____ Python bot using CCXT (Binance/Bybit/OKX), running on Linux VPS (systemd/Docker) Strategy (initial
We’re seeking an MQL4 developer for an MT4 EA that replicates the behavior and UI seen on our live observer account (straddle, pyramiding, basket exits, compact control panel). Full source required. Platform: MT4 (MQL4) Scope: replicate live behavior and panel interactions Deliverables: MQ4 + EX4, brief user guide Observer account (read‑only) will be shared in chat. If interested, please reply with: 2–3 similar EA
We need an experienced MQL5 developer to build a custom Expert Advisor that executes trades based on TradingView alerts , with the following advanced features: Entry Execution via TradingView Alerts: Integrate MT4/MT5 with TradingView to trigger trades directly from TradingView alerts (using webhooks or a bridging solution). Multi-Timeframe Cross-Verification: Strategy must cross-verify signals across 2-3
I would like to develop a strategy in Ninja Trader that places bracket orders above and below the current price. There needs to be an input option for the number of ticks above and below the current bid / ask Example: place a limit order 20 ticks above the current ask price in NQ and 20 ticks below the current bid price. There needs to be an input for the time of day this strategy would be executed. Example

プロジェクト情報

予算
30 - 100 USD
開発者用
27 - 90 USD
締め切り
最高 10 日