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.

Sign up for GitHub

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

Jump to bottom

Allow weak finality for synced historical blocks #3514

Closed
piotr-dziubecki opened this issue Dec 20, 2022 · 1 comment
Closed

Allow weak finality for synced historical blocks #3514

piotr-dziubecki opened this issue Dec 20, 2022 · 1 comment
Assignees
@Fraser999 @EdHastingsCasperAssociation
Labels
release blocker PR to be merged before releasing

Comments

@piotr-dziubecki
Copy link

The block synchronizer should be updated to only require strict finality for blocks of the current protocol version. An attempt to acquire strict finality should still be made, but failure can be ignored for older blocks.
@piotr-dziubecki piotr-dziubecki added the release blocker PR to be merged before releasing label Dec 20, 2022
EdHastingsCasperAssociation added a commit to EdHastingsCasperAssociation/casper-node that referenced this issue Jan 10, 2023
@EdHastingsCasperAssociation
casper-network#3514 allow weak finality for synced historical blocks
ce8a063
Merged
@EdHastingsCasperAssociation
Copy link
Collaborator

first pass PR up, handing off to @Fraser999

casperlabs-bors-ng bot added a commit that referenced this issue Jan 10, 2023
@casperlabs-bors-ng @EdHastingsCasperAssociation
Merge #3555
6a773ee 
3555: Allow weak finality for synced historical blocks r=EdHastingsCasperLabs a=EdHastingsCasperLabs

#3514 

Co-authored-by: Ed Hastings <ed@casperlabs.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Fraser999 Fraser999

@EdHastingsCasperAssociation EdHastingsCasperAssociation

Labels
release blocker PR to be merged before releasing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Fraser999 @EdHastingsCasperAssociation @piotr-dziubecki