guys...
I am extremely delighted to invite you to participate in my first solo round, Codeforces Round 1050 (Div. 4), starting on Sep/13/2025 17:35 (Moscow time). There will be $$$7$$$ problems to be solved in $$$2$$$ hours and $$$15$$$ minutes.
The format of the event will be identical to Div. 3 rounds:
We urge participants whose rating is 1400+ not to register new accounts for the purpose of narcissism but to take part unofficially. Please do not spoil the contest for the official participants.
Only trusted participants of the fourth division will be included in the official standings table. This is a forced measure for combating unsporting behavior. To qualify as a trusted participant of the fourth division, you must:
Regardless of whether you are a trusted participant of the fourth division or not, if your rating is less than 1400 (or you are a newcomer/unrated), you may choose to participate rated or unrated.
PLEASE NOTE the rule restricting AI use. If you are caught using AI in an unorthodox manner, either by us manually or detected automatically, YOUR ACCOUNT WILL BE TERMINATED and your entire family will be sent to my basement (which has no toilets available). We will be actively scouring submissions and terminating rulebreakers.
I would like to thank the following individuals for making this contest possible:
Myself for coordinating the round
.
Vladosiya for russian translations.
reirugan for improving the statements.
The following testuwuers: Proof_by_QED, reirugan, -firefly-, Filikec, Friedrich, mathtsai, __baozii__, Non-origination, chromate00, SpyrosAliv, Intellegent, Dominater069, Hori, RobinFromTheHood, pop, yse, Vladosiya, Lechaa, beaten_by_ai, macaquedev, catgirl, kingbass, tin.le2, ByteRaider, Trace_X1729, AksLolCoding, expertaq, kwant, santaclaus67, akane646, Hana05, .Habiba., apollo07, shuniko, Jteh, avighnakc, nifeshe, Edeeva, Eikyu, wuhudsm, and temporary1.
I know it has been a while without a division 4, so GLHF!
Hello Codeforces.
I was stuck on a 3 hour flight with nothing to do, so what better way to spend my time than catching up on the new CSES problems. But it turns out I finished those too quick so I guess I'm writing the solutions for some of them here. No one probably asked.
This will only cover the new problems from the 2025 update and in the Additional Problems I section. For old problem solutions you can probably find them somewhere on the internet. For new problems not in this section, some of their solutions are in this blog.
Codeforces! Proof_by_QED, chromate00, larush, Edeeva, and I would like to invite you to participate in Codeforces Round 1003 (Div. 4), starting on 09.02.2025 17:35 (Московское время). We have baked $$$8$$$ problems to be solved in $$$2$$$ hours and $$$15$$$ minutes. We hope the problems will be interesting, unique...and skibidi.
The format of the event will be identical to Div. 3 rounds:
We urge participants whose rating is 1400+ not to register new accounts for the purpose of narcissism but to take part unofficially. Please do not spoil the contest for the official participants.
Only trusted participants of the fourth division will be included in the official standings table. This is a forced measure for combating unsporting behavior. To qualify as a trusted participant of the fourth division, you must:
Regardless of whether you are a trusted participant of the fourth division or not, if your rating is less than 1400 (or you are a newcomer/unrated), you may choose to participate rated or unrated.
PLEASE NOTE the rule restricting AI use. If you are caught using AI in an unorthodox manner, either by us manually or detected automatically, YOUR ACCOUNT WILL BE TERMINATED. We will be actively scouring submissions and terminating rulebreakers.
Anyways, I would like to orz the following:
Vladosiya for coordinating.
Our growing family of testuwuers: [VIP] Dominater069, Error_Yuan, amoeba4, Intellegent, [VIP] Friedrich, temporary1, efishel, 18o3, -firefly-, __baozii__, monadtransformer, Sacharlemagne, Lilypad, kevlu8, Filikec, [VIP-] macaquedev, beaten_by_ai, mathtsai, DivinePunishment, pianapolataa, reirugan, and pop.
MikeMirzayanov for running this site for 15 years. 15 years ago, I was still eating crayons.
Problem Credits: Proof_by_QED
Analysis: larush
Problem Credits: Lilypad
Analysis: larush
Problem Credits: Friedrich
Analysis: macaquedev
Problem Credits: Proof_by_QED
Analysis: Proof_by_QED
Problem Credits: Friedrich
Analysis: DivinePunishment
Problem Credits: Proof_by_QED, cry
Analysis: -firefly-
Problem Credits: chromate00
Analysis: macaquedev
It seems like all GIFs in problem statements are broken.
Remember when the triangle in the notes section of 2009D - Сатьям и подсчет used to animate? I sure did, because I spent 2 hours making it (5 minutes on the actual GIF and the other 115 minutes on compressing the image size). Now it's just a static image D;
It's worth noting that Polygon never supported GIFs, I just converted my GIF to an APNG then uploaded it as a PNG as described in this comment.
But it's a new era now and that has broken as well. If anyone finds any other bypasses, then please let me know. Otherwise, KAN and MikeMirzayanov may have to actually implement GIFs D;
Problem Credits: cry
Analysis: macaquedev
Problem Credits: Lilypad
Analysis: Lilypad, macaquedev
Problem Credits: cry
Analysis: macaquedev
Problem Credits: cry, Proof_by_QED
Analysis: macaquedev
Problem Credits: Proof_by_QED,Lilypad
Analysis: macaquedev, chromate00
Problem Credits: chromate00, Proof_by_QED
Analysis: DivinePunishment
Problem Credits: Lilypad
Analysis: macaquedev
Problem Credits: Lilypad
Analysis: Proof_by_QED
Problem Credits: cry
Analysis: chromate00
Proof_by_QED, Lilypad and I are very
to invite you to participate in Codeforces Round 993 (Div. 4), which will start on Dec/15/2024 17:35 (Moscow time). There will be $$$8$$$ problems, with one split into two subtasks, to be solved in $$$2$$$ hours and $$$15$$$ minutes. Participate or you'll have to wait another millennium for a Div. 4 round.
The format of the event will be identical to Div. 3 rounds:
We urge participants whose rating is 1400+ not to register new accounts for the purpose of narcissism but to take part unofficially. Please do not spoil the contest for the official participants.
Only trusted participants of the fourth division will be included in the official standings table. This is a forced measure for combating unsporting behavior. To qualify as a trusted participant of the fourth division, you must:
Regardless of whether you are a trusted participant of the fourth division or not, if your rating is less than 1400 (or you are a newcomer/unrated), you may choose to participate rated or unrated.
We want to express overwhelming gratitude to the following orzosities for making the contest possible:
Vladosiya for reviewing the contest.
(VIP+) chromate00 for the idea for one of the problems.
Our testuwuers: awesomeguy856, (VIP) Dominater069, Error_Yuan, Edeeva, -firefly-, (VIP) Friedrich, 18o3, Intellegent, amoeba4, Starlight-Sailor, efishel, yoru_sacri, larush, (VIP+) chromate00, DivinePunishment, kevlu8, reirugan, mathtsai, RobinFromTheHood, Filikec, macaquedev, pianapolataa, and members of my high school's coding club including but not limited to IceWolf898, MC3297, and ETL.
(MVP++) MikeMirzayanov for Codeforces and Polygon.
sum, Proof_by_QED and I are like a dog with two tails to welcome you to participate in Codeforces Round 988 (Div. 3) at Nov/17/2024 17:35 (Moscow time). We have cooked up $$$7$$$ problems to be solved in $$$2$$$ hours and $$$15$$$ minutes.
The round will be hosted by rules of educational rounds (extended ICPC). Thus, solutions will be judged on preliminary tests during the round, and after the round, it will be a 12-hour phase of open hacks. After open hacks all accepted solutions will be rejudged on successful hacks.
Note that the penalty for each wrong submission in this round is 10 minutes. Also, note the rule restricting AI use!!! If you are caught using AI in an unorthodox manner, bad things will happen to you. We will be watching you all...
IMPORTANT!!! There is at least one interactive problem in the problemset. Please familiarize yourself with the guide for interactive problems beforehand.
Remember that only the trusted participants of the third division will be included in the official standings table. As it is written by link, this is a compulsory measure for combating unsporting behavior. To qualify as a trusted participant of the third division, you must:
Regardless of whether you are a trusted participant of the third division or not, if your rating is less than 1600, then the round will be rated for you (unless you register unrated).
We would like to orz the following individuals for making the contest possible:
Vladosiya for the pogU coordination.
Our army of testuwuers: (VIP) Dominater069, amoeba4, Friedrich, awesomeguy856, AlperenT, Error_Yuan, 18o3, Intellegent, efishel, Edeeva, Lilypad, wuhudsm, Vladosiya, Filikec, kevlu8, (VIP) chromate00, Prady, mathtsai, SolCollider, larush, RobinFromTheHood, macaquedev, and dazlersan1.
MikeMirzayanov for being MikeMirzayanov.
Problem Credits: cry
Analysis: cry
Problem Credits: cry
Analysis: chromate00
Problem Credits: sum
Analysis: chromate00
Problem Credits: cry
Analysis: chromate00
Problem Credits: Proof_by_QED
Analysis: Intellegent
Problem Credits: Proof_by_QED
Analysis: Proof_by_QED
Problem Credits: Proof_by_QED
Analysis: Proof_by_QED

Note the unusual starting time. This round starts 30 minutes before the standard starting time.
Proof_by_QED and I are extremely excited to invite you to Codeforces Round 979 (Div. 2) on 19.10.2024 17:05 (Московское время). You will be given 7 problems and 2 hours and 15 minutes to solve them. One problem will be split into two subtasks. This round will be rated for all participants with rating below 2100.
This round is based on... absolutely nothing.
We would like to mention the following individuals for making the contest possible:
Our coordinatorz satyam343 for his active and insightful coordination once again. ORZ!!!!
Our testuwuwuwuers for their efforts in improving this gramazing contest: nifeshe (VIP tester), Thienu, imirdy, Dominater069, A_G, Everule, LipArcanjo, omeganot, MridulAhi, 18o3, Edeeva, IceKnight1093, andrewtam, JagguBandar, Friedrich, Intellegent, cadmiumky, aryanc403, awesomeguy856, kingmessi, amoeba4, malachi_toney_goat, DNR, alexlikemath007, fishy15, Vladosiya, trash-can, CutSandstone, chromate00, ntarsis30, Non-origination, redpanda, Lilypad, kevlu8, MC3297, mathtsai, jcai972, and our honorary newbie tester tibinyte2006.
Alexdat2000 for translating the statements to Russian.
The most jacked user on this list, MikeMirzayanov, for developing Codeforces and Polygon.
Score Distribution: $$$250 - 500 - 1000 - 1500 - 2000 - 2500 - (3000 + 1500)$$$
Below is a timeline of the changes made to the round from start to finish. I hope this can depict what setting a contest is actually like for aspiring problemsetters. Please give me feedback about this in the comments. What else about the round would you like to know? Was this helpful?
Problem Credits: Proof_by_QED
Analysis: Proof_by_QED
Problem Credits: Proof_by_QED
Analysis: Proof_by_QED
Problem Credits: Proof_by_QED
Analysis: Proof_by_QED
Problem Credits: Proof_by_QED, cry
Analysis: cry
Problem Credits: Proof_by_QED, cry, satyam343
Analysis: cry
Problem Credits: Proof_by_QED, satyam343
Analysis: Proof_by_QED
Problem Credits: Proof_by_QED, satyam343
Analysis: satyam343

Proof_by_QED and I are very delighted to invite you to participate in Codeforces Round 971 (Div. 4), which will start on 03.09.2024 17:35 (Московское время). There will be $$$7$$$ problems, with one split into three subtasks, to be solved in $$$2$$$ hours and $$$30$$$ minutes. We encourage you to participate and hope you have fun, regardless of your division!
The format of the event will be identical to Div. 3 rounds:
We urge participants whose rating is 1400+ not to register new accounts for the purpose of narcissism but to take part unofficially. Please do not spoil the contest for the official participants.
Only trusted participants of the fourth division will be included in the official standings table. This is a forced measure for combating unsporting behavior. To qualify as a trusted participant of the fourth division, you must:
Regardless of whether you are a trusted participant of the fourth division or not, if your rating is less than 1400 (or you are a newcomer/unrated), you may choose to participate rated or unrated.
We want to express overwhelming gratitude to the following orzosities for making the contest possible:
Vladosiya for his awesome coordination and mesanu for reviewing the problemset once again.
Our MVTs (Most Valuable Testuwuers), satyam343 and Dominater069, for their dedicated contributions.
The rest of our army of testuwuers: omeganot, nika-skybytska, awesomeguy856, 18o3, Lilypad, chromate00, Sacharlemagne, ntarsis30, Prady, Non-origination, TheYashB, ETL, Orange905, MC3297, mathtsai, macaquedev, jcai972, and cj8450.
MikeMirzayanov for all that jazz.
01100 00000 11000 10011 00111 01000 10010 01001 01110 10100 10001 01101 00100 11000 01011 00100 00000 00011 10100 10010 10010 10011 00000 10001 10110 00000 10001 00011
UPD: The round will be unrated, even though m1.codeforces.com, m2.codeforces.com, and m3.codeforces.com were functioning correctly. While there were issues on the main site (which lasted more than an hour), no participant was able to view the leaderboard, ask a question, or receive an answer.
Thanks for participating! Despite the round being unrated, we hope you've enjoyed the problemset. We put a lot of effort into this round :prayge:
I want to give huge thanks to Dominater069 and satyam343 for their heavy contributions to the subtasks of G. If you're participating out of competition, we hope you enjoyed attempting these bonus subtasks. Otherwise, we hope you will enjoy upsolving them!
Problem Credits: cry
Analysis: cry
Problem Credits: cry
Analysis: cry
2009C - The Legend of Freya the Frog
Problem Credits: Proof_by_QED
Analysis: cry
Problem Credits: Proof_by_QED
Analysis: cry
2009E - Klee's SUPER DUPER LARGE Array!!!
Problem Credits: cry
Analysis: cry
Bonus: Solve in $$$\mathcal{O}(1)$$$.
Problem Credits: cry
Analysis: cry
2009G1 - Yunli's Subarray Queries (easy version)
Problem Credits: cry, Proof_by_QED
Analysis: Proof_by_QED
2009G2 - Yunli's Subarray Queries (hard version)
Analysis: Solution 1: Proof_by_QED, Solution 2: awesomeguy856
2009G3 - Yunli's Subarray Queries (extreme version)
Analysis: Dominater069
Hello Codeforcers, especially fellow problemsetters.
I'm lazy. I like setting cool problems, but I don't enjoy preparing them. Sometimes, I take longer to prepare a problem than coming up with the idea. Surely I'm not the only one. My laziness has motivated me to make this blog about a feature I think will benefit the future of problemsetting and more frequent contests for codeforces.
I propose that there should be a hub for crowdsourcing useful generators from past problems. Similar to a hub for Minecraft mods, I think there should be something similar for testlib generators. Authors of past rounds should be able to upload generators to that hub. They should be able to specify the tags (number theory, brute force, tree) solutions that their generator targets to TLE, and be able to specify what makes their generator special. For example, there can be generators focused on special kinds of trees required to make strong tests for a certain tree query problem. Future problemsetters should be able search up the types of generators they need for their own problems and examine these posted generators and modify it to their own needs. This should save them a lot time. Sometimes, they can recognize other problems on CF and think "man, it would be nice if I had a generator that this problem also requires".
Here's an example, consider 1985E - Секретный ящик. The solution to it requires to loop through all possible factors of two of the three integers given in the input. Obviously, inputs that are big but also have a lot of factors should be nice. If only someone made a generator on selecting random numbers with large amount of factors in a range, like a more extensive list of Highly Composite Numbers :weary:
Anyways, TLDR: this would be quite cool though :v
In the comments section of my most recent round, there has been a lot of misconceptions about interpreting score distribution. This blog is just to inform the correct way of understanding them from a problemsetter standpoint.
The biggest misconception I saw was score distributions are always almost equal to its difficulty. This is not true. Do you really think 1852A - Набор Ntarsis is a rated 500 problem?
The correct way to interpreting score distribution is looking at the differences between each adjacent gaps. I will give suggestions on interpreting difference in points in a Div. 2 round. Div. 1 Scoring may be different because the difficulty curve is different.
Usually, a $$$250$$$ point gap means the two problems are relatively similar in difficulty but with a slight difficulty increment. A $$$500$$$ point gap represents the standard gap between adjacent problems that you'd expect. I think any gap $$$750$$$ or above means there is a decently large difficulty discrepancy between the two problems. I will use Codeforces Round 965 (Div. 2) as an example.
Problems A and B are expected to be similar difficulty with B being slightly challenging. B and C are $$$500$$$ apart, which means that the difficulty difference between B and C is expected to be larger than that for A and B. In hindsight, I probably should've assigned a $$$750$$$ point difference. This is also why you shouldn't rely on score distribution to determine whether you should approach a problem or not, as the assigned difference could be higher or lower than the actual gap. Again, there is a $$$250$$$ gap between C and D so they are expected to be relatively close in difficulty but D should still be harder than C; same for D and E1.
Problems with subtasks usually come with $$$(x + y)$$$ in the announcement blog, with $$$x$$$ being the score assigned to the easy version and $$$y$$$ for the harder version. In most round, this usually means that if the easy version is a stand-alone problem, then it should be assigned $$$x$$$ points. If only hard version is proposed, then it should be worth $$$x+y$$$ points. However, I don't believe that this should always be the case in the future, which is why this blog is also a suggestion to future problemsetters.
Originally, E1 was going to be assigned $$$2000$$$ points and E2 assigned $$$1000$$$ points. Then, one of our testers, Dominater069 said "I wrote 10 mins of ds for E1 for $$$2000$$$ points... And then take 30 mins just for $$$1000$$$ points?" I thought about this and I was like, he has a point. There has been a lot of instances where the hard version is a lot harder than the easy version, but isn't worth a significant amount of points on its own. Therefore, I think setters should weigh the hard version like a standalone problem, and decrease its value based on how much of the observation that the easy version gives away.
Lastly, score distributions aren't always accurate. They are usually only decided by setters, the coordinator, and a small subset of the testers. You shouldn't get scared if you see a large score gap between problems. Most of the time, us setters also get surprised by the performance of you codeforcers.
sum, satyam343, and I are extremely ecstatic to invite you to Codeforces Round 965 (Div. 2) on 10.08.2024 17:35 (Московское время). You will be given 5 problems and 2 hours to solve them. 1 problem will have subtasks. This round will be rated for all participants with rating below 2100. We spent the most time cooking up this round than any other round, so it means a lot if you will participate.
We would like to orz the following individuals for making the contest possible:
Our coordinatorz satyam343 for his gracious coordination and donation of his own problems to this contest.
Our testuwuers: Benq, omeganot, maxwellzen, 244mhq, null_awe, Dominater069, A_G, Yam, IceKnight1093, Phi-001, CSQ31, fishy15, Java, kingmessi, Pols_Agyi_Pols, harsh__h, awesomeguy856, TyroWhizz, andrewtam, oursaco, 18o3, lethan3, Stefan2417, milind0110, willy108, amsraman, MridulAhi, AryRDW, h2rsh, page_fault, IceWolf898, US3RN4M3, callmepandey, jay_jayjay, flight, xug, Qualified, Sacharlemagne, chromate00, ntarsis30, redpanda, Faizal, windreaper, TheYashB, Prady, Non-origination, waidenf, ETL, oddvalue, and Rahuldeb5.
Alexdat2000 for translating the statements to Russian.
MikeMirzayanov for developing Codeforces and Polygon (mentioning this so I don't lose 1000 social credits).
Score Distribution: $$$500 - 750 - 1250 - 1500 - (1750 + 1750)$$$
Hello Codeforces!
If you've somehow been living under a barn, USACO is the largest online competitive programming contest for the USA high school students. As I myself am a USA high school student about to graduate, I'd like to reflect on my experience with contributing problems to USACO. By the way, I don't select problems that end up on each contest — I just contribute possible candidates. Also, I guess this is inspired by xiaowuc1's blog, who also used to be a pretty active USACO problemsetter.
The difficulty column is purely based on my own opinion.
| # | Problem | Contest | Difficulty | Comments |
|---|---|---|---|---|
| 1 | Circular Barn | Silver, 2022 December | 1700 | This was my first attempt at setting a problem. Tbh, I had no idea what I was doing. Originally, this problem going to involve Goldbach's Conjecture and I came up with the basic idea involving game theory. However, I had no idea how to solve it (it was probably impossible anyways) so I did what any newbie wannabe problem writer does — send it to a friend and hope they solve it. Not only did US3RN4M3 end up solving the problem, he modified it to a much better version. He also ended up preparing the test cases of the problem. orz. |
| 2 | Moo Language | Bronze, 2023 US Open | 1900 | erm.. I think I was prepping for the PSAT lol. Best problem of all time. I came up with $$$\mathcal{O}(N)$$$ solution a couple days before the contest, but I guess the problem had already been prepared. P.S. I think the other two bronze problems in this contest are just as hard. |
| 3 | Farmer John Actually Farms | Bronze, 2023 December | 1400 | The original problem had $$$a_i$$$ multiplied by $$$h_i$$$ after each day instead of addition. The intended solution was using logs with real numbers. However, we noticed that there can be floating point rounding issues, so I changed the problem to addition and slapped on a permutation $$$t$$$ to make it seem more original. |
| 4 | Milk Exchange (Bronze) | Bronze, 2024 February | 1200 | I don't remember how this problem came to be. |
| 5 | Milk Exchange (Gold) | Gold, 2024 February | 2200 | Was discussing and whining about preparing the bronze problem with sum, and he came up with this buff. Initially we both couldn't solve it so we enlisted omeganot's assistance. |
| 6 | Maximizing Productivity | Bronze, 2024 February | 1100 | I don't know why I proposed this problem. Nowadays, the standards I set for myself would forbid me from proposing this. Note that there was absolutely no reason for queries to exist — asking for the minimum time for each $$$V$$$ from $$$1$$$ to $$$N$$$ suffices. I think I wanted to make it seem more original, lol. |
| 7 | Logical Moos | Bronze, 2024 US Open | 1600 | The inspiration for this problem came from Truths (CALICO Spring 2022 Contest) where the samples were just a bunch of bitwise characters between ones and zeroes. I stared at this for a while and wondered: what happens if I remove "()" and "!" and made it not an annoying DP problem... |
| 8 | Farmer John's Favorite Permutation | Bronze, 2024 US Open | 1600 | I just thought of removing elements from both the front and back of the array, and came up with this problem. When solving it, I found the solution to be super nice. It is one of the "accidentally setting a good problem" moments of all time. |
| 9 | Farmer John's Cheese Block | Bronze, 2024 December | 1000 | I don't actually like this problem, and I don't know why it got chosen. Initially, the problem was phrased as placing a floating box in a dark room, shining a flashlight on one side, and counting the number of lit squares on the other side. Unfortunately, this goes against how physics works. We needed something concrete. You know what's concrete... Bricks. You know what can easily be carved... Cheese. |
| 10 | Cowdependence | Gold, December 2024 | 2100 | I proposed this problem before the 2023-2024 season, and it went unused for the entire season, so I forgot about this problem. I originally proposed it for silver since it technically only really required binary search and two pointers :D |
| 11 | Interstellar Intervals | Gold, December 2024 | 2300 | This problem went through a long journey. First, it was based on a problem proposal based on Geometry Dash by sum that was proposed for Codeforces Round 965 (Div. 2). Essentially, the solution of that problem required DP on positions with the same parity since intervals had to be even length, but it was quite boring, so I tried to modify it in many ways. After some extensive discussion, satyam343 modified the problem to its current state. At first, went in reserves for a potential D1C. However when I presented the problem to Benq for testing, he solved it in .3 seconds. Then, satyam343 said it's no longer Div. 1 quality... After that, I shipped the problem to USACO. Also, the name of this problem was due to my HSR addiction. |
| 12 | Farmer John's Favorite Operation | Silver, January 2025 | 1600 | I misread Calendars (mBIT November 2020) while doing a virtual contest with some friends and came up with this. By the way, it was surprising that both o1-mini and DeepSeek R1 failed to solve the problem during testing. |
| 13 | Cow Checkups (Bronze) | Bronze, January 2025 | 1200 | Originally proposed for a d2B but wasn't up to quality. The idea was maximizing the number of indices such that $$$a_i = i$$$ after reversing one subarray. Of course, satyam343 would end up rejecting it. Then I asked Proof_by_QED if I could propose for USACO Bronze and he agreed. When preparing, we found a very similar problem so we decided to modify it. Instead of $$$a_i = i$$$, we could just give another array $$$b$$$ and ask for $$$a_i = b_i$$$. Genius! sum would end up struggling to prepare good test cases so instead of asking for maximum number of indices we just asked for all possible reversals. |
| 14 | Cow Checkups (Silver) | Silver, January 2025 | 1600 | When modifying the bronze problem, sum over all possible reversals came naturally. We then realized it can be solved in subquadratic, so that was cool. |
| 16 | Reflection | Bronze, February 2025 | 800 | Unable to make the problem more interesting :( |
| 17 | The Best Lineup | Silver, February 2025 | 1400 | Originally a Div.2 B / Div.4 E / Bronze division candidate. The idea of the problem is mainly by Proof_by_QED. Lilypad and I just testsolved and tweaked the operation a bit. I formalized the problem into the current statement and prepared it. I liked this problem, though I don't think it belonged in silver. I think it is too easy, but somehow the other two silver problems in the contest are even easier... By the way, both o3-mini high and deepseek R1 failed to solve it. This proves that is still possible to set problems that AI can brick. It just has to be high quality though :p |
| 18 | The Best Subsequence | Gold, February 2025 | 2300 | I was high when I proposed this problem with only a $$$\mathcal{O}(N^2)$$$ solution. Luckily it is a certain LGM that reviewed the problem and came up with a subquadratic solution. |
| 19 | It's Mooin' Time III | Bronze, Open 2025 | 1200 | I tried to modify It's Mooin' Time II while in the shower. |
| 20 | Election Queries | Gold, Open 2025 | 2100 | Probably one of my favorite problems that I've ever set. This problem was originally Problem D in Codeforces Round 979 (Div. 2), but as you probably read in the Round Timeline, we burned through quite a bit of D replacements... This problem was D'''''' btw, if you can keep track. Anyways, it wasn't used because we were worried about it being a tad too difficult and too much implementation (codeforces participants can't handle writing more than 50 lines of code before whining), so I thought it was perfect for USACO. Difficulty wise, I thought it was definitely on the easy side of gold, but I was surprised to see the other two problems even easier... |
Honorable Mentions
| # | Problem | Contest | Difficulty | Comments |
|---|---|---|---|---|
| 1 | Bessie's Birthday Cake | CodeTON Round 8 (Div. 1+2) | 1300 | I proposed this problem for USACO bronze just before the 2023-2024 season. However, it wasn't selected for any contests for the entire season. I liked this problem, and I didn't want this problem to sit in the USACO backend database for an entire year, so I proposed it for codeforces. Later, Benq would tell me that he didn't think it was a good fit for USACO. |
| 2 | Farm Game | CodeTON Round 8 (Div. 1+2) | 2300 | I proposed this for 2024 Open Gold Contest, but wasn't selected :( I still think it's one of my best problems to date. womp womp for USACO. Thanks to sum for extensively discussing the problem with me and solving it in the end. |
| 3 | Determine Winning Islands In Race | CF Round 965 (Div. 2) | 2100 | Was originally proposed for USACO Bronze. I think I may have misjudged the difficulty by just a little. |
I accidentally copied a CodeChef problem.
I was just made aware by satyam343 that 1996A - Ноги somehow COINCIDES EXACTLY with FARMLEGS.
I had zero idea this problem even existed before right now. I even thought satyam343 was trolling and thought this problem was only published after my contest. It wasn't until I looked at submission dates that I noticed the problem was created more than three months ago... My problem was based on a mixture of middle-school word problems and me casually thinking of USACO cows.
Regarding how even the constraints are exactly the same: The constraints were initially $$$t \leq 10^5$$$ and $$$n \leq 2 \cdot 10^5$$$, but a tester did $$$O(tn)$$$ and still passed all test cases. Obviously, this is hackable, so we have to either decide to add a third test case with all tests being $$$2 \cdot 10^5$$$ or make $$$O(tn)$$$ comfortably pass. We didn't want to blow up queue even more, so we resorted to the latter option.
Anyways, this is way too funny, so I have to make a blog. This is also even more ironic since I advertised a CodeChef contest in the comments :skull:
sum and I are overjoyed to welcome you to participate in Codeforces Round 962 (Div. 3) on 26.07.2024 17:35 (Московское время). This contest is the last stop on our mission to problemset for every division. We hope you've been enjoying our stuff so far!
The round will be hosted by rules of educational rounds (extended ICPC). Thus, solutions will be judged on preliminary tests during the round, and after the round, it will be a 12-hour phase of open hacks. After open hacks all accepted solutions will be rejudged on successful hacks.
You will be given 7 problems and 2 hours and 15 minutes to solve them.
Note that the penalty for each wrong submission in this round is 10 minutes.
Remember that only the trusted participants of the third division will be included in the official standings table. As it is written by link, this is a compulsory measure for combating unsporting behavior. To qualify as a trusted participant of the third division, you must:
Regardless of whether you are a trusted participant of the third division or not, if your rating is less than 1600, then the round will be rated for you.
We would like to orz the following individuals for making the contest possible:
Vladosiya for the quality coordination.
Benq and satyam343 for overseeing the creation of this contest.
Yam, omeganot, TyroWhizz, awesomeguy856, 18o3, Sokol080808, Phi-001, milind0110, trash-can, Proof_by_QED, carnation13, JuicyGrape, Pa_sha, Qualified, Prady, ntarsis30, waidenf, Non-origination, Orange905, AceKnight7, ETL for testing the contest and providing valuable feedback.
Thank you for reading and we hope you have a fun and educational interstellar adventure :3
Problem Credits: cry
Analysis: cry
Problem Credits: sum
Analysis: cry
Problem Credits: cry
Analysis: cry
Problem Credits: sum
Analysis: cry
Problem Credits: cry
Analysis: cry
Problem Credits: sum
Analysis: cry
Problem Credits: cry
Analysis: cry, awesomeguy856
Problem Credits: sum
Analysis: cry
Problem Credits: satyam343
Analysis: cry
Problem Credits: cry, satyam343
Analysis: sum, satyam343, Dominater069
Problem Credits: cry
Analysis: cry
Problem Credits: cry, sum, satyam343
Analysis: sum
Problem Credits: cry, sum, satyam343
Analysis: sum
sum and I are very delighted, ecstatic, enchanted, euphoric, excited, exultant, jubilant, overjoyed, and proud to invite you to participate in Codeforces Round 952 (Div. 4), which will start on Jun/11/2024 17:35 (Moscow time). There will be $$$8$$$ problems, with one split into two subtasks, to be solved in $$$2.5$$$ hours.
As usual, I have to copy and paste the following...
The format of the event will be identical to Div. 3 rounds:
We urge participants whose rating is 1400+ not to register new accounts for the purpose of narcissism but to take part unofficially. Please do not spoil the contest for the official participants.
Only trusted participants of the fourth division will be included in the official standings table. This is a forced measure for combating unsporting behavior. To qualify as a trusted participant of the fourth division, you must:
Regardless of whether you are a trusted participant of the fourth division or not, if your rating is less than 1400 (or you are a newcomer/unrated), then the round will be rated for you.
We want to express overwhelming gratitude to the following individuals for making the contest possible:
Vladosiya and mesanu for coordinating the contest and reviewing the problems.
Dominater069, omeganot, Phi-001, flamestorm, nika-skybytska, willy108, ScarletS, mark, yuan-shen, Proof_by_QED, htetgm, buffering, TheYashB, haochenkang, ETL, natalina, MC3297, and lcsc0 for testing the round.
MikeMirzayanov for the usual.
We suggest reading all of the problems as we have put mucho effort into all of them. Best of luck, mis amigos!
UPD: Editorial
This was our first time setting a Div.4 contest. We sincerely hope you enjoyed the problems!
Problem Credits: cry
Analysis: cry
Problem Credits: cry
Analysis: cry
Problem Credits: sum
Analysis: cry
Problem Credits: cry
Analysis: cry
Problem Credits: cry
Analysis: cry
Problem Credits: cry, sum
Analysis: cry, sum
Problem Credits: cry
Analysis: cry
Problem Credits: sum
Analysis: sum
Problem Credits: sum
Analysis: sum