[user:jaiveer_017,2026-05-17] is clearly cheating.↵
↵
I was looking at the standings for today’s contest and found something absolutely ridiculous. A user currently rated 1491 (Specialist/Newbie level) somehow pulled off a Grandmaster-level performance, solving A, B, C1, C2, D, and E1 in less than two hours with barely any penalties.↵
↵
Solving D and E1 that fast with almost zero wrong answers is completely unnatural for a 1400-level player. But the real proof is in the source code. If you look closely, it's incredibly obvious that these solutions are either copy-pasted from a Telegram group or generated by AI mid-contest.↵
↵
### Suspicious Evidence #1: The Shifting Template↵
If you look at his submissions for A, B, C1, and C2, he uses a standard copy-paste template. But suddenly, in submission D, he randomly adds `#include <cstdint>` and `using ull = unsigned long long;` to his standard boilerplate. Why would you change your base template in the middle of a contest just to solve D?↵
↵
### Suspicious Evidence #2: Completely Unnecessary Type Casting↵
His template literally has `#define int ll` to handle large numbers globally. Despite this, in his C2 submission, the code suddenly switches to using explicit `uint64_t` arrays and bizarre casts like `uint64_t ua = a;` alongside `stoull(s)`. This is a classic sign of someone pasting an AI-generated solution (which often defaults to strict `uint64_t` types for large ranges) into their existing `#define int ll` template without knowing how it actually works.↵
↵
### Suspicious Evidence #3: The Compilation Error↵
On C2, he got a Compilation Error (submission [submission:374783367]) at 17:15, and then magically got an Accepted verdict just 4 minutes later ([submission:374787736]). This usually happens when a cheater messes up their copy-paste job from a Telegram channel or ChatGPT window, hits submit without testing locally, and then quickly fixes the missing bracket or mismatched variable.↵
↵
It's really sad seeing people artificially boost their ratings like this. You don't jump from 1491 to solving E1 flawlessly without external help.↵
↵
*It would be great if user himself accepts that he indeed cheated and apologise in front of community by commeting down this blog. I am one of his well wisher and want him to grow but not by wrong means. He seems to be student at iitd and is setting wrong example for his juniors, its really sad to see that.*↵
↵
Dear Codeforces team and contest writers ([user:Sanae,2026-05-18]), please look into this and take action. ↵
↵
(Feel free to check the codes yourself: [submission:374741006], [submission:374752298], [submission:374766811], [submission:374787736], [submission:374811210], [submission:374840800])
↵
I was looking at the standings for today’s contest and found something absolutely ridiculous. A user currently rated 1491 (Specialist/Newbie level) somehow pulled off a Grandmaster-level performance, solving A, B, C1, C2, D, and E1 in less than two hours with barely any penalties.↵
↵
Solving D and E1 that fast with almost zero wrong answers is completely unnatural for a 1400-level player. But the real proof is in the source code. If you look closely, it's incredibly obvious that these solutions are either copy-pasted from a Telegram group or generated by AI mid-contest.↵
↵
### Suspicious Evidence #1: The Shifting Template↵
If you look at his submissions for A, B, C1, and C2, he uses a standard copy-paste template. But suddenly, in submission D, he randomly adds `#include <cstdint>` and `using ull = unsigned long long;` to his standard boilerplate. Why would you change your base template in the middle of a contest just to solve D?↵
↵
### Suspicious Evidence #2: Completely Unnecessary Type Casting↵
His template literally has `#define int ll` to handle large numbers globally. Despite this, in his C2 submission, the code suddenly switches to using explicit `uint64_t` arrays and bizarre casts like `uint64_t ua = a;` alongside `stoull(s)`. This is a classic sign of someone pasting an AI-generated solution (which often defaults to strict `uint64_t` types for large ranges) into their existing `#define int ll` template without knowing how it actually works.↵
↵
### Suspicious Evidence #3: The Compilation Error↵
On C2, he got a Compilation Error (submission [submission:374783367]) at 17:15, and then magically got an Accepted verdict just 4 minutes later ([submission:374787736]). This usually happens when a cheater messes up their copy-paste job from a Telegram channel or ChatGPT window, hits submit without testing locally, and then quickly fixes the missing bracket or mismatched variable.↵
↵
It's really sad seeing people artificially boost their ratings like this. You don't jump from 1491 to solving E1 flawlessly without external help.↵
↵
*It would be great if user himself accepts that he indeed cheated and apologise in front of community by commeting down this blog. I am one of his well wisher and want him to grow but not by wrong means. He seems to be student at iitd and is setting wrong example for his juniors, its really sad to see that.*↵
↵
Dear Codeforces team and contest writers ([user:Sanae,2026-05-18]), please look into this and take action. ↵
↵
(Feel free to check the codes yourself: [submission:374741006], [submission:374752298], [submission:374766811], [submission:374787736], [submission:374811210], [submission:374840800])
