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

Research zkSNARK Semaphore RLN blocker: Shamir in SNARK #10

Closed
oskarth opened this issue Nov 8, 2019 · 2 comments
Closed

Research zkSNARK Semaphore RLN blocker: Shamir in SNARK #10

oskarth opened this issue Nov 8, 2019 · 2 comments

Comments

@oskarth
Copy link
Member

@oskarth oskarth commented Nov 8, 2019

Problem

For Semaphore RLN https://ethresear.ch/t/semaphore-rln-rate-limiting-nullifier-for-spam-prevention-in-anonymous-p2p-setting/5009 we need to embed the Shamir logic inside the SNARK in order to do slashing for spam. Currently the implementation is trusted and very hacky https://github.com/vacp2p/research/blob/master/zksnarks/semaphore/src/hello.js#L450

Acceptance criteria

  1. Shamir logic is integrated into the SNARK, and glue code around uses this

  2. (Optional?) Ideally it works for precomputed proofs too, requires some more thinking here

  3. Number of constraints don't explode too much, or at least understanding of overhead this would bring

Notes

Requires hacking actual SNARKs, and then some more thought around precomputes (no signal?) / complexity / etc.

Note that this doesn't apply to the Semaphore voting etc use case.

@decanus decanus added this to the zkSNARKS Feasibility milestone Apr 16, 2020
@oskarth
Copy link
Member Author

@oskarth oskarth commented Sep 15, 2020

@barryWhiteHat is Shamir logic part of the SNARK for rlnapp?

@barryWhiteHat
Copy link

@barryWhiteHat barryWhiteHat commented Sep 15, 2020

Yes its ready to go. Just needs UI :)

@oskarth oskarth closed this Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants