fast leader handover: populate ParentMeta children
#606
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.
Problem and Summary of Changes
During Alpenglow, validators will receive
BlockComponents which will result in a changing parent:BlockHeader: sets the initial block parentUpdateParent: switches the parent according to Alpenglow fast leader handover protocolThese components currently fit within one shred each. On each shred's arrival, we need to maintain the full tree of parent and children relationships. While
ParentMetamaintains parent relationships, this PR introduces children relationships, essential forgenerate_new_bank_forks.In addition to extending
ParentMetawith achildrenfield, we introduce aPendingNextSlotsMetacolumn to track children for blocks awaiting parent metadata, i.e., blocks that aren't yet in theParentMetacolumn.