Build a Robust Forexo Trading Bot MT5 EA with Risk Controls, Backtesting, and Myfxbook/FXBlue Linking

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 scope)

• Entry: any of (liquidity sweep + BOS, breaker/OTE, EMA crossover, RSI filter, session/time window).

• Exit: fixed TP/SL, ADR-based targets, trailing stop, time-based exit.

• Filters: session (London/NY), high-impact news (optional), spread/slippage guard.

Risk Management (must-have)

• Fixed % risk per trade, max daily loss, max total drawdown auto-shutdown

• Position sizing (per-pair caps), N max concurrent trades

• Optional DCA safety orders with hard stop (no martingale without cap)

Core Features

• Configurable via external file (JSON/INI)

• Backtesting + walk-forward (MT5 Tester / Python–vectorbt/backtrader)

• Live metrics push to Myfxbook/FXBlue (MT) or a simple web dashboard (Flask)

• Logging, error handling, re-connect logic, order-idempotency

• VPS deploy script + runbook

Deliverables

1. Source code + build/run instructions

2. Config templates + parameter guide

3. Backtest report (last 2–5 years, multiple symbols) with equity curve, PF, win-rate, max DD, Sharpe, monthly returns

4. One-pager on risk assumptions & failure modes

5. 2–4 weeks warranty/bug-fix

Acceptance Criteria / KPIs (for demo/small live):

• Max peak-to-valley drawdown ≤ __% in backtest; PF ≥ __; at least __ symbols tested

• Live/dry-run stability for __ trading days without crashes

• All risk-limits enforce correctly (prove via logs)

Nice-to-Have

• News/calendar filter, spread/volatility adaptive sizing, partial TP, pyramiding with caps

What to include in your proposal

• 3 relevant projects (links/GitHub)

• Brief on your preferred stack & why

• Estimated timeline & milestones

• Fixed price or hourly + estimate

• Your thoughts on my strategy outline (improvements/risks)