Jury Session Record of the 19th of December 2007Organizing the Automated Trading Championship 2007, we cared about the purity of the competition and equality of conditions for all Participants. For this purpose before the Championship start we carried out automated checking of all Expert Advisors and prospective Participants for multiple registrations. This checking was aimed at revealing groups of almost identical Expert Advisors written by one developer, but sent under different names. Thus developers try to increase their chances for winning. Having conducted such a check before the Championship, we prevented the participation of many developers. For this reason the prize-winner of the previous Championship (GODZILLA) does not participate in the current competition. Besides, a group consisting of 14 EAs from one developer from Italy was not admitted to the Championship. The automated checkup helped to avoid many problems. We checked quite easily 2000 prospective participants and two thirds of them were not admitted. However it was almost impossible to check the remaining 603 participants manually. At that, for preventing the undeserved winning of frauds, we decided to check manually the leading 10 Participants of the Championship. For this purpose we gathered the information from Participants' authorization logs on the Championship website and on the trading server. We were interested in multiple logins to different accounts from one and the same IP-address. During the last week of the Championship we checked the logs and found out that authorizations for accounts of 14 Indonesian Participants were made from the same IP-addresses. In other words one developer has submitted 14 copies of one Expert Advisor (which is actually a standard Moving Average EA) with insufficient changes and regularly checked it on all 14 accounts. Examination of compiled EX4 files showed the presence of a unique text line "Error in history" (text lines are not encoded) in EA bodies which proves their identity. This fact violates the following rules of the Automated Trading Championship 2007:
One of these 14 Participants is the "developer" under the nickname admadinata, which is now among the leading positions and is contending for the prize. However the revealed violations of the Championship rules do not allow him to participate and demand his disqualification. It was decided to call a new session of the Jury. The Jury Members voted about disqualification of the above Participants.
The Jury decided to disqualify the above Participants by a majority of votes. Created: 2007.12.20 Author: MetaQuotes
Renat wrote: draz wrote: I think, you didnt check prices and charts... Look at the last 3 deals:So if everything stays the same and his "real" s/l at 1.9925 gets hit, or price stays above 1.9847, server error will make him a 3rd place winner??? And you can do nothing even if this is so obvious error? 200 pips spike! I don't believe this. ![]() 3 orders was closed by stop loss at real market price 1.9847. I did look at charts. Spike occurred at 23:11h CET . Becaouse of that spike(1.9626) s/l was modified at 23:12 CET to 1.9739, and as result trades were closed at 23:14 CET. So, trades are closed only becouse of 200 pips error spike. I can't believe that this is OK. Hi Metaquotes
Though i didn´t agree what happened to winwin2007, i´ve to say that this was a good decision. Everyone cheating should be desqualified. PERIOD draz wrote: I think, you didnt check prices and charts... Look at the last 3 deals:So if everything stays the same and his "real" s/l at 1.9925 gets hit, or price stays above 1.9847, server error will make him a 3rd place winner??? And you can do nothing even if this is so obvious error? 200 pips spike! I don't believe this. ![]() 3 orders was closed by stop loss at real market price 1.9847. 2007.12.21 14:52
Renat wrote: IV. Trading Terms
So if everything stays the same and his "real" s/l at 1.9925 gets hit, or price stays above 1.9847, server error will make him a 3rd place winner??? And you can do nothing even if this is so obvious error? 200 pips spike! I don't believe this. draz wrote: Question for Renat: I would like to know how are the trades form participant Pegasmaster closed at 1. 9837.?! In trading Jurnal Order Close request does not exist!!!!
![]() 2007.12.21 14:01
IV. Trading Terms
2007.12.21 13:13
Question for Renat: I would like to know how are the trades form participant Pegasmaster closed at 1. 9837.?! In trading Jurnal Order Close request does not exist!!!! I guess this is because of 200 pips error tick on GBP/USD at 23:11. His real trailed s/l is at 1.9925. S/L tab in Account History shows that trade is closed at Stop Loss 1.9739 and Price tab shows 1.9837??!! Low on GBP/USD is 1.9810.
admadinata wrote: ucs9360 wrote: i agree with you...I don't care who is winner, but I do care the rules. It's too late to disqualify a participant, especially the IP issues. If they must be disqualified, please do it quickly, at least one or two weeks ago, not one day ago, not just like that. The Jury got almost three months to check top 5, again, especially the IP issues. I use dynamic IP too, what if in my area have two or more participants? We may have the same IP sometimes, I think. In that case, I'll be disqualified? However, I agree that don't let one program take all the prize. We are too busy to check TOP10 permanently over 3 months. It is enough to check TOP10 at last week. 2007.12.21 11:07
for next contest i hope metaquotes organized rules more clearly avoid this situation
most hot issue is winwin2007 then with this rules "Stop Out Level is 50%"
i saw other participants balance decrease 50% and more (i called with margin call)
but nothing judge with them. No problem disqualification me from this contesst
but you claim me using moving average are you sure? let's get clear i'm using 4
indicators inside : ATR, RSI, Envelopes, Price Action and no one previous indicators
named it with moving average or maybe different country have different identification?
i don't know. About proxies yes i used it sometimes cause make my conection more
fast and cheap but using it for multiple registrations just show me that i'm nut,
let the angel of death put me this time if i'm lier. Finally decision of jury is
rules too and every participants must be respect that
|
|








We are too busy to check TOP10 permanently over 3 months. It is enough to check TOP10 at last week.
I don't think it's too difficult to write a program which can check logs everyday. Give me rules, maybe, I can help.
It may NOT a good idea to eliminate a participant (or winner) at last few day or last week, because no one can
accept this kind of judgement without fighting. If they should fail, don't let them have chance to see they can
win the prize, then the Jury comes in and say "no, you don't". Although the championship is over, but I'm hoping
next time would be better. Don't do it manually, busy would not be an excuse and timing can make it different. Thanks.