We had to develop our own system of ex4-protection to our indicator, because we’ve seen the cracking of all other solutions. As a system, this has some properties that do not allow the protection of any EA or indicator, but if they are eliminated, it would be now the strongest protection we have:
-The ex4 code must be able to separate a smaller part of algorithm which needs a few amount of data from mt4, and without this part, the EA/indicator will not work properly.
-The smaller part of algorithm must be capable of converting to a server-side programming language.
-Due to the internet latency we can not use a smaller part of algorithm in every tick, but we can use it at every candle-close.
The ex4 able to decompile, but the cracker see only the larger part of algorithm. In itself it's useless.
We don't use any restrict such as mt4 account number or computer hardware.
We can identify the client with an generated username and we can detect abuses with the traffic log on the server.
-The ex4 code must be able to separate a smaller part of algorithm which needs a few amount of data from mt4, and without this part, the EA/indicator will not work properly.
-The smaller part of algorithm must be capable of converting to a server-side programming language.
-Due to the internet latency we can not use a smaller part of algorithm in every tick, but we can use it at every candle-close.
The ex4 able to decompile, but the cracker see only the larger part of algorithm. In itself it's useless.
We don't use any restrict such as mt4 account number or computer hardware.
We can identify the client with an generated username and we can detect abuses with the traffic log on the server.
Last edited:
