You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cancelable consensus thread, meaning if working on term and suddenly we know this term is invalid (eg. node sync brings a new block), we should be able to cancel the current term immediately and move forward to the new one (even if stuck doing a blocking operation).
Future cache should be limited so we don't exhaust memory
When reliving history (for example when going through node sync and seeing old blocks, or when playing through the future cache when we arrive to an already active term) - we should not try to participate in this history (even when we're leader)
Handle failures in external API calls gracefully. For example, if trying to get a committee and the API fails, we should handle this gracefully and retry after some time so consensus doesn't get stuck.
The text was updated successfully, but these errors were encountered:
Improve robustness of node downtime and restarts - PBFT-like algorithms resync eventually when the views align, so if the time between first node start and last required start is 3 days, it will take 6 days to sync to the same view
Cancelable consensus thread, meaning if working on term and suddenly we know this term is invalid (eg. node sync brings a new block), we should be able to cancel the current term immediately and move forward to the new one (even if stuck doing a blocking operation).
Future cache should be limited so we don't exhaust memory
When reliving history (for example when going through node sync and seeing old blocks, or when playing through the future cache when we arrive to an already active term) - we should not try to participate in this history (even when we're leader)
Handle failures in external API calls gracefully. For example, if trying to get a committee and the API fails, we should handle this gracefully and retry after some time so consensus doesn't get stuck.
The text was updated successfully, but these errors were encountered: