File-Based Master–Slave Trade Copying for MetaTrader 5

Summary

This description outlines a MetaTrader 5 trade copier with a master account and one or more slave accounts. The master writes position information to a shared binary file, which slave instances poll to replicate changes. The copier is intended to synchronize opening and closing positions as well as stop-loss and take-profit levels, and it includes symbol mapping for brokers that use different instrument names.

The stated operational design checks for changes every 50 milliseconds, verifies that copied positions remain valid, and closes slave positions when the corresponding master position disappears. It also anticipates failed orders, communication interruptions, unavailable symbols, and broker price differences. The description claims to preserve exact position sizes and exit levels, but gives no implementation details, latency measurements, reliability tests, or treatment of account-size differences and execution slippage. The account-copying concept is clear, while evidence that risk remains identical across brokers or accounts is not supplied.

Key ideas

• A master account publishes position data for one or more slave accounts to copy.
• The design uses a shared binary file for communication between terminal instances.
• It aims to synchronize entries, exits, stop losses, and take profits.
• Symbol mapping is included to account for broker-specific naming differences.
• Polling and error handling are described, but no reliability or execution test results are given.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.