Finalize domain block only when the new finalized block is higher than last finalized #1540
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nazar-pc
approved these changes
Jun 13, 2023
liuchengxu
deleted the
finalize-domain-block-only-when-new-finalized-is-higher
branch
i1i1
added a commit
to autonomys/subspace-pulsar-sdk
that referenced
this pull request
Jun 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue about the domain block finalization, by only attempting to finalize the block when the new finalized block is newer than the last finalized one. Ref paritytech/substrate#14347
Unsure whether this patch should be backported to the gemini-3d branch and make a new release regarding the gemini-3e around the corner.
Code contributor checklist: