fix: hyperchain sync #2035
Open
fix: hyperchain sync #2035
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
yaboiishere
force-pushed
the
fix-hyperchain-sync
branch
from
1951016 to
15807cd
Compare
microblocks keyblock
vatanasov
force-pushed
the
fix-hyperchain-sync
branch
from
412f376 to
aad3a62
Compare
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.
The hyperchains implementation in the node reverses the way key and microblocks are ordered. This is only done for hyperchains.
The current way is that there is a keyblock followed by all of it's microblocks until a new keyblock is produced, where after it are it's microblocks. The breaking change here is that in hc the microblocks come first followed by the keyblock they belong to. This resulted in the mdw creating sync mutations for key blocks at height N with the microblocks inside them for the next keyblock N+1.