# Commitment scheme

This article needs additional citations for verification. (October 2014) (Learn how and when to remove this template message) |

A **commitment scheme** is a cryptographic primitive that allows one to commit to a chosen value (or chosen statement) while keeping it hidden to others, with the ability to reveal the committed value later.^{[1]} Commitment schemes are designed so that a party cannot change the value or statement after they have committed to it: that is, commitment schemes are *binding*. Commitment schemes have important applications in a number of cryptographic protocols including secure coin flipping, zero-knowledge proofs, and secure computation.

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

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 perhaps first formalized by Gilles Brassard, David Chaum, and Claude Crepeau in 1988,^{[2]} as part of various Zero-Knowledge protocols for *NP*, based on various types of commitment schemes (see also: ^{[3]}^{[4]}). But the concept was used without being treated formally prior to that.^{[5]}^{[6]} The notion of commitments appeared earliest in works by Manuel Blum,^{[7]} Shimon Even,^{[8]} and Shamir et al.^{[9]} The terminology seems to have been originated by Blum,^{[6]} although commitment schemes can be interchangeably called **bit commitment schemes**—sometimes reserved for the special case where the committed value is a bit. Earlier to that, commitment via one-way hash functions was considered, e.g., as part of, say, Lamport signature, the original one-time one-bit signature scheme.

## Contents

## Applications[edit]

### Coin flipping[edit]

Suppose Alice and Bob want to resolve some dispute 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 Alice and Bob are not in the same place a problem arises. Once Alice has "called" the coin flip, Bob can stipulate the flip "results" to be whatever is most desirable for him. Similarly, if Alice doesn't announce her "call" to Bob, after Bob flips the coin and announces the result, Alice can report that she called whatever result is most desirable for her. Alice and Bob can use commitments in a procedure that will allow both to trust the outcome:

- Alice "calls" the coin flip but only tells Bob a
*commitment*to her call, - Bob flips the coin and reports the result,
- Alice reveals what she committed to,
- Bob verifies that Alice's call matches her commitment,
- 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.^{[5]}^{[7]}

A real-life application of this problem exists, when people (often in media) commit to a decision or give an answer in a "sealed envelope", which is then opened later. "Let's find out if that's what the candidate answered", for example on a game show, can serve as a model of this system.

Keybase has implemented a HMAC based version of coin flipping. ^{[10]}

### Zero-knowledge proofs[edit]

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, and only reveal what should be revealed later in the proof.^{[11]} 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 to the prover.^{[12]}

### Signature schemes[edit]

The Lamport signature scheme is a digital signature system that relies on maintaining two sets of secret data packets, publishing verifiable hashes of the data packets, and then selectively revealing partial secret data packets in a manner that conforms specifically to the data to be signed. In this way, the prior public commitment to the secret values becomes a critical part of the functioning of the system.

Because the Lamport signature system cannot be used more than once (see the relevant article for details), a system to combine many Lamport Key-sets under a single public value that can be tied to a person and verified by others was developed. This system uses trees of hashes to compress many published lamport-key-commitments sets into a single hash value that can be associated with the prospective author of later verified data.

### Verifiable secret sharing[edit]

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.^{[13]}

## Defining the security[edit]

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 – a computationally unbounded adversary can simply generate *Commit(x,open)* for every value of *x* and *open* until finding a pair that outputs *C*, and in a perfectly binding scheme this uniquely identifies *x*.

### Computational binding[edit]

Let *open* be chosen from a set of size , i.e., it can be represented as a *k* bit string, and let 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 and of increasing length *k*, the probability that and 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 secure, if for all algorithms that run in time *t* and output the probability that and is at most .

### Perfect, statistical, and computational hiding[edit]

Let be the uniform distribution over the opening values for security parameter *k*.
A commitment scheme is respectively perfect, statistical, or computational hiding, if for all the probability ensembles and are equal, statistically close, or computationally indistinguishable.

### Impossibility of universally composable commitment schemes[edit]

It is impossible to realize commitment schemes in the universal composability
(UC) framework. The reason is that UC commitment has to be *extractable*, as shown by Canetti and Fischlin^{[14]} and
explained below.

The ideal commitment functionality, denoted here by *F*, works
roughly as follows. Committer *C* sends value *m* to *F*, which
stores it and sends "receipt" to receiver *R*. Later, *C* sends "open" to
*F*, which sends *m* to *R*.

Now, assume we have a protocol *π* that realizes this functionality. Suppose
that the committer *C* is corrupted. In the UC framework, that essentially means
that *C* is now controlled by the environment, which attempts to distinguish
protocol execution from the ideal process. Consider an
environment that chooses a message *m* and then tells *C* to act as prescribed
by *π*, as if it has committed to *m*. Note here that in order to realize
*F*, the receiver must, after receiving a commitment, output a
message "receipt". After the environment sees this message, it tells *C* to open
the commitment.

The protocol is only secure if this scenario is indistinguishable from the ideal
case, where the functionality interacts with a simulator *S*. Here,
*S* has control of *C*. In particular, whenever *R* outputs "receipt",
*F* has to do likewise. The only way to do that is for
*S* to tell *C* to send a value to *F*. However, note
that by this point, *m* is not known to *S*. Hence, when the
commitment is opened during protocol execution, it is unlikely that
*F* will open to *m*, unless *S* can extract *m* from
the messages it received from the environment before *R* outputs the receipt.

However a protocol that is extractable in this sense cannot be statistically
hiding. Suppose such a simulator *S* exists. Now consider an
environment that, instead of corrupting *C*, corrupts *R* instead. Additionally
it runs a copy of *S*. Messages received from *C* are fed into
*S*, and replies from *S* are forwarded to *C*.

The environment initially tells *C* to commit to a message *m*. At some point in
the interaction, *S* will commit to a value *m'*; this message is
handed to *R*, who outputs *m'*. Note that by assumption we have *m' = m* with
high probability. Now in the ideal process the simulator has to come up with
*m*. But this is impossible, because at this point the commitment has not been
opened yet, so the only message *R* can have received in the ideal process is a
"receipt" message. We thus have a contradiction.

## Construction[edit]

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 in the random oracle model[edit]

Bit-commitment schemes are trivial to construct in the random oracle model. Given a hash function H with a 3*k* bit output, to commit the *k*-bit message *m*, Alice generates a random *k* bit string *R* and sends Bob H(*R*||*m*). The probability that any *R*', *m*' exist where *m*' ≠ *m* such that H(*R*'||*m*') = H(*R*||*m*) is ≈ 2^{−k}, but to test any guess at the message *m* Bob will need to make 2^{k} (for an incorrect guess) or 2^{k-1} (on average, for a correct guess) queries to the random oracle.^{[15]}. We note that earlier schemes based on hash functions, essentially can be thought of schemes based on idealization of these hash functions as random oracle.

### Bit-commitment from any one-way permutation[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

to Bob, where 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 generator[edit]

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^{[16]} 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 3*n* bits, then if Alice wants to commit to a bit *b*:

- Bob selects a random 3
*n*-bit vector*R*and sends*R*to Alice. - Alice selects a random
*n*-bit vector*Y*and computes the 3*n*-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*) *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*) *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 each (that's 2^{2n}) while *R* is picked out of 2^{3n} values. She does not pick *R*, so there is a 2^{2n}/2^{3n} = 2^{−n} probability that a *Y'* satisfying the equation required to cheat will 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 problem and beyond[edit]

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. One consequence of this is that if the space of possible values of *x* is small, then an attacker could simply try them all and the commitment would not be hiding.

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 with perfect completeness, and the decommitment is the string of random bits used to encrypt *x*. An example of an information-theoretically hiding commitment scheme is the Pedersen commitment scheme, which is binding under the discrete logarithm assumption. Additionally to the scheme above, it uses another generator *h* of the prime group and a random number *r*. The commitment is set .^{[17]}

These constructions are tightly related to and based on the algebraic properties of the underlying groups, and the notion originally seemed to be very much related to the algebra. However, it was shown that basing statistically binding commitment schemes on general unstructured assumption is possible, via the notion of interactive hashing
for commitments from general complexity assumptions (specifically and originally, based on any one way permutation) as in ^{[18]}.

## Quantum bit commitment[edit]

It is an interesting question in quantum cryptography if *unconditionally secure* bit commitment protocols exist 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, this is impossible, as Dominic Mayers showed in 1996 (see ^{[19]} for the original proof). 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 binding 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.^{[20]}

## See also[edit]

## References[edit]

**^**Oded Goldreich (2001). Foundations of Cryptography: Volume 1, Basic Tools, (draft available from author's site). Cambridge University Press. ISBN 0-521-79172-3. (see also http://www.wisdom.weizmann.ac.il/~oded/foc-book.html)^{:224}**^**Gilles Brassard, David Chaum, and Claude Crepeau,*Minimum Disclosure Proofs of Knowledge*, Journal of Computer and System Sciences, vol. 37, pp. 156–189, 1988.**^**Goldreich, Oded; Micali, Silvio; Wigderson, Avi (1991). "Proofs that yield nothing but their validity".*Journal of the ACM*.**38**(3): 690–728. CiteSeerX 10.1.1.420.1478. doi:10.1145/116825.116852.**^**Russell Impagliazzo, Moti Yung: Direct Minimum-Knowledge Computations. CRYPTO 1987: 40-51- ^
^{a}^{b}Moni Naor,*Bit Commitment Using Pseudorandomness*, Journal of Cryptology 4: 2 pp. 151–158, 1991. - ^
^{a}^{b}Claude Crépeau,*Commitment*, MCgill.ca, accessed April 11, 2008 - ^
^{a}^{b}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 David A. Klarner, ed.,*The Mathematical Gardner*, pp. 37–43. Wadsworth, Belmont, California, 1981.**^**Cryptographic coin flipping, now in Keybase**^**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**^**Gennaro; Rosario; Rabin, Michael O.; Rabin, Tal. "Simplified VSS and fast-track multiparty computations with applications to threshold cryptography".*Proceedings of the Seventeenth Annual ACM Symposium on Principles of Distributed Computing*. 1998, June.**^**R. Canetti and M. Fischlin. Universally Composable Commitments.**^**Wagner, David (2006),*Midterm Solution*, p. 2, retrieved 26 October 2015**^**"Citations: Bit Commitment using Pseudorandom Generators - Naor (ResearchIndex)". Citeseer.ist.psu.edu. Retrieved 2014-06-07.**^**Tang, Chunming; Pei, Dingyi; Liu, Zhuojun; He, Yong (16 August 2004). "Pedersen: Non-interactive and information-theoretic secure verifiable secret sharing" (PDF).*Cryptology ePrint Archive*. Advances in Cryptology CRYPTO 1991 Springer. Archived (PDF) from the original on 2007-04-17.**^**Moni Naor, Rafail Ostrovsky, Ramarathnam Venkatesan, Moti Yung: Perfect Zero-Knowledge Arguments for NP Using Any One-Way Permutation. J. Cryptology 11(2): 87-108 (1998)[1]**^**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