Solving the Chicken & Hen Problem of MProve
MProve is the first proof of reserves for Monero. Monero 1 is a decentralized cryptocurrency, meaning it is secure digital cash operated by a network of users. It uses ring signatures, ring confidential transactions, and stealth addresses to hide the origins, amounts, and destinations of all transactions. Transactions on the Monero blockchain are untraceable. Read more about Monero here.
MProve leverages the ring signatures to generate a proof of reserves. In simple words, it considers an anonymity set which includes the set of exchange-owned addresses. To generate MProve, an exchange selects from Monero blockchain. The commitment for each . The exchange defines the quantity as follows where is randomly chosen from . Further, the exchange publishes ring signatures verifiable by the pair of public keys and linkable ring signatures verifiable by the pair of public keys . Each contains key-images . These key-images help detect collusion and double spending. Checking if the published key-image doesn’t match existing key-images on the blockchain ensures that the exchange is not using an already-spent address in its proof. Thus, a typical MProve is of the form
The problem is with the key-images for s.t which are a part of . Let’s say an exchange publishes a MProve proof at time . Now if that exchange tries to spend from address at some time , the transaction also includes the same key-image as the one present in the MProve proof. So, any observer will know that address was owned by that exchange from the proof given at . An obvious way out of this seems to change the way we define key-images in MProve. But then we won’t be able to detect double spending in that case. Revealing key-images seem to be unavoidable.
The way I thought I would solve this paradoxical situtation was to somehow prove that the key-images we generate do not use any of the private information of the existing spent addresses on the blockchain. Solving MProve drawback essentially means that we come up with an efficient proof of reserves which does two things:
- Checks for double spending using the already existing key images
- Ensure non-collusion between exchanges
Specifically, let be a one-time address owned by the exchange with as the secret key, and let be a key-image from the blockchain, indicating that the funds from address have already been spent, we have
If we prove, for each , that the discrete-log of w.r.t is not equal to the discrete-log of w.r.t , for each spent address on the Monero blockchain, we are done. We can now have another definition of key-images in out proof of reserves. This fixes the paradoxical situation. Stay tuned to know how exactly we do it as we are in process of writing the manuscript of the protocol!