HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
aw31
openai-imo-2025-proofs
OPEN SOURCE2025–2025
aw31 / openai-imo-2025-proofs

openai-imo-2025-proofs

Discover this repository through its Hacker News conversations.

9Distinct people
10Mentions
0Explicit recommenders
481GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day10 dated mentions

Observed mentions: 2025-07-19 09:53:34 UTC to 2025-08-09 17:41:47 UTC.

0123452025-07-19 00:00:00 UTC to 2025-07-20 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 commentsJul 192025-07-20 00:00:00 UTC to 2025-07-21 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-07-21 00:00:00 UTC to 2025-07-22 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-07-22 00:00:00 UTC to 2025-07-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-23 00:00:00 UTC to 2025-07-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-24 00:00:00 UTC to 2025-07-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-25 00:00:00 UTC to 2025-07-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-26 00:00:00 UTC to 2025-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-27 00:00:00 UTC to 2025-07-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-28 00:00:00 UTC to 2025-07-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-29 00:00:00 UTC to 2025-07-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 292025-07-30 00:00:00 UTC to 2025-07-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-31 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-08-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-02 00:00:00 UTC to 2025-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-03 00:00:00 UTC to 2025-08-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-04 00:00:00 UTC to 2025-08-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-05 00:00:00 UTC to 2025-08-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-06 00:00:00 UTC to 2025-08-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-07 00:00:00 UTC to 2025-08-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-08 00:00:00 UTC to 2025-08-09 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-08-09 00:00:00 UTC to 2025-08-10 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 9

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 192025-07-19 00:00:00 UTC2025-07-20 00:00:00 UTC514
Jul 202025-07-20 00:00:00 UTC2025-07-21 00:00:00 UTC110
Jul 212025-07-21 00:00:00 UTC2025-07-22 00:00:00 UTC202
Jul 222025-07-22 00:00:00 UTC2025-07-23 00:00:00 UTC000
Jul 232025-07-23 00:00:00 UTC2025-07-24 00:00:00 UTC000
Jul 242025-07-24 00:00:00 UTC2025-07-25 00:00:00 UTC000
Jul 252025-07-25 00:00:00 UTC2025-07-26 00:00:00 UTC000
Jul 262025-07-26 00:00:00 UTC2025-07-27 00:00:00 UTC000
Jul 272025-07-27 00:00:00 UTC2025-07-28 00:00:00 UTC000
Jul 282025-07-28 00:00:00 UTC2025-07-29 00:00:00 UTC000
Jul 292025-07-29 00:00:00 UTC2025-07-30 00:00:00 UTC000
Jul 302025-07-30 00:00:00 UTC2025-07-31 00:00:00 UTC000
Jul 312025-07-31 00:00:00 UTC2025-08-01 00:00:00 UTC000
Aug 12025-08-01 00:00:00 UTC2025-08-02 00:00:00 UTC000
Aug 22025-08-02 00:00:00 UTC2025-08-03 00:00:00 UTC000
Aug 32025-08-03 00:00:00 UTC2025-08-04 00:00:00 UTC000
Aug 42025-08-04 00:00:00 UTC2025-08-05 00:00:00 UTC000
Aug 52025-08-05 00:00:00 UTC2025-08-06 00:00:00 UTC000
Aug 62025-08-06 00:00:00 UTC2025-08-07 00:00:00 UTC000
Aug 72025-08-07 00:00:00 UTC2025-08-08 00:00:00 UTC000
Aug 82025-08-08 00:00:00 UTC2025-08-09 00:00:00 UTC101
Aug 92025-08-09 00:00:00 UTC2025-08-10 00:00:00 UTC101

What Hacker News says

1 sources
One point that Karpathy has made in some of his videos is that using additional tokens in the prompt can facilitate computation. If you ask a transformer to do some basic math, it will be more likely to get the right answer (or at least a better approximation) with a more verbose prompt. To me, this backs up the use of more conversational language ("Please," etc.) when prompting. However, that seems to be contradicted by what was shown recently with the successful International Math Olympiad effort. Their prompts, such as https://github.com/aw31/openai-imo-2025-proofs/blob/main/pro... , were very terse. It's hard to tell where the prompt stops and the CoT response starts, in fact. So there is probably some interplay between the need for attention sinks and the use of step-by-step reasoning. It might not be too surprising if the latte
Read the rest
r works because it's an indirect way to optimize the former.
In How attention sinks keep language models stable

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.