-
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
BEEFY spec #682
BEEFY spec #682
Conversation
Initial spelling fixes
Fix speling
fix some spelling issues
small fixes
Spelling fixes
Quick spelling fixes
fix spelling errors
fix spelling errors
fix spelling errors
Some quick spelling fixes
Quick spelling fixes
Quick spelling fixes
Quick spelling fixes
Quick spelling fixes
Quick spelling fixes
Quick spelling fixes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review of "Bridge design (BEEFY)" section.
… Implementer's Guide
removed BEEFY analysis file
@Noc2 Can you please take a look. After your review, can merge this for now. Potentially, the random Subsampling protocol can be added to the implementer's guide in a different PR. |
small fixes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we keep the Motivation section, or should this be part of the implementer guide?
small fixes
Change it back to Motivation
I suggest merging this PR for now. How the light client verifies (via interactive Random Subsampling of signatures) BEEFY payload can be part of the implementers guide in a separate PR. |
First draft of the BEEFY spec.
TODOs: