One source, separately configured receivers
The source account places a trade. Its sender component shares the supported trade event with the connected receiver components. Each receiver checks its own settings and sends an order to its own broker. The broker accepts or rejects that order; the copier does not move money between accounts.
Cipher Trade Copier uses the master-account workflow. Posting a message to Telegram is not the same as placing a source-account trade. Telegram signal reading would require a separate supported integration.
Six settings to check
| Setting area | Why it matters |
|---|---|
| Source connection | The receiver must be connected to the intended master through the supplied connection process. |
| Lot-size method | Confirm fixed lots, a multiplier or another supported method for that receiver. |
| Maximum exposure | Check available order-size and account-risk limits. |
| Symbol mapping | Match broker suffixes and contract specifications, such as XAUUSD and GOLD. |
| Stops and targets | Confirm which stop, target and later modifications the build copies. |
| Copy permissions | Confirm allowed symbols, direction, sessions and start/stop behavior. |
A simple sizing example
If the supplied build supports a lot multiplier, a 0.10-lot source trade with a 0.50× multiplier requests 0.05 lots on the receiver. A receiver using fixed 0.02 lots instead requests 0.02 lots. The broker's minimum size and lot step still apply. Equal lots do not mean equal risk when contract specifications or account sizes differ.
Check the whole trade lifecycle
- Test a new source trade on a demo setup.
- Compare symbol, direction, volume, stop and target on each receiver.
- Test supported modifications and source closure.
- Check the documented behavior for existing trades when connecting.
- Confirm what happens after a disconnect or restart before turning copying back on.
If a receiver misses a trade
Check its connection, license, terminal permissions, symbol mapping, available margin and broker trading hours. Read the sender and receiver logs at the time of the source trade. If an order was rejected, use the broker error to identify the cause rather than sending repeated orders.
Final control names, supported operations and screenshots will follow the released copier build. Never assume that an offline receiver will replay every missed trade.