-
Notifications
You must be signed in to change notification settings - Fork 3
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
Replace queue of future messages with some other catch-up mechanism #130
Comments
An alternative to the in-instance catchup mechanism could be speculatively starting a new instance. |
@Kubuxu and I discussed, and concluded that with a power table delay we don't need speculative execution. We can just check signatures and queue messages. I think it will be safe to drop equivocations at QUALITY too, or in any phase that proceeds from a timeout regardless of messages received. |
See #151. These probably need to be done together:
The host should fetch finality certificates to skip over instances to get within 10 of the currently executing one. |
This issue is about messages for future instances, not future rounds in this instance. But it's tightly coupled to #151 so I'll expect scope there and close this one. |
#124 (for #122) added a queue of messages for future instance, but opens up lots of DOS risk (#12) because they can't be validated. This should be removed before production use.
Brief thoughts about what to do instead:
The text was updated successfully, but these errors were encountered: