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

Definition & Security Proofs for Merkle Trees #4

Open
4 tasks
quangvdao opened this issue Dec 18, 2024 · 0 comments
Open
4 tasks

Definition & Security Proofs for Merkle Trees #4

quangvdao opened this issue Dec 18, 2024 · 0 comments
Assignees
Labels
core Important features to be worked on by the core team

Comments

@quangvdao
Copy link
Collaborator

quangvdao commented Dec 18, 2024

This issue tracks all development of Merkle trees. This is the basic vector commitment scheme that is required for all proof systems we care about (later development may bring in other schemes such as KZG, Bulletproofs, etc.)

We would like to prove completeness, extractability, and hiding for Merkle trees. These proofs (extractability and hiding) are non-trivial, and will require serious effort (from the core team or a serious outside contributor). The reference for this is in Chiesa & Yogev's recent zkSNARK textbook.

Relevant files in ZKLib:

Depends on progress in #2 to be able to state security properties for Merkle commitments.

Tasks:

  • Flesh out the definitions of Merkle trees, especially the opening phase.
  • Prove completeness of Merkle commitments.
  • Initial development of the extractability proof.
  • Initial development of the hiding proof.

References:

The textbook has more details but the paper might be an easier first read.

@quangvdao quangvdao self-assigned this Dec 18, 2024
@quangvdao quangvdao added the core Important features to be worked on by the core team label Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Important features to be worked on by the core team
Projects
None yet
Development

No branches or pull requests

1 participant