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

Implement Wesolowski VDF #343

Closed
kchalkias opened this issue Jan 7, 2023 · 3 comments · Fixed by #647
Closed

Implement Wesolowski VDF #343

kchalkias opened this issue Jan 7, 2023 · 3 comments · Fixed by #647
Assignees
Labels
enhancement New feature or request

Comments

@kchalkias
Copy link
Collaborator

Note that we don't need to handle the trusted setup part at this stage.
Paper: https://eprint.iacr.org/2018/623
Analysis and comparison with Pietrzak scheme: https://crypto.stanford.edu/~dabo/pubs/papers/VDFsurvey.pdf

@jonas-lj
Copy link
Contributor

jonas-lj commented Jan 17, 2023

Just to clarify: We do as Ethereum 2.0 and use Wesolowski + RSA groups, and we can assume that an RSA modulus with unknown factorization is given?

I'll start by adding RSA groups to fastcrypto and then build the VDF afterwards.

@kchalkias
Copy link
Collaborator Author

@jonas-lj exactly, we assume that each application can pick their own group (Sui doesn't need to know how this was computed, ie different smart contracts might pin different n)

@jonas-lj
Copy link
Contributor

@jonas-lj exactly, we assume that each application can pick their own group (Sui doesn't need to know how this was computed, ie different smart contracts might pin different n)

That makes sense. I think we could make the construction for generic hidden order groups, allowing eg. ideal class groups in the future such that no trusted setup is needed at all.

@jonas-lj jonas-lj linked a pull request Sep 12, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
@jonas-lj @kchalkias and others