ESP32-S3 Bench Guide
ESP32‑S3 N16R8 벤치 가이드: 실시간 핀아웃, 강의, 시뮬레이터 및 벤치 로그
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기A collection of formalized statements of conjectures in Lean.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
A collection of formalised statements of conjectures in
Lean, using
mathlib.
Join our channel on the leanprover Zulip
While there is a growing corpus of formalised theorems including proofs, there
is a lack of open conjectures where only the statement has been formalised. This
would be useful for a few reasons. It could
• Become a great benchmark for automated theorem provers and automated
formalisation tools.
• Help clarify the precise meaning of conjectures through formalisation.
• Encourage the expansion of mathlib by highlighting needed definitions.README 전문 보기 ↗A collection of formalised statements of conjectures in Lean, using mathlib.
Explore the docs: Formal Conjectures Documentation
Join our channel on the leanprover Zulip
While there is a growing corpus of formalised theorems including proofs, there is a lack of open conjectures where only the statement has been formalised. This would be useful for a few reasons. It could
mathlib by highlighting needed definitions.It is our hope that this initiative will form the seed of a much richer dataset of formalised conjectures.
Formalizing mathematical statements without proofs is inherently challenging. Subtle inaccuracies can arise where the formal statement might not perfectly capture the nuances of the original conjecture. To mitigate this issue, we will rely on careful human review of contributions, and plan to periodically leverage AlphaProof to help identify potential misformalisations.
Contributions are most welcome — consider adding (or even just opening an issue describing) your favourite conjecture. See CONTRIBUTING.md for the full contribution guide, including ways to contribute, the step-by-step process, file structure conventions, attribute usage, and style guidelines.
This is a Lean 4 project managed with lake and a dependency mathlib. You
first need to
install elan, lake, lean and if you want vscode
and then run
lake exe cache get
lake build
The directory structure is organised by the type of sources of the conjectures. There are two special directories:
FormalConjecturesUtil contains utilities like the
category attribute, the
question attribute and some
linters.FormalConjecturesForMathlib contains code potentially suitable to be upstreamed to
mathlib. Here we follow
mathlib's directory structure.For details on the @[category], @[formal_proof], @[AMS], @[question] attributes
that statements in this repository use, see
CONTRIBUTING.md.
This repo will track the monthly tagged releases of mathlib (which correspond to Lean releases), rather than tracking mathlib master.
To minimize friction when adding problem statements that need definitions that
are not yet in mathlib, such definitions can be added to the FormalConjecturesForMathlib
directory. This ensures that the addition of these problems to
formal-conjectures is not locked to the mathlib release cadence.
When lean-toolchain is updated on main, a GitHub Actions workflow
automatically adds a git tag of the form v4.{X}.{Y}, following mathlib's
tagging convention.
Stable benchmark snapshots are tagged using the format
bench-v{N}-lean4.{X}.{Y}, where:
v{N} (Benchmark version): Identifies the set of problems included in
the benchmark. The benchmark version is bumped whenever problems are added,
removed, or when misformalizations are corrected.lean4.{X}.{Y} (Lean version): Identifies the Lean 4 toolchain
version used for that snapshot.Tags are immutable: fixes to misformalizations are never patched into an existing
benchmark version but instead go into v{N+1}.
If your work has used formal-conjectures, please consider citing it via
@misc{FormalConjectures,
author = {{The Formal Conjectures Authors}},
title = {{T}he {F}ormal {C}onjectures {R}epository},
year = {2025},
url = {https://github.com/google-deepmind/formal-conjectures},
}
@article{FormalConjecturesPaper,
authors = {Firsching, Moritz and Lezeau, Paul and Mercuri, Salvatore
and Horv{\'a}th, Mikl{\'o}s Z and Dillies, Ya{\"e}l and S{\"o}nne, Calle and Wieser, Eric and
Zhang, Fred and Hubert, Thomas and Ag{\"u}era y Arcas, Blaise and Kohli, Pushmeet},
title = {{F}ormal {C}onjectures: {A}n {O}pen and {E}volving {B}enchmark for {V}erified {D}iscovery in {M}athematics},
year = {2026},
url = {https://arxiv.org/abs/2605.13171v1},
}
Copyright 2025 The Formal Conjectures Authors. All software is licensed under the Apache License, Version 2.0 (Apache 2.0); you may not use this file except in compliance with the Apache 2.0 license. You may obtain a copy of the Apache 2.0 license at: https://www.apache.org/licenses/LICENSE-2.0
All other materials are licensed under the Creative Commons Attribution 4.0 International License (CC-BY). You may obtain a copy of the CC-BY license at: https://creativecommons.org/licenses/by/4.0/legalcode.
The content may be based on third party sources and may in some cases include third party content. The original source for each conjecture is indicated by a URL within the source file. Third party content may be subject to different licensing requirements. In particular:
Unless required by applicable law or agreed to in writing, all software and materials distributed here under the Apache 2.0 or CC-BY license are distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the licenses for the specific language governing permissions and limitations under those licenses.
This is not an official Google product.