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
We need to store certificates boosting immutable blocks indefinitely in order to serve them to syncing peers.
The goal of this ticket is to design the corresponding storage component. This component must efficiently support the operations required by the mechanism we use to diffuse certificates to syncing peers (see #3).
Important to keep in mind: It can be the case that a block is boosted by multiple certificates.
Two ideas:
A new, independent component of the ChainDB. Implementation could be backed by something similar to the existing ImmutableDB, or potentially by the lsm-tree lbrary.
We could enrich the ImmutableDB to store certificates next to their corresponding blocks. One neat thing about this approach is that certain certificates (before cooldown periods) will be stored in block bodies either way.
The text was updated successfully, but these errors were encountered:
We need to store certificates boosting immutable blocks indefinitely in order to serve them to syncing peers.
The goal of this ticket is to design the corresponding storage component. This component must efficiently support the operations required by the mechanism we use to diffuse certificates to syncing peers (see #3).
Important to keep in mind: It can be the case that a block is boosted by multiple certificates.
Two ideas:
The text was updated successfully, but these errors were encountered: