Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lelantus: Towards Confidentiality and Anonymity of Blockchain Transactions From Standard Assumptions #14

Closed
nopara73 opened this issue Apr 17, 2020 · 2 comments

Comments

@nopara73
Copy link
Contributor

Found another interesting paper: https://eprint.iacr.org/2019/373.pdf

We achieve transaction anonymity with a Zerocoin setup which is implemented through 1-out-of-many proofs over generalized Pedersen commitments as is discussed in [4]. Each coin is associated with a unique serial number and a monetary value. The serial number is explicitly revealed during the spend operation in order to prevent the double-spending of the coin. The users will be able to merge, split and redeem multiple
coins
while also providing a balance proof to ensure that the transaction’s input and output values add up and no value is generated out of thin air. This proof generation method leverages the unique design properties of 1-out-of-many protocol, which is used to prove the validness of spent coins without revealing their origins and also encode coin value information necessary for generating a zero-knowledge balance proof.

@nopara73 nopara73 changed the title Lelantus? : Towards Confidentiality and Anonymity of Blockchain Transactions From Standard Assumptions Lelantus: Towards Confidentiality and Anonymity of Blockchain Transactions From Standard Assumptions Apr 17, 2020
@nothingmuch
Copy link
Contributor

nothingmuch commented Apr 17, 2020

Since this scheme relies on decoy inputs, it would require the blindedcommitments to be published by the coordinator before output registration can proceed.

The coordinator may lie about the set of commitments, showing individual users disjoint sets. Mitigating this his requires an additional synchronous phase similar to the transaction signing phase, where all users sign the set of commitments, and only proceed to output registration if all other users have signed, otherwise their output registrations may be linked to their inputs.

@nopara73
Copy link
Contributor Author

#30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants