Papers › MiniF2F: a cross-system benchmark for formal Olympiad-level mathematics

MiniF2F: a cross-system benchmark for formal Olympiad-level mathematics

31 Aug 2021ICLR 2022 4arXiv:2109.00110archive 2025-07-28

Kunhao Zheng, Jesse Michael Han, Stanislas Polu

We present miniF2F, a dataset of formal Olympiad-level mathematics problems statements intended to provide a unified cross-system benchmark for neural theorem proving. The miniF2F benchmark currently targets Metamath, Lean, Isabelle (partially) and HOL Light (partially) and consists of 488 problem statements drawn from the AIME, AMC, and the International Mathematical Olympiad (IMO), as well as material from high-school and undergraduate mathematics courses. We report baseline results using GPT-f, a neural theorem prover based on GPT-3 and provide an analysis of its performance. We intend for miniF2F to be a community-driven effort and hope that our benchmark will help spur advances in neural theorem proving.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

The archive's official repository (openai/minif2f) was not harvested; the 3 samples below come from 1 community repository.

Syntology 3 code samples harvested from 1 repository linked to this paper: 3 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: community (archive-listed): 3 samples from 1 repository, 3 ran (0 with no instrument failure; 3 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

openai/minif2f officialmentioned in papermentioned on GitHubSyntology: not harvested report
facebookresearch/minif2f mentioned on GitHubSyntology: 3 samples, 3 ran (3 instrument-failed) · 0 unverified report
rah4927/lean-dojo-mew mentioned on GitHubMITSyntology: not harvested report
yangky11/minif2f-lean4 mentioned on GitHubMITSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

3 samples harvested: 3 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran · our draft was wrong

Licence: 0 of the 3 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from facebookresearch/minif2f. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

facebookresearch/minif2f community (archive-listed) 3 samples, 3 ran (3 instrument-failed) · 0 unverified
reserved_notation_check lean/scripts/lint_style.py ran · our draft was wrong MIT (permissive) · 6cd16db0c1444e10 · report fixture: returned list · level recorded 2026-09-22
set_option_check lean/scripts/lint_style.py ran · our draft was wrong MIT (permissive) · 26a8582dd6f1cac7 · report fixture: signature lines:list/1/str, path:str/0/str · returned list · level recorded 2026-09-22
small_alpha_vrachy_check lean/scripts/lint_style.py ran · our draft was wrong MIT (permissive) · 9a6fcf24bb8c49fb · report fixture: signature lines:list/1/str, path:str/0/str · returned list · level recorded 2026-09-22

Tasks

Automated Theorem Proving

Datasets

Introduced by this paper, per the archive.

MiniF2F

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Automated Theorem Proving miniF2F-test Lean GPT-f ITP Lean #18 of 29 Archive leaderboard report
Automated Theorem Proving miniF2F-test Lean GPT-f Pass@1 24.6 #18 of 29 Archive leaderboard report
Automated Theorem Proving miniF2F-test Lean GPT-f Pass@32 29.2 #18 of 29 Archive leaderboard report
Automated Theorem Proving miniF2F-test Lean GPT-f cumulative 29.2 #18 of 29 Archive leaderboard report
Automated Theorem Proving miniF2F-test Lean tidy ITP Lean #26 of 29 Archive leaderboard report
Automated Theorem Proving miniF2F-test Lean tidy Pass@1 18 #26 of 29 Archive leaderboard report
Automated Theorem Proving miniF2F-test Lean tidy cumulative 18 #26 of 29 Archive leaderboard report
Automated Theorem Proving miniF2F-test Metamath GPT-f ITP Metamath #29 of 29 Archive leaderboard report
Automated Theorem Proving miniF2F-test Metamath GPT-f Pass@1 1.3 #29 of 29 Archive leaderboard report
Automated Theorem Proving miniF2F-test Metamath GPT-f cumulative 1.6 #29 of 29 Archive leaderboard report
Automated Theorem Proving miniF2F-valid Lean GPT-f Pass@1 23.9 #1 of 10 Archive leaderboard report
Automated Theorem Proving miniF2F-valid Lean GPT-f Pass@8 29.3 #1 of 10 Archive leaderboard report
Automated Theorem Proving miniF2F-valid Metamath GPT-f Pass@1 1 #2 of 10 Archive leaderboard report
Automated Theorem Proving miniF2F-valid Metamath GPT-f Pass@8 2 #2 of 10 Archive leaderboard report
Automated Theorem Proving miniF2F-valid Lean tidy Pass@1 16.8 #7 of 10 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

AdamAttentionAttention DropoutBPECosine AnnealingDense ConnectionsDropoutGPT-3Layer NormalizationLinear LayerLinear Warmup With Cosine AnnealingMulti-Head AttentionResidual ConnectionSoftmaxWeight Decay

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections