-
Notifications
You must be signed in to change notification settings - Fork 7
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 finality certificates #14
Closed
3 tasks done
Milestone
Comments
Initially, we can skip the deltas for MVP of this. So the minimal target becomes a format that allows for the validation of the aggregated decide message. Line 18 in 650d48b
It should expand to contain BLS signature, signers representation, and power table representation. |
4 tasks
Stebalien
added a commit
that referenced
this issue
May 29, 2024
This implements finality certificates and power table deltas. This adds: 1. Methods for applying/making power table deltas. 2. A method for validating a chain of finality certificates. Notes: - Finality certificates include the power-table delta between the power table used to validate the current certificate and the next certificate. They don't include the delta implied by the chain head. We'll have to address this when we implement the finality certificate exchange protocol, but I expect we'll communicate these power-deltas separate from the certificates. - I used `PowerEntries` instead of `PowerTable` objects because I doubt we'll need the performance. But I'm happy to change that. fixes #5 fixes #14
github-merge-queue bot
pushed a commit
that referenced
this issue
May 30, 2024
* Implement finality certificates This implements finality certificates and power table deltas. This adds: 1. Methods for applying/making power table deltas. 2. A method for validating a chain of finality certificates. Notes: - Finality certificates include the power-table delta between the power table used to validate the current certificate and the next certificate. They don't include the delta implied by the chain head. We'll have to address this when we implement the finality certificate exchange protocol, but I expect we'll communicate these power-deltas separate from the certificates. - I used `PowerEntries` instead of `PowerTable` objects because I doubt we'll need the performance. But I'm happy to change that. fixes #5 fixes #14 * Test some more invalid cases
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implement the creation of finality certificates from a strong quorum of signed DECIDE messages. See design doc.
Dependencies
The text was updated successfully, but these errors were encountered: