Secure Multiparty Delegated Quantum Computation: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
This [https://arxiv.org/abs/1606.09200 example protocol] achieves the functionality of [[Secure Client- Server Delegated Computation|Delegation Quantum Computation]] to a server for multiple Clients with the guarantee that Server is unknown of any Clients' inputs/outpts/computation. This protocol is an extension of [[Prepare-and-Send Universal Blind Quantum Computation]] in the multiparty setting.
This [https://arxiv.org/abs/1606.09200 example protocol] achieves the functionality of [[Secure Client- Server Delegated Computation|Delegation Quantum Computation]] to a server for multiple Clients with the guarantee that Server is unknown of any Clients' inputs/outputs/computation. This protocol is an extension of [[Prepare-and-Send Universal Blind Quantum Computation]] in the multiparty setting.
 
'''Tags:''' [[:Category:Multi Party Protocols|Multi Party (three)]], [[:Category:Quantum Functionality|Quantum Functionality]], [[:Category:Universal Task|Universal Task]]
[[Category:Multi Party Protocols]] [[Category:Quantum Functionality]][[Category:Universal Task]]
 


==Assumptions==
==Assumptions==
Line 14: Line 18:
* '''Input qubits:''' For the input qubit states, each client one-time pads their qubit and uses secret sharing schemes to share the secret values with other clients. The honest behaviour for every client is enforced via the given protocol. The server then one-time pads them and measures the one-time padded qubits and announces the measurement values.
* '''Input qubits:''' For the input qubit states, each client one-time pads their qubit and uses secret sharing schemes to share the secret values with other clients. The honest behaviour for every client is enforced via the given protocol. The server then one-time pads them and measures the one-time padded qubits and announces the measurement values.
* '''Non-output and non-input qubits:''' The clients send the qubits in random phases allowed in MBQC. The server then one-time pads them and announces the measurement values.
* '''Non-output and non-input qubits:''' The clients send the qubits in random phases allowed in MBQC. The server then one-time pads them and announces the measurement values.
* '''Output qubits:''' The server prepares them in the </math>|+\rangle</math> state.
* '''Output qubits:''' The server prepares them in the <math>|+\rangle</math> state.
* '''Graph state:''' The server entangles the qubits to a brickwork state.
* '''Graph state:''' The server entangles the qubits to a brickwork state.


Write, autoreview, editor, reviewer
3,129

edits

Navigation menu