Suspicious problem setter and tester

Revision en1, by Christine-, 2025-02-03 13:43:16

Introduction

Hello, Codeforces!

I want to share my suspicions about harsh__h.

I wouldn't write the blog if he was not a relatively high ranked individual who both participated in problem setting and testing. Yesterday, I accidentally noted that the 6th place (standings), in Codeforces Round 1002 (Div. 2), which turned to be harsh__h, had very suspicious submissions. Next, I will try to explain in detail what got my attention in the order in which I uncovered it.

Part 1. Codeforces Round 1002 Div2.

During the contest in problems A(304070640), B(304090034), C(304111128) harsh__h doesn't use spaces between brackets. That is, he writes, say, for(ll i=0;i<n;i++){ not for (ll i = 0; i < n; i++) {. Also, for the newline he uses endl cout << mex << endl;, and these are not interactive problems.

Next, In problems D (304092485), E(304129652), in which I think he used chatgpt, harsh__h uses spaces between brackets and keywords, for example, writing for (ll i = 0; i < n; i++) { instead of for(ll i=0;i<n;i++){. Here for the newline he uses ‘\n', cout << (ans == inf ? -1 : ans) << '\n';

In addition, compare how he read the graph just a week ago in another graph task 303111414. A week ago it was

for(ll i=0;i<n-1;i++){
    ll x,y;cin>>x>>y;
    x--;
    y--;
    adj[x].push_back(y);
    adj[y].push_back(x);
}

and yesterday it was

for (ll i = 0; i < m1; i++) {
     ll a, b;
     cin >> a >> b;
     --a;
     --b;
     g1[a].push_back(b);
     g1[b].push_back(a);
     e1.push_back({a, b});
}

Note also, that in 304129652 he doesn’t use spaces even in cin/cout. cout<<ans<<endl;

After the contest I noted the unusual codestyle and here was his reaction

So he didn’t comment on the code style, instead he argued that he solved E1, E2, and that he, Codeforces master, doesn’t know if ChatGPT can solve a very straightforward 2059D - Graph and Graph.

Then, there was this guy MayankBhakat, probably his friend, who tried very hard to defend harsh__h, trying to ignore very suspicious codestyle.

Part 2. Educational Codeforces Round 173.

First, at this point harsh__h is a master, so Educational Codeforces Round 173 (Rated for Div. 2) is unrated for him. In this round harsh__h made submissions in very short intervals.

Let’s break it down.

2043A - Coin Transformation. In this submission 298252659 he doesn’t use his template. Also, it is very unusual when a codeforces master writes 50 lines of code to fail to solve Div2A. Then goes this submission 298254253. Now it is AC, and apparently, and someone left some comments).

Then, just 1 minute after he is done with A, he sends D 298254978, where he also does not use the template.

Then, 1 minute after the last D submission, he sends E 298257018 with the same code style as in A, D, which differs significantly from his usual style.

Then, 1 minute after the last E submission, he sends F, etc. So the submission history looks like this

I think that I made my point.

Conclusion

Could you please MikeMirzayanov, Vladosiya, KAN check the submissions? harsh__h participated in problem setting and in testing in the past. I believe that this case should be investigated to keep the integrity and fairness of the future rounds. I really hope that harsh__h just has a very peculiar codestyle. Unfortunately, I am not sure at all that this is the case.

Also, I tried my best to not make any accusations bu unfortunately the reaction of harsh__h MayankBhakat made me too emotional in my comments. For that I am deeply sorry.

Tags problem setter, testing, suspicious

History

 
 
 
 
Revisions
 
 
  Rev. Lang. By When Δ Comment
en6 English Christine- 2025-02-03 18:12:30 1601 Checked older contest with high performance. Also suspicious
en5 English Christine- 2025-02-03 14:08:36 1 Tiny change: 'sations bu unfortuna' -> 'sations but unfortuna'
en4 English Christine- 2025-02-03 13:50:35 10
en3 English Christine- 2025-02-03 13:46:36 0 (published)
en2 English Christine- 2025-02-03 13:45:52 79
en1 English Christine- 2025-02-03 13:43:16 4175 Initial revision (saved to drafts)