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
C-complexComplex changes across multiple modules. Possibly will require additional research.EpicIssue used to track development status of a complex feature, aggregates several issuesS-babeissues related to block production functionality.
Currently Gossamer has 2 main points where a block is imported, if the block is acquired through the network then we start the importing in the sync package, do the validations, execution and then pass it to core.HandleBlockImport to finish the block import handling block consensus messages and applying forced changes if needed. However, if the block was produced by the node the import is partially done in the babe package and then passed to core.HandleProducedBlock
What I'm proposing here is to have a single point to handle/import blocks no matter how we acquire them, that way we can add a pipeline of checks and modifications (for example check if epochs were skipped) without repeating the logic in different places.
In Substrate, this approach is used, also while importing the block is passed a set of parameters that help the import function to configure the import pipeline properly to a given block.
P1sar
added
S-babe
issues related to block production functionality.
C-complex
Complex changes across multiple modules. Possibly will require additional research.
labels
Mar 14, 2024
C-complexComplex changes across multiple modules. Possibly will require additional research.EpicIssue used to track development status of a complex feature, aggregates several issuesS-babeissues related to block production functionality.
Issue summary
core.HandleBlockImport
to finish the block import handling block consensus messages and applying forced changes if needed. However, if the block was produced by the node the import is partially done in thebabe
package and then passed tocore.HandleProducedBlock
The text was updated successfully, but these errors were encountered: