IG PRT cannot untick Decryption of Codes in Report an automatic trading problem

• 03/26/2018 at 6:18 AM #66399
  David

  Hello fellow IG PRT traders. I went to submit a new report on an automatic trading problem and I noticed that I cannot untick the “I authorize the decryption of the codes of my personal indicators, trading systems…”

  Would some if you check if this is the same for you?

  Since when did this happen without notification?

  

  David

  Participant

  Topics: 24

  Replies: 170

  Been thanked: 31 times
  03/26/2018 at 9:18 AM #66414
  GraHal

  Yes it is greyed out for me also @David

  

  GraHal

  Participant

  Topics: 214

  Replies: 8829

  Been thanked: 2200 times
  03/26/2018 at 6:42 PM #66476
  Ulrike

  Hi David,

  if you want ProRealTime to analyze the behavior of one of your trading systems the developer needs to have access to the code of this specific strategy.

  As you may know your codes are encrypted by encryption keys before being sent to the ProOrder server. They are not transmitted over the internet without encryption. In addition, to preserve the confidentiality of your codes, no ProRealTime employee knows all of the encryption codes.

  Please note that you authorize access to only the specific code mentioned in the report window and only for the given technical report.

  Best regards,

  Ulrike

   

  

  Ulrike

  Moderator

  ProRealTime

  Topics: 0

  Replies: 88

  Been thanked: 32 times
  03/26/2018 at 11:05 PM #66489
  David

  Hi Ulrike

  Thanks for your explanation.

  I would feel a little more confident if PRT staff were the only personnel with access to the code because there’s no conflict of interest but I have to submit it to IG. IG is a market maker and giving a market maker more insight into my strategy gives them better insight/advantage to protect or hedge themselves against my trading in advance with no benefit to me or possibly adverse benefit.

  I’m confident a backtest can be done within the specified timeframe and dates to compare an instance of live erroneous trades against backtest results without the need to access a traders intellectual property. That has been sufficient until this recent disabling of this function which now sits there to tease us. Furthermore this was disabled without any communication of this happening. So can you please tell me why we used to be able to untick it and now we cannot untick it?

  

  David

  Participant

  Topics: 24

  Replies: 170

  Been thanked: 31 times
  03/27/2018 at 1:03 PM #66536
  Ulrike

  Hi David,

  IG employees do not know the encryption codes and will not be able to access your codes. Only developers working for ProRealTime and IT-Finance (the developer of ProRealTime software) have access to these codes and as outlined above no employee knows all of the encryption codes for confidentiality reasons.

  You mention the following situation as an example:

  compare an instance of live erroneous trades against backtest results

  Especially in these cases we need to access your code because the behavior between backtests and automated tradings systems is not the same and we need for example to check if

  • the start date and hour of backtest and automated strategy are exactly the same
  • the amount of pre-loaded historical data is exactly the same (very important when you use conditions based on cumulative indicators) as signals will otherwise not be the same

  If the developer doesn’t have access to the code he can only analyze if an order generated by your system has been sent correctly to the market, placed and executed but he won’t be able to see why this order has been placed by your system.

  Please note that the authorization is only necessary for technical support concerning Code or Automated Trading; this checkbox doesn’t even exist in the other sections of the technical report window such as Manual Trading, Data or other.

  Best,

  Ulrike

   

   

   

   

  

  Ulrike

  Moderator

  ProRealTime

  Topics: 0

  Replies: 88

  Been thanked: 32 times
  03/27/2018 at 1:42 PM #66544
  David

  Hi Ulrike

  In my other topic post here Pierre said that IG gets the request first and then send it to PRT. And when I spoke with my IG contact they stated, the IG IT people are waiting for me to submit the system with the error. You are saying IG don’t get to see the code, am I misunderstanding something because I’m confused – could you please clarify this for me.

  In regards to:

  Especially in these cases we need to access your code because the behavior between backtests and automated tradings systems is not the same and we need for example to check if

  • the start date and hour of backtest and automated strategy are exactly the same

  • the amount of pre-loaded historical data is exactly the same (very important when you use conditions based on cumulative indicators) as signals will otherwise not be the same

  I find it hard to accept this justification. When I submit the system with an error it will have the date it was original committed to ProOrder Autotrading, the list of trades. I confidently assume you can also see what time it was started to actually trade if it was stopped and/or restarted. So if you run the backtest as per the history of starting the system or the last time it was started you should see the report results without looking at the code. Then you can compare this with the live trades and if they don’t match you can see there’s an error. The same applies for pre-loaded historical data, its not like I can change it in the code if its been running in ProOrder because its saved and cannot be changed.

  I would understand that if you run a backtest on the system that I have submitted with my claim of a live erroneous trading and the results of the backtest and live are the same and I keep arguing that there’s an error with PRT and not my code, then you have every right to ask to inspect the code to decide if there really is an error with either PRT or my code.

  I hope you can help me understand better – thank you.

  

  David

  Participant

  Topics: 24

  Replies: 170

  Been thanked: 31 times
  04/03/2018 at 6:54 AM #66973
  David

  Ulrike I just received an email from IG with a screenshot of my code. How did they get access to this code if it is as you state?

  IG employees do not know the encryption codes and will not be able to access your codes. Only developers working for ProRealTime and IT-Finance (the developer of ProRealTime software) have access to these codes and as outlined above no employee knows all of the encryption codes for confidentiality reasons.

  You either don’t know what actually happens when issues are submitted via PRT or you’re being dishonest to me.

  

  David

  Participant

  Topics: 24

  Replies: 170

  Been thanked: 31 times
  04/03/2018 at 10:22 AM #67014
  Despair

  Wow, this was a big one! :-O

  

  Despair

  Blocked

  Topics: 97

  Replies: 1034

  Been thanked: 218 times
  04/05/2018 at 4:09 PM #67315
  Ulrike

  Hi David,

  Regarding Code Protection

  When you save your codes within your platform, they are automatically encrypted before being sent to our servers.

  Like all content that is encrypted, a key is required to access the source code. As I explained above, when you request support for a specific trading system, we need to decrypt this system to access its code (2 separate keys required, including 1 that is only accessible by an IT-Finance manager).

  However, for direct IG customers, since IG is in-between all the exchanges between ProRealTime/IT-Finance and yourself, they will be able to see the code included in our email response to you.
  We are aware of this contradiction and some improvements in our support procedures might solve this soon – see Pierre’s message here to learn more

  Regarding Support

  Even though some trading system or backtesting issues can be stated by simply looking at the results or orders that were sent, to determine the cause of the issue, our technical teams need access to the code.

  Regards,

  Ulrike

  

  Ulrike

  Moderator

  ProRealTime

  Topics: 0

  Replies: 88

  Been thanked: 32 times
• Author
  Posts