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

Poseidon version of SnapDeals #1547

Merged
merged 2 commits into from
Jan 28, 2022
Merged

Poseidon version of SnapDeals #1547

merged 2 commits into from
Jan 28, 2022

Conversation

Kubuxu
Copy link

@Kubuxu Kubuxu commented Dec 7, 2021

Signed-off-by: Jakub Sztandera kubuxu@protocol.ai

Copy link
Contributor

@DrPeterVanNostrand DrPeterVanNostrand left a comment

Choose a reason for hiding this comment

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

Thanks for writing this! Looks good to me.

A couple of comments/questions:

  • It looks like this is a single partition circuit, am I correct in thinking that?
  • I think that restructuring this module makes sense when the vanilla side is built (mostly Merkle tree/proof shape changes) after the trusted-setup is run, e.g. maybe splitting the empty_sector_update crate into two modules sha and poseidon (which signify TreeD's hasher and shape).

storage-proofs-update/src/challenges.rs Show resolved Hide resolved
storage-proofs-update/src/vanilla.rs Outdated Show resolved Hide resolved
storage-proofs-update/tests/circuit.rs Outdated Show resolved Hide resolved
storage-proofs-update/tests/common/mod.rs Show resolved Hide resolved
storage-proofs-update/tests/common/mod.rs Show resolved Hide resolved
storage-proofs-update/src/circuit_poseidon.rs Outdated Show resolved Hide resolved
storage-proofs-update/src/circuit_poseidon.rs Outdated Show resolved Hide resolved
storage-proofs-update/src/circuit_poseidon.rs Outdated Show resolved Hide resolved
storage-proofs-update/src/circuit_poseidon.rs Outdated Show resolved Hide resolved
storage-proofs-update/src/circuit_poseidon.rs Outdated Show resolved Hide resolved
@Kubuxu
Copy link
Author

Kubuxu commented Dec 15, 2021

t looks like this is a single partition circuit, am I correct in thinking that?

Yes, it is a single partition.

I think that restructuring this module makes sense when the vanilla side is built (mostly Merkle tree/proof shape changes) after the trusted-setup is run, e.g. maybe splitting the empty_sector_update crate into two modules sha and poseidon (which signify TreeD's hasher and shape).

Agreed, I wanted to limit changes to SHA version that is why I moved new vanilla definitions to the circuit module itself and avoided touching the SHA sides in general where possible.

@Kubuxu Kubuxu changed the base branch from empty-sector-update to master December 15, 2021 19:24
Copy link
Contributor

@DrPeterVanNostrand DrPeterVanNostrand left a comment

Choose a reason for hiding this comment

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

Looks good to me. Thanks!

@cryptonemo
Copy link
Collaborator

@Kubuxu Can we get this rebased against latest so that it can have final review before merge?

@DrPeterVanNostrand DrPeterVanNostrand merged commit b72bc95 into master Jan 28, 2022
@BlocksOnAChain
Copy link
Collaborator

@Kubuxu @DrPeterVanNostrand @cryptonemo - Just wanted to say I'm glad we got this one in the scope. Great idea and all the work behind it. 🎉 👍

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.

4 participants