Journal article
Practical blind quantum computation with parity quantum computing framework
- Abstract:
- Blind quantum computation (BQC) allows clients with limited quantum capabilities to delegate computational tasks to remote quantum servers while keeping the privacy of their data. However, existing BQC protocols often fail to balance resource consumption and practical feasibility, which is particularly significant in the noisy intermediate-scale quantum era. In this paper, we propose a practical BQC model based on the parity quantum computing framework. It requires the server to perform operations only on adjacent qubits and eliminates the need for additional SWAP gates when two-qubit gates should be applied to non-adjacent qubits, greatly facilitating the physical implementation on real quantum devices. Furthermore, we prove that the proposed BQC model ensures the privacy of client’s information and satisfies the property of verifiability which enables clients to identify dishonest servers. Finally, a detailed example is given and simulated on the IBM’s quantum platform to demonstrate its feasibility.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Publisher copy:
- 10.1088/2058-9565/ae54c5
Authors
+ National Natural Science Foundation of China
More from this funder
- Funder identifier:
- https://ror.org/01h0zpd94
- Grant:
- 12171044
- Publisher:
- IOP Publishing
- Journal:
- Quantum Science and Technology More from this journal
- Volume:
- 11
- Issue:
- 2
- Article number:
- 025033
- Publication date:
- 2026-03-31
- DOI:
- EISSN:
-
2058-9565
- ISSN:
-
2058-9565
- Language:
-
English
- Keywords:
- Pubs id:
-
2401440
- Local pid:
-
pubs:2401440
- Deposit date:
-
2026-04-21
- ARK identifier:
Terms of use
- Copyright holder:
- IOP Publishing Ltd
- Copyright date:
- 2026
- Rights statement:
- © 2026 IOP Publishing Ltd. All rights, including for text and data mining, AI training, and similar technologies, are reserved.
If you are the owner of this record, you can report an update to it here: Report update to this record