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
This is needed for full nodes that don't keep block history to hold the very first non origin block slot number in a case where block #1 is pruned from disk.
What should be done here is:
When finalization happens you should check if one of the blocks being finalized is block #1 if so you should persist its slot number in the database, then everytime you want to get the chain first slot you should use that value
On the node initialization you should check if the entry is in the database, if so you should retrieve it and cache it, you can place the persistency under dot/state/slot.go as well as field to hold the persisted chain first slot.
EclesioMeloJunior
added
C-simple
Minor changes changes, no additional research needed. Good first issue/review.
S-babe
issues related to block production functionality.
labels
Apr 9, 2024
Description
This is needed for full nodes that don't keep block history to hold the
very first non origin block slot number
in a case where block#1
is pruned from disk.What should be done here is:
#1
if so you should persist its slot number in the database, then everytime you want to get the chain first slot you should use that valuedot/state/slot.go
as well as field to hold the persisted chain first slot.Depends on fix(lib/epoch): use correctly very first slot number #3795
More context about epoch changes: https://hackmd.io/@-8f0KkDaSXGl-AgsJkF8Jg/B1LIdTxAa
This task should be done on top of branch
eclesio/move-slot-to-header
or after the merge of PR feat(babe, epoch): retrieve first slot number correctly #3841Maybe check in the
retrieveFirstNonOriginBlockSlot
if the entry is in the databaseThe text was updated successfully, but these errors were encountered: