Article
Version 2
This version is not peer-reviewed
Solving NP-Complete Problems Efficiently
Version 1
: Received: 22 August 2024 / Approved: 22 August 2024 / Online: 22 August 2024 (11:00:00 CEST)
Version 2 : Received: 7 September 2024 / Approved: 12 September 2024 / Online: 13 September 2024 (05:21:18 CEST)
Version 2 : Received: 7 September 2024 / Approved: 12 September 2024 / Online: 13 September 2024 (05:21:18 CEST)
How to cite: Vega, F. Solving NP-Complete Problems Efficiently. Preprints 2024, 2024081631. https://doi.org/10.20944/preprints202408.1631.v2 Vega, F. Solving NP-Complete Problems Efficiently. Preprints 2024, 2024081631. https://doi.org/10.20944/preprints202408.1631.v2
Abstract
The P versus NP problem is a fundamental question in computer science. It asks whether problems whose solutions can be quickly verified can also be quickly solved. Here, "quickly" refers to computational time that grows proportionally to the size of the input (polynomial time). While the problem's roots trace back to a 1955 letter from John Nash, its formalization is attributed to Stephen Cook and Leonid Levin. Despite extensive research, a definitive answer remains elusive. Closely tied to this is the concept of NP-completeness. If a single NP-complete problem could be solved efficiently, it would imply that all problems in NP can be solved efficiently, proving that P equals NP. This work posits that MONOTONE ONE-IN-THREE 3SAT, a notoriously difficult NP-complete problem, can be solved efficiently, thereby establishing the equivalence of P and NP.
Keywords
complexity classes; Boolean formula; graph; completeness; polynomial time
Subject
Computer Science and Mathematics, Data Structures, Algorithms and Complexity
Copyright: This is an open access article distributed under the Creative Commons Attribution License which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.
Comments (0)
We encourage comments and feedback from a broad range of readers. See criteria for comments and our Diversity statement.
Leave a public commentSend a private comment to the author(s)
* All users must log in before leaving a comment