Build a simple copy-trading bot architecture for your own demo accounts

Free education, not signals. This lesson is part of EarnSouthAfrica's free forex course. It does not tell you what to buy or sell, it does not promise income, and it should be practised on a demo account before any real-money decision.

A trade copier usually has two sides: a provider that publishes trade instructions and a receiver that reads those instructions and mirrors them according to local risk settings. This lesson teaches the architecture for your own demo accounts or transparent consent-based projects.

Do not build tools that scrape private groups, bypass platform rules, steal signals, or access accounts without permission. That is not education; it is abuse. The safer beginner architecture is local, demo-only, and explicit.

What you should be able to do after this lesson

• Understand provider and receiver EA roles.
• Design a file-based demo copier using the common files folder.
• Add consent, security, symbol mapping, and risk controls.

Architecture overview

• Provider EA: watches account trades and writes a signal file to the terminal common folder.
• Signal file: contains symbol, action, provider ticket, entry, stop, target, and timestamp.
• Receiver EA: reads the file, maps symbols, checks risk rules, and opens or closes local trades.
• Risk layer: limits lot size, maximum open trades, max drawdown, and allowed symbols.

Example signal file format

provider_ticket,symbol,action,volume,stop_loss,take_profit,timestamp
123456,EURUSD,BUY,0.01,1.0800,1.0920,2026-05-30T10:00:00Z

The receiver should not blindly copy volume. It should calculate its own risk or use a small multiplier with a hard maximum.

Receiver pseudo-flow

1. Open the common signal CSV file.
2. Read the newest signal.
3. Ignore old signals or duplicate provider tickets.
4. Map provider symbol to local broker symbol if needed.
5. Check allowed symbol, max spread, max positions, and risk cap.
6. Calculate receiver lot size.
7. Place the trade on demo only.
8. Log every action and error.

Minimum safety rules

• Demo-only until you can explain and test every step.
• No third-party credentials in code or files.
• No copying without explicit permission.
• No fixed-return claims if you share the tool.
• Receiver controls risk independently from provider volume.

Academy-grade study plan

Testing is where most trading fantasies collapse. The professional standard is to make tests harder to fake: realistic ticks, costs, execution delay, out-of-sample data, forward demo, versioning, and a clear rejection rule.

Course element	What you must produce
Primary artifact	Test protocol and deployment log
Lesson focus	Build a simple copy-trading bot architecture for your own demo accounts
Working environment	Demo account, notebook, exported platform data, or local code sandbox. Never live funds for first practice.
Completion standard	You can explain the concept, reproduce the exercise, identify failure modes, and show evidence without relying on a seller's claims.

Instructor workflow

Use this workflow as if an instructor were marking the lesson. The important question is not whether the topic sounds familiar. The question is whether your notes, screenshots, calculations, logs, or code prove that you can apply build a simple copy-trading bot architecture for your own demo accounts under controlled conditions.

• Define the hypothesis and rejection standard before running a backtest.
• Separate in-sample design, out-of-sample validation, and forward demo observation.
• Record broker, symbol, timeframe, modeling mode, spread assumptions, commission, slippage, and settings.
• Treat deployment as an operations problem: uptime, logs, VPS, updates, kill switch, and monitoring.

Worked case study: Backtest looks profitable, forward demo disagrees

A bot produces an attractive historical report, then struggles on forward demo because spread widens, entries occur around news, and one parameter set was over-optimized. The paid-course response is not to hunt for a prettier report. It is to document the mismatch, isolate the cause, and decide whether the system needs simpler rules, lower risk, or rejection.

After reading the scenario, write the decision you would make before checking the suggested workflow above. Then compare your decision with the operating model. The gap between those two answers is the part of the lesson that deserves another demo repetition.

Professional template

Complete this template in your own notebook. A paid course would normally hide this kind of operating document behind worksheets; here it is part of the free lesson.

Field	Standard
Test purpose	Development, validation, stress test, bug check, execution check, or deployment rehearsal.
Data conditions	Date range, symbol, timeframe, modeling mode, costs, delay, and broker context.
Pass/fail standard	Minimum sample, maximum drawdown, sensitivity tolerance, and out-of-sample behaviour.
Deployment control	Version, settings, VPS state, kill switch, monitoring cadence, and rollback plan.

Failure-mode lab

Paid courses often sell confidence. A serious course teaches you how the idea breaks. Before continuing, test the failure modes below on demo, paper, or code review. If you cannot describe the failure, you are not ready to trust the concept.

• Optimizing until the report looks good, then calling the final settings 'the strategy'.
• Ignoring tick mode, spread, commission, delay, swap, and broker-specific symbols.
• Running live because a short forward test happened to start with wins.
• Updating platform, EA, or settings without recording what changed.

Evidence pack and pass standard

Do not mark this lesson complete because you read it. Mark it complete only when you can show the evidence below. Keep the files in a dated folder so your learning history survives platform updates, memory gaps, and sales pressure.

• A one-page note explaining build a simple copy-trading bot architecture for your own demo accounts without sales language or copied definitions.
• A screenshot, export, calculation, log, or code file that proves the practical work was completed on demo.
• A written stop rule that says when this topic must not be used with real money.
• A test protocol with at least one rejected configuration and the reason it failed.
• A deployment log that proves you can stop, restart, and verify automation cleanly.

Assessment rubric

Level	What it looks like
Not ready	You can repeat the vocabulary but cannot complete the demo task, calculate the risk, explain the failure mode, or show evidence.
Course pass	You can complete the practical task on demo, explain the decision rules, show evidence, and name the conditions where the idea must not be used.
Strong pass	You can teach the concept to someone else, find edge cases, document a rejected example, and improve the template without weakening risk controls.

Advanced homework

• Run the same test with worse spread and compare the equity curve.
• Create a one-page post-mortem for the worst backtest period.
• Build a rollback checklist for an EA version that behaves unexpectedly.

Practical drill

Do this lesson as a controlled exercise, not as a reason to trade live. Open a demo account or notebook, write the lesson title, and record what you changed, clicked, calculated, or checked. If the lesson includes code, compile it only in a demo environment and keep the original version unchanged so you can compare edits safely.

• Write a one-paragraph explanation of build a simple copy-trading bot architecture for your own demo accounts in your own words.
• Take one screenshot or note that proves you completed the platform, maths, research, or code task.
• Record one risk rule that would stop you from using this idea with real money.
• If anything feels unclear, repeat the lesson before moving to the next module.

How scammers misuse this topic

Scammers often take real concepts and wrap them in urgency. They may use platform jargon, bot screenshots, copied profit charts, or official-sounding language to make a paid offer feel safe. A real concept is not the same as a safe offer. Before paying anyone, ask whether you can verify the provider, reproduce the calculation, test the claim on demo, understand the risk, and walk away without pressure.

Checkpoint before continuing

• You can draw provider, file, receiver, and risk-layer boxes.
• You understand why receiver lot size must be local.
• You can explain the consent and security rules before coding.

Official references

These lessons are written as free education. When platform features or rules matter, verify against the official source before using real money.

• MQL5 documentation
• MQL5 CTrade documentation
• MetaTrader 5 signals help

Risk note: leveraged forex and contracts for difference can lose money quickly. EarnSouthAfrica is an educational publisher, not a broker, adviser, signal provider, or money manager.