Skip to content
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

When to pull certificates #176

Open
ranchalp opened this issue Apr 24, 2024 · 3 comments
Open

When to pull certificates #176

ranchalp opened this issue Apr 24, 2024 · 3 comments

Comments

@ranchalp
Copy link
Collaborator

A participant may be stuck trying to decide on an f3 instance. While the message rebroadcast mechanism #169 resolves this when no correct participant has terminated yet the instance (push of messages in current instance), if other correct participants have already terminated the instance, the stragglers need to ask for the finality certificate (pull).

A decision needs to be made on when a stuck participant decides to ask around for certificates.

@ranchalp
Copy link
Collaborator Author

A suggestion is to set a periodic timeout to ask for certificates for the current instance.

Perhaps once per 30 seconds (once per epoch), if the participant has not terminated the current instance. This gives time to at least 2-3 rounds of the current instance before even asking (a request for a certificate is not a heavy message to send anyways).

To be discussed though.

@Stebalien
Copy link
Member

Given #151, we can probably be even looser with the timeout as we can validate up to N instances ahead.

@Stebalien
Copy link
Member

If we haven't seen/agreed on an instance within some period of time, pull finality certificates with some exponential backoff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants