Template:Confusing
In cryptography, a **commitment scheme** allows one to commit to a value while keeping it hidden, with the ability to reveal the committed value later. Commitments are used to bind a party to a value so that they cannot adapt to other messages in order to gain some kind of inappropriate advantage. They are important to a variety of cryptographic protocols including secure coin flipping, zerno-knowledge proofs, and secure computation.

Interactions in a commitment scheme take place in two phases:

- the
*commit phase*during which a value is chosen and specified - the
*reveal phase*during which the value is revealed and checked

In simple protocols, the commit phase consists of a single message from the sender to the receiver. This message is called *the commitment*. It is essential that the specific value chosen cannot be known by the receiver at that time (this is called the *hiding* property). A simple reveal phase would consist of a single message, *the opening*, from the sender to the receiver, followed by a check performed by the receiver. The value chosen during the commit phase must be the only one that the sender can compute and that validates during the reveal phase (this is called the *binding* property).

The concept of commitment schemes was first formalized by Gilles Brassard, David Chaum, and Claude Crepeau in 1988,^{[1]} but the concept was used without being treated formally prior to that.^{[2]}^{[3]} The notion of commitments appeared earliest in works by Manuel Blum,^{[4]} Shimon Even,^{[5]} and Shamir et al. ^{[6]} The terminology seems to have been originated by Blum^{[3]}, although commitment schemes can be interchangeably called **bit commitment schemes**—sometimes reserved for the special case where the committed value is a binary bit.

## ApplicationsEdit

### Coin flippingEdit

Suppose Alice and Bob want to resolve some dilemma via coin flipping. If they are physically in the same place, a typical procedure might be:

- Alice "calls" the coin flip
- Bob flips the coin
- If Alice's call is correct, she wins, otherwise Bob wins

If they are not in the same place, this procedure is faulty. Alice would have to trust Bob's report of how the coin flip turned out, whereas Bob knows what result is more desirable for him. Using commitments, a similar procedure is:

- Alice "calls" the coin flip and tells Bob only a
*commitment*to her call, - Bob flips the coin and reports the result,
- Alice reveals what she committed to
- If Alice's revelation matches the coin result Bob reported, Alice wins

For Bob to be able to skew the results to his favor, he must be able to understand the call hidden in Alice's commitment. If the commitment scheme is a good one, Bob cannot skew the results. Similarly, Alice cannot affect the result if she cannot change the value she commits to.^{[2]}^{[4]}

A way to visualize a commitment scheme is to think of the sender as putting the value in a locked box, and giving the box to the receiver. The value in the box is hidden from the receiver, who cannot open the lock themselves. Since the receiver has the box, the value inside cannot be changed—merely revealed if the sender chooses to give them the key at some later time.

### Zero-knowledge proofsEdit

One particular motivating example is the use of commitment schemes in zero-knowledge proofs.
Commitments are used in zero-knowledge proofs for two main purposes: first, to allow the prover to participate in "cut and choose" proofs where the verifier will be presented with a choice of what to learn, and the prover will reveal only what corresponds to the verifier's choice. Commitment schemes allow the prover to specify all the information in advance in a commitment, and only reveal what should be revealed later in the proof.^{[7]} Commitments are also used in zero-knowledge proofs by the verifier, who will often specify their choices ahead of time in a commitment. This allows zero-knowledge proofs to be composed in parallel without revealing additional information.^{[8]}

### Verifiable secret sharingEdit

Another important application of commitments is in verifiable secret sharing, a critical building block of secure multiparty computation. In a secret sharing scheme, each of several parties receive "shares" of a value that is meant to be hidden from everyone. If enough parties get together, their shares can be used to reconstruct the secret, but even a malicious cabal of insufficient size should learn nothing. Secret sharing is at the root of many protocols for secure computation: in order to securely compute a function of some shared input, the secret shares are manipulated instead. However, if shares are to be generated by malicious parties, it may be important that those shares can be checked for correctness. In a verifiable secret sharing scheme, the distribution of a secret is accompanied by commitments to the individual shares. The commitments reveal nothing that can help a dishonest cabal, but the shares allow each individual party to check to see if their shares are correct.

## Defining the security of commitment schemesEdit

Formal definitions of commitment schemes vary strongly in notation and in flavour. The first such flavour is whether the commitment scheme provides perfect or computational security with respect to the hiding or binding properties. Another such flavour is whether the commitment is interactive, i.e. whether both the commit phase and the reveal phase can be seen as being executed by a Cryptographic protocol or whether they are non-interactive, consisting of two algorithms *Commit* and *CheckReveal*. In the latter case *CheckReveal* can often be seen as a derandomised version of *Commit*, with the randomness used by *Commit* constituting the opening information.

If the commitment *C* to a value *x* is computed as *C:=Commit(x,open)* with *open* the randomness used for computing the commitment, then *CheckReveal(C,x,open)* simply consists in verifying the equation *C=Commit(x,open)*.

Using this notation and some knowledge about mathematical functions and probability theory we formalise different versions of the binding and hiding properties of commitments. The two most important combinations of these properties are perfectly binding and computationally hiding commitment schemes and computationally binding and perfectly hiding commitment schemes. Note that no commitment scheme can be at the same time perfectly binding and perfectly hiding.

### Computational bindingEdit

Let *open* be chosen from a set of size

$ 2^k $
, i.e., it can represented as a *k* bit string, and let

$ Commit_k $
be the corresponding commitment scheme. As the size of *k* determines the security of the commitment scheme it is called the security parameter. Then for all non-uniform probabilistic polynomial time algorithms that output

$ x,x' $ and

$ open,open' $
of increasing length *k*, the probability that

$ x \neq x' $ and

$ Commit_k(x,open)=Commit_k(x',open') $
is a negligible function in *k*. This is a form of Asymptotic analysis. It is also possible to state the same requirement using Concrete security: A commitment scheme *Commit* is

$ (t,\epsilon) $
secure, if for all algorithms that run in time *t* and output

$ x,x',open,open' $ the probability that

$ x \neq x' $ and

$ Commit(x,open)=Commit(x',open') $ is at most

$ \epsilon $ .

### Perfect, statistical and computational hidingEdit

Let

$ U_k $ be the uniform distribution over the

$ 2^k $
opening values for security parameter *k*. A commitment scheme is perfect, statistical, computational hiding, if for all

$ x\neq x' $ the probability ensembles

$ \{Commit_k(x,U_k)\}_{k\in\N} $ and

$ \{Commit_k(x',U_k)\}_{k\in\N} $ are equal, statistically close, or computationally indistinguishable.

## Constructing commitment schemesEdit

A commitment scheme can either be perfectly binding (it is impossible for Alice to alter her commitment after she has made it, even if she has unbounded computational resources) or perfectly concealing (it is impossible for Bob to find out the commitment without Alice revealing it, even if he has unbounded computational resources) but not both.

### Bit-commitment from any one-way permutation (or injective one way function)Edit

One can create a bit-commitment scheme from any one-way function that is injective. The scheme relies on the fact that every one-way function can be modified (via the Goldreich-Levin theorem) to possess a computationally hard-core predicate (while retaining the injective property). Let *f* be an injective one-way function, with *h* a hard-core predicate. Then to commit to a bit *b* Alice picks a random input *x* and sends the triple

- $ (h,f(x),b \oplus h(x)) $

to Bob, where

$ \oplus $
denotes XOR, i.e. addition modulo 2. To decommit Alice simply sends *x* to Bob. Bob verifies by computing *f(x)* and comparing to the committed value. This scheme is concealing because for Bob to recover *b* he must recover *h(x)*. Since *h* is a computationally hard-core predicate, recovering *h(x)* from *f(x)* with probability greater than one-half is as hard as inverting *f*. Perfect binding follows from the fact that *f* is injective and thus *f(x)* has exactly one preimage.

### Bit-commitment from a pseudo-random generatorEdit

Note that since we do not know how to construct a one-way permutation from any one-way function, this section reduces the strength of the cryptographic assumption necessary to construct a bit-commitment protocol.

In 1991 Moni Naor^{[9]} showed how to create a bit-commitment scheme from a cryptographically secure pseudorandom number generator. The construction is as follows. If *G* is pseudo-random generator such that *G* takes *n* bits to *3n* bits, then if Alice wants to commit to a bit *b*

- Bob selects a random
*3n*-bit vector*R*and sends*R*to Alice. - Alice selects a random
*n*-bit vector*Y*and computes the*3n*-bit vector*G(Y)*. - If
*b*=1 Alice sends*G(Y)*to Bob, otherwise she sends the bitwise exclusive-or of*G(Y)*and*R*to Bob.

To decommit Alice sends *Y* to Bob, who can then check whether he initially received *G(Y)* or

$ G(Y) \oplus R $
. This scheme is statistically binding, meaning that even if Alice is computationally unbounded she cannot cheat with probability greater than 2^{-n}. For Alice to cheat, she would need to find a *Y'*, such that

$ G(Y') = G(Y) \oplus R $
. If she could find such a value, she could decommit by sending the truth and Y, or send the opposite answer and Y'. However, G(Y) and G(Y') are only able to produce 2^{n} possible values while R and the commitment are both picked out of 2^{3n} values in the set of possible *3n*-bit values. She does not pick R, so there is a strong probability that a Y' satisfying the equation required to cheat will not exist.

The concealing property follows from a standard reduction, if Bob can tell whether Alice committed to a zero or one, he can also distinguish the output of the pseudo-random generator *G* from true-random, which contradicts the cryptographic security of *G*.

### A perfectly binding scheme based on the discrete log problemEdit

Alice chooses a group of prime order *p*, with generator *g*.

Alice randomly picks a secret value *x* from *0* to *p* − 1 to commit to and calculates *c* = *g*^{x} and publishes *c*. The discrete logarithm problem dictates that from *c*, it is computationally infeasible to compute *x*, so under this assumption, Bob cannot compute *x*. On the other hand, Alice cannot compute a *x'* <> *x*, such that *g*^{x'} = *c*, so the scheme is binding.

This scheme isn't perfectly concealing as someone could find the commitment if he manages to solve the discrete logarithm problem. (In fact, this scheme isn't hiding at all with respect to the standard hiding game, where an adversary should be unable to guess which of two messages he chose were committed to - similar to the IND-CPA game. A better example of a perfectly binding commitment scheme is one where the commitment is the encryption of *x* under a semantically secure, public-key encryption scheme, and the decommitment is the string of random bits used to encrypt *x*.)

## Quantum bit commitmentEdit

It is an interesting question in quantum cryptography if there exist *unconditionally secure* bit commitment protocols on the quantum level, that is protocols which are (at least asymptotically) binding and concealing even if there are no restrictions on the computational resources. One could hope that there might be a way to exploit the intrinsic properties of quantum mechanics, as in the protocols for unconditionally secure key distribution.

However, Dominic Mayers (see ^{[10]} for the original proof) showed in 1996, that this is impossible. Any such protocol can be reduced to a protocol where the system is in one of two pure states after the commitment phase, depending on the bit Alice wants to commit. If the protocol is unconditionally concealing, then Alice can unitarily transform these states into each other using the properties of the Schmidt decomposition, effectively defeating the bindingness property.

One subtle assumption of the proof is that the commit phase must be finished at some point in time. This leaves room for protocols that require a continuing information flow until the bit is unveiled or the protocol is cancelled, in which case it is not binding anymore.^{[11]}

## See also Edit

## ReferencesEdit

- ↑ Gilles Brassard, David Chaum, and Claude Crepeau,
*Minimum Disclosure Proofs of Knowledge*, Journal of Computer and System Sciences, vol. 37, pp. 156–189, 1988. - ↑
^{2.0}^{2.1}Moni Naor,*Bit Commitment Using Pseudorandomness*, Journal of Cryptology 4: 2 pp. 151–158, 1991. - ↑
^{3.0}^{3.1}Claude Crépeau,*Commitment*, MCgill.ca, accessed April 11, 2008 - ↑
^{4.0}^{4.1}Manuel Blum,*Coin Flipping by Telephone*, Proceedings of CRYPTO 1981, pp. 11–15, 1981, reprinted in SIGACT News vol. 15, pp. 23–27, 1983. - ↑ Shimon Even.
*Protocol for signing contracts.*In Allen Gersho, ed.,*Advances in Cryptography*(proceedings of CRYPTO '82), pp. 148–153, Santa Barbara, CA, USA, 1982. - ↑ A. Shamir, R. L. Rivest, and L. Adleman,
*Mental Poker.*In D. Klarner, ed.,*The Mathematical Gardner*, pp. 37–43. Wadsworth, Belmont, California, 1981. - ↑ Oded Goldreich, Silvio Micali, and Avi Wigderson,
*Proofs that yield nothing but their validity, or all languages in NP have zero-knowledge proof systems,*Journal of the ACM, 38: 3, pp. 690–728, 1991 - ↑ Oded Goldreich and Hugo Krawczyk,
*On the Composition of Zero-Knowledge Proof Systems*, SIAM Journal on Computing, 25: 1, pp. 169–192, 1996 - ↑ Citations: Bit Commitment using Pseudorandom Generators - Naor (ResearchIndex)
- ↑ Brassard, Crépeau, Mayers, Salvail: A brief review on the impossibility of quantum bit commitment
- ↑ A. Kent: Secure classical Bit Commitment using Fixed Capacity Communication Channels