A potential reputation XP exploit was brought to my attention today which has now been fixed. In the process of fixing this exploit I discovered the likely causes and solutions to two elusive problems that have been around for a while, they were:
[list=1]
[*]Excessive contract expiration occurring in a single race (sometimes 3-4 races taken off of a contract)
[*]Excessive reputation XP being awarded in a single race (usually 2-3x the expected amount)
[/list]
It turns out that there was nothing inherently wrong with the code, but it required a series of unexpected events to occur to trigger the behavior of the code in the wrong way. This is why until now it was not possible to see anything wrong with the code itself, but by playing around with certain triggers of the code in testing an exploit I stumbled on the triggers causing these other issues.
Since several threads have been created on these issues over the last few months, rather than responding to them all an announcement seems more apt. I would ask everyone to remain vigilant in tracking whether or not these issues reoccur, but I believe the root cause should be addressed now.









