Job finished

Execution time 39 days
Feedback from customer
He is a sweetheart, lovely person to work with. Wish you good luck. Cheers
Feedback from employee
Great client and very kind person. Excellent communication, and smooth collaboration from start to finish. I truly enjoyed working with him and would be happy to do so again. Best wishes

Specification

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 automate entry, exit, and hedging logic with configurable risk parameters.

2. Scope

The system will:

Operate on one or multiple trading instruments (e.g., EUR/USD, XAU/USD , Forex pairs).

Run on MT5, or a custom broker API.

it has to Support both backtesting and live trading.

3. Strategy Overview

Concept Summary:

The Hedging Strategy opens an initial position in one direction. Lets say its buy order, If price moves against the trade by a set distance (e.g., X pips), an opposite hedge position is opened with a larger lot size (e.g., multiplier M). When the market reverses, the combined profit from the positions offsets previous losses.

Once target profit is achieved, all positions are closed and the system resets.

This is just an over view for you to understand the scope of work , i will share the requirement specifications once we finalize and we are on the same page. 


Responded

1
Developer 1
Rating
(324)
Projects
503
19%
Arbitration
33
42% / 30%
Overdue
33
7%
Busy
1
Developer 1
Rating
(15)
Projects
19
16%
Arbitration
5
40% / 40%
Overdue
0
Free
2
Developer 2
Rating
(58)
Projects
85
27%
Arbitration
24
13% / 58%
Overdue
7
8%
Loaded
2
Developer 2
Rating
(772)
Projects
1039
44%
Arbitration
50
8% / 50%
Overdue
116
11%
Free
3
Developer 3
Rating
(21)
Projects
28
4%
Arbitration
4
25% / 0%
Overdue
3
11%
Working
3
Developer 3
Rating
(2)
Projects
2
0%
Arbitration
0
Overdue
0
Free
4
Developer 4
Rating
(16)
Projects
22
41%
Arbitration
6
33% / 50%
Overdue
0
Free
4
Developer 4
Rating
(270)
Projects
552
49%
Arbitration
57
40% / 37%
Overdue
228
41%
Working
5
Developer 5
Rating
(1)
Projects
1
0%
Arbitration
0
Overdue
0
Free
5
Developer 5
Rating
(307)
Projects
551
35%
Arbitration
79
32% / 42%
Overdue
199
36%
Loaded
6
Developer 6
Rating
(390)
Projects
416
30%
Arbitration
74
19% / 72%
Overdue
52
13%
Working
7
Developer 7
Rating
(6)
Projects
5
0%
Arbitration
2
50% / 50%
Overdue
2
40%
Free
8
Developer 8
Rating
(500)
Projects
968
74%
Arbitration
27
19% / 67%
Overdue
100
10%
Working
Published: 1 article, 6 codes
9
Developer 9
Rating
(12)
Projects
47
85%
Arbitration
1
0% / 100%
Overdue
9
19%
Free
10
Developer 10
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
11
Developer 11
Rating
(45)
Projects
63
52%
Arbitration
5
0% / 40%
Overdue
1
2%
Free
12
Developer 12
Rating
(4)
Projects
7
0%
Arbitration
3
33% / 33%
Overdue
3
43%
Working
13
Developer 13
Rating
(16)
Projects
35
23%
Arbitration
4
0% / 50%
Overdue
2
6%
Working
14
Developer 14
Rating
(295)
Projects
471
39%
Arbitration
102
40% / 24%
Overdue
78
17%
Busy
Published: 2 codes
15
Developer 15
Rating
(77)
Projects
243
74%
Arbitration
7
100% / 0%
Overdue
1
0%
Free
Published: 1 article
16
Developer 16
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
17
Developer 17
Rating
(1)
Projects
1
100%
Arbitration
0
Overdue
0
Free
18
Developer 18
Rating
(159)
Projects
284
35%
Arbitration
18
22% / 61%
Overdue
42
15%
Loaded
19
Developer 19
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
20
Developer 20
Rating
Projects
1
0%
Arbitration
1
100% / 0%
Overdue
0
Working
21
Developer 21
Rating
(10)
Projects
19
42%
Arbitration
6
0% / 50%
Overdue
3
16%
Working
22
Developer 22
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
23
Developer 23
Rating
(14)
Projects
15
40%
Arbitration
2
50% / 50%
Overdue
1
7%
Free
24
Developer 24
Rating
(338)
Projects
407
53%
Arbitration
20
55% / 15%
Overdue
29
7%
Loaded
25
Developer 25
Rating
(24)
Projects
30
13%
Arbitration
12
0% / 67%
Overdue
8
27%
Working
26
Developer 26
Rating
(64)
Projects
144
46%
Arbitration
19
42% / 16%
Overdue
32
22%
Working
27
Developer 27
Rating
(11)
Projects
18
28%
Arbitration
4
50% / 50%
Overdue
1
6%
Free
28
Developer 28
Rating
Projects
0
0%
Arbitration
1
0% / 100%
Overdue
0
Free
29
Developer 29
Rating
(249)
Projects
255
30%
Arbitration
0
Overdue
3
1%
Free
Published: 2 codes
30
Developer 30
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
31
Developer 31
Rating
(511)
Projects
549
53%
Arbitration
13
69% / 15%
Overdue
3
1%
Free
32
Developer 32
Rating
(2)
Projects
1
0%
Arbitration
1
0% / 0%
Overdue
1
100%
Free
33
Developer 33
Rating
(574)
Projects
945
47%
Arbitration
309
58% / 27%
Overdue
125
13%
Free
34
Developer 34
Rating
(73)
Projects
83
64%
Arbitration
5
100% / 0%
Overdue
9
11%
Free
35
Developer 35
Rating
(6)
Projects
6
0%
Arbitration
0
Overdue
2
33%
Free
36
Developer 36
Rating
(16)
Projects
20
0%
Arbitration
10
0% / 80%
Overdue
6
30%
Free
37
Developer 37
Rating
(3)
Projects
1
100%
Arbitration
3
0% / 100%
Overdue
0
Free
Similar orders
I need a AI signal generating bot for forex trading that use the latest ai technology to track real time forex market, analyse and give signals. The bot should operate such that when i put it in a chart it will analyse the market, after several minutes it will display whether the trade is buying or selling. It should display the one minute, five minute,15minute, 30 minute, one hour, 4 hours and daily time frame
Task Title Implement Martingale Lot Scaling Sync Between Master and Slave MT4 Trade Copier Background I am using a local master–slave trade copier setup with: 1 Master MT4 4 Slave MT4 terminals Trades are currently copied correctly (entry, direction, symbol, SL/TP). Lot size handling currently copies either: the exact master lot, or a fixed base lot defined on the slave (e.g., always 0.01 or 1.0). Problem When the
step by step and structure this into a full IEEE 830 / ISO/IEC/IEEE 29148 style Requirements Specification. This format will include: Introduction System Overview Functional and Performance Requirements Traceability Matrix (linking requirements to test cases) Verification and Validation Compliance Standards 1. Introduction 1.1 Purpose The purpose of this document is to define the technical requirements for the
Project Title: MT5 Algo Trading EA (Single Strategy + License Panel + Ownership + Manual Trade) --- Project Description I am looking for an experienced MT5 (MQL5) developer to create a clean, stable and professional Algo Trading EA for my company and future clients. This is a long-term business project, not a one-time personal EA. --- 1. Strategy Requirements - Only 1 single trading strategy - No martingale - No grid
// Add this to your EA after ExportState() function void SendToBase44(const string state, const string dir, double entry, double sl, double tp) { string url = " https://preview-sandbox--ee0a32a725b788974de435e8cef40b7a.base44.app/api/functions/receiveEAState "; string headers = "Content-Type: application/json\r\n"; string json = "{" "\"symbol\":\""+_Symbol+"\","
For only developer who understand Chaos/ Profiunity trading system by Bill WIlliams, Create The Profitunity System Trading based on Bill Williams Chaos theory, Trade based on Trend Affirmation in Daily, entry in H4, using Williams Fractal, Williams Alligator, Awesome Oscillator, Accelerator Oscillator, Market Facilitation Index. Balance Line, entry on Reversal, add on while market show continuation sign. Please quote
1.Sinyal Perdagangan : Sinyal beli: garis MACD utama memotong garis sinyal ke atas (macd_current>signal_current && macd_previous<signal_previous). Sinyal jual: garis MACD utama memotong garis sinyal ke bawah (macd_current<signal_current && macd_previous>signal_previous). Gambar di bawah menunjukkan kasus beli dan jual. 2. Posisi ditutup pada sinyal yang berlawanan: Posisi beli ditutup pada sinyal jual, dan posisi
specification High-Frequency Candle Momentum Scalper 1. Strategy Overview Core Logic: The EA identifies the current color of the active candle (Bullish or Bearish). Entry Trigger: It opens positions only after a specific duration of the candle has passed (e.g., after 30 seconds on a 1-minute candle) to confirm the direction. 2. Entry Logic (The "Half-Candle" Rule) Timeframe: M1 (Default, but adjustable). Time Filter

Project information

Budget
50 - 250 USD
Deadline
from 1 to 10 day(s)