Localizing and excluding quantum information; or, how to share a quantum secret in spacetime release_b2h6ipgjvvdsvdffm32rhhhmuq

by Patrick Hayden, Alex May

Abstract

When can quantum information be localized to each of a collection of spacetime regions, while also excluded from another collection of regions? We answer this question by defining and analyzing the localize-exclude task, in which a quantum system must be localized to a collection of authorized regions while also being excluded from a set of unauthorized regions. This task is a spacetime analogue of quantum secret sharing, with authorized and unauthorized regions replacing authorized and unauthorized sets of parties. Our analysis yields the first quantum secret sharing scheme for arbitrary access structures for which the number of qubits required scales polynomially with the number of authorized sets. We also study a second related task called state-assembly, in which shares of a quantum system are requested at sets of spacetime points. We fully characterize the conditions under which both the localize-exclude and state-assembly tasks can be achieved, and give explicit protocols. Finally, we propose a cryptographic application of these tasks which we call party-independent transfer.
In application/xml+jats format

Published in Quantum by Verein zur Forderung des Open Access Publizierens in den Quantenwissenschaften
ISSN-L 2521-327X
Page(s) 196
Release Date 2019-10-24
Publisher Verein zur Forderung des Open Access Publizierens in den Quantenwissenschaften
Primary Language en (lookup)

Known Files and URLs

application/pdf  768.2 kB
sha1:7750194e568d5576bb23...
web.archive.org (webarchive)
quantum-journal.org (web)
Read Full Text
Type  article-journal
Stage   published
Date   2019-10-24
Container Metadata
Open Access Publication
In DOAJ
Not in ISSN ROAD
ISSN-L:  2521-327X
Fatcat Entry
Work Entity
grouping other versions (eg, pre-print) and variants of this release
Cite This Release
Fatcat Bits

State is "active". Revision:
15a925ab-5ef0-4960-8fd8-4eb1019f2b8c
As JSON object via API