Commitment Schemas

学习笔记

Two-pharse commitment

• Pros
  • The existance of commitment is public, the sender must reveal it, or will be punished.
  • Can hide the value.
• Cons:
  • Can not hide ether sending.
  • Can not hide the existence of this commitment
  • It may be vulnerable to front-runnig attack, if no nonce in the commitment.

Multi-pharse commitment

A extension of two-pharse commitment. The key idea is to add a index in the commitment

• Pros
  • It provides a solution for a long-time-running commit-reveal activity.
• Cons
  • Can not hide the existence of this commitment
  • Can not hide ether sending.
  • It may be vulnerable to front-runnig attack if no nonce in the commitment.
  • Compute the commitment with index and preimage, and then compared the result with the commitment to guess the preimage of the commitment.

Submarine commitment

https://hackingdistributed.com/2017/08/28/submarine-sends/
https://libsubmarine.org/
https://github.com/lorenzb/libsubmarine

Key idea: Send ether to a fresh address, such as X=Hash(senderAddress, data, initial(Code))

Example code:

contract Forwarder {
    address constant addrContract = 0x123;
    function () {
        if (msg.sender == addrContract)
            addrContract.send(this.balance);
    }
}
// 依赖Create2 op code. contractAddress = Hash(callerAddress, nonce, initial(Code))
// Send ether to a fresh address which is a contract, so we can retrieve the money in the address.

• Pros:
  • Can hide the commitment (even the ether) by hide the tx in all of the similar tx in the commit pharse, this is a k-anoymity privacy.
• Cons:
  • The existance of commitment is not public, the sender can choose to not reveal it and will not be punished.