Job finished
Execution time 17 days
Specification
1. Introduction
1.1. Purpose
The purpose of this EA is to automate the EMA crossover strategy to achieve consistent trading results in the Forex market. Users will manually input the two EMA periods to allow for testing various combinations and identifying a successful trading system.
1.2. Scope
The EA will operate on major currency pairs, indices, and stocks across multiple timeframes to enable testing of different timeframes.
2. Functional Requirements
2.1. Trading Strategy
Entry Conditions
- Buy Signal: A buy order is initiated when the slow EMA crosses above the fast EMA.
- Sell Signal: A sell order is initiated when the slow EMA crosses below the fast EMA.
- Time Window: Include a time window when entries can be taken. This will allow trades to be initiated only within specific hours of the day.
Exit Conditions
- Close Buy Position: The buy position is closed when the slow EMA crosses below the fast EMA.
- Close Sell Position: The sell position is closed when the slow EMA crosses above the fast EMA.
- Exits Based on Signal: Exits do not depend on the time of day. They can happen only when an exit signal is given.
- Negative Stop Loss Trailing: Include a negative stop loss trailing until an opposite signal is given. Exit the trade when an opposite signal occurs.
Breakeven Condition
- Breakeven:
Breakeven will have two conditions that a user will have to set in the settings section. Below are the conditions. All will be tested to have a better setting that is profitable,
- Condition 1: Include a breakeven condition to be set at the close of the buy or sell candle when 3 consecutive candles close above or below the crossover, depending on whether it is a buy or sell.
- Condition 2: Include a breakeven condition to be set after a number of pips have been covered.
Stop Loss Placement
- Stop Loss at Candle Low: Set a stop loss at the low of the candle that provided the signal.
- Stop Loss Distance: Allow users to specify the distance from the signal candle low to the stop loss in pips.
- Breakeven at Signal Entry: If the stop loss moves a certain number of pips, set the breakeven to the entry point of the signal.
- Adjustable Stop Loss: Be able to adjust the stop loss, especially when there is news or other market events that may impact trading conditions.
Order Types
- Market Orders
2.2. Risk Management
- Position Sizing: The position size will be 1% of the account balance per trade.
- Stop Loss: The stop loss is marked as the last point in the buying signal. However, it must meet a certain number of pips. If it moves a certain number of pips, set the breakeven to the entry point of the signal.
- Adjustable Stop Loss: Be able to adjust the stop loss, especially when there is news or other market events that may impact trading conditions.
- Take Profit: Fixed take profit at 100 pips.
- Trailing Stop: No trailing stop will be used.
2.3. Money Management
- Lot Size: Set the lot size for each trade based on user input or calculated based on the position size percentage.
- Maximum Drawdown: 30% of the account balance.
- Maximum Number of Open Positions: Only one position (either long or short) will be open at any time.
2.4. Trade Management
- Hedging: Hedging will not be used.
- Martingale or Grid Strategies: These strategies will not be used.
3. Technical Requirements
3.1. Platform
MetaTrader 5 (MT5)
3.2. Programming Language
MQL5
3.3. Performance
- Execution Speed: Orders should be executed in less than a second, if possible.
- Resource Usage: The EA should minimize CPU and memory usage.
4. Non-Functional Requirements
4.1. Reliability
- Uptime: The EA should maintain 99.9% uptime.
- Error Handling: The EA should handle errors gracefully and log them for further analysis.
4.2. Maintainability
- Code Documentation: The code should be well-documented with comments explaining the logic.
- Modularity: The code should be modular to facilitate future updates or changes.
4.3. Security
- Access Control: Only the admin can modify EA settings.
- Data Protection: Sensitive data should be handled securely.
5. User Interface Requirements
5.1. Inputs
- Indicator Parameters:
- Fast EMA period: Varies
- Slow EMA period: Varies
- Risk Parameters:
- Position size (percentage of account balance): 1%
- Stop loss: User-defined distance in pips from the signal candle low.
- Take profit: 100 pips
- Trade Parameters:
- Maximum drawdown: 30%
- Maximum number of open positions: 1
- Lot size: User-defined or calculated based on the position size percentage.
- Time Window Parameters:
- Start Time: The start of the time window for taking entries.
- End Time: The end of the time window for taking entries.
5.2. Outputs
- Trade Logs: Detailed logs of each trade, including entry and exit points, position size, and profit/loss.
- Performance Reports: Daily performance reports detailing key metrics such as profit factor, drawdown, and win rate.
6. Testing Requirements
6.1. Backtesting
- Historical Data: Use historical data from the past 2 years.
- Performance Metrics: Evaluate metrics such as profit factor, drawdown, win rate, and total net profit.
6.2. Forward Testing
- Demo Account Testing: Test the EA on a demo account for 3 months to validate performance.
- Live Testing: Test the EA in a live environment with limited funds for 1 month.
7. Documentation Requirements
7.1. User Guide
- Installation Instructions: Step-by-step guide on how to install the EA on MT5.
- Configuration Guide: Detailed instructions on how to configure the EA’s settings.
- Usage Guide: How to start and stop the EA, and interpret its outputs.
7.2. Technical Documentation
- Code Documentation: Include in-line comments and explanations within the code.
Responded
1
Rating
Projects
329
29%
Arbitration
36
25%
/
64%
Overdue
10
3%
Working
2
Rating
Projects
90
29%
Arbitration
24
13%
/
58%
Overdue
7
8%
Working
3
Rating
Projects
129
25%
Arbitration
23
30%
/
52%
Overdue
8
6%
Free
4
Rating
Projects
5
0%
Arbitration
3
0%
/
100%
Overdue
1
20%
Working
5
Rating
Projects
20
10%
Arbitration
4
50%
/
50%
Overdue
5
25%
Free
6
Rating
Projects
1
0%
Arbitration
4
0%
/
50%
Overdue
0
Working
7
Rating
Projects
9
22%
Arbitration
12
42%
/
58%
Overdue
0
Free
8
Rating
Projects
5
20%
Arbitration
3
0%
/
100%
Overdue
2
40%
Free
9
Rating
Projects
9
33%
Arbitration
11
0%
/
100%
Overdue
2
22%
Free
10
Rating
Projects
80
10%
Arbitration
38
8%
/
58%
Overdue
6
8%
Free
11
Rating
Projects
186
41%
Arbitration
24
58%
/
21%
Overdue
13
7%
Free
12
Rating
Projects
91
13%
Arbitration
34
26%
/
59%
Overdue
37
41%
Free
Similar orders
Professional MT5 Expert Advisor – Multi-Engine Trading Framework Description I'm looking for an experienced MQL5 developer to build a professional MetaTrader 5 Expert Advisor. This is not a simple indicator-based EA. The system should be designed using a modular architecture with a strong focus on maintainability, optimization, and future scalability. The first version should include the following features. Market
Looking for an MT5 Expert Advisor developer with: Minimum 1 year of verified activity on the MetaTrader Market Positive, real user reviews Ability to build EAs without Bollinger Bands Fully configurable parameters (risk, filters, SL/TP, trading hours) Free test version available before any payment Clear communication and ongoing support If you meet these requirements, please send your MQL5 profile or portfolio
Akram boushaba
30 - 500 USD
مرحبا كيف حالكم انا اكرم مهتم بالتداول احاول ان اصمم برنامج روبوت قادر على التداول من تلقاء نفسه من يمكنه ان يساعدني او يعلمني كيف استطيع فهل ذلك وسأكون ممتناً له وشكرا لكم
MetaTrader In-App Trade Alerts An existing MetaTrader terminal is already running on my side, but its account is kept hidden for privacy reasons. I need a specialist to wire up native in-app notifications so that every time a position is opened or later closed I see an immediate pop-up inside the platform—no emails or SMS, just the built-in alert window (and the usual MT push to mobile if that comes automatically
EA Crafter
500+ USD
Act as a professional Quantitative Developer and Risk Manager. I want to build a systematic trading strategy rulebook that prioritizes capital preservation and statistical edge over raw performance. Please generate a structured trading strategy using the following framework: 1. ASSET CLASS & TIMEFRAME: - Asset: [e.g., Apple (AAPL), Bitcoin (BTC), or EUR/USD] - Timeframe: [e.g., 5-minute, 1-hour, Daily] 2. CORE
JOB TITLE: XAUUSD ONLY MQL5 Strategy Developer Needed To Improve Existing MT5 EA Winrate JOB DESCRIPTION: I already have a working MetaTrader 5 Expert Advisor with a fixed set file and existing trading logic. The strategy is based on Volume Profile / Delta bias, ATR-based TP/SL, ATR deviation filtering, ATR trade spacing, break-even after TP1, and TP lock management. I am looking for an experienced MQL5 / trading
مطلوب مبرمج اكسبيرت
30+ USD
أحتاج إلى مستشار خبير لمنصة MetaTrader 5 (MT5) مصمم كآلة حالة محدودة (FSM). يجب أن ينفذ أوامر السوق فقط بناءً على مستويات أسعار يحددها المستخدم. يجب ألا يستخدم أي مؤشرات أو تحليل فني أو أوامر معلقة أو ذكاء اصطناعي أو قرارات تداول تلقائية. يجب أن ينفذ المستشار الخبير ببساطة تسلسلًا محددًا مسبقًا لمستويات الأسعار كما يحددها المستخدم تمامًا، مع إدارة دقيقة للحالة، ودورة نشطة واحدة في كل مرة، ومعالجة الفجوات السعرية،
Make Ea from Investor login
30 - 100 USD
Message me please for the investor login. You will replicate the ea and I shall tell u some things about it, I am not paying over $100. You should have great skills. The EA can handle any market and shall not blow the account
Мне нужен простой торговый бот, написанный исключительно на Python. Бот должен подключаться к терминалу MetaTrader 5 через официальную библиотеку Python "MetaTrader5". Объем кода невелик (около 250 строк). КРИТИЧЕСКИ ВАЖНЫЕ ТРЕБОВАНИЯ: 1. НЕТ КОДА MQL5: Весь проект должен быть написан только на Python. 2. ВНЕШНЯЯ КОНФИГУРАЦИЯ: У бота должен быть внешний конфигурационный файл (config.ini или settings.json). Я должен
Dashboard Backtest
30 - 500 USD
Hello, I have a question. Is it possible to create an offline version of MetaTrader for backtesting multi-timeframe dashboards? Specifically, I would like the dashboard to receive historical data from multiple timeframes (such as M1, M5, M15, H1, and H4) during a backtest and operate exactly as it does in live trading. Is this technically possible, or do MetaTrader's backtesting limitations prevent this
Project information
Budget
30 - 100 USD
Deadline
from 1 to 2 day(s)