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

Refactored backend for updated v2 contracts #270

Merged
merged 5 commits into from
Mar 4, 2024
Merged

Conversation

sifnoc
Copy link
Member

@sifnoc sifnoc commented Feb 27, 2024

  • Added a zk_snark_proof field to the Snapshot struct.
  • Named the structure KZGProof to represent both the grand sum proof and the inclusion proof.

@sifnoc sifnoc changed the title fix: backend for updated v2 contract Refactor backend for updated v2 contracts Feb 27, 2024
@sifnoc sifnoc changed the title Refactor backend for updated v2 contracts Refactored backend for updated v2 contracts Feb 27, 2024
@sifnoc sifnoc marked this pull request as ready for review February 28, 2024 07:02
@sifnoc sifnoc requested a review from alxkzmn February 28, 2024 07:02

Without publishing the commitment, users cannot verify their inclusion proof on the Summa contract. This is because the inclusion verifier function internally requires the `mst_root`, but users only know the `timestamp` associated with the round and the verifier functions does not requre `mst_root` directly.
Without publishing the commitment, users cannot verify their inclusion proof on the Summa contract. This is because the inclusion verifier function internally requires the snark proof, but users only know the timestamp associated with the round and the verifier functions does not requre the snark proof directly.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

*without CEX publishing the commitment


Without publishing the commitment, users cannot verify their inclusion proof on the Summa contract. This is because the inclusion verifier function internally requires the `mst_root`, but users only know the `timestamp` associated with the round and the verifier functions does not requre `mst_root` directly.
Without publishing the commitment, users cannot verify their inclusion proof on the Summa contract. This is because the inclusion verifier function internally requires the snark proof, but users only know the timestamp associated with the round and the verifier functions does not requre the snark proof directly.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest to capitalize the SNARK everywhere not to confuse with the imaginary animal 😃

@sifnoc sifnoc merged commit 66ebc91 into v2 Mar 4, 2024
6 checks passed
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

Successfully merging this pull request may close these issues.

2 participants