
DI security4— basically, we play a nonlocal game on a random subset of the rounds, with the in-
formal goal of ensuring that the devices cannot both win the nonlocal game on those rounds with
high probability and still be able to usefully clone the resulting states. (Note, however, that our
results are not based on parallel self-testing theorems; rather, the only place we invoke self-testing
is to study a single protocol round, after which we separately derive a parallel-repetition theorem
to analyze the entire protocol. In particular, this means that in principle one could substitute the
self-testing argument with other methods for analyzing single protocol rounds.)
We provide a formal definition of uncloneable encryption with variable keys and its related
security criteria in Section 3.1. As indicated in the illustrative example above, the main difference
between our definition and that introduced by [BL20] is that the whole private key that was used
in the encryption needs to be stored, and there is a key release procedure that takes the private
key as input, uses additional private randomness, and outputs an independent decryption key
each time one is requested (here by independent we mean the additional private randomness is
independent for each decryption key). Additionally, since we work in the DI setting, our encryp-
tion procedure involves a small amount of interaction5to implement the “testing” step, and we
include an option to abort the procedure if this test fails. Such features are typically required in DI
cryptography protocols, which rely on rigidity properties of various interactive procedures (such
as non-local games, taking into account the need to check whether the game is won) to “test” if
the device behaviour is close to the ideal case, as mentioned above. For instance, such interaction
was also present in the [GMP23] scheme, which was DI under computational assumptions.6
Under those definitions, our main result regarding the achievability of DI uncloneable encryp-
tion with variable keys is stated in Theorem 14, and the scheme achieving this is described in
Scheme 1. Some additional notable features of our scheme are as follows:
• The uncloneable encryption scheme of [GMP23], which is device-independent with compu-
tational assumptions, allows for some noise in the devices, but their approach requires the
noise parameter to vanish in the limit of large message length n. In contrast, our protocol
tolerates a constant level of noise in the honest devices. (For the device-dependent unclone-
able encryption schemes, to our knowledge none of them have explicitly analyzed noise in
the devices, though it should be possible to modify some of the schemes to account for this.)
• Most DI cryptographic protocols that guarantee information theoretic security require that
there is no communication between the devices of different parties involved in the protocol.
Our security proof is based on the parallel repetition of a form of a non-local game; it was
4To see that the [BL20] scheme does not work if the state preparation is untrusted, observe that if the state prepared is
simply a classical record of the values (a,x)rather than the Wiesner states |ax⟩, then it is trivially insecure. If converted
to an entanglement-based protocol in which the client performs some choice of measurement xand obtains an output
a, observe that if the client’s measurements are untrusted, then the devices could just be implementing a completely
classical strategy in which for each round the output ais perfectly deterministic for each x, in which case all dishonest
parties will know the value of aonce given x. (If desired, this deterministic behaviour could be made undetectable by
any statistical checks involving only the frequency distribution of aand/or x, by instead making the value of afor each
xa function of some classical “hidden variable” Λ, a copy of which is held by all dishonest parties.)
5However, this interaction can potentially be removed if the client can impose some additional constraints on their
devices; we elaborate on this in Remark 7.
6We stress however that despite this interactive aspect, we do not assume the receiver has to be honest in our setup.
While a dishonest receiver could of course lie about the outputs of their devices, this poses no problems for a DI security
proof, because such behaviour can always be absorbed into the operations/measurements performed by the dishonest
party — this line of reasoning has been used in many previous works on cryptographic scenarios with some potentially
dishonest receiver (including uncloneable encryption) such as [FM18,GMP23,KT23]. (See also Remark 2later below.)
5