Even then it could not be safe. I once got a heads up from a computer dude that reckoned Metatrader can probably see the EA's if they want to. There's a lot of two ways comm's and we wouldn't know if it's copying and sending the EA's back to some server.
I don't want to start rumors, but it for total security you have to write and control all the software running on the computer you're using.
Personally I think MT is ok for learning and experimenting, but C++ and API's are the way to go if one ever gets beyond a few thousand bucks in the account.
I've heard about custom MT4's that allow EA peeking, I think it was FXPro (dont quote me on this) that modified their MT4 to do that. Most Market Maker brokers wont go to the trouble since 95% of people lose and if you're not scalping they can hedge the risk anyway. (and if you're scalping they'll kick you off) - They way the MM's get to see code is by holding contests that why I never submit. They're ran by brokers and you submit cleanly written source code!!
What I would do if I was in the EA selling business is write an EA that calculates the trade levels and directions on server A, and write the information to server B.
Then release a small EA to the clients to go and read those levels on server B. It should be possible. Myfxbook has an Ea that sends information to a server, so if it can send it must be able to fetch.
There are several possible layers of protection, I will sort it from the worst to the best:
1. Compiled EA - useless, the EA can be easily decomplied with a 3rd party service for a minimal fee.
2. EA cobined with a dll - this is a better solution since all of the EA's logic is in the dll which is much harder to decompile, although not impossible (Take for example Microsoft or Apple who can't prevent their operating systems protections' from being cracked).
3. Remote hosting of the logic as Elkart suggested - this is one of the better protections possible, since there is nothing to decompile - the EA only receives buy/sell orders from a remote machine. This comes with a price though - latency. For scalping systems this would be a huge disatvantage since it's all about perfect timing.
4. Standalone execution - this would be the best solution, however it will cost accordingly. For each managed account you would need local access to the platform - either by having a MetaTrader open for each client on your own private machine, or access to the API of the broker used. This method of course also has some latency, but it's reduced to the minimum since lower latency can be achieved only if your machine is located in the same datacenter of the broker's.
Since the 4th soultion is not viable for most of the average EA creators, I would recommend using the 3rd solution if the EA is not sensitive to latency.
고위험 경고: 외환 거래는 모든 투자자에게 적합하지 않을 수 있는 높은 수준의 위험을 수반합니다.
레버리지는 추가적인 위험 및 손실 노출을 만듭니다. 외환 거래를 결정하기 전에 투자 목표, 경험 수준 및 위험 허용 오차를 신중하게 고려하십시오.
초기 투자의 일부 또는 전부를 잃을 수 있습니다. 잃을 여유가 없는 돈을 투자하지 마십시오. 외환 거래와 관련된 위험에 대해 스스로 교육하고 궁금한 점이 있으면 독립 금융 또는 세무사에게 조언을 구하십시오.
모든 데이터 및 정보는 정보 제공 목적으로만 있는 그대로 제공되며 거래 목적이나 조언을 위한 것이 아닙니다.
과거의 성과는 미래의 결과를 나타내는 것이 아닙니다.