dorsal/arxiv
View SchemaQuantum bit string sealing
| Authors | Guang-Ping He |
|---|---|
| Categories | |
| ArXiv ID | quant-ph/0502091 |
| URL | https://arxiv.org/abs/quant-ph/0502091 |
| DOI | 10.1142/S0219749906002079 |
| Journal | International Journal of Quantum Information, 4, 677 (2006). |
Abstract
Though it was proven that secure quantum sealing of a single classical bit is impossible in principle, here we propose an unconditionally secure quantum sealing protocol which seals a classical bit string. Any reader can obtain each bit of the sealed string with an arbitrarily small error rate, while reading the string is detectable. The protocol is simple and easy to be implemented. The possibility of using this protocol to seal a single bit in practical is also discussed.
{
"annotation_id": "f7e4e34a-4be5-46d3-b172-de8ca8206e42",
"date_created": "2026-03-02T18:02:13.623000Z",
"date_modified": "2026-03-02T18:02:13.623000Z",
"file_hash": "a607f60de25733f1564ebdab1ea41d99c922af3d3563d0ff06c41d17a21d606c",
"private": false,
"record": {
"abstract": "Though it was proven that secure quantum sealing of a single classical bit is\nimpossible in principle, here we propose an unconditionally secure quantum\nsealing protocol which seals a classical bit string. Any reader can obtain each\nbit of the sealed string with an arbitrarily small error rate, while reading\nthe string is detectable. The protocol is simple and easy to be implemented.\nThe possibility of using this protocol to seal a single bit in practical is\nalso discussed.",
"arxiv_id": "quant-ph/0502091",
"authors": [
"Guang-Ping He"
],
"categories": [
"quant-ph"
],
"doi": "10.1142/S0219749906002079",
"journal_ref": "International Journal of Quantum Information, 4, 677 (2006).",
"title": "Quantum bit string sealing",
"url": "https://arxiv.org/abs/quant-ph/0502091"
},
"schema_id": "dorsal/arxiv",
"source": {
"execution_id": "114338dc-ebdc-4b5a-a456-11c482ddfe09",
"id": "arXiv Dataset IDs",
"type": "Model",
"variant": "snapshot-2026-03-01",
"version": "0.1.0"
},
"user_id": 1000002
}