Dukascopy Support Board • View topic - DDSJFX-202 Add built-in obfuscater to internal compiler

[quantisan]

Can we have the option (only enabled for final release build) to obfuscate our strategy and indicator when compiling to .jfx within the platform?

This will encourage more professionals develop strategies and indicators in JForex as maintaining our intellectual property is vital in this line of work.

I understand that we can obfuscate our external library as discussed in this other thread (link). But I'd imagine that this is such an essential feature for people that are releasing their strategy/indicator to clients that this feature might as well be integrated in the platform rather than for everyone to butcher their code unnecessarily.

This can be done with the Proguard API as you probably know.

Thank you for your attention.

RoadRunner

I think this would be a useful feature.
Good idea!

Guest · **User rating:** -

[quantisan] wrote:

Can we have the option (only enabled for final release build) to obfuscate our strategy and indicator when compiling to .jfx within the platform?

This will encourage more professionals develop strategies and indicators in JForex as maintaining our intellectual property is vital in this line of work.

I understand that we can obfuscate our external library as discussed in this other thread (link). But I'd imagine that this is such an essential feature for people that are releasing their strategy/indicator to clients that this feature might as well be integrated in the platform rather than for everyone to butcher their code unnecessarily.

This can be done with the Proguard API as you probably know.

Thank you for your attention.

Same thoughts here. Is there any policy or technique dukascopy is using to protect the strategies and indicators when compiling within the platform? I would be interested to hear from Dukascopy officially.