# P versus NP problem

Open problem in computer science:If the answer to a problem is easy to check, is the problem itself easy to solve?(more open problems in computer science) |

**Lua error in package.lua at line 80: module 'strict' not found.**

The **P versus NP problem** is a major unsolved problem in computer science. Informally speaking, it asks whether every problem whose solution can be quickly verified by a computer can also be quickly solved by a computer. It was essentially first mentioned in a 1956 letter written by Kurt Gödel to John von Neumann. Gödel asked whether a certain NP-complete problem could be solved in quadratic or linear time.^{[2]} The precise statement of the P versus NP problem was introduced in 1971 by Stephen Cook in his seminal paper "The complexity of theorem proving procedures"^{[3]} and is considered by many to be the most important open problem in the field.^{[4]} It is one of the seven Millennium Prize Problems selected by the Clay Mathematics Institute to carry a US$1,000,000 prize for the first correct solution.

The informal term *quickly*, used above, means the existence of an algorithm for the task that runs in polynomial time. The general class of questions for which some algorithm can provide an answer in polynomial time is called "class **P**" or just "**P**". For some questions, there is no known way to find an answer quickly, but if one is provided with information showing what the answer is, it is possible to verify the answer quickly. The class of questions for which an answer can be *verified* in polynomial time is called **NP, which** stands for "nondeterministic polynomial time."

Consider the subset sum problem, an example of a problem that is easy to verify, but whose answer may be difficult to compute. Given a set of integers, does some nonempty subset of them sum to 0? For instance, does a subset of the set {−2, −3, 15, 14, 7, −10} add up to 0? The answer "yes, because the subset {−2, −3, −10, 15} adds up to zero" can be quickly verified with three additions. There is no known algorithm to find such a subset in polynomial time (there is one, however, in exponential time, which consists of 2^{n}-n-1 tries), but such an algorithm exists if **P** = **NP**; hence this problem is in **NP** (quickly checkable) but not necessarily in **P** (quickly solvable).

An answer to the **P** = **NP** question would determine whether problems that can be verified in polynomial time, like the subset-sum problem, can also be solved in polynomial time. If it turned out that **P** ≠ **NP**, it would mean that there are problems in **NP** (such as **NP**-complete problems) that are harder to compute than to verify: they could not be solved in polynomial time, but the answer could be verified in polynomial time.

Aside from being an important problem in computational theory, a proof either way would have profound implications for mathematics, cryptography, algorithm research, artificial intelligence, game theory, multimedia processing, philosophy, economics and many other fields.

## Contents

- 1 Context
- 2 NP-complete
- 3 Harder problems
- 4 Problems in NP not known to be in P or NP-complete
- 5 Does P mean "easy"?
- 6 Reasons to believe P ≠ NP
- 7 Consequences of solution
- 8 Results about difficulty of proof
- 9 Claimed solutions
- 10 Logical characterizations
- 11 Polynomial-time algorithms
- 12 Formal definitions
- 13 Popular culture
- 14 See also
- 15 Notes
- 16 References
- 17 Further reading
- 18 External links

## Context

The relation between the complexity classes **P** and **NP** is studied in computational complexity theory, the part of the theory of computation dealing with the resources required during computation to solve a given problem. The most common resources are time (how many steps it takes to solve a problem) and space (how much memory it takes to solve a problem).

In such analysis, a model of the computer for which time must be analyzed is required. Typically such models assume that the computer is *deterministic* (given the computer's present state and any inputs, there is only one possible action that the computer might take) and *sequential* (it performs actions one after the other).

In this theory, the class **P** consists of all those *decision problems* (defined below) that can be solved on a deterministic sequential machine in an amount of time that is polynomial in the size of the input; the class **NP** consists of all those decision problems whose positive solutions can be verified in polynomial time given the right information, or equivalently, whose solution can be found in polynomial time on a non-deterministic machine.^{[5]} Clearly, **P** ⊆ **NP**. Arguably the biggest open question in theoretical computer science concerns the relationship between those two classes:

- Is
**P**equal to**NP**?

In a 2002 poll of 100 researchers, 61 believed the answer to be no, 9 believed the answer is yes, and 22 were unsure; 8 believed the question may be independent of the currently accepted axioms and therefore is impossible to prove or disprove.^{[6]}

In 2012, 10 years later, the same poll was repeated. The number of researchers who answered was 151: 126 (83%) believed the answer to be no, 12 (9%) believed the answer is yes, 5 (3%) believed the question may be independent of the currently accepted axioms and therefore is impossible to prove or disprove, 8 (5%) said either don't know or don't care or don't want the answer to be yes nor the problem to be resolved.^{[7]}

## NP-complete

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

To attack the **P** = **NP** question, the concept of **NP**-completeness is very useful. **NP**-complete problems are a set of problems to each of which any other **NP**-problem can be reduced in polynomial time, and whose solution may still be verified in polynomial time. That is, any **NP** problem can be transformed into any of the **NP**-complete problems. Informally, an **NP**-complete problem is an **NP** problem that is at least as "tough" as any other problem in **NP**.

**NP**-hard problems are those at least as hard as **NP** problems, i.e., all **NP** problems can be reduced (in polynomial time) to them. **NP**-hard problems need not be in **NP**, i.e., they need not have solutions verifiable in polynomial time.

For instance, the Boolean satisfiability problem is **NP**-complete by the Cook–Levin theorem, so *any* instance of *any* problem in **NP** can be transformed mechanically into an instance of the Boolean satisfiability problem in polynomial time. The Boolean satisfiability problem is one of many such **NP**-complete problems. If any **NP**-complete problem is in **P**, then it would follow that **P** = **NP**. Unfortunately, many important problems have been shown to be **NP**-complete, and not a single fast algorithm for any of them is known.

Based on the definition alone it is not obvious that **NP**-complete problems exist; however, a trivial and contrived **NP**-complete problem can be formulated as follows: given a description of a Turing machine M guaranteed to halt in polynomial time, does there exist a polynomial-size input that M will accept?^{[8]} It is in **NP** because (given an input) it is simple to check whether M accepts the input by simulating M; it is **NP**-complete because the verifier for any particular instance of a problem in **NP** can be encoded as a polynomial-time machine M that takes the solution to be verified as input. Then the question of whether the instance is a yes or no instance is determined by whether a valid input exists.

The first natural problem proven to be **NP**-complete was the Boolean satisfiability problem. As noted above, this is the Cook–Levin theorem; its proof that satisfiability is **NP**-complete contains technical details about Turing machines as they relate to the definition of **NP**. However, after this problem was proved to be **NP**-complete, proof by reduction provided a simpler way to show that many other problems are also **NP**-complete, including the subset-sum problem discussed earlier. Thus, a vast class of seemingly unrelated problems are all reducible to one another, and are in a sense "the same problem".

## Harder problems

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Although it is unknown whether **P** = **NP**, problems outside of **P** are known. A number of succinct problems (problems that operate not on normal input, but on a computational description of the input) are known to be **EXPTIME**-complete. Because it can be shown that **P** ≠ **EXPTIME**, these problems are outside **P**, and so require more than polynomial time. In fact, by the time hierarchy theorem, they cannot be solved in significantly less than exponential time. Examples include finding a perfect strategy for chess (on an *N* × *N* board)^{[9]} and some other board games.^{[10]}

The problem of deciding the truth of a statement in Presburger arithmetic requires even more time. Fischer and Rabin proved in 1974 that every algorithm that decides the truth of Presburger statements has a runtime of at least for some constant *c*. Here, *n* is the length of the Presburger statement. Hence, the problem is known to need more than exponential run time. Even more difficult are the undecidable problems, such as the halting problem. They cannot be completely solved by any algorithm, in the sense that for any particular algorithm there is at least one input for which that algorithm will not produce the right answer; it will either produce the wrong answer, finish without giving a conclusive answer, or otherwise run forever without producing any answer at all.

## Problems in NP not known to be in P or NP-complete

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

It was shown by Ladner that if **P** ≠ **NP** then there exist problems in **NP** that are neither in **P** nor **NP**-complete.^{[1]} Such problems are called **NP**-intermediate problems. The graph isomorphism problem, the discrete logarithm problem and the integer factorization problem are examples of problems believed to be **NP**-intermediate. They are some of the very few **NP** problems not known to be in **P** or to be **NP**-complete.

The graph isomorphism problem is the computational problem of determining whether two finite graphs are isomorphic. An important unsolved problem in complexity theory is whether the graph isomorphism problem is in **P**, **NP**-complete, or **NP**-intermediate. The answer is not known, but it is believed that the problem is at least not **NP**-complete.^{[11]} If graph isomorphism is **NP**-complete, the polynomial time hierarchy collapses to its second level.^{[12]}^{[13]} Since it is widely believed that the polynomial hierarchy does not collapse to any finite level, it is believed that graph isomorphism is not **NP**-complete. The best algorithm for this problem, due to Laszlo Babai and Eugene Luks has run time 2^{O(√nlog(n))} for graphs with *n* vertices.

The integer factorization problem is the computational problem of determining the prime factorization of a given integer. Phrased as a decision problem, it is the problem of deciding whether the input has a factor less than *k*. No efficient integer factorization algorithm is known, and this fact forms the basis of several modern cryptographic systems, such as the RSA algorithm. The integer factorization problem is in **NP** and in **co-NP** (and even in **UP** and **co-UP**^{[14]}). If the problem is **NP**-complete, the polynomial time hierarchy will collapse to its first level (i.e., **NP** = **co-NP**). The best known algorithm for integer factorization is the general number field sieve, which takes expected time

to factor an *n*-bit integer. However, the best known quantum algorithm for this problem, Shor's algorithm, does run in polynomial time. Unfortunately, this fact doesn't say much about where the problem lies with respect to non-quantum complexity classes.

## Does P mean "easy"?

All of the above discussion has assumed that **P** means "easy" and "not in **P**" means "hard", an assumption known as *Cobham's thesis*. It is a common and reasonably accurate assumption in complexity theory; however, it has some caveats.

First, it is not always true in practice. A theoretical polynomial algorithm may have extremely large constant factors or exponents thus rendering it impractical. On the other hand, even if a problem is shown to be **NP**-complete, and even if **P** ≠ **NP**, there may still be effective approaches to tackling the problem in practice. There are algorithms for many **NP**-complete problems, such as the knapsack problem, the traveling salesman problem and the Boolean satisfiability problem, that can solve to optimality many real-world instances in reasonable time. The empirical average-case complexity (time vs. problem size) of such algorithms can be surprisingly low. An example is the simplex algorithm in linear programming, which works surprisingly well in practice; despite having exponential worst-case time complexity it runs on par with the best known polynomial-time algorithms.^{[16]}

Second, there are types of computations which do not conform to the Turing machine model on which **P** and **NP** are defined, such as quantum computation and randomized algorithms.

## Reasons to believe P ≠ NP

According to polls,^{[6]}^{[17]} many computer scientists believe that **P** ≠ **NP**. A key reason for this belief is that after decades of studying these problems no one has been able to find a polynomial-time algorithm for any of more than 3000 important known **NP**-complete problems (see List of **NP**-complete problems). These algorithms were sought long before the concept of **NP**-completeness was even defined (Karp's 21 **NP**-complete problems, among the first found, were all well-known existing problems at the time they were shown to be **NP**-complete). Furthermore, the result **P** = **NP** would imply many other startling results that are currently believed to be false, such as **NP** = **co-NP** and **P** = **PH**.

It is also intuitively argued that the existence of problems that are hard to solve but for which the solutions are easy to verify matches real-world experience.^{[18]}

<templatestyles src="Template:Blockquote/styles.css" />

If

P=NP, then the world would be a profoundly different place than we usually assume it to be. There would be no special value in "creative leaps," no fundamental gap between solving a problem and recognizing the solution once it's found.

On the other hand, some researchers believe that there is overconfidence in believing **P** ≠ **NP** and that researchers should explore proofs of **P** = **NP** as well. For example, in 2002 these statements were made:^{[6]}

<templatestyles src="Template:Blockquote/styles.css" />

The main argument in favor of

P≠NPis the total lack of fundamental progress in the area of exhaustive search. This is, in my opinion, a very weak argument. The space of algorithms is very large and we are only at the beginning of its exploration. [...] The resolution of Fermat's Last Theorem also shows that very simple questions may be settled only by very deep theories.

<templatestyles src="Template:Blockquote/styles.css" />

Being attached to a speculation is not a good guide to research planning. One should always try both directions of every problem. Prejudice has caused famous mathematicians to fail to solve famous problems whose solution was opposite to their expectations, even though they had developed all the methods required.

## Consequences of solution

One of the reasons the problem attracts so much attention is the consequences of the answer. Either direction of resolution would advance theory enormously, and perhaps have huge practical consequences as well.

### P = NP

A proof that **P** = **NP** could have stunning practical consequences, if the proof leads to efficient methods for solving some of the important problems in **NP**. It is also possible that a proof would not lead directly to efficient methods, perhaps if the proof is non-constructive, or the size of the bounding polynomial is too big to be efficient in practice. The consequences, both positive and negative, arise since various **NP**-complete problems are fundamental in many fields.

Cryptography, for example, relies on certain problems being difficult. A constructive and efficient solution^{[Note 1]} to an **NP**-complete problem such as 3-SAT would break most existing cryptosystems including:

- public-key cryptography,
^{[19]}a foundation for many modern security applications such as secure financial transactions over the Internet; and - symmetric ciphers such as AES or 3DES,
^{[20]}used for the encryption of communications data. - one-way functions used in cryptographic hashing. The problem of finding a pre-image that hashes to a given value
^{[21]}must be difficult to be useful, and ideally should require exponential time. However, if P=NP, then finding a pre-image M can be done in polynomial time, through reduction to SAT.^{[22]}

These would need to be modified or replaced by information-theoretically secure solutions not inherently based on P-NP equivalence.

On the other hand, there are enormous positive consequences that would follow from rendering tractable many currently mathematically intractable problems. For instance, many problems in operations research are **NP**-complete, such as some types of integer programming and the travelling salesman problem. Efficient solutions to these problems would have enormous implications for logistics. Many other important problems, such as some problems in protein structure prediction, are also **NP**-complete;^{[23]} if these problems were efficiently solvable it could spur considerable advances in life sciences and biotechnology.

But such changes may pale in significance compared to the revolution an efficient method for solving **NP**-complete problems would cause in mathematics itself. Gödel, in his early thoughts on computational complexity, noted that a mechanical method that could solve any problem would revolutionize mathematics:^{[24]}^{[25]}

<templatestyles src="Template:Blockquote/styles.css" />

If there really were a machine with φ(n) ∼ k ⋅ n (or even ∼ k ⋅ n

^{2}), this would have consequences of the greatest importance. Namely, it would obviously mean that in spite of the undecidability of the Entscheidungsproblem, the mental work of a mathematician concerning Yes-or-No questions could be completely replaced by a machine. After all, one would simply have to choose the natural number n so large that when the machine does not deliver a result, it makes no sense to think more about the problem.

Similarly, Stephen Cook says^{[26]}

<templatestyles src="Template:Blockquote/styles.css" />

...it would transform mathematics by allowing a computer to find a formal proof of any theorem which has a proof of a reasonable length, since formal proofs can easily be recognized in polynomial time. Example problems may well include all of the CMI prize problems.

Research mathematicians spend their careers trying to prove theorems, and some proofs have taken decades or even centuries to find after problems have been stated—for instance, Fermat's Last Theorem took over three centuries to prove. A method that is guaranteed to find proofs to theorems, should one exist of a "reasonable" size, would essentially end this struggle.

Donald Knuth has stated that he has come to believe that P = NP, but is reserved about the impact of a possible proof:^{[27]}

<templatestyles src="Template:Blockquote/styles.css" />

[...] I don't believe that the equality P = N P will turn out to be helpful even if it is proved, because such a proof will almost surely be nonconstructive.

### P ≠ NP

A proof that showed that **P** ≠ **NP** would lack the practical computational benefits of a proof that **P** = **NP**, but would nevertheless represent a very significant advance in computational complexity theory and provide guidance for future research. It would allow one to show in a formal way that many common problems cannot be solved efficiently, so that the attention of researchers can be focused on partial solutions or solutions to other problems. Due to widespread belief in **P** ≠ **NP**, much of this focusing of research has already taken place.^{[28]}

Also **P** ≠ **NP** still leaves open the average-case complexity of hard problems in **NP**. For example, it is possible that SAT requires exponential time in the worst case, but that almost all randomly selected instances of it are efficiently solvable. Russell Impagliazzo has described five hypothetical "worlds" that could result from different possible resolutions to the average-case complexity question.^{[29]} These range from "Algorithmica", where **P** = **NP** and problems like SAT can be solved efficiently in all instances, to "Cryptomania", where **P** ≠ **NP** and generating hard instances of problems outside **P** is easy, with three intermediate possibilities reflecting different possible distributions of difficulty over instances of **NP-hard** problems. The "world" where **P** ≠ **NP** but all problems in **NP** are tractable in the average case is called "Heuristica" in the paper. A Princeton University workshop in 2009 studied the status of the five worlds.^{[30]}

## Results about difficulty of proof

Although the **P** = **NP**? problem itself remains open despite a million-dollar prize and a huge amount of dedicated research, efforts to solve the problem have led to several new techniques. In particular, some of the most fruitful research related to the **P** = **NP** problem has been in showing that existing proof techniques are not powerful enough to answer the question, thus suggesting that novel technical approaches are required.

As additional evidence for the difficulty of the problem, essentially all known proof techniques in computational complexity theory fall into one of the following classifications, each of which is known to be insufficient to prove that **P** ≠ **NP**:

Classification | Definition |
---|---|

Relativizing proofs | Imagine a world where every algorithm is allowed to make queries to some fixed subroutine called an oracle, and the running time of the oracle is not counted against the running time of the algorithm. Most proofs (especially classical ones) apply uniformly in a world with oracles regardless of what the oracle does. These proofs are called relativizing. In 1975, Baker, Gill, and Solovay showed that P = NP with respect to some oracles, while P ≠ NP for other oracles.^{[31]} Since relativizing proofs can only prove statements that are uniformly true with respect to all possible oracles, this showed that relativizing techniques cannot resolve P = NP. |

Natural proofs | In 1993, Alexander Razborov and Steven Rudich defined a general class of proof techniques for circuit complexity lower bounds, called natural proofs. At the time all previously known circuit lower bounds were natural, and circuit complexity was considered a very promising approach for resolving P = NP. However, Razborov and Rudich showed that, if one-way functions exist, then no natural proof method can distinguish between P and NP. Although one-way functions have never been formally proven to exist, most mathematicians believe that they do, and a proof or disproof of their existence would be a much stronger statement than the quantification of P relative to NP. Thus it is unlikely that natural proofs alone can resolve P = NP. |

Algebrizing proofs | After the Baker-Gill-Solovay result, new non-relativizing proof techniques were successfully used to prove that IP = PSPACE. However, in 2008, Scott Aaronson and Avi Wigderson showed that the main technical tool used in the IP = PSPACE proof, known as arithmetization, was also insufficient to resolve P = NP.^{[32]} |

These barriers are another reason why **NP**-complete problems are useful: if a polynomial-time algorithm can be demonstrated for an **NP**-complete problem, this would solve the **P** = **NP** problem in a way not excluded by the above results.

These barriers have also led some computer scientists to suggest that the **P** versus **NP** problem may be independent of standard axiom systems like ZFC (cannot be proved or disproved within them). The interpretation of an independence result could be that either no polynomial-time algorithm exists for any **NP**-complete problem, and such a proof cannot be constructed in (e.g.) ZFC, or that polynomial-time algorithms for **NP**-complete problems may exist, but it's impossible to prove in ZFC that such algorithms are correct.^{[33]} However, if it can be shown, using techniques of the sort that are currently known to be applicable, that the problem cannot be decided even with much weaker assumptions extending the Peano axioms (PA) for integer arithmetic, then there would necessarily exist nearly-polynomial-time algorithms for every problem in **NP**.^{[34]} Therefore, if one believes (as most complexity theorists do) that not all problems in **NP** have efficient algorithms, it would follow that proofs of independence using those techniques cannot be possible. Additionally, this result implies that proving independence from PA or ZFC using currently known techniques is no easier than proving the existence of efficient algorithms for all problems in **NP**.

## Claimed solutions

While the **P** versus **NP** problem is generally considered unsolved,^{[35]} many amateur and some professional researchers have claimed solutions. Gerhard J. Woeginger has a comprehensive list.^{[36]} An August 2010 claim of proof that **P** ≠ **NP**, by Vinay Deolalikar, a researcher at HP Labs, Palo Alto, received heavy Internet and press attention after being initially described as "seem[ing] to be a relatively serious attempt" by two leading specialists.^{[37]} The proof has been reviewed publicly by academics,^{[38]}^{[39]} and Neil Immerman, an expert in the field, had pointed out two possibly fatal errors in the proof.^{[40]} In September 2010, Deolalikar was reported to be working on a detailed expansion of his attempted proof.^{[41]} However, opinions expressed by several notable theoretical computer scientists indicate that the attempted proof is neither correct nor a significant advancement in the understanding of the problem.^{[42]} This assessment prompted a May 2013 *The New Yorker* article to call the proof attempt "thoroughly discredited."^{[43]}

## Logical characterizations

The **P** = **NP** problem can be restated in terms of expressible certain classes of logical statements, as a result of work in descriptive complexity.

Consider all languages of finite structures with a fixed signature including a linear order relation. Then, all such languages in **P** can be expressed in first-order logic with the addition of a suitable least fixed-point combinator. Effectively, this, in combination with the order, allows the definition of recursive functions. As long as the signature contains at least one predicate or function in addition to the distinguished order relation, so that the amount of space taken to store such finite structures is actually polynomial in the number of elements in the structure, this precisely characterizes **P**.

Similarly, **NP** is the set of languages expressible in existential second-order logic—that is, second-order logic restricted to exclude universal quantification over relations, functions, and subsets. The languages in the polynomial hierarchy, **PH**, correspond to all of second-order logic. Thus, the question "is **P** a proper subset of **NP**" can be reformulated as "is existential second-order logic able to describe languages (of finite linearly ordered structures with nontrivial signature) that first-order logic with least fixed point cannot?".^{[44]} The word "existential" can even be dropped from the previous characterization, since **P** = **NP** if and only if **P** = **PH** (as the former would establish that **NP** = **co-NP**, which in turn implies that **NP** = **PH**).

## Polynomial-time algorithms

No algorithm for any **NP**-complete problem is known to run in polynomial time. However, there are algorithms for **NP**-complete problems with the property that if **P** = **NP**, then the algorithm runs in polynomial time (although with enormous constants, making the algorithm impractical). The following algorithm, due to Levin (without any citation), is such an example below. It correctly accepts the **NP**-complete language SUBSET-SUM. It runs in polynomial time if and only if **P** = **NP**:

// Algorithm that accepts theNP-complete language SUBSET-SUM. // // this is a polynomial-time algorithm if and only ifP=NP. // // "Polynomial-time" means it returns "yes" in polynomial time when // the answer should be "yes", and runs forever when it is "no". // // Input: S = a finite set of integers // Output: "yes" if any subset of S adds up to 0. // Runs forever with no output otherwise. // Note: "Program number P" is the program obtained by // writing the integer P in binary, then // considering that string of bits to be a // program. Every possible program can be // generated this way, though most do nothing // because of syntax errors.

FOR N = 1...∞ FOR P = 1...N Run program number P for N steps with input S IF the program outputs a list of distinct integers AND the integers are all in S AND the integers sum to 0

THEN OUTPUT "yes" and HALT

If, and only if, **P** = **NP**, then this is a polynomial-time algorithm accepting an **NP**-complete language. "Accepting" means it gives "yes" answers in polynomial time, but is allowed to run forever when the answer is "no" (also known as a *semi-algorithm*).

This algorithm is enormously impractical, even if **P** = **NP**. If the shortest program that can solve SUBSET-SUM in polynomial time is *b* bits long, the above algorithm will try at least 2^{b}−1 other programs first.

## Formal definitions

### P and NP

Conceptually speaking, a *decision problem* is a problem that takes as input some string *w* over an alphabet Σ, and outputs "yes" or "no". If there is an algorithm (say a Turing machine, or a computer program with unbounded memory) that can produce the correct answer for any input string of length *n* in at most *cn ^{k}* steps, where

*k*and

*c*are constants independent of the input string, then we say that the problem can be solved in

*polynomial time*and we place it in the class

**P**. Formally,

**P**is defined as the set of all languages that can be decided by a deterministic polynomial-time Turing machine. That is,

where

and a deterministic polynomial-time Turing machine is a deterministic Turing machine *M* that satisfies the following two conditions:

*M*halts on all input*w*and- there exists such that , where
*O*refers to the big O notation and

**NP** can be defined similarly using nondeterministic Turing machines (the traditional way). However, a modern approach to define **NP** is to use the concept of *certificate* and *verifier*. Formally, **NP** is defined as the set of languages over a finite alphabet that have a verifier that runs in polynomial time, where the notion of "verifier" is defined as follows.

Let *L* be a language over a finite alphabet, Σ.

*L* ∈ **NP** if, and only if, there exists a binary relation and a positive integer *k* such that the following two conditions are satisfied:

- For all , such that (
*x*,*y*) ∈*R*and ; and - the language over is decidable by a Turing machine in polynomial time.

A Turing machine that decides *L _{R}* is called a

*verifier*for

*L*and a

*y*such that (

*x*,

*y*) ∈

*R*is called a

*certificate of membership*of

*x*in

*L*.

In general, a verifier does not have to be polynomial-time. However, for *L* to be in **NP**, there must be a verifier that runs in polynomial time.

#### Example

Let

Clearly, the question of whether a given *x* is a composite is equivalent to the question of whether *x* is a member of COMPOSITE. It can be shown that COMPOSITE ∈ **NP** by verifying that it satisfies the above definition (if we identify natural numbers with their binary representations).

COMPOSITE also happens to be in **P**.^{[45]}^{[46]}

### NP-completeness

There are many equivalent ways of describing **NP**-completeness.

Let *L* be a language over a finite alphabet Σ.

*L* is **NP**-complete if, and only if, the following two conditions are satisfied:

*L*∈**NP**; and- any
*L′*in**NP**is polynomial-time-reducible to*L*(written as ), where if, and only if, the following two conditions are satisfied:- There exists
*f*: Σ* → Σ* such that for all*w*in Σ* we have: ; and - there exists a polynomial-time Turing machine that halts with
*f*(*w*) on its tape on any input*w*.

- There exists

## Popular culture

- The film
*Travelling Salesman*, by director Timothy Lanzone, is the story of four mathematicians hired by the US government to solve the P vs. NP problem.^{[47]}

## See also

- Game complexity
- Unique games conjecture
- Unsolved problems in computer science
- Unsolved problems in mathematics

## Notes

- ↑ Exactly how efficient a solution must be to pose a threat to cryptography depends on the details. A solution of or better and a reasonable constant term would be disastrous. On the other hand, a solution that is or worse in almost all cases would not pose an immediate practical danger.

## References

- ↑
^{1.0}^{1.1}R. E. Ladner "On the structure of polynomial time reducibility," Journal of the ACM, 22, pp. 151–171, 1975. Corollary 1.1. ACM site. - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑ Sipser, Michael:
*Introduction to the Theory of Computation, Second Edition, International Edition*, page 270. Thomson Course Technology, 2006. Definition 7.19 and Theorem 7.20. - ↑
^{6.0}^{6.1}^{6.2}**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑ Lance Fortnow. Computational Complexity Blog: Complexity Class of the Week: Factoring. 13 September 2002.
- ↑ Pisinger, D. 2003. "Where are the hard knapsack problems?" Technical Report 2003/08, Department of Computer Science, University of Copenhagen, Copenhagen, Denmark
- ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.**, point 9. - ↑ See
**Lua error in package.lua at line 80: module 'strict' not found.**for a reduction of factoring to SAT. A 512 bit factoring problem (8400 MIPS-years when factored) translates to a SAT problem of 63,652 variables and 406,860 clauses. - ↑ See, for example,
**Lua error in package.lua at line 80: module 'strict' not found.**in which an instance of DES is encoded as a SAT problem with 10336 variables and 61935 clauses. A 3DES problem instance would be about 3 times this size. - ↑ Find a message
*M*that when hashed by the function*H()*gives a digest*h*, or*H(M)=h* - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑ History of this letter and its translation from
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.**From pages 359–376 of Optimization Stories, M. Grötschel (editor), a special issue of ¨ Documenta Mathematica, published in August 2012 and distributed to attendees at the 21st International Symposium on Mathematical Programming in Berlin. - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑ R. Impagliazzo, "A personal view of average-case complexity," sct, pp.134, 10th Annual Structure in Complexity Theory Conference (SCT'95), 1995
- ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑ T. P. Baker, J. Gill, R. Solovay.
*Relativizations of the*. SIAM Journal on Computing, 4(4): 431–442 (1975)**P**=?**NP**Question - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.**. - ↑
**Lua error in package.lua at line 80: module 'strict' not found.**. - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑ Science News, "Crowdsourcing peer review"
- ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑ Gödel’s Lost Letter and P=NP, Update on Deolalikar’s Proof that P≠NP
- ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑ Elvira Mayordomo. "P versus NP"
*Monografías de la Real Academia de Ciencias de Zaragoza***26**: 57–68 (2004). - ↑
**Lua error in package.lua at line 80: module 'strict' not found.** - ↑ AKS primality test
- ↑
**Lua error in package.lua at line 80: module 'strict' not found.**

## Further reading

**Lua error in package.lua at line 80: module 'strict' not found.****Lua error in package.lua at line 80: module 'strict' not found.****Lua error in package.lua at line 80: module 'strict' not found.**Online drafts**Lua error in package.lua at line 80: module 'strict' not found.****Lua error in package.lua at line 80: module 'strict' not found.****Lua error in package.lua at line 80: module 'strict' not found.****Lua error in package.lua at line 80: module 'strict' not found.****Lua error in package.lua at line 80: module 'strict' not found.**- Fortnow, Lance.
*The Golden Ticket: P, NP, and the Search for the Impossible*ISBN 9780691156491. Princeton University Press. Princeton, NJ (2013)

## External links

- The Clay Mathematics Institute Millennium Prize Problems
- The Clay Math Institute Official Problem Description PDF (118 KB)
- Gerhard J. Woeginger. The P-versus-NP page. A list of links to a number of purported solutions to the problem. Some of these links state that P equals NP, some of them state the opposite. It is probable that all these alleged solutions are incorrect.
- Scott Aaronson 's Shtetl Optimized blog: Reasons to believe, a list of justifications for the belief that P ≠ NP