Proving Bounds for the Randomized Maxcut Approximation Algorithm in Lean4
Posted14 days agoActive10 days ago
abhamra.comResearchstory
informativepositive
Debate
20/100
Formal VerificationLean4Approximation Algorithms
Key topics
Formal Verification
Lean4
Approximation Algorithms
Discussion Activity
Light discussionFirst comment
4d
Peak period
2
96-102h
Avg / period
1.5
Key moments
- 01Story posted
Dec 20, 2025 at 8:16 AM EST
14 days ago
Step 01 - 02First comment
Dec 24, 2025 at 5:11 AM EST
4d after posting
Step 02 - 03Peak activity
2 comments in 96-102h
Hottest window of the conversation
Step 03 - 04Latest activity
Dec 24, 2025 at 12:10 PM EST
10 days ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Discussion (3 comments)
Showing 3 comments
sevensor
10 days ago
I’m interested by this recent development where people are using LLMs with Lean to prove things that haven’t been formalized yet. This seems like a really good fit for LLMs. They’re good at translating approximate language to formal language, they’re good at information retrieval, and any failures are mitigated by Lean itself. I haven’t tried it, but I imagine failure modes might be proving useless lemmas along the way, taking a needlessly roundabout approach, or inadvertently proving something different than what you set out to do.
bo1024
10 days ago
Nice!
I'd imagine that defining a cut as simply a partition of the vertices (rather than a subset of edges) may simplify things slightly.
vatsachak
10 days ago
Nice intro challenge
View full discussion on Hacker News
ID: 46335961Type: storyLast synced: 12/24/2025, 6:30:33 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.