We had to develop our own system of ex4-protection, because we’ve seen the cracking of all other solutions. It's not able to crack, because some part of the algorithm, which is running on the server, can not be accessed. 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.
There are many ways to protect the Ex4 (or DLL), but sooner or later a "pirate" could decompile them. In this method the cracker sees only the larger part of algorithm. In itself, the ex4 file is useless and he never have a chance to access to the smaller part of algorithm on the server.
We don't use any restriction, such as mt4 account number or computer hardware. We can identify the client with the generated username and we can detect abuses with the traffic log on the server. If necessary, we can turn off separately each copy of the indicator or EA remotelly by username.