dorsal/arxiv
View SchemaThe Trouble with Quantum Bit Commitment
| Authors | Dominic Mayers |
|---|---|
| Categories | |
| ArXiv ID | quant-ph/9603015 |
| URL | https://arxiv.org/abs/quant-ph/9603015 |
Abstract
In a recent paper, Lo and Chau explain how to break a family of quantum bit commitment schemes, and they claim that their attack applies to the 1993 protocol of Brassard, Cr\'epeau, Jozsa and Langlois (BCJL). The intuition behind their attack is correct, and indeed they expose a weakness common to all proposals of a certain kind, but the BCJL protocol does not fall in this category. Nevertheless, it is true that the BCJL protocol is insecure, but the required attack and proof are more subtle. Here we provide the first complete proof that the BCJL protocol is insecure.
{
"annotation_id": "f9afd225-83f9-4ed1-b77b-3adab13fd1fe",
"date_created": "2026-03-02T18:02:37.374000Z",
"date_modified": "2026-03-02T18:02:37.374000Z",
"file_hash": "aca290a10b58852650fc7aa55f13c6a101e63b10cfb5903fd7ae1a2a2d100fad",
"private": false,
"record": {
"abstract": "In a recent paper, Lo and Chau explain how to break a family of quantum bit\ncommitment schemes, and they claim that their attack applies to the 1993\nprotocol of Brassard, Cr\\\u0027epeau, Jozsa and Langlois (BCJL). The intuition\nbehind their attack is correct, and indeed they expose a weakness common to all\nproposals of a certain kind, but the BCJL protocol does not fall in this\ncategory. Nevertheless, it is true that the BCJL protocol is insecure, but the\nrequired attack and proof are more subtle. Here we provide the first complete\nproof that the BCJL protocol is insecure.",
"arxiv_id": "quant-ph/9603015",
"authors": [
"Dominic Mayers"
],
"categories": [
"quant-ph"
],
"title": "The Trouble with Quantum Bit Commitment",
"url": "https://arxiv.org/abs/quant-ph/9603015"
},
"schema_id": "dorsal/arxiv",
"source": {
"execution_id": "c1e01da1-2b64-44f0-a265-22265b7f9648",
"id": "arXiv Dataset IDs",
"type": "Model",
"variant": "snapshot-2026-03-01",
"version": "0.1.0"
},
"user_id": 1000002
}