Coordination
Consensus
In the Byzantine setting the focus is often on detectable agreement.
Algorithms
Algorithm for quantum byzantine agreement
- constant expected number of rounds compared for the randomized (adaptive adversary)
- Assumptions:
- adaptive full information adversary
- failure models: Byzantine / crash faults
- States:
- Byzantine needs verifiable (can agree that secret can be recovered) secret sharing for random numbers
Improved Consensus in Quantum Networks
- Assumptions:
- adaptive full information adversary
- failure models: Byzantine / crash faults
- requires fewer Bell pairs by using some kind of gossip protocol
NB The arity of entanglement is still
Simulations / physical realization
Netsquid-based:
-
Resource-aware System Architectural Model for Implementation of QBA
Proposes specific circuit implementation for the Ben-Or's algorithm
Detectable Byzantine agreement (DBA)
NB Apparently, for DBA no one needs to maintain quantum state, hence the size and decoherence time of quantum memory are irrelevant.
Classical presentation is given in Detectable Byzantine Agreement Secure Against Faulty Majorities:
- Correctness all honest players commonly accept or reject the protocol. If all accept, then the protocol achieves broadcast
- Completeness if no player is corrupted, all accept
- Fairness if any honest player rejects, then the adversary gets no information about the sender's input
Further problem decomposition is presented in Detectable Byzantine Agreement Secure Against Faulty Majorities introducing
Detectable Precomputation:
- Correctness: all honest players commonly accept or reject the protocol. If all accept, then strong broadcast will be achievable
- Completeness if no player is corrupted, all accept
- Independence any honest player's input value need not be known
Protocols based on correlated lists
A Quantum solution to the Byzantine agreement problem
- for weak agreement (or detectable broadcast), where a single faulty player may force everyone to abort
- States: (Aharonov tri-partite qutrit states)
- N = 3, f = 1
Experimental demonstration of a quantum protocol for Byzantine agreement and liar detection
Explicitly says that the key is to construct secret and correlated lists
- Based on the list , , and that are correlated and are produced from 4-qubit entangled states
- States:
- N = 3, f = 1
Quantum detectable Byzantine agreement for distributed data trust management in blockchain:
- a lot of pairwise interaction among the lieutenants and the general
- States: , , (GHZ-like)
- N > f + 1
Quantum Byzantine Agreement for Any Number of Dishonest Parties
- trusted quantum source
- States: (multi-partite qudits)
- N > f + 1
- gives counterexamples for two other works (not listed here) to be incorrect
A Quantum Detectable Byzantine Agreement Protocol using only EPR pairs
- States: (EPR pairs)
- N > f + 1
Protocols based on quantum signatures
These are to a large degree also based on correlated lists):
Beating the fault-tolerance bound for byzantine agreement
- Recusrive algorithm, similar to the one in LSP
- Unlike LSP, signatures cannot be verified by all the parties
- N > 2 f
Simulations / physical realization
-
Beating the fault-tolerance bound for byzantine agreement
-
The algorithm is from the same paper
-
All the quantum part is done in a lab using "four-intensity decoy-state BB84 key generation process"
-
-
Noise-Aware Detectable Byzantine Agreement for Consensus-based Distributed Quantum Computing
- focus is on the epr algorithm (TODO: double check)
- filter batches of EPR-pairs testing fidelity and dropping those with the fidelity below the threshold
- noise-mitigation techniques
Other works
- Quantum Distributed Consensus: not quite a "consensus" as the outcome is _always random
Simulations / physical realization
-
Benchmarking of Quantum Protocols: evaluating the following algorithms with NetSquid:
- quantum coin (i.e., smth that can be emitted and later verified)
- anonymous qubit transmission via -state
- verifiable blind quantum computation
- quantum digital signature
Common sources of noise:
- noisy operations
- noisy memory
- noisy channels
They have implementation.