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.

Sign up for GitHub

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

Jump to bottom

beacon: Misc. future improvements #3668

Closed

3 tasks

Yawning opened this issue Feb 1, 2021 · 1 comment

Labels

c:beacon

Contributor

Yawning commented Feb 1, 2021

Here are a number of open-ended future improvements that could be made to the beacon code:

Consider using pairing based cryptography for faster PVSS performance.
Consider incorporating some of the optimizations from the SCRAPE paper.
Figure out a good way to do accounting of block proposers, and if such a metric is sufficient, slash for non-participation.

Yawning added the golang label

Yawning mentioned this issue

Make the random beacon suck less #3180

Merged

21 tasks

kostko added c:beacon and removed golang labels

Contributor Author

Yawning commented Dec 16, 2021

All of these are only relevant for the beacon that will be replaced (Code already merged) in the next major upgrade.

Yawning closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment