-
Notifications
You must be signed in to change notification settings - Fork 70
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
Compare Babe Spec and Babe Implementation with Babe paper #144
Comments
Currently the more important part is the relative time protocol part of it because the slot selection part is going to be replaced by the SASS. Babe research write up can be found here: https://github.com/w3f/research/blob/master/docs/polkadot/BABE/Babe.md |
It is the latest writeup. If you have any questions, you can ask me. |
I am updating our spec to the latest write up right now. Current progress it tracked in w3f/research-internal#110 |
@FlorianFranzen is going to the current host spec according to the latest babe spec with recent constant hardcoded. |
The Babe spec is being followed up in issue #168 |
I found the randomness was not being recycled correctly, to which wei proposed a fix in paritytech/substrate#5788 although they'll compare with another fix approach. We should figure out if the randomness recycles from one epoch waits long enough before being used in another epoch. |
Fix merged paritytech/substrate#5876 I donno if they merged the whole migration machinery yet though. |
We need to compare babe implementation with babe spec and submit any discrepency to research-security-issues repo.
The text was updated successfully, but these errors were encountered: