-
Notifications
You must be signed in to change notification settings - Fork 106
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
rfc: Parallel Verification #763
Conversation
This comment has been minimized.
This comment has been minimized.
60841b0
to
26e9d89
Compare
An initial draft RFC for parallel verification.
26e9d89
to
b657cf5
Compare
Describe how the CheckpointVerifier interacts with chain state updates.
b657cf5
to
a237763
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
LGTM, also I know we haven't discussed this but I think for RFC PRs we should require that everyone on the zebra team signs off on the PR (or abstains from voting if its not relevant to what they're working on) before merging.
Can we automate this check? |
It doesn't look like it:
|
@teor2345 we could setup rfcbot like this rust-lang/rfcs#2965 (comment) |
I'd be OK with maintaining a social convention for this, given the small size of our team. |
In the absence of GitHub integration, I'm also happy with a social convention. |
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.
This looks good and is well-scoped! I would like to try to keep using the structural/semantic/contextual language we used before. Using "contextual verification" rather than "state update" means that we stay focused on the verification aspect rather than on all the other details of state updates.
And remove some duplicate references to BlockHeight checks.
And rewrite some stages for clarity.
An initial draft RFC for parallel verification.
Rendered
TODO: