-
Notifications
You must be signed in to change notification settings - Fork 168
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
VRF implementation #144
Comments
Have you seen our IETF Internet draft on VRFs? (The bug in CONIKS and KT you mention above was reported by us...) |
Thank you for pointing it out to us, we'll definitely have a look when we'll tackle this issue then. It's definitely better if we can try to stick to the (future) standards ;) |
Hi Sharon, yes I've definitely seen your I-D on VRFs! Nice work, and I've been hoping to find time to do a more detailed read and comment pass; will try to before (or worst-case during) the Prague IETF. Looking forward to meeting and catching up there hopefully! |
Yes, see you in Prague! Would love to work with you guys, |
Now that we have DLEQ merged upstream, we can implement in a more or less straightforward way a VRF. The groundwork is already done in https://github.com/dedis/paper_17_sosp_omniledger/blob/master/gossip/vrf.go
It is mostly a question of API and arranging stuff around...
Also we must verify that this implementation is correct regarding the bug raised in the CONIKS repo and KT repo.
The text was updated successfully, but these errors were encountered: