Write, autoreview, editor, reviewer
3,129
edits
Line 4: | Line 4: | ||
== Outline == | == Outline == | ||
The general idea is that a classical Client gives instructions to a quantum Server to perform certain actions (quantum computation). Those actions lead to the Server having as output a single qubit, which is randomly chosen from within a set of | The general idea is that a classical Client gives instructions to a quantum Server to perform certain actions (quantum computation). Those actions lead to the Server having as output a single qubit, which is randomly chosen from within a set of chosen (by the Client) states. On the other hand, Client is supposed to know the classical description of the state. To achieve this task, the instructions/quantum computation the Client uses are based on a family of trapdoor, two regular, one-way functions with certain extra properties (see Properties and Definitions). Trapdoor one-way functions are hard to invert (e.g. for the Server) unless someone (the Client in this case) has some extra “trapdoor” information tk. Two-regular functions have two pre-images for every value in the range of the function. This extra information helps the Client classically reproduce the quantum computation to recover the classical description of the single qubit state, while it is still hard to classically reproduce for the Server. Simple modifications to the protocol could achieve other similar sets of states.<br/><br/> | ||
The protocol can be divided into two stages, Preimages Superposition, where Client instructs the Server to generate the superposition using one-way function and, Squeezing, where the Server is instructed by the Client to meausre the qubits and deliver the outcomes, which she (Client) would use to classically compute the value of r. | The protocol can be divided into two stages, Preimages Superposition, where Client instructs the Server to generate the superposition using one-way function and, Squeezing, where the Server is instructed by the Client to meausre the qubits and deliver the outcomes, which she (Client) would use to classically compute the value of r. | ||
*'''Preparation.''' The Client randomly selects a function with required properties, which is public (Server knows), but the trapdoor information needed to invert the function is known only to the Client. | *'''Preparation.''' The Client randomly selects a function with required properties, which is public (Server knows), but the trapdoor information needed to invert the function is known only to the Client. |