Editing Gottesman and Chuang Quantum Digital Signature
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
The [https://arxiv.org/abs/quant-ph/0105032 example protocol] achieves the functionality of [[Quantum Digital Signature|(Quantum) Digital Signatures (QDS)]] allowing the exchange of classical messages from sender to multiple recipients, with a guarantee that the signature has come from a genuine sender. | The [https://arxiv.org/abs/quant-ph/0105032 example protocol] achieves the functionality of [[Quantum Digital Signature|(Quantum) Digital Signatures (QDS)]] allowing the exchange of classical messages from sender to multiple recipients, with a guarantee that the signature has come from a genuine sender, using quantum memory. It comes with all the [[Quantum Digital Signature#Properties|Properties]] of QDS. Such protocols require parties to store quantum states for comparison at a later stage. <br/><br/> | ||
'''Tags:''' [[:Category:Multi Party Protocols|Multi Party (three)]], [[:Category:Quantum Enhanced Classical Functionality|Quantum Enhanced Classical Functionality]], [[:Category:Specific Task|Specific Task]], [[Quantum Digital Signature]], [[Prepare and Measure Quantum Digital Signature]], [[Measurement Device Independent Quantum Digital Signature (MDI-QDS)]] | '''Tags:''' [[:Category:Multi Party Protocols|Multi Party (three)]], [[:Category:Quantum Enhanced Classical Functionality|Quantum Enhanced Classical Functionality]], [[:Category:Specific Task|Specific Task]], [[Quantum Digital Signature]], [[Prepare and Measure Quantum Digital Signature]], [[Measurement Device Independent Quantum Digital Signature (MDI-QDS)]] | ||
[[Category:Multi Party Protocols]][[Category:Quantum Enhanced Classical Functionality]][[Category:Specific Task]] | [[Category:Multi Party Protocols]][[Category:Quantum Enhanced Classical Functionality]][[Category:Specific Task]] | ||
Line 5: | Line 5: | ||
==Assumptions== | ==Assumptions== | ||
* Perfect devices and channels have been assumed | * Perfect devices and channels have been assumed | ||
* It has been assumed that all recipients have received correct and identical copies of | * It has been assumed that all recipients have received correct and identical copies of Sender's public key (explained later) | ||
* All participants know, the map which takes private keys to public keys, threshold value of acceptance (<math>c_1</math>) and threshold value for rejection (<math>c_2</math>) | * All participants know, the map which takes private keys to public keys, threshold value of acceptance (<math>c_1</math>) and threshold value for rejection (<math>c_2</math>) | ||
==Outline== | ==Outline== | ||
Gottesman and Chuang signature scheme is based on quantum [https://en.wikipedia.org/wiki/One-way_function one way functions], which take classical bit string as input and give quantum states as output. Quantum Digital Signature (QDS) protocols can be divided into two stages: the distribution stage, where quantum signals (public keys) are sent to all recipients, and the messaging stage, where classical messages are signed, sent and verified. Here, we take the case of three parties, one sender (referred to as seller) and two receivers (buyer and verifier) sharing a one bit message. | |||
*''' | *'''Distribution:''' For each message bit (say 0 and 1) sender selects a classical bit string. This is chosen to be her private key. Using the quantum one way function, Sender generates the output of the quantum one-way function/map, which (the output) she calls her public key and as assumed, distributes them to each recipient, for each message bit. In the end of this step, each recipient has two public keys, one for message bit 0 and one for message bit 1. | ||
*'''Messaging:''' Sender sends her message bit with the associated private key. The Receiver performs the map on the private key (quantum one way function takes the sent private key as input) and the compares the output thus generated with the public key received in the previous stage. If the number of unmatched bits are below rejection threshold, the message is declared valid, else invalid. If the number of unmatched bits is below acceptance threshold, it is declared transferable, else not transferable. | |||
* ''' | |||
==Properties== | ==Properties== | ||
*Sending m bits message uses O(m) quantum bits for each recipient. | |||
*The public keys can be used only once. | *The public keys can be used only once. | ||
*Only limited (T) distribution of public keys should be allowed, such that <math>T < L/n</math>, where quantum public key is an 'n' qubit state. | *Only limited (T) distribution of public keys should be allowed, such that <math>T < L/n</math>, where quantum public key is an 'n' qubit state and L is the length of classical bit string. | ||
* Unlike some classical information-theoretic (unconditional security) schemes which require secure anonymous broadcast channel or noisy channel, which are hard to achieve resources, the quantum scheme provides information-theoretic security by only demanding plausible quantum channels and modest interaction between parties involved. | * Unlike some classical information-theoretic (unconditional security) schemes which require secure anonymous broadcast channel or noisy channel, which are hard to achieve resources, the quantum scheme provides information-theoretic security by only demanding plausible quantum channels and modest interaction between parties involved. | ||
* The scheme is secure against forgery if <math>(1-\delta^2)(M-G)>c_2M</math>, where | * The scheme is secure against forgery if <math>(1-\delta^2)(M-G)>c_2M</math>, where <math>\delta</math> depends on the public keys and hence the quantum one way functions, M is the number of private keys chosen for each message bit, <math>G=2^{-(L-Tn)}2M</math>, and c_2 is the threshold for rejection. | ||
== Requirements == | == Requirements == | ||
*'''Network Stage:''' [[Category: Quantum Memory Network Stage]][[:Category: Quantum Memory Network Stage|Quantum Memory]] | *'''Network Stage:''' [[Category: Quantum Memory Network Stage]][[:Category: Quantum Memory Network Stage|Quantum Memory]] | ||
* ''' | *'''Relevant Network Parameters:''' | ||
*'''Benchmark values:''' No experimental implementation using qubits. See [[Gottesman and Chuang Quantum Digital Signature#Further Information|Experimental Papers (1)]] for implementation using coherent states. | *'''Benchmark values:''' No experimental implementation using qubits. See [[Gottesman and Chuang Quantum Digital Signature#Further Information|Experimental Papers (1)]] for implementation using coherent states. | ||
== | ==Pseudocode== | ||
==Further Information== | ==Further Information== | ||
This protocol was the first ever scheme designed for Quantum Digital Signatures. Due to unavailability of quantum memory at the current stage, this scheme has not seen enough experimental implementations, yet variations of the same without the need of quantum memory has some progress such as [[Prepare and Measure Quantum Digital Signature]], [[Measurement Device Independent Quantum Digital Signature (MDI-QDS)]], etc.. | This protocol was the first ever scheme designed for Quantum Digital Signatures. Due to unavailability of quantum memory at the current stage, this scheme has not seen enough experimental implementations, yet variations of the same without the need of quantum memory has some progress such as [[Prepare and Measure Quantum Digital Signature]], [[Measurement Device Independent Quantum Digital Signature (MDI-QDS)]], etc.. | ||
Following is the list of few more protocols with similar requirement (quantum memory) but small variations. | Following is the list of a few more protocols with similar requirement (quantum memory) but small variations. | ||
'''Theoretical Papers''' | |||
# [https://arxiv.org/abs/quant-ph/0105032 GC (2001)] | # [https://arxiv.org/abs/quant-ph/0105032 GC-QDS (2001)] uses [[quantum one way function]] f(); Private keys: classical input x, Public keys: quantum output f(x). | ||
##'''Requires''' quantum memory, quantum one way function, authenticated quantum and classical channels, [[SWAP Test]] (universal quantum computer). | |||
##Security: [[Information-theoretic]] | |||
#[https://arxiv.org/abs/quant-ph/0601130 ACJ (2006)] discusses coherent states comparison with a QDS scheme outlined in the last section. | #[https://arxiv.org/abs/quant-ph/0601130 ACJ (2006)] discusses coherent states comparison with a QDS scheme outlined in the last section. | ||
##Protocol uses the same protocol as (2) but replaces qubits with [[coherent states]], thus replacing SWAP-Test with [[Coherent State Comparison]]. Additionally, it also requires quantum memory, authenticated quantum and classical channels, [[multiports]]. | ##Protocol uses the same protocol as (2) but replaces qubits with [[coherent states]], thus replacing SWAP-Test with [[Coherent State Comparison]]. Additionally, it also requires quantum memory, authenticated quantum and classical channels, [[multiports]]. | ||
##Security: [[Information-theoretic]] | ##Security: [[Information-theoretic]] | ||
#[https://www.sciencedirect.com/science/article/pii/S0030402617308069 | #[https://www.sciencedirect.com/science/article/pii/S0030402617308069 SWZY (2017)] Discusses an attack and suggests corrections on existing QDS scheme using single qubit rotations. Protocol uses rotation, qubits, [[one-way hash function]]; Private keys: angle of rotation, Public keys: string of rotated quantum states. | ||
##'''Requires''' [[random number generator]], [[one-way hash function]], quantum memory, key distribution. | ##'''Requires''' [[random number generator]], [[one-way hash function]], quantum memory, key distribution. | ||
##'''Security:''' [[Computational]] | ##'''Security:''' [[Computational]] | ||
'''Experimental Papers''' | |||
#[https://www.nature.com/articles/ncomms2172 | #[https://www.nature.com/articles/ncomms2172 CCDAJB (2012)] uses phase encoded coherent states, [[coherent state comparison]] | ||
##Loss from multiport=7.5 dB, Length of the key= <math>10^6</math> | ##Loss from multiport=7.5 dB, Length of the key= <math>10^6</math> | ||
<div style='text-align: right;'>''*contributed by Shraddha Singh''</div> | <div style='text-align: right;'>''*contributed by Shraddha Singh''</div> |